@keyser Thanks for the reply. I have a spare port on my router and I will use it to experiment with.

@chris.doldolia The 2100 has a 4 port switch. The documentation page I linked above will allow you to treat a given port as (change it to become) a separate network interface. In the default configuration the individual ports cannot have an IP address because they are all the same LAN. If you want to add a VLAN and have it work on all four ports then I think you need to add the VLAN to "port 5" which is the switch. You might post your Interfaces > Switches pages, and Interfaces > Assignments pages.

Now, I can start configure more rules on the FW + connecting the Netgate directly to my ISP Modem. Great Is there a recommende list of FW settings laying around? I saw several of the Youtube videos where they kind of had their own focus. Based on the description, this would be a GUEST network. Here’s an example for you: Note: GUEST users are not allowed to use pfSense’s DNS server. Instead, I’m using DHCP to provide a public DNS server for them. [image: 1753873577326-5f99a867-d081-4c33-ac6a-de697d0826fb-image.png] Internal network alias is an alias that contains all my local networks.

@SteveITS Yep. The address in that /29 was given by DHCP.

@johnpoz You just don't get the different in working on layer 3 and layer 2. It is why you have default gateways and default routes and they are different. ThAT SEEMS TO BE OVER YOUR HEAD. Your firewall to the world is going to be layer 3. You are lost in pfsense and you can't see the forest for the trees. Go away John please do not reply to my threads. I will try not to post any more here. And yes I ran a small team of network people a long time ago. I had over 4000 PCs and around 50 locations so get over it. You ran me off last time and I went back to Cisco over pfsense. Look back in the threads years ago. Plus pfsense was having routing issues or slowdowns on routing as I was doing layer 3 back then at home. Version 2.8 is fast now which is good. Having a connection of 10gig reduces your latency whether you run full 10gig or not. I have 1 gig of data on a 10gig connection. I think this is best you can do now for home. I have a Cisco 10gig layer 3 switch I plan to install soon. So I can push the extra data bandwidth.

@spickles I would think the easiest way to replace a Cisco ASA 5505 would be use pfsense as a firewall not a router. Keep using your Cisco L3 switch. I do that at my home. I use an Cisco L3 switch and route between my L3 switch and pfsense. You lose pfsense control over your local network. This would not be an issue with you as you will already have that with your L3 switch. Setup pfsense with no vlans and keep all the vlans on your L3 switch. Then set up your firewall rules and static routes to your L3 switch.

Indeed, I have to consult the community on how to configure the captive portal, too.

Thanks! Surfshark does not support IPv6. DHCPv6 Server is not running on Guest Guest VLAN IPv6 Configuration Type is None. [image: 1751811989749-e300cdf0-d2f6-472a-bc37-67536aa7f008-image.png] Router Advertisement Router Mode is Disabled [image: 1751812258868-585e8e78-a12d-4437-8663-7ea80d8c1555-image.png] Added a Guest firewall rule at the top of the stack to block IPv6 traffic [image: 1751812578788-7cf2241b-4d32-4d08-9a25-75e272d7ae31-image.png] Also tested disabling IPv6 in the APN on my phone. Didn't help. We're still having problems with some apps/content on our phones.

I managed to solve this myself today. The reason I can't ping the client directly connected to the igc1 of pfsense is because of the Bitdefender stealth mode setting. Once I turned it off, I can now ping the client. I came up with this solution because I tried Ubuntu on a flash drive, and I can ping it, so there is a problem with the firewall of the Windows machine. That's why I checked all the firewall settings one by one on the Windows client.

@Dobby_ Thought I'd be the only one who would ever use a number like 300 in an IP address.

Ok I tried your solution, and it's ok. Really thank you, for the solution and for the explaination. I really don't like doing thing without understanding what I'm doing and why. One more time Thank you

@Bob-Dig said in CANNOT PING VLAN INTERFACE IP FROM SAME VLAN: @HHUBS said in CANNOT PING VLAN INTERFACE IP FROM SAME VLAN: Or I should ping it from the same VLAN even if no rules are added? No, it is the firewall and with that, it is able and will block the connection without rules. Different would be to ping a host on a switch, which is in the same LAN. Then the connection is not hitting the firewall in the first place and the firewall can do nothing about it. @johnpoz said in CANNOT PING VLAN INTERFACE IP FROM SAME VLAN: @HHUBS out of the box the only interface with default rule to allow is lan that defaults to an any any rule, anti-lockout.. If you create a new interface be it vlan or native you would have to add the rules you want. Yes by default no rules would hit the default deny and yes block ping, or any other access. Thank you so much for your help.

I got it to work. It had to do with not setting mtu of 1400. I can now do dns lookup and it works! Thank you for your suggestions.

@scottlindner if the goal is leverage 2.5ge connection - yeah a small 2.5ge seems like a good solution. You could then if enough ports on this new switch - leverage lacp from the 1 gig switch to provide for more bandwidth to the router. This wont help with a single connection, but it would provide for more bandwidth for multiple devices on the 48 port to the router interface through the 2.5ge switch. Yeah a 48 port 2.5ge managed is prob not all that cheap ;) You could then also move a vlan or both off your current lan interface onto their own 2.5ge interface. Maybe a 16 port 2.5ge switch price is more budget friendly? This would give you plenty of ports to work with - you could have 3 different uplinks for your networks, and then 2 or more as lacp to your 1 ge switch, and leave plenty of ports for 2.5ge APs into the new switch. Or maybe 8 port is enough?

@Gblenn I would have followed up earlier but have been busy with both the network and other stuff. I still appreciate your advice. And I have been reading more about the concept of VLANs. The old D-Link is still in the rack and I use it for a "backup" so I can go back to this if the Unifi switch does not work. Theres is another problem that I haven't been able to solve. The Unifi controller holds all the configured wired and wireless networks even if I use hardware reset on the switch. But no matter what I do, the switch appears to be offline after a few moments. And even if it still handles the traffic according to the configuration, it is offline in the sense that I can't ping it or log in with ssh. When I use the old switch and just connect the new one through a single cable, the switch can be adopted and configured. I have read a lot of post about similar issues at the Ubiquiti Forum. Some suggests to manually change the inform host like this set-inform http://ip-of-controller:8080/inform. This seems not to change anything. Other suggestions are to add an 43 option to the DHCP server (pfSense) or make a host override at the same place. Do you have any suggestions?