Not only that, usually it's deployed to keep networks separate, so say that a companies accounting department can't access the systems for the R&D department, and R&D can not access the production network and vice-versa.
Yep, I thought that one was obvious but thanks for explaining.
Even if you set VLANs up on a managed switch it's still on the same hardware and therefore the result of the switches software. Vlan tagging is VLAN tagging, regardless on if you set it up through PFsense (and the PFsense software sets it), or if you set it up on a managed switch (and the switches software sets it), VLAN tagging is VLAN tagging.
So what managed switch is used then ? I know I think that it can provide, IDS/IPS etc but wouldn't be cheaper for business to just use PfSense as it can provide similar capabilities and features but for free ?
When I had my issue with improper shutdown I had just bought my gateway and thought there was something wrong with the device and called NetGate. They are the ones that told me what I was experiencing was because the device was shutdown improperly. The first question out of the guy was to ask me if it had lost power or just gotten unplugged. That's when they said that if it got shutdown wrong it could not only lock you out of the web configuration, but it could create other anomalous behaviors as well.
So, how did you get back into it and fixed it ? When Web Interface is locked I imagine there's no other way to get into the box than either tunnel to it via SSH or do a factory reset and restore the configuration file ?
You can do it that way. Just make sure that you set the network IPs in the routers first. So say the PFsense is 192.168.1.1, you set one router as 192.168.2.1, and the second router as 192.168.3.1. You don't need to setup VLANs to configure it like that and keep network separation.
I'm a bit confused by it, I won't be getting another two routers but rather Wi-Fi access point which I would need to pin via Ethernet Port to the PfSense box. Also, I don't think that changing IP addresses like [PFsense 192.168.1.1 / Access Point 192.168.2.1] would do any good because the Access Point is plugged under PfSense and the users under this AP can for example still run scan PfSense IP and discover various devices connected under PfSense box as well as access it's web configuration page. At least that was the case when I was playing around with normal router without VLANs which then had another router connected on the LAN side. I don't know if I have explained it the right way but I have tried my best to do so.
Also a Zotec box should come with a WIFI card, it'll take some configuration on your part (or so I've read) but you can set it up for wireless too.
In the recent days I have done more research about Intel processors and their security and it looks like I would rather build my own mini box using AMD Ryzen processor because there are new vulnerabilities in Intel's micro chips which affects most of the Intel processors. I know there will be fixes coming down in a couple of weeks but I think until they appear in PfSense it might take some time. COming back to those vulnerabilities, they are called Meltdown and Spectre. There are no cases in the wild but PoC was released and I would rather not risk anything as it's the matter of time until someone figures it out and start attacking various targets.
Now, to the build itself, I just need to look for AMD Ryzen processor which supports AES-NI and it should work fine I presume ?
The last link will show you how to configure VLANs
Helpful links
https://www.techhelpguides.com/2017/06/12/ultimate-pfsense-openvpn-guide/
https://www.infotechwerx.com/blog/Policy-Routing-Certain-Traffic-Through-OpenVPN-Client-Connection
http://supratim-sanyal.blogspot.com/2017/04/pfsense-pfblockerng-ultimate-list-of-ip.html
https://nettb.com/blog/2015/03/pfsense-dns-leak-when-connected-to-vpn-fix/
https://nguvu.org/pfsense/pfsense-baseline-setup/
My main use case is Selective Routing. pfBlocker allows me to create IPv4 lists. I then use the Firewall-Rules-Lan to use the list to route the traffic to the appropriate WAN or VPN interface.
Thanks for providing links. I'm a bit confused about selective routing, why do you need to use it ? Sorry, I'm kindda new to PfSense as it's my first time using it. Also, I have find some security issues with some VPN's and I was wondering when deploying OpenVPN via PfSense I would be vulnerable to it ?
Massive security issue:certain VPN providers on OE. Even tho that it looks like the issue is with a VPN Provider as well as the specificly mentioned "OS", I was wondering if this could expose any internal servers, other computers or simply my my PfSense services like SSH in my network to the internet aka WAN side by just using VPN Provider + OpenVPN ?
It might be a stupid question but I would like to ask to make sure I have the right information, when using OpenVPN on the router level, does that mean we as user's give the VPN provider access to all our network and computers since PfSense is our main router which handles our network and its devices, or does VPN only applies to internet packets when travelling from one location to another ?
Last edited: