Isn't anyone else having this problem??? (Solved)
-
Hi all,
I posted this in the webgui forum, but did not get any feedback. I'll try it here and see if I do any better…
I've just installed 2.0 RC1 on a Dell PowerEdge 1850. This server was previously in production using v1.2.3 and running fine.
I don't get far into the web configuration before I start having issues...
The 1st thing I did is go to the Advanced tab and set the notification info for email. When clicking save, it takes between 30 - 45 seconds before I can continue (Is this normal?). Then I go to the General Setup and set the hostname, etc. When clicking save, this takes about 15 seconds (OK, better). Then I go to start configuring my gateways and static routes. I can get through creating the Gateways without issue. But, when I start creating static routes, I have all kinds of problems. Either after clicking Save or Apply Configuration, my web browser will time out. I won't be able to reconnect that session for 1 to 2 minutes. It will then reconnect, but the page I was working on did not save. I can usually get 1 route in at a time before this process repeatedly happens. Now, as soon as my browser is timed out, I can close the browser, re-open it and get logged in no problem. However, I can only make about 1 change before I get timed out again.
Now, back at the console. When this happens, my CPU usage in nothing. However, if I watch the filter logs, as soon as GUI stops responding, I see a ton of the following:
rule 1/0(match): block in em0: 192.168.13.4.xxxxx > 192.168.13.1.443 ...
rule 2/0(match): block out em0: 192.168.13.1.443 > 192.168.13.4.xxxxx ...These alternate and then are followed up by the following:
rule 2/0(match): block out on em0: 192.168.13.1.443 > 192.168.13.4.xxxxx: tcp 4 [bad hdr length xx - too short, < 20]
(The X's are random numbers based on the current port in use)
I've had this problem now on multiple servers. I've tried installing and configuring v1.2.3 on the 1850 that I'm working on now with no problems.
Can anyone help out here?
Thanks,
Jeff
-
Do you have an interface down and that interface is in a Gateway Group? I'm having lots of similar problems when that happens on RC1 AMD64.
-
Not sure about the "Gateway Group". But, I am configuring it offline. However, one time I did try plugging the WAN port into a switch just so it would have a link. (Gateway was obviously not reachable) Still had the same problem.
-
State killing is overzealous when a WAN is down it appears. Under System>Advanced, Misc, check the box under Gateway Monitoring to not kill states. Does that make it stop?
-
It could be a dns issue … i have seen webgui act strange in multi-wan situations when 1 or more or all gateways are offline
Removing the default system info widget from the dashboard seems to help in some cases.
perhaps setting dns to an ip that is reachable (and does not time out on port 53 but rejects) will sort it out
-
Chris,
That did the trick !!!!!
THANK YOU ;D
So should I uncheck that box once it is back in production? Or is it safer to leave it checked at this point? What's the drawback to leaving it checked?
Thanks again!
Jeff
-
@cmb:
State killing is overzealous when a WAN is down it appears. Under System>Advanced, Misc, check the box under Gateway Monitoring to not kill states. Does that make it stop?
Thanks for this advice. It sounds like I was having the same (or similar) issue that kronso mentioned (two gateways in a 'balanced' gateway group), where connections were being dropped even if they were going through the WAN that stayed up.
Now running "2.0-RC2 (amd64) built on Fri May 27 14:15:10 EDT 2011", but the issue was happening even with that version, right up until that setting was changed.
Maybe a note mentioning something about this setting could be placed on the Gateway Groups page?