https://doc.pfsense.org/index.php/OpenVPN_Remote_Access_Server Or are you talking about connecting pfsense as a client to some VPN service you have purchased or run somewhere else?

@Chrismallia: Throw out the router and buy a dedicated AP In larger professional environments I would agree but in any application where budget is a concern, routers often offer better bang for the buck. In SOHO applications, where budgets are often very tight, the additional switch ports are also often useful additions. It's very simple: If the router have an AP mode (as the router in this thread have with original firmware) - use that and connect to any port. If the router doesn't have an AP mode - don't connect anything to the WAN port and disable the DHCP server (if another DHCP server is already present in the network).

Nothing definite unfortunately. Typically you would see a watchdog timeout error from one of the msk NICs on the console. You might try leaving a serial console connected to see it anything is shown. Did you see this without the modified drivers? I've no idea what those were compiled against or what changes went into them. I didn't compile those 10.X modules. Steve

"class c ip adress dmz" Is that public or rfc1918? Do devices behind pfsense (that I take it you are calling ps box) access stuff in the dmz? But yes normally how you access something like a AP from remote would be with a vpn.  Do your AP have gateways set pointing to pfsense?

https://forum.pfsense.org/index.php?topic=113842.msg632969#msg632969

Ive also come across this, but I still have internet on all the pc's [image: PFSense.png] [image: PFSense.png_thumb]

@xlameee: I already checked the vpn settings they are OK Well you say that, but it isn't working and you haven't posted your VPN configuration or really any details at all so I'm doubting that you have it all set up properly. Also, you named your interface VPN_LAN, do you have a normal LAN? Are you using a VPN server or client? What are your firewall rules? What are your NAT rules? Is there any useful output in your logs? You said it was working for 8 months, what changed? Did it just stop working one day? If so there is probably something useful in your logs. We need details if you want help. A list of your interfaces and saying you can't ping stuff doesn't mean anything.

I've seen dpginger not come back up after transient packetloss. I've had this happen a few times in the past few months where my ISP would fail-over, resulting in a few seconds of pure loss in the middle of the night, only to wake up and see my quality graph showing 100% loss since that event until I restart the service. It's possible dpinger is just not recovering from loss and continues to mark the interface as offline?

At status log: /system_authservers.php: ERROR! ldap_get_user_ous() could not bind to server .

@jimp: Just /cf/conf/config.xml The RRD is a lost cause. The Soekris device could only run 32-bit, and whatever you replace it with should be 64-bit, so you can't just straight-copy the RRD files. Well crud. So much for that. If you could boot that pfSense install and do a config backup from the GUI you could include the RRD in an architecture-independent way there, to import into a new system. But either way it's not worth the extra headaches. Oh well. I guess that's better than starting from scratch. Thanks for the info, hopefully my PFsense appliance will show up early next week and I can get that going.

Those a FIN packets, indicating the TCP state should die. This is only a symptom of a problem. What this does mean is the connection is created and established. Something is going wrong when your PS4 is trying to end a connection.

I put my NAS,Server and Router in one box.They are hosted under ESXI6.5 and I pass through my disks to nas vm with a LSI-92118I card(flashed into it mode already) .

…Now to come up with a revised numbering scheme for 100+ domestic devices!

NanoBSD is no more secure or protected than the standard FreeBSD installation is. From the functional point of view they are identical. The differences are only in the way the configuration files are handled to reduce unnecessary writes on media that doesn't cope well with excessive writing such as CF cards.