Great. This is definitely a step in the right direction even it could use some further refining later. It isn't going to confuse anyone who already understands the situation and it will probably eliminate most of the incorrect gateway issues for people who don't.

Steve

If you think that it might be a signal issue, when your internet starts to act up point your browser to http://192.168.100.1 that should give you a diagnostic page where you can see what's going on with the signal. If you don't know what the numbers mean post them here and I will interpret them. Might be a good idea to record what they look like when things are fine too, that way you have a good baseline.

Still not sure I understand the issue. A diagram might help here if you can't solve it yourself.

Steve

Hmm, interesting. Hard to see what it might have been that caused a high php load. That could have just been a symptom of course, something else actually triggering the php script.

Steve

Is this a new setup or something that has been working any just failed?

Zero packets sounds like you have a layer 1 problem so possibly bad cable, bad switch port, bad NIC.

Other clients can ping each other across the switch? Are you using Static addressing throughout?

Steve

Really, extremely, dramatically lower!  :o
http://www.norgie.net/documentation/firebox/

Hence my advice here: https://doc.pfsense.org/index.php/PfSense_on_Watchguard_Firebox#Firebox_II_and_III
I'm not sure quite where the 1000 falls in the II or III model range but it's down there.

I'd be surprised if you can push 50Mbps through that box without any packages.

Steve

@johnpoz:

So use WPAD and autoconfiguration of the proxy then..  Duhh!!

excuse me sir  ;D
what is WPAD and i cant find menu on the proxy server?
i am so interest on filtered https with non transparency mode with autoconfig any device

best regards  :)

Power cycling modem and router/firewall should do the trick 99% of the time. Shut both down then power up the modem and wait until it is fully booted before powering up the router/firewall.

On a side note, whenever I set up new edge device my IP changes (the modem sees a new MAC address). I then clone my MAC address from like 10 routers ago and reboot the modem and it issues me the same IP that I've been using for years. Comcast won't sell me a static without converting to a business class connection but my dynamic has been essentially static, so why bother?

My home setup gets shutdown at the end of each day ….. so no long durations of up-time, but there have been days where system locks up and seems to do it more than once in a day when its misbehaving ...... have to perform a power reset ......

The Final release version of 2.1 is unstable on my hardware. There was a time in the early 2.1 beta it was rock solid.

One of these days when I feel up to it, I will investigate the logs to see if their are any clues as to why the lockups.

Thank you very much.

Duplicate?
https://forum.pfsense.org/index.php/topic,57028.0.html

Thanks for the quick input phil.davis

I was looking at Shielded CAT6 for in rack runs.
Outside of the Rack there is only 3 feeds, 2 are for the WIFI and the other one is for my entertainment center ( Smart TV, Receiver, PS3 and PVR )

Yup that's what I was talking about. With all this NSA stuff going on its got a lot of people including me paranoid.

There was an effort to write an Android app to make interaction with the webgui easier on a small screen:
http://forum.pfsense.org/index.php/topic,61416.0.html
Not really ideal though in my opinion. I think most people here would agree that pfSense would be better with greater front-end/back-end separation. At the moment it's difficult to write an alternative gui because so much is tied to the front end code.

Steve

Before the "unseen default deny rule" I put explicit deny rule/s on WAN that block and not log whatever garbage there is on WAN that I cannot do anything about and do not care about. For example, one of my ISPs has a lot of rubbish floating about on their internal network that provides the final metro wireless hop to us.
Status->System Logs->Settings you can also disable logging of the default deny rule. Then put rules yourself to explicitly block and log stuff you want to see. But usually you want to see the stuff that you are not expecting, i.e. things that do not match any of the rules you thought up.