Either it has some CPU/cache/memory hardware problem that is causing page table references or some critical bit of the kernel got corrupted on the CF card - "page fault while in kernel mode" should never "just start happening". The easiest thing to do is to take out the CF card and re-write it a new good pfSense nanoBSD image. If that works then you are in luck. If the CF card gives errors when writing it, then you know to get another CF card. If you still get "page fault while in kernel mode" on a clean pfSense boot, then there has to be some hardware problem on the board. Since the CPU, memory is all fixed to the Alix board there is not much benefit in knowing if it is CPU or memory or…

Did you get a chance to power cycle everything, if so did it "fix" the problem?

I am using 2 to test currently, although will be using 3 when I go live. At the moment I have set the non-active one to not be in the "allconnections" gateway group so only the 2 active ones are in there.

Yeah, I think I might do that

also posted here: https://www.reddit.com/r/PFSENSE/comments/320qhb/killed_out_of_swap_space/ which is where I originally replied.

@Codewarrior: Hey, Pretty new to pfsense and I'm honestly a bit confused. I was trying to connect a test computer to a domain that is outside our local network. upon typing in the domain I get prompted to login upon logging in, I get an error stating "The network path was not found" (I get this with fake credentials or with real ones) This only happend when its behind pfsense. If I connect it directly to the internet I can connect without a problem. Windows firewall is disabled and I have the DNS server setup as the domain server as well. Most settings are default and not alot has been changed. Pinging the domain's address connects to the correct IP address. Screenshots http://d3gq0spernq6eg.cloudfront.net/9n91y.jpg (Censored for anonymity) http://d3gq0spernq6eg.cloudfront.net/y9f9c.jpg http://d3gq0spernq6eg.cloudfront.net/w11vc.jpg Any assistance or links to appropriate documentation would be greatly appreciated! Solved. Had nothing to do with Pfsense was a problem on the Windows server with file and printer sharing being disabled on the network adapter Works fine after enabling it.

@irj972: With appropriate hardware you see a 10%hit on your non vpn throughput I'm on a 120/10 and see 111/9 usually aes256 blah blah aes-ni on a c2758 board etc Right.  I've got a c2558 board and think I'll be OK in that regard.  I'm more concerned with the speed of the Air VPN servers.

Well I guess if it's on a separate virtual interface and only that interface has offloading enabled in the host then maybe. The offloading options in pfSense are global though so I would expect it to affect all servers equally. Also the slowing down described here doesn't sound like the 0.4Kbps described in the known symptoms. However since this is a known issue I would definitely be disabling off-loading everywhere anyway, that's why I linked to it. I don't use Xen so I'm completely open to being wrong here.  ;) Steve

It's a pretty much accurate comment.  Though the resource in the /documentation is using the traditional way. :)  https://doc.pfsense.org/index.php/Using_Captive_Portal_with_FreeRADIUS#CaptivePortal_Self-Registration:FreeRADIUS.2B_MySQL

Thank you very much for your reply. Managed to get it done by re-mounting the file system to read write.

I see what you are saying here, but I should mention that the remote PC is not company owned equipment either. Which means I am not going to have exclusive access to it. This is another reason why I was thinking the manual proxy route would be better. No one has so far answered my question, does that mean that it is not possible to do what I am thinking or does it just mean that no one has done it before?

Can you resolve names or not?  If you can resolve names it's not a DNS problem. What are the firewall rules you put on your LAN? You mention load balance and default gateway.  Which is it?  For the former you set Gateway: GWGROUP for the latter, you set Gateway: default

No one an idea? vnstat2 info                       rx      /      tx      /    total    /  estimated em0:       Mar '15    987.65 MiB  /  485.98 MiB  /    1.44 GiB       Apr '15    13.06 GiB  /  625.77 MiB  /  13.67 GiB  /  52.27 GiB     yesterday    363.27 MiB  /  131.27 MiB  /  494.54 MiB         today    357.13 MiB  /  46.83 MiB  /  403.96 MiB  /    476 MiB em1:       Mar '15        57 KiB  /      0 KiB  /      57 KiB       Apr '15    649.12 MiB  /  12.09 GiB  /  12.72 GiB  /  48.64 GiB     yesterday    124.28 MiB  /  191.94 MiB  /  316.22 MiB         today    59.52 MiB  /  141.16 MiB  /  200.68 MiB  /    235 MiB ath0_wlan1:       Mar '15      4.18 GiB  /      0 KiB  /    4.18 GiB       Apr '15    92.84 MiB  /      0 KiB  /  92.84 MiB  /      0 KiB     yesterday    29.23 MiB  /      0 KiB  /  29.23 MiB         today      4.95 MiB  /      0 KiB  /    4.95 MiB  /      --    ath0_wlan2:       Apr '15      3.16 MiB  /      0 KiB  /    3.16 MiB  /      0 KiB     yesterday      2.47 MiB  /      0 KiB  /    2.47 MiB         today      241 KiB  /      0 KiB  /    241 KiB  /      --   

re1: <realtek 8111="" 8168="" b="" c="" cp="" d="" dp="" e="" f="" g="" pcie="" gigabit="" ethernet=""> port 0xd000-0xd0ff mem 0xf0004000-0xf0004fff,0xf0000000-0xf0003fff irq 18 at device 0.0 on pci3 re1: ASPM disabled re1: Chip rev. 0x48000000 re1: MAC rev. 0x00000000</realtek> php-fpm[67150]: /rc.linkup: Hotplug event detected for GVT(lan) but ignoring since interface is configured with static IP

Those files will be overwritten by upgrades. Outside of that, nothing else should touch them. Should be easy to use the system patches package to patch that file.