Messages

With 23.1 and before i had an MTU of 1500 over my PPPoE connection.
With an dummy interface on the physical interface MTU set to 1512 [Vlan 4bits PPPoE 8bits].

ISP is KPN Netherlands, PPPoE over vlan6.

After the upgrade to 23.7 everything seemed to work fine, but when looking into interfaces - Overview PPPoE I saw that my MTU was 1492!

Fixed the problem to assign an interface to igb0_vlan6 and set the MTU there to 1508.

Is there anything changed why the MTU is not honored in 23.7?

After updating to 23.1.2 my system log is full of messages from apps.plugin.

Code Select Expand

2023-03-09T13:32:12
apps.plugin Cannot fetch process 71508 command line (command 'pgrep')
2023-03-09T13:30:20
apps.plugin Cannot fetch process 18869 command line (command 'pgrep')
2023-03-09T13:29:22
apps.plugin Cannot fetch process 23812 command line (command 'pgrep')
2023-03-09T13:29:13
apps.plugin Cannot fetch process 12741 command line (command 'pgrep')

When i tried to restart Netdata the folowing message appeared in the logs.

Code Select Expand

apps.plugin should either run as root (now running with uid 302, euid 302) or have special capabilities. Without these, apps.plugin cannot report disk I/O utilization of other processes. Your system does not support capabilities. To enable setuid to root run: sudo chown root:netdata /usr/local/libexec/netdata/plugins.d/apps.plugin; sudo chmod 4750 /usr/local/libexec/netdata/plugins.d/apps.plugin;

Is something changed in the permissions of Netdata?

I am running OPNsense 22.1.10, requesting prefix through PPPoE "/48".

Everything is working fine clients can get an IPv6 address through SLAAC.
When I was trying to run Wireguard over IPv6 and it didn't connect.

In Wireguard client i was trying to connect to the IPv6 address that was on the LAN site of my OPNsense install.

After some digging around I found out that the Wireguard interface IPv6 address was showing up in an traceroute from the internet to my LAN IPv6 address.
Also when I run a traceroute "from the internet" to any of my clients in my LAN is see the extra hop with the IP address of the Wireguard interface.

When restarting Wireguard the extra hop from the traceroute was gone, and I am able to connect to Wireguard over IPv6.

How is it possible that this extra hop is added after reboot?

Removed patch 4b6fa9e, upgrade to 22.1.5 and IPv6 is working instantly.

The FE80 address is the gateway for IPv6.
I think the info in the SSH screenshot is wrong, because the Preifx ID "0" is selected for LAN and not WAN.

Thanks for the patch!

If there is anything else you would like know, let me know and i take a look.

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!