61
19.7 Legacy Series / Re: Problems with 19.7
« on: July 30, 2019, 02:49:28 am »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.My ISP has some idiosyncrasies.
I have this issue on one of my connections
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.