Messages

Nameserver is there

Code Select Expand

root@router:~ # cat /tmp/pppoe0_nameserverv6
2a02:a47f:e000::53
2a02:a47f:e000::54


I only request an prefix.

Also investigating your MTU solution, but that isn't working for me.
Some websites aren't available at all!
I have a PPPoE tunnel over VLAN 6.
I have created an unused (only for setting MTU) interface IGB0 with an MTU of 1508, on top of that VLAN6, and on top of that PPPoE.

When looking at https://www.speedguide.net/analyzer.php i can see that I am using an MTU of 1500.

opnsense-patch 4b6fa9e
Did solve the problem for me.

Patch removed en reloaded the PPPoE device.

Code Select Expand

root@router:~ # cat /tmp/pppoe0_routerv6
fe80::1251:72ff:fe23:3288

Also the default IPv6 route is gone in the GUI.

Then applied https://github.com/opnsense/core/commit/4b6fa9e556690 and IPv6 is working again!
Also the default route is back in the GUI.

Without the patch installed i did see the "IPv6 delegated prefix" xxxx:xxxx:xxxx::/48 in the overview.

At the moment i am unable to check without the patch installed.
But with the patch installed i see the default link local gateway.

Code Select Expand

root@router:~ # cat /tmp/pppoe0_routerv6
fe80::1251:72ff:fe23:3288
root@router:~ #

Before i installed the update i didn't see the default gateway in the gui.

I will try to lookup the file tonight.

Well with the patch applied my clients AND the OPNsense box are able to connect over IPv6.

Code Select Expand

***GOT REQUEST TO AUDIT CONNECTIVITY***
Currently running OPNsense 22.1.4_1 (amd64/OpenSSL) at Tue Mar 29 09:52:34 CEST 2022
Checking connectivity for host: pkg.opnsense.org -> 89.149.211.205
PING 89.149.211.205 (89.149.211.205): 1500 data bytes
1508 bytes from 89.149.211.205: icmp_seq=0 ttl=59 time=5.230 ms
1508 bytes from 89.149.211.205: icmp_seq=1 ttl=59 time=5.271 ms
1508 bytes from 89.149.211.205: icmp_seq=2 ttl=59 time=5.811 ms
1508 bytes from 89.149.211.205: icmp_seq=3 ttl=59 time=5.129 ms

--- 89.149.211.205 ping statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.129/5.360/5.811/0.265 ms
Checking connectivity for repository (IPv4): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 783 packages processed.
All repositories are up to date.
Checking connectivity for host: pkg.opnsense.org -> 2001:1af8:4f00:a005:5::
PING6(1548=40+8+1500 bytes) 2a02:a450:839:dddd:: --> 2001:1af8:4f00:a005:5::
1508 bytes from 2001:1af8:4f00:a005:5::, icmp_seq=0 hlim=59 time=3.404 ms
1508 bytes from 2001:1af8:4f00:a005:5::, icmp_seq=1 hlim=59 time=3.280 ms
1508 bytes from 2001:1af8:4f00:a005:5::, icmp_seq=2 hlim=59 time=3.301 ms
1508 bytes from 2001:1af8:4f00:a005:5::, icmp_seq=3 hlim=59 time=3.398 ms

--- 2001:1af8:4f00:a005:5:: ping6 statistics ---
4 packets transmitted, 4 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 3.280/3.346/3.404/0.056 ms
Checking connectivity for repository (IPv6): https://pkg.opnsense.org/FreeBSD:13:amd64/22.1
Updating OPNsense repository catalogue...
Fetching meta.conf: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
OPNsense repository update completed. 783 packages processed.
All repositories are up to date.
***DONE***

Before applying the patch there was no default route for IPv6, with the patch applied the default IPv6 route was there again.

Also dutch ISP KPN FTTH . (PPPoE over Vlan 6)

My German isn't good at all but on twitter I read this thread, https://twitter.com/opnsense/status/1507439603082579978 where "opnsense-patch 1a5dfc932f8" is mentioned.

I tried applying the patch and reload the PPPoE interface and IPv6 is working again!

The default IPv6 route was missing, with the patch applied it was there again.

After upgrading to OPNsense 22.1.4_1 i have no IPv6 connectivity.

Through DHCPv6 over PPPoE i  am able to get an /48 prefix, which is served to the clients through radvd "Track interface".
Clients in my lan network are getting an IPv6 address but pining an IPv6 host is not possible. (Ping within the /64 network works)
When running a ping from the gui, "ping6: sendmsg: No route to host" is the message.

In OPNsense 22.1.3 I had the same setup without any issues!

On 21.7 the IPV6 ip address generation did the same.

https://forum.opnsense.org/index.php?topic=26335.0

IGB0: 40:XX:XX:02:cb:17 WAN
IGB1: 40:XX:XX:02:cb:18 LAN currently unused
IGB2: 40:XX:XX:02:cb:19 GUEST
IGB3: 40:XX:XX:02:cb:1a unused
IGB4: 40:XX:XX:02:cb:1b unused
IGB5: 40:XX:XX:02:cb:1c LAN


Last night i moved my LAN from IGB1 to IGB5, the link local address on opnsense ends with CB:1C as expected.
I was also able to ping the link local address from the lan to opnsense.

From my guest network i am unable to ping opnsense through link local ending with CB:19.

Before is switched my LAN to IGB5 i had it on IGB1.
In this scenario is was unable to ping the link local address of opnsense.
The link local address was the same CB:18 address as link local of the PPPoE tunnel!

I am not having any problems with guest interface but found this behaviour strange.

IGB0 sorry :-[

In Interfaces Overview WAN the fe80::4262:31ff:fe02:cb19/64 is used as link local.

pppoe0 runs on top of IGB0!
Thats the strange thing!

So i suspected the link local address would be generated from the MAC address of IGB0 and not IGB2.

The pppoe tunnel is build over Vlan6 on IGB0

Hi,

It looks like the link local address of the WAN PPPoE is the same as the link local address of the LAN interface.

Code Select Expand

igb2: flags=8a43<UP,BROADCAST,RUNNING,ALLMULTI,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=802028<VLAN_MTU,JUMBO_MTU,WOL_MAGIC>
ether 40:62:31:02:cb:19
inet6 fe80::4262:31ff:fe02:cb19%igb2 prefixlen 64 scopeid 0x3
inet6 2a02:a450:839:XXXX:XXXX:XXXX:fe02:cb19 prefixlen 64
inet 172.19.0.1 netmask 0xffffff00 broadcast 172.19.0.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

pppoe0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> metric 0 mtu 1500
inet6 fe80::4262:31ff:fe02:cb17%pppoe0 prefixlen 64 scopeid 0xf
inet6 fe80::4262:31ff:fe02:cb19%pppoe0 prefixlen 64 scopeid 0xf
inet 77.XXX.XXX.91 --> 195.190.228.50 netmask 0xffffffff

There are no troubles using IPv6 connectivity on the IGB2 LAN network.
From the LAN side i am unable to ping the link local address of the router!
Running a traceroute from a client to google reports the GUA address as the first hop.

Anyone capable of explaining this behaviour?

Dag,

Op IGB1 de Vlans 10 en 20 aanmaken.
IGB1 naar switch als Trunk met vlans 10 en 20, van switch 1 een trunk met wederom vlan 10 en 20 naar switch 2.

Dit lijkt mij de makkelijkste oplossing, of er moet nog iets mogelijk zijn met LAGG, om zo IGB 1 en 2 tot 1 interface te maken.