ConfigServer Community Forum

Hi,

Seems like Bogon is active on eth1 even though I excluded it from firewall rules in:

ETH_DEVICE_SKIP = eth1

I run internal network using 192.168.0.x to connect to internal NAS server.

Looks like the newest csf update causes this to break. It was fine in earlier versions. I had the server set to autoupdate csf and found out this morning that it had issues connecting to NAS (it wouldn't ping to any internal network ip). Once I disabled Bogon, it was fine again.

Kevin

I confirmed this by logging into server running csf 3.43 and bogon enabled (LF_BOGON = 1) and eth1 excluded (ETH_DEVICE_SKIP = eth1).

It was pinging all internal ips.

Then I did a manual upgrade to 4.03 and restarted firewall.
I could not ping any internal ips.

I disabled bogon and restarted and I could ping all internal ips again.

This will be fixed in v4.04