OPNsense Forum

Archive => 18.1 Legacy Series => Topic started by: Taomyn on March 27, 2018, 08:49:28 am

Title: Suddenly lost web traffic and some inbound NATs stopped
Post by: Taomyn on March 27, 2018, 08:49:28 am

I woke up this morning to find I had no access to websites, and further investigation shows my inbound NATs are not working. I think it's related to this, but I can't work out where to look as the message is incomplete:

Code: [Select]

Mar 27 05:33:08 opnsense: /usr/local/etc/rc.newwanip: New alert found: There were error(s) loading the rules: no IP address found for <!DOCTYPE
Mar 27 05:33:07 opnsense: /usr/local/etc/rc.filter_configure: New alert found: There were error(s) loading the rules: no IP address found for <!DOCTYPE
Mar 27 05:33:04 opnsense: /usr/local/etc/rc.newwanip: ROUTING: no IPv6 default gateway set, trying wan on 'pppoe0' (fe80::eab7:48ff:fed9:a00)
Mar 27 05:32:56 opnsense: /usr/local/etc/rc.linkup: ROUTING: no IPv6 default gateway set, trying wan on 'pppoe0' ()
Mar 27 05:32:30 opnsense: /usr/local/etc/rc.linkup: ROUTING: no IPv6 default gateway set, trying wan on 'pppoe0' ()
Mar 27 05:32:15 opnsense: /usr/local/etc/rc.linkup: ROUTING: no IPv6 default gateway set, trying wan on 'pppoe0' ()
Mar 27 05:32:15 opnsense: /usr/local/etc/rc.filter_configure: New alert found: There were error(s) loading the rules: no IP address found for <!DOCTYPE
Mar 27 05:22:48 opnsense: /usr/local/etc/rc.newwanip: New alert found: There were error(s) loading the rules: no IP address found for <!DOCTYPE
Mar 27 05:22:46 opnsense: /usr/local/etc/rc.newwanip: ROUTING: no IPv6 default gateway set, trying wan on 'pppoe0' (fe80::8a43:e1ff:fe00:9400)
Mar 27 05:22:39 opnsense: /usr/local/etc/rc.bootup: New alert found: There were error(s) loading the rules: no IP address found for <!DOCTYPE
Mar 27 05:22:28 opnsense: /usr/local/etc/rc.bootup: ROUTING: no IPv6 default gateway set, trying wan on 'pppoe0' (fe80::8a43:e1ff:fe00:9400)
Mar 27 05:22:23 opnsense: /usr/local/etc/rc.bootup: New alert found: There were error(s) loading the rules: no IP address found for <!DOCTYPE

Any ideas how I can find what "<!DOCTYPE[/size][size=78%]" is referring to?[/size]

Title: Re: Suddenly lost web traffic and some inbound NATs stopped
Post by: Taomyn on March 27, 2018, 08:59:07 am

Update, I managed to fix it by disabling the option "Allow IPv6" on the Firewall, Settings, Advanced screen.


No idea why this would suddenly happen, I don't use IPv6 as it's mostly broken for me and so anywhere it can be enabled on the interfaces they remain disabled.


If I can provide logs for investigation let me know which ones.

Title: Re: Suddenly lost web traffic and some inbound NATs stopped
Post by: kug1977 on March 27, 2018, 10:01:42 am

Hi, are you on OPNsense 18.1.5 too?

Title: Re: Suddenly lost web traffic and some inbound NATs stopped
Post by: franco on March 27, 2018, 10:07:28 am

https://github.com/opnsense/core/issues/2298

Bad bogons for IPv6.

Run this:

# /usr/local/etc/rc.update_bogons


Cheers,
Franco

Title: Re: Suddenly lost web traffic and some inbound NATs stopped
Post by: Taomyn on March 27, 2018, 12:18:33 pm

Ok did that, and this is returned, hope it's ok:

Code: [Select]

root@bart:~ # /usr/local/etc/rc.update_bogons
No ALTQ support in kernel
ALTQ related functions disabled
No ALTQ support in kernel
ALTQ related functions disabled
No ALTQ support in kernel
ALTQ related functions disabled
No ALTQ support in kernel
ALTQ related functions disabled

Title: Re: Suddenly lost web traffic and some inbound NATs stopped
Post by: franco on March 27, 2018, 02:21:01 pm

Looks good, output is in system log:

# clog /var/log/system.log