Could not find IPv6 gateway - but we're not using IPv6
-
version 2.2.3-RELEASE (i386), not running IPv6. Our logs are full of:
php: rc.filter_configure_sync: Could not find IPv6 gateway for interface (wan).
and
php: rc.filter_configure_sync: Could not find IPv6 gateway for interface (opt1).Both interfaces comprise a dual-wan with wan-to-opt1 failover set up.
I found some references to scheduling as the trigger for this, and we are using schedules, but again - not ipv6. BUT - I have also noticed that pfBlockerNG has created ipv6 rules. If I delete these pfb rules individually, will pfblockerNG re-create them? Is that even a possible cause of these log entries over and over?
-
Do you actually have IPv6 disabled in System - Advanced - Networking - IPv6 Options - Allow IPv6?
-
Yep.
-
Also, if I delete the v6 pfblockerNG rules in Firewall/Rules, they are, in fact, re-created. So that's not an option.
-
I went through the pfblockerNG tabs and cleared the ipv6 lists, and that removed all the v6 entries from the firewall rules. I'll let you know how that pans out.
-
It's early yet, but clearing the IPv6 lists from each pfblockerNG tab seems to have corrected it. As a note, clicking on an entry will unselect all but that one entry, and ctrl-click will unselect that entry.
-
Useless log noise. Ignore. Known bug.
P.S. The "disable" checkbox disables nothing. It blocks all IPv6 traffic. Even written there.
-
Useless log noise. Ignore. Known bug.
P.S. The "disable" checkbox disables nothing. It blocks all IPv6 traffic. Even written there.
The problem with noise is that it makes the signals harder to find - I had an entire screen of nothing but that message.
I know it's not some earth-shattering issue, but I had time today to look at it, and I wanted to see if I could alleviate it. I did. Also did the "save" thing on my interfaces to get rid of the "radvd: sendmsg" messages.
I like it when I can get to a "C" or a "D" item every now and again.
-
Yeah. There's some noise. There's a bug about it. What more you want here? You have the PHP code. Go fix it yourself if you cannot wait.
-
Yeah. There's some noise. There's a bug about it. What more you want here? You have the PHP code. Go fix it yourself if you cannot wait.
Dude - if I somehow lent the impression that I was jumping in your Wheaties because I was having some petty log noise, I apologize, but frankly, I don't think I did. I certainly WAS NOT intentionally attacking you.
I posted my issue, I posted that I cleared it up, and I posted what I did to clear it. I do not know why you're doling out this much attitude.
-
