You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, I saw this error when running zeekctl ( and zeekctl cron):
Error: must run zeekctl on same machine as the manager node. The manager node has IP address
127.0.1.1 and this machine has IP addresses: 128.3.x.y, fe80::3eec:efff:fe28:8c5a,
fe80::3eec:efff:fe28:8c5b, 127.0.0.1, ::1
Turns out this is some soft Linuxism where linux's netcfg creates this entry in /etc/hosts where
127.0.0.1 localhost
127.0.1.1 fqdn
This seems to have surfaced quite suddently and automatically on me.
While I changed the node.cfg to explicity use IP address instead of hostname as a workaround, I do see that /usr/local/zeek/lib/broctl/ZeekControl/config.py has hardcoded 127.0.0.1, ::1
Would be useful if zeekctl (aka config.py) handles 127.0.0.0/8 instead
So, I saw this error when running zeekctl ( and zeekctl cron):
Turns out this is some soft Linuxism where linux's
netcfg
creates this entry in/etc/hosts
whereThis seems to have surfaced quite suddently and automatically on me.
While I changed the node.cfg to explicity use IP address instead of hostname as a workaround, I do see that
/usr/local/zeek/lib/broctl/ZeekControl/config.py
has hardcoded127.0.0.1, ::1
Would be useful if
zeekctl
(akaconfig.py
) handles 127.0.0.0/8 insteadPS: https://serverfault.com/questions/363095/why-does-my-hostname-appear-with-the-address-127-0-1-1-rather-than-127-0-0-1-in
The text was updated successfully, but these errors were encountered: