Bug #4102
closedCould not find IPv4/IPv6 gateway for interface log spam
0%
Description
There is no IPv4 nor IPv6 assigned to the interface, there was a dynamic IPv6 GW created on 2.1.x, which was made default for the tunnel to work, exactly as suggested per docs: https://doc.pfsense.org/index.php/Using_IPv6_on_2.1_with_a_Tunnel_Broker#Set_Gateway
Now, with 2.2 RC, a bogus $IFACENAME_TUNNELV4 dynamic gateway gets created in addition to $IFACENAME_TUNNELV6, and keeps spamming the logs with incredible amount of useless stuff:
Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:45:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:30:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:15:10 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3). Dec 12 09:00:11 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (opt3).
Additionally, need to disable monitoring manually for that phantom GW manually.
Updated by Kill Bill almost 10 years ago
Guys, can you tell me how to stop logging this junk at least? This renders the system log absolutely useless with firewall schedules in place.
Updated by Kill Bill about 9 years ago
https://github.com/pfsense/pfsense/pull/1784
Dunno why this needs to be logged or what kind of debugging is this supposed to be conducive to.
Updated by Chris Buechler about 9 years ago
- Subject changed from IPv6 GIF tunnel - Could not find IPv4 gateway for interface to Could not find IPv4/IPv6 gateway for interface log spam
- Category set to Logging
- Status changed from New to Resolved
- Target version set to 2.2.5
- Affected Version changed from 2.2 to All
fixed, thanks