@stephenw10 Um, I do tend to go a wee bit overboard on the pfBlockerNG lists... ;-)

Thank you for your kind reply.

I forwarded your suggestions to our dev team.

For now this ticket is closed.

Thanks again.

Yeah the VLAN interfaces are treated exactly like any other interface; you can apply firewall rules to them individually.

@stephenw10 This was what i was going to respond to you with in my 2 cents comment but i let it go.
The redmine is spot on. If you are doing a Multi-WAN set up than as part of the configuration you should, explicitly, enable gateway actions because thats the whole point. Otherwise, keep the gateway action disabled.
The RRD graphs are very valuable so i would keep the monitoring enabled for sure.

Thanks again for your help. I think you're 10/10 with my issues now? 😊

I would replace it.

This is a bit different from the tuntap issue. I've captured the details here. armv7 kernels currently differ from arm64 and amd64 in that they do not statically link the if_gif module, so it must be loaded at runtime. A change has been authored for this and an update to the System Patches package is forthcoming.

@rcoleman-netgate thanks for the info and help. Have a great day.

Yeah you can do this if you have a tunnel or transport subnet between the two locations are can NAT the traffic at both ends.
It sounds like you are trying to have the 192.168.0.0/24 subnet on two interfaces on the same pfSense router here though. That cannot work.

@clevers
Tried a web search?

Virtualizing pfSense Software with VMware vSphere / ESXi

@steveits

Thank You -- I have set it to 1.1.1.1. (CloudFlare) - and it appears to have made the red go 'bye-byez'

c40bfc16-2797-4b99-bea6-5912060b408a-image.png

What actual errors are you seeing? At either end?

@gertjan
Thanks! I meant swapping it with the drive with the Untangle installation if I can’t configure the pfSense installation to my liking. As suggested by @stephenw10, this might be easier than reinstalling and restoring from backup while I’m still doing all these tests and optimization.

You almost certainly don't want to have VLAN1 tagged on any port. VLAN1 should usually exist inside the switch only so you should probably just have that untagged on 1 and 5-8 or only on 1 with every other port excluded.

I don't expect an AP like that to be doing any routing so I would try to disable the WAN ports entirely and setup only a LAN. Though I don't have any direct experience with Omada gear like that.

Steve

On top of that tip from @stephenw10 you should be able to set up also the following things;

Create a user for each device and user that should be connect to the NAS According to that users set up user Privilegs to the files and folders on that NAS Set up on the PCs shortcuts to that NAS folders.

If you are using LDAP and/or Radius don´t forget to sort
all users/PCs with an certificate and/or set up the machines
correctly in the LDAP role

Either working with VLANs and/or plain routing you must
set up firewall ruiles on the pfSense according to both
subnets or on the Switch you are using the right
matching ACLs.

The Akismet plugin for NodeBB has basically zero configuration options. The only thing you can set is the reputation level above which it no longer applies.

Check for IPv6. pfSense will provide IPv6 by default if it sees it available and many devices will try to use it by default. If something upstream changed you might have IPv6 when you didn't before.