<![CDATA[Rules for vlan]]>How can i limit 1 single computer to only access from internet and not access other computers in the same network?

]]>https://forum.netgate.com/topic/101537/rules-for-vlanRSS for NodeSat, 11 Jul 2026 08:58:23 GMTWed, 15 Jun 2016 13:06:06 GMT60<![CDATA[Reply to Rules for vlan on Wed, 15 Jun 2016 14:43:43 GMT]]>thank you :)

]]>https://forum.netgate.com/post/631833https://forum.netgate.com/post/631833Wed, 15 Jun 2016 14:43:43 GMT<![CDATA[Reply to Rules for vlan on Wed, 15 Jun 2016 14:20:32 GMT]]>255.255.255.255 is not a subnet.. that host specific /32 mask..  Not sure what you think that does?  Normally that would never be placed on a client - that sort of mask is used in routing or a firewall rule to represent that specific IP.

If you don't want a client on a network to talk to other clients on the network normally you would use a switch that provides private vlan support.

https://en.wikipedia.org/wiki/Private_VLAN

]]>https://forum.netgate.com/post/631822https://forum.netgate.com/post/631822Wed, 15 Jun 2016 14:20:32 GMT<![CDATA[Reply to Rules for vlan on Wed, 15 Jun 2016 13:17:32 GMT]]>ok, thougt it was possible with subnet 255.255.255.255, but i gues they can just change it.

]]>https://forum.netgate.com/post/631802https://forum.netgate.com/post/631802Wed, 15 Jun 2016 13:17:32 GMT<![CDATA[Reply to Rules for vlan on Wed, 15 Jun 2016 13:08:30 GMT]]>"other computers in the same network?"

You would need to do that switch level.  Pfsense has nothing to do with traffic between computers on the same network.  If your talking traffic from one network/vlan to another network/vlan on pfsense then sure you can create the appropriate firewall rules.

But when computer on 192.168.1.100 talks to 192.168.1.101 pfsense is not part of this conversation at all..

]]>https://forum.netgate.com/post/631797https://forum.netgate.com/post/631797Wed, 15 Jun 2016 13:08:30 GMT