[SOLVED] 24.7.4 Erratic PPPoE IPv6 Problems

[REB00T]

At least in previous versions, if the interface wasn't assigned Hardware CRC, LRO and TSO remained enabled. Ipv4/Ipv6 is none/none. With crowdsec disabled and having reloaded the interface no ipv6 prefix is picked up.

[franco]

Ok, fair point. Though that is no longer needed today.

Next step would be to add an IPv6 pass rule for ICMPv6 on the WAN interface for testing purposes to see if the traffic is silently dropped somehow. You could also enable logging of default rule blocking (Firewall: Settings: Advanced) to see if it pops up in the live log.


Cheers,
Franco

[REB00T]

So after just waiting, no prefix is picked up. But upon hitting save and applying in the interface configuration screen a few times it does get a prefix. Having left it alone for a long time it did not seem to work without the above procedure.

PS. No ipv6-icmp traffic gets logged as dropped/rejected and the allow rule did not get hit.

[REB00T]

Curiously, subsequent reloads and the above procedure do seem to work. The prefix gets picked up again fairly consistently.

[REB00T]

After a reboot with crowdsec enabled, after a significant amount of time though, the problem appeared again. Then another reboot after disabling crowdsec, the problem persists. I do not think it is some kind of rate limiting from my ISP because the back to back tests before behaved fine. Anything stand out in the logs?

[franco]

Can you share the PPP log as well? Maybe it's similar to https://github.com/opnsense/dhcp6c/issues/39


Thanks,
Franco

[REB00T]

Left it alone last night with crowdsec disabled. Nothing has changed. Attached the pppoe log.

[franco]

This is a bit odd:

2024-09-19T22:22:05   Informational   ppp   [opt3] IFACE: Rename interface ng0 to pppoe0   
2024-09-19T22:22:05   Informational   ppp   [opt3] IFACE: Up event   
2024-09-19T22:22:05   Notice   ppp   ppp-linkup: executing on pppoe0 for inet   
2024-09-19T22:22:05   Informational   ppp   [opt3] xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx
2024-09-19T22:22:05   Informational   ppp   [opt3] IPCP: LayerUp   

According to the log ppp-linkup is calledbefore ng0 is renamed to pppoe0, but it's already told the interface name is pppoe0. In theory that's asking for trouble, but I've never seen someone raise such an issue before.


Cheers,
Franco

[REB00T]

This is a bit odd:

2024-09-19T22:22:05   Informational   ppp   [opt3] IFACE: Rename interface ng0 to pppoe0   
2024-09-19T22:22:05   Informational   ppp   [opt3] IFACE: Up event   
2024-09-19T22:22:05   Notice   ppp   ppp-linkup: executing on pppoe0 for inet   
2024-09-19T22:22:05   Informational   ppp   [opt3] xxx.xxx.xxx.xxx -> xxx.xxx.xxx.xxx
2024-09-19T22:22:05   Informational   ppp   [opt3] IPCP: LayerUp   

According to the log ppp-linkup is calledbefore ng0 is renamed to pppoe0, but it's already told the interface name is pppoe0. In theory that's asking for trouble, but I've never seen someone raise such an issue before.


Cheers,
Franco

I don't think I have a peculiar configuration. There is a vlan on top of the physical WANPARENT interface, with pppoe0 on top of that.

[franco]

I know, just something weird being observed there. Merging the ppp log into the system log would provide the means to fix that longterm.  :)


Cheers,
Franco

[REB00T]

I remember you writing that the relevant patch won't be in 24.7.5, but just to confirm, the behaviour seems to be the same. Otherwise smooth as always!

[franco]

This was about the other dhcp6c fix, right?


Cheers,
Franco

[REB00T]

I believe so

[franco]

Ok you are still running that successfully or you need another build for it?

The update may have scrubbed the test package due to version change.


Cheers,
Franco

[REB00T]

Haven't applied the patched build. The work around of requesting just a prefix works for now. Do you want me to test it?