ipv6 renew (?) takes the pppoe interface down

[MosheL]

Important notices

Before you add a new report, we ask you kindly to acknowledge the following:

• [x] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
• [X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Describe the bug

System 3 WANs installed. the WAN interface is disabled (old Cable ISP I was removed someday). OPT7 - PPPoE WAN (the WAN we work with) with only IPv4 from Fiber to LAN device. 1 WAN is Android USB. it is general disabled but sometimes I connect my Android device when the Fiber failed.

THE PROBLEM

PPPoE connection, static IP from DHCP, no IPv6 from ISP. The system is working correctly in general. after some days the connection is stopped. when I open the GUI I see the FiberWan (opt7) has no IP. I can open /status_interfaces.php, hit [reload] and then the Internet working again.

To Reproduce

I suspect create a PPPoE without IPv6 support from the ISP side as I see a IPV6 in the logs, but can't know really.

Expected behavior

Internet need to be working.

Describe alternatives you considered

I tried to change the IPv6 status from 6to4, none, and other options. both of them not work to solve thie problem.

**Relevant log files **

LOGS from the time of disconnect:

2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: Static Routes: Gateway IP could not be found for IP REMOVED
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: Static Routes: Gateway IP could not be found for 192.168.7.1/24
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: Static Routes: Gateway IP could not be found for 2001:470:6b12:b0::1/50
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: Static Routes: Gateway IP could not be found for 10.1.130.0/22
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: keeping current default gateway '2002:c058:6301::'
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: setting IPv6 default route to 2002:c058:6301::
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: IPv6 default gateway set to opt7
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: skipping IPv4 default route
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: IPv4 default gateway set to opt9
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: ROUTING: entering configure using 'opt7'
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: On (IP address: 2002:54e4:74d5::) (interface: FiberWan[opt7]) (real interface: pppoe0).
2022-08-22T08:52:39	Error	opnsense	/usr/local/etc/rc.newwanipv6: IPv6 renewal is starting on 'pppoe0'

// opt9 from the logs, is a OpenVPN connection, failed as the main connection failed down.

and after recoonect from [reload] button:

2022-08-22T08:53:45	Error	opnsense	/usr/local/etc/rc.newwanipv6: IPv6 renewal is starting on 'pppoe0'
2022-08-22T08:53:45	Error	opnsense	/usr/local/etc/rc.newwanip: On (IP address: 84.228.116.213) (interface: FiberWan[opt7]) (real interface: pppoe0).
2022-08-22T08:53:45	Error	opnsense	/usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'pppoe0'
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: Static Routes: Gateway IP could not be found for 2001:470:6b12:b9:223:242:ac11:3/49
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: Static Routes: Gateway IP could not be found for 192.168.7.1/24
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: Static Routes: Gateway IP could not be found for 2001:470:6b12:b0::1/50
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: Static Routes: Gateway IP could not be found for 10.1.130.0/22
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: keeping current default gateway '2002:c058:6301::'
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: setting IPv6 default route to 2002:c058:6301::
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: IPv6 default gateway set to opt7
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: skipping IPv4 default route
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: IPv4 default gateway set to opt9
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: ROUTING: entering configure using 'opt7'
2022-08-22T08:53:44	Error	opnsense	/usr/local/etc/rc.configure_interface: The interface IPv4 address '' on interface 'opt7' is not public, not configuring 6to4 tunnel

If applicable, information from log files supporting your claim.

Environment the problem is in OpnSense 22.1 and up.

OPNsense 22.7.2-amd64 FreeBSD 13.1-RELEASE-p1 OpenSSL 1.1.1q 5 Jul 2022

Intel(R) Celeron(R) CPU J1900 @ 1.99GHz (4 cores, 4 threads)

Thanks.

[MosheL]

Thanks for response:

I want to add something from today's log:

2022-08-23T04:10:19	Error	opnsense	/usr/local/etc/rc.newwanip: Failed to detect IP for WLAN2[opt5]
2022-08-23T04:10:19	Error	opnsense	/usr/local/etc/rc.newwanip: IPv4 renewal is starting on 'em2'

em2 and opt5 has no IPv4. the IPv4 address (and v6 also) is disabled on the interfaces.

[fichtner]

I referenced this ticket by accident. I'm not sure what's going on here but I can say that if the PPPoE pushes an IPv6 it will be added by the PPPoE daemon and how the 6to4 plays into this I have no clue.

So to reiterate IPv6 renew takes place on PPPoE even if no IPv6 mode was set. If this messes with things we can look into it but we need to avoid strange things like using 6to4 to mess with the results.

Cheers, Franco

[OPNsense-bot]

This issue has been automatically timed-out (after 180 days of inactivity).

For more information about the policies for this repository, please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

If someone wants to step up and work on this issue, just let us know, so we can reopen the issue and assign an owner to it.

[MosheL]

the problem was disappeared after an upgrade. Thanks