24.7.7 - Not responding to IPv6 Neighbor Advertisments (Solved)

[techyporcupine]

Hello! I just recently set up HE's Tunnel Broker for IPv6 on my OPNsense install, and have it working for the most part, except devices only get IPv6 addresses after being connected for a couple of minutes, and I can see devices sending Neighbor Advertisements with TCPdump, but the router doesn't respond, and the devices only get V6 IP's after an unsolicited advertisement.

A screenshot of the RA page is attached.

[meyergru]

Is this on a VM by any chance? There is a known IPv6 multicast problem in Linux networking (see here).

[techyporcupine]

This is actually on a VM running on Proxmox. I was about to update this post, but I switched from using PCI passthrough for the NICs to a Bridge in Proxmox and now the issue seems resolved?!

[meyergru]

I would use vtnet, because it is faster than the emulation these days and also would disable multicast snooping for good measure. In my experiments, it always worked for a few minutes and then failed.

[techyporcupine]

It's still going strong with the Linux bridge config! I think I'll just leave it like this now, because I don't seem to be having any problems. I wonder if maybe the Realtek NICs were a problem before?

[meyergru]

It's still going strong with the Linux bridge config! I think I'll just leave it like this now, because I don't seem to be having any problems. I wonder if maybe the Realtek NICs were a problem before?

FreeBSD Realtek drivers have been known to cause problems in the past. By using them bridged, you do not have to rely on FreeBSD drivers. Matter-of-fact, the vtnet drivers are often more performant than FreeBSD native drivers.

[techyporcupine]

Oh wonderful! I think I'll mark this as solved!

[techyporcupine]

Marking as solved.

[techyporcupine]

Nevermind I don't actually think I can mark it as solved

[meyergru]

You can edit the thread title. BTW: Did you see this?

[techyporcupine]

I did not! I saw a couple similar ones but not that!