For anyone finding this in 2024, I had to enable "Multicast Enhancement" for the Unifi Wifi network AND I had to disable Hotspot 2.0. Only then did the Router Advertisements flow down to wifi clients. I was sitting in wireshark on a MacOS 14.6 laptop client and suddenly there was a flurry of traffic. Pro-tip: You may have to wait for the RA interval for the Unifi change to make a difference. Default is 200 seconds, you can change this in the RA Server settings. I set mine to 10 seconds then clicked the button to restart the RA server. This worked! [image: 1730900736051-screenshot-2024-11-06-084436.png] [image: 1730900948556-screenshot-2024-11-06-084835.png]

@johnpoz My drawing above is the existing config. The Netgear switch is completely unused. I would be fine using that if need be for the VLAN or port 5 or 6, although from Example 1 here, which I was going to loosely follow for the VLAN tagging, it appears to me, I should be able to remove a port from VLAN 1. https://www.tp-link.com/us/faq-788.html Tim

Everything depends on your setup. Would need more details. Post a network map. Are your VLANs terminated on PFsense or your switch? Post your server1.conf What are the IP's in the VLAN you're trying to access? What do the rules look like on your LAN and OpenVPN tab?

Two things that I forgot to mention are that I already have OpenVPN set up successfully for my normal network and that since I'm new to the pfSense concept, I've never worked with VLANs on it before. I do, however, understand the VLAN broad concept since I've taken a Principles of Networking class as a computer systems administration student at my university.

teşekkür ederim ilginiz için

Create a LAGG on pfsense and on the switch stack. Use the LAGG as the vlan parent.

Correct, the patches above are copies of the changes made in the repository that will be used to build pfSense 2.4.4-p1. So not "hacks" exactly. If it's all working for you now then there shouldn't be anything to worry about. When you upgrade to 2.4.4-p1 the manually edited files will be replaced with the copies from the new release, which already contain these changes.

You will neef IGMP proxy for 'discovery' to work. Unless you can use mDNS instead in which case try Avahi. Of coarse if you can enter the IP address of the NAS directly in the devices then you don't need either. But alas that's too easy for most manufacturers it seems. Steve

@johnpoz When I installed pfSense on the new router I created two interfaces... I had read on the basic firewall page that OPT interfaces have no rules and forgot that - thanks for setting me straight and waking me up. Firewall rules are scary but I'm getting there.

@dbinoj I'll try that as soon as I get home. Thanks :)

The copy jobs will be between nas to vsphere and external. Probably it will be smb3, i did not decide yet. After removing the whole lagg config on pfsense and switch it works! I can work with that but i'm still interested why it did not work with lag...