Replies: 1 comment 2 replies
-
|
Hi, Sorry, the above description is a bit confusing.
BTW it shoudl be working as only 2 days ago this user confirmed it: #1523 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment



Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I installed 2 instances of NetAlertX containers (v26.2.6), hosts are in different VLANs and different subnets. Taken separately, they both work. Seems very promising.
I would like to synchronise the device's data from #2 (192.168.c.d) to #1 (192.168.a.b)
In #2 I configured the API_TOKEN (from #1), SYNC_node_name (NAX-mgmnt), SYNC_encryption_key (from #1) , SYNC_hub_url (http://192.168.a.b:20212), SYNC_devices (checked). Result: the HUB (#1) gets nothing, node (#2) does not even try to send something (router-firewall detects no traffic).
Tried different SYNC_RUN+SYNC_RUN_SCHD values, tried SYNC_plugins (ARPSCAN), restarted container several times - still nothing.
I can get the answer from docker shell (curl -v http://192.168.a.b:20212) and this traffic is detected in router.
I changed LOG_LEVEL to 'trace'. Didn't discover anything special.
Any ideas? I just don't understand what I don't understand.
Beta Was this translation helpful? Give feedback.
All reactions