Same here on a Alix2d13 afer update to 2.2
Also VDSL with VLAN 7
Disable IPSEC stops the crashes.
Any new information here?

I didn't understand this magic.

If I add 192.168.2.1 as VIP and delete the same VIP then I can ping my pfsense IP 192.168.1.11 from VLAN 2 i.e 192.168.2.x same way for all VLANs. But if I restart pfsense it is not pinging, again I have to add VIP and delete the same VIP.

Any idea?

Check out the bug report in https://redmine.pfsense.org/issues/3669

Note that there are 2 parts to the restarting fix:

First part relates to IPv4 script /etc/rc.newwanip - this fix is rolled into 2.1.4 and later.
Second part relates to IPv6 script /etc/rc.newwanipv6 - appears to be awaiting review (despite ticket being marked Resolved). Also impacts 2.2 release

In the meantime it is easy to manually apply the fix and stop the restarts.

https://doc.pfsense.org/index.php/Dig_command_on_pfSense_2.2_and_later has existed for a while, just sayin'. :-)

Wow, bad cable or bad adapter? Were you using 115,200bps for both?

Good catch I would have rules that out.  ;) Odd that 2.2RC worked and 2.2-rel didn't.  :-\

Steve

When you reinstalled from scratch did it work?

Yes worked for me on 32-bit architecture.
I have backup not the latest one but at least several months old make my life easier. Still looking for SquidGuard & HAVP package to work! I hope that you will get the solution soon.

Good luck

One thread is enough. See https://forum.pfsense.org/index.php?topic=87728.0 (The "Intel Atom" is absolutely useless info when debugging undetected NICs.)

Hey thanks for all the help. The client has decided to ship us the firewall/vpn appliance that will be used in the production environment. So we will be halting work on this VM solution until it becomes necessary again. I'm pretty sure your suggestion to set up another vm in the cluster to manage it would work but I might still be stuck with the same problem of not being able to navigate out of my cluster. I also think it would be helpful for me to work with a standard windows server or ubuntu distro to troubleshoot my vm networking issues. Once I fix that I bet I could troubleshoot the PF Sense thing better. anyways, thanks for the help. IF I come back to this and find a solution, I'll post it here.

Cheers!

There have been problems that somehow the PID file for an OpenVPN instance can get updated with a new PID but the new process dies because the old process is still there, or some similar timing interaction. In that case the dashboard code is trying to query the OpenVPN status of a PID that does not exist - so it shows down. But actually the OpenVPN instance is happily running with some other PID and users are happy.
As you report, if you kill all the processes then start them 1-by-1 it all goes green. That is because the PIDs in the PID files now match the PIDs of the running processes.
Actually you will probably find that from a user point of view all OpenVPN instances were working fine.

If someone can pin down the sequence of events that causes this, then it can be fixed some day :)

none of these suggestions are working, I'm going to try a fresh 2.2 install and restore my conf and see what happens.

Thanks to the quick reply!

I have noted after your message that the page loads with the port 8002. But then gets lost when trying to load on the port 8000.

EDIT:
Your post showed me the right direction. Indeed I had a mis configured Form in one of my Log in Pages.
I had the complete address including the port 8000 as a target instead of just the variable.

This however seemed to work till the last Version but the upgrade process seemed to not light this.

Thanks for your help!

After creating the nat rule,  you do not need a firewall rules to wan on high port.

You can also listen only on loopback and then nat it from wan 80 .

@BBcan177:

If you are only using the country blocking features of pfBlocker then those lists do not require conversion as they are already in cidr format.

I would disable pfBlocker. Then confirm if /var/db/aliastables is clear of all pfBlocker files. If not, delete any remaining files.

Then enable pfBlocker and reboot to see if it's still slow.

I have developed a new package called pfBlockerNG which is currently being reviewed by the devs.

BBcan177 - Any timeline from the devs on pfBlockerNG making it into the packages?  I have been waiting for this to hit mainstream since last year when talking to you.  Looks as if it may be the best fix for us PFblocker user folks. Thanks again for your hard work on it.

Ash,

@Accounts:

Traffic Shaper: Limiter…I had both an In and Out set under this. I had them both set via a Firewall rule. I had no traffic going via that rule after the upgrade to 2.2. I removed the In limiter and just set the Out and it started passing traffic and limiting correct.

Hmm.  The UI doesn't seem to allow an Out limiter without an In limiter set …

See some interesting behavior with the Queues however… after the primary crashed and restarted, it appears traffic shaping isn't either being reported correctly or it's not working. Normally about 50% of our traffic is VOIP:


Is this a full install to a HD or Nano? Is it 64bit?

Steve

WTF.  Someone should seriously disable the http version of that page, especially when it has anything to do with entering a password - always enforce/encourage good security practices guys!  Despite the fact of it simply being a mailing list, people (sadly) tend to reuse legit passwords and usernames all the time.

https://lists.pfsense.org/mailman/listinfo/announce