@xtropx:

I was able to recoup some lost space by deleting the .pbi in /tmp.

That's interesting because the standard config in Nano is to mount /tmp as a ram drive. I'm not even sure you can do anything else without some work. Did it actually change the disk usage?

Steve

Ah ok.
The Marvell 88e8053 NICs as reported in the link can suffer a lock-up. In the Watchguard boxes it usually only happens under heavy load and is reported as a "watchdog timeout" in the logs. There is an easy workaround though:
https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Known_Issues_2
The firmware (actually more like a group of register settings) update didn't help the watchdog issue. It only removed errors from yhd boot log. Are you seeing those errors? Which version are you NICs running? What does the following report:

Steve

There is already an existing thread open with suggestions to try.

Edit: Here - https://forum.pfsense.org/index.php?topic=75069.msg413219#msg413219

Can you access the firewall via console?  Check your CPU status.  Perhaps something is gumming up the works, so to speak.

I have been playing with GRE tunnels recently and I have them working fine on 2.1.2.  The only caveat is that the tunnels still need to be manually started after a reboot.  I am surprised that using 'ifconfig gre0 up' doesn't bring the tunnel up.

Are you able to ping the tunnel endpoints?  Did something happen to any of your rules to stop allowing GRE through?  Is either firewall on a DHCP address and the address changed after the upgrade/reboot?

someone any ideas which rules i must set for LAN traffic?

Not supporting hostap mode is what i was afraid of, it's the whole reason i have wanted wifi working  :-[

This little box is so nice with the dual Lan and not to crazy expensive. I will just have to use my TP-Link - TL-WA901ND 2.0, as my wifi access point then. Mulit-SSID da thing  ;D

May give building a kernel module in a VM a go at some point because as you say it does not look like it's too crazy mad scary to do.

Thanks for the help/info  8)

I skipped the errors and it installed. Not sure what to think of that, but at least it is working.

I don't see why it wouldn't work, though if this is a critical system I'd probably do a update to 2.0.3 first, just in case.

Just add a firewall rule to the single interface (presumably still WAN) that allows that traffic. Usually if you've only configured one interface such a rule will already be there.
You would only add a route like that to allow the pfSense box to access another subnet via some other internal router. Not to allow access to it. This routing would usually be taken care of by your existing router.

Steve

Thank you, I think that might have fixed it.
Good karma to you :-)

OK that should be good then. No inherent worries there. As with any update, be sure to take a backup first but otherwise, kick it off and see what happens.

Thanks so much guys… I've got some work to do. :-D

Thank you. It helped me.

You can use something like Security Onion to monitor your network.  It's very in-depth security and monitoring tool.  This is probably overkill what you need but wouldn't hurt to take a look.

I think all found out the solution, but: Perhaps that helps for others
https://forum.pfsense.org/index.php?topic=75427.0

I assume 65.65.65 is not your real subnet?

A common cause of not get internet access on LAN is having set a gateway on the LAN interface. Do you see more than one gateway in System: Routing: Gateways:?

A common way to use assigned static IPs would be to use virtual IPs on the WAN and 1:1 NAT them to devices on the LAN. If you need to use the public IPs on the LAN you'll need to disable NAT.

Steve