1
Zenarmor (Sensei) / Re: Error about misconfigured interfaces
« on: June 18, 2024, 12:49:53 am »
I am also seeing this error, as a banner on the dashboard:
> Possible deployment misconfiguration: devices with public IP addresses detected
> Zenarmor's health check system detected 7195 devices with public ip addresses associated with them.
Under “Live Sessions” I see connections with correct internal src and external dst addresses, but where the “Device” is listed as the IP of the destination address. For example, I see a connection from a local Macbook to iCloud on VLAN1, where the device shows up as a public iCloud IP “Device (ip4:#.#.#.#)” instead of the private Macbook IP.
This started in May, but I just upgraded to 1.17.4 and opnsense 24.1.8 with no change. After rebooting, I still see the warning and incorrect Device names for new connections.
I currently have Zenarmor running in passive mode, monitoring 7 VLANs on a LAGG. (Zenarmor is configured to monitor each VLAN individually, as having it monitor the underlying LAGG interfaces separately resulted in packet loss in the past, due to some connections using both interfaces.)
I have multi-wan setup, but only internal VLANs are configured.
> Possible deployment misconfiguration: devices with public IP addresses detected
> Zenarmor's health check system detected 7195 devices with public ip addresses associated with them.
Under “Live Sessions” I see connections with correct internal src and external dst addresses, but where the “Device” is listed as the IP of the destination address. For example, I see a connection from a local Macbook to iCloud on VLAN1, where the device shows up as a public iCloud IP “Device (ip4:#.#.#.#)” instead of the private Macbook IP.
This started in May, but I just upgraded to 1.17.4 and opnsense 24.1.8 with no change. After rebooting, I still see the warning and incorrect Device names for new connections.
I currently have Zenarmor running in passive mode, monitoring 7 VLANs on a LAGG. (Zenarmor is configured to monitor each VLAN individually, as having it monitor the underlying LAGG interfaces separately resulted in packet loss in the past, due to some connections using both interfaces.)
I have multi-wan setup, but only internal VLANs are configured.