OPNsense Forum
Archive => 19.7 Legacy Series => Topic started by: bimmerdriver on July 28, 2019, 09:30:50 pm
-
I updated my release system to 19.7 today. There are two problems, which were both present in the pre-release versions.
The firmware reporter is reporting, "Unfortunately we have detected at least one programming bug."
Here is the error:
[28-Jul-2019 11:37:05 America/Vancouver] PHP Warning: vsprintf(): Too few arguments in /usr/local/etc/inc/util.inc on line 986
The other problem is that Gateway Monitor (WAN_DHCP6) is not starting. There are no errors in any of the logs that appear to be related to this problem (although it could be that I'm not looking in the right place for the smoking gun). There is only one instance of dpinger running and that is for WAN_DHCP.
I also noticed that every time I try to start the gateway monitor, another instance of the above PHP warning is issued.
My offer still stands to make the system available for someone to take a look at.
-
https://github.com/opnsense/core/issues/3604
-
https://github.com/opnsense/core/issues/3604
Thank you for posting. I was looking on github and I saw that issue. My system has only one IPv6 gateway, so I'm not sure if the symptoms are the same.
It may be unclear in my post, but IPv6 is working properly with no issues at all. The only issue is that the gateway monitor is not working.
-
See Francos comment mid way down. I believe you also use the dhcp6c Send Solicit option which means the ISP does not advertise a route. Causes the gateway to be not fully operable in 19.7 so dpinger does not start.
I have this issue on one of my connections
-
See Francos comment mid way down. I believe you also use the dhcp6c Send Solicit option which means the ISP does not advertise a route. Causes the gateway to be not fully operable in 19.7 so dpinger does not start.
I have this issue on one of my connections
My ISP has some idiosyncrasies.
Their edge router requires the DHCP message exchange to take place before the RS/RA message exchange. Their edge router will not reply to an RS message until after a prefix has been delegated. I've debated this exhaustively with one of their engineers. They think this is a "security" feature so I doubt it will ever change.
Rather than sending periodic unsolicited RA messages to the all-nodes multicast address, their edge router sends individual unsolicited RA messages to the unicast source address of the host that sent the RS message. (Apparently this is because some of their access devices cannot accept unsolicited RA messages sent to the all-nodes multicast address.) Their alcatel/nokia routers can do this. Their juniper routers cannot do this. They are trying to get juniper to support this, but in the interim, customers who are unlucky enough to be connected to a juniper router do not receive unsolicited RA messages, so IPv6 will not stay working.
Their edge router delegates a /56 prefix. No other sizes.
Their edge router does not provide a WAN GUA address.
**Sense supports this configuration. OPNsense used to support it, but a change in 19.7 broke the gateway monitor. Otherwise, IPv6 works fine. I would be happy to provide log messages or whatever or even access to the system if someone wants to take a look.
-
Here are some screen captures from my system. I'm not sure this problem is the same problem as others have reported.
Consistently, every time I try to restart the gateway monitor, this error is generated:
[30-Jul-2019 18:34:51 America/Vancouver] PHP Warning: vsprintf(): Too few arguments in /usr/local/etc/inc/util.inc on line 986
-
Okay, so much for the last post. I just updated. Now the gateway is missing and the error is gone. Maybe it is the same problem, after all.