It seems you have connected your pfSense to an existing network. pfSense sets the LAN IP to 192.168.1.1 by default. For existing networks this would not fit. At first you may to configure the LAN interface on the shell and assign an unique IP in your network. Then you get access to the web interface.

Bridge what connections? What do you think you need to bridge?

@Harvy66: I'm just going to wait for 2.2 stable, then try it out again. Might take quite some time. Meanwhile, snaps seem to be back.

There is a new advanced option in 2.1 that will allow the creation of a RAM disk to store logs on. It is documented somewhere, just search for it.

It sounds like the transparent proxy is blocking port 443 which the game login might be using to authenticate. You either need to apply the proxy settings in the game itself or create an exception in the firewall rules for the game server IP address. Just my thoughts. Look at this post: https://forum.pfsense.org/index.php?topic=62256.msg405719#msg405719  and reply #243. This should also work for your situation.

Reinstall the box.

Some random lawyer sending your bills doesn't sound to me like something that stands any ground. In switzerland there are various places to get help with situations like this. I'm sure in germany there are similar agencies available (see http://www.beobachter.ch/justiz-behoerde/gesetze-recht/artikel/rechtsstreitigkeiten_rechtsberatung-zum-nulltarif/ )

Okay guys, I found out that the router has an option to use as an access point. It disables everything except for wireless. Thanks for the help. No double NAT or a different subnet

Under Firewall: Virtual IPs: https://doc.pfsense.org/index.php/What_are_Virtual_IP_Addresses%3F#Proxy_ARP Steve

try disable the automatic update dashboard check In system-firmware-upgrade settings Dashboard check Disable the automatic dashboard auto-update check. If your connections are down your going to have issues with dns as mentioned, you could see if turning this off helps the dashboard display faster.

If that really is the MAC of the firewall, then look for a layer 2 loop. Something is causing the packets to come back into pfSense on that interface after it sends them out.

I don't have an Alix box to compare that behaviour to and I agree it's not what I'd expect to see on other equipment but if both boxes are doing it and one is working then it seems unlikely to be the cause of your problem. @opalit: less than 512M detected, disabling APC. That's normal on the Alix which has 256MB. Steve

As an update: I by now have my replacement Dell, so I could test my pfSense1 to the memory test. It has been running memtest86 for 24 hours with no problem whatsoever. I also discovered in the bios the motherboard will automatically scale back the frequency; the bios said 'RAM 1600, actual 1333'. A wise man who knows many, many things whispered in my ear I should try the PSU (thank you, wise man  ;D), so this is what I will do next. And else I will remove pfblocker, since that appeared to keep on crashing on line 262 constantly. Thank you for your help  ;D