A vpn connection on pfsense is just amounts to a different gateway you can policy route whatever you want through that gateway.  As to inbound from that connection - yes you can limit what it can talk to..

@chpalmer: no one here has figured out the crystal ball we stole from the weird looking lady at the carnival.. I think I know the problem. My gramma mentioned someone stole her personalised lawn bowling ball. Funny that. p.s. beware she is really pissed. >:(

Did you register your device? https://www.netgate.com/register/ Once you register your device (which is free) using its serial number, you get a login to the portal which has a link to the firmware. The "CCCC" repeating string is the BIOS waiting for a serial upload of a working boot environment. You should be able to write the firmware to an SD card and boot/reinstall from there as the FAQ suggests.

I'm using 3 Linksys routers (as dumb AP devices) loaded with DD-WRT for the last …. many years ! Version : Firmware: DD-WRT v24-sp2 (10/10/09) std My wifi network is hooked up to pfSense, OPT2, using 192.168.2.1/24. AP1 has IP 1912.168.2.2 AP2 has IP 1912.168.2.3 AP3 has IP 1912.168.2.4 For all AP's : Subnet Mask : 255.255.255.0 Gateway : 192.168.2.1 Local DNS : 192.168.2.1 Local DHCP server : disabled. WAN Connection Type : disabled. All my AP's are hooked up to pfSense using a central switch, but daisy chaining from OPT1 to AP1 to AP2 etc is also possible (I never use the WAN port, even when it is declared as another LAN port).

pfSense can run with one NIC. You could use VLANs to create multiple interfaces. It can also run with just one interface though if you're using it just as a VPN end point for example. Steve

@doktornotor: @craymore: @doktornotor: These things are simply EOL. Having issues even when updating due to lack of RAM, especially if you hit some bigger package update (python, perl comes to mind.) EOL ?!  :o Yeah, these are certainly EOLed as far as pfSense is concerned (together with rest of x86 arch). x86 is gone with 2.4. I mean, recycle them to run LEDE/OpenWrt or something similar on it and they can keep running for lot more years, but pfSense/FreeBSD is getting a pain to run on these. For details of will no longer be supported from 2.4 onwards: https://forum.pfsense.org/index.php?topic=121255.0

Ah, yes no way I know of to recover from that if you're seeing those errors. A fresh CF card is the safest way anyway. You still have the old one to boot from if there's an issue. Steve

I would try re-assigning LAN to nfe1 to be sure it's not a configuration issue. You can do that from the console menu. Depending on exactly which IC that re NIC is using you may need to disable hardware off loading etc. https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards Steve

Hi Gertjan, tks for the reply, I think I didn`t express myself very well. When I said that I changed some configurations  I mean that I changed on the webGui interface, not on the XML file. I did that just to have sure that the recovery really has returned all the previous configurations. But, about the second question, I tried to backup just a small part and tried to recovery again, but the error persists. I tried with the DHCP area, Captive Portal, aliases, then I quitted. What I think is really strange is to not receive any message of error, even on the log file. Any new ideas would be great. For now, just to have a way to load the backup configuration again, I logged by ssh terminal and manually replaced the config.xml on /cf/conf/ directory. That works, but I know thats not the right way to do it. Well, again, tks for the suggestions. regards

My Apologies. I thought that transparent mode meant the user not having to enter any proxy info in IE.  My mistake. I will do further reading and investigation as to what NIC I have to bind to the proxy.  At this time, I am binding both of them - but in all reality its my understanding that even if I just bind a single interface, both are being joined by the bridge anyhow. In essence, by selecting a single NIC, in bridge mode, both are being seen as one by pfsense. I am just trying to understand that.

@phil.davis: And we seem to have lost our crystal ball, do let us know if you find it ;) Make sure you have power-cycled everything. Have the front-end modem up first then bring up the pfSense box. If I had a crystal ball I would be banging my head on it right now  :o After changing one setting at a time and having no luck, I did what you suggested (and what seems obvious) … power everything down, bring up the modem, then the Pf box, then the peripherals ... presto! Can you delete this post and we will just act like it never happened. lol

Great thanks. Looking forward to finally giving the install a try this weekend!

How many switchports do you need? The Cisco Small Business stuff, like SG300-10, -20 or -28, is considered capable and price worthy in here. I wouldn't use a PoE switch to power a single AccessPoint but use a PoE injector instead. A cheaper switch that might fit is TP-Link TL-SG3210. Personally I'd stay away from everything with a Netgear sticker on it.

I have never seen that work successfully. I haven't spent long trying though. But yeah, there's no easy way and you shouldn't be using flash for caching anyway. TINC is available in 2.3.3 snapshots BTW. And in 2.4 but that won't run on an X750e. Steve

If you run through the setup wizard keeping the default subnet and then change the LAN subnet afterwards do you hit the same issue? Steve