03-09-2020 07:28 AM - edited 03-09-2020 08:18 AM
Hi, I have a SG250-26 release 2.5.0.90 and I am facing an IPv6 deployment problem.
I've build an IPv6 SLAAC & stateful router on Pfsense, but the communication between devices through the switch is not working.
I can see RA and RS in and out of the switch, devices connected to the switch therefore are getting an a valid IPv6 address (via RD, ULA type), but it is impossible to get unicast of ICMPv6 (ping) working between devices connected to the switch.
Is there an option I must allow/enable to get this ICMPv6 messages to working?
I also have a problem with DHCPv6 solicit messages.
Bridge Multicast Filtering is enabled (forwarding method via IP group address).
03-10-2020 01:30 PM
Bear in mind that the NS is sent on the solicited node multicast address, so any kind of multicast filtering might interfere. It would make sense to disable the multicast filtering and see if the NS and NA could be exchanged.
Regards,
03-10-2020 02:28 PM
Thanks for the feedback. At first glance I did not see any improvements. I'll have to perform some more testing to confirm if it changed anything. I have the MLD snooper/querrier enabled as well... of course it only works if filtering is on, but when it's enabled should I not see an entry in the MLD group table like "ff02::1:2" when a DHCPv6 solicit is sent by a client? Because that's also not working :(
05-05-2020 08:43 AM
It may sound stupid, but I'll ask anyway. Do I need to turn on IPv6 interface on the switch to actively enable IPv6 unicast traffic? Meaning do I need to assign an IPv6 address to my switch for it to allow IPv6 unicast traffic through my network or should it just let everything pass through it?
I am managing my switch over IPv4 and until now did not see a need to enable IPv6 interface and routing, but perhaps I should start there?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide