Yes you could use pools in one subnet and filter them differently using aliases but you can't filter traffic between the clients on one subnet that way. Traffic would just go between them directly without passing through pfSense. Only one interface.
Really you need to use VLANs in there to separate the traffic at layer 2.

Steve

@stephenw10 said in iwifw() module loading show ERROR in dmesg, if it needed on server ?:

It's already not loading them. You can see they are not listed in your kldstat output.

Adding those lines to loader.conf won't change anything. They are loader variables you have to add them there, adding them as sysctls does nothing.

You are only seeing those lines at all because you're booting verbose.

Thank You Steve (and all others here!) for patience and help with this case.
Have a nice day!

This is a Proxmox topic and i'm not an expert on it.

@sujan-0 said in Wireless interface not visible:

I have installed pfSence successfully with 2 network interface vmbr0 and vmbr1

vmbr1 has no network adapter connected yet.
If you install pfSense with to interfaces, it uses the first one for WAN, the second for LAN. However, it allows only access on LAN, but that might be connected to vmbr1 which is not connected to any network.

If you only enable one interface, the GUI should be accessible on this.
Or if you're running other VMs on Proxmox, you can connect to vmbr1 as well as pfSense and access the GUI from there.

However, basically if your router provides DHCP, pfSense should pull an IP from it on WAN if it's connected to vmbr0.

post-up iptables -t nat -A POSTROUTING -s '192.168.8.0/24' -o wlan0 -j MASQUERADE

I think, there is no reason to have a masqerading rule on the wifi.

I would suggest you reconsider the configuration of your setup with pfSense, by following this guide:
https://www.netgate.com/docs/pfsense/wireless/use-an-existing-wireless-router-with-pfsense.html