![]() Lastly the guest wireless network (vlan 30). DNS resolution and communication is working for this interface Member interfaces of the bridge, allow all ![]() Now note that my firewalls are very general because this isn't a strict deployment but heres what I have so farīridge Interface of LAN_PORT(original LAN) and the private wireless network (no vlan) ![]() I've at least attempted an ASCII diagram below Because of this, I was to block all traffic except traffic going outward (no subnet communication). Now, the guest network will be open and utilizing the captive portal for authentication. With the DNS Resolver disabled, NxFilter has become the DNS server and works great on both the bridge (LAN + Private Wifi), and on the Devices wifi. The WebGUI has been moved to another port for access. It's installed on my pfSense and uses ports 53 (DNS), 80 (HTTP), and 443 (HTTPS). Similar to the DNS Resolver, I'm using NxFilter to handle the DNS. Guest and Devices have their own interfaces, dhcp servers, and are located on different subnets. With that unifi AP, I have 3 wireless networks: "Private" bridged with the LAN, Guest(VLAN 30), and Devices(VLAN 20). ![]() So I have a single pfSense unit with a Unifi AP attached to it. Pass | IPv4+IPv6 | Guest net | * | LAN address | 53 Edit Solved it by setting an explicit rule passing traffic from guest net to the bridge port 53, 80, and 443.Įx. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |