pfsense very restrictive
hashbang last edited by
I'm a newbie mostly working on linux OS. I just wanted to test bsd so i chose pfsense. I frankly think its too restrictive.
- Enforcing default policy to drop. No way to change it ( or is there a way )
- CLI i find buggy. I added a wan ip adress with gateway. Then i changed the ip address to something else and changed the gateway but the older gateway was still in config. I checked it in config.xml. I'd too reset to get the gateway working
- I could find no way to work with confs, if i dont find web-ui adequate.
- Added a vlan on lan and i got locked from internet side. I didnt find any reason why I got locked eventhough i configured only the lan side
My most of work is remote installation and support. I installed and configured from cli and I'm still locked. I simply gave up.
- Huh? The default rules on lan for outbound are any any - ie allow all..
- No idea what your doing there - the preferred way to admin pfsense is via gui
- Again whole idea behind pfsense is gui.. If you don't like/want gui then find another firewall/router distro would be my suggestion.
- No idea what you did, so can not answer or even guess to what your problem was.
Um, yeah seems like you might have been better using FreeBSD if you just wanted to try *BSD.
pfSense is tailored specifically to be a firewall/router and to be mainly configured from the GUI. A lot of what might apply in FreeBSD, such as editing conf files, does not apply in pfSense. All the config is stored in one xml file.
So he wanted pfsense to just be his bsd box? Yeah not going to be good for that ;)