What on earth do you mean here? This doesn't make any sense. There's nothing to bypass, the traffic will either never hit the firewall if the WSUS server is on the same LAN, or will get routed to another subnet. Are you trying to cache WSUS with Squid or some such stupid idea?

I guess a combination of access hours using firewall rules and then captive portal vouchers that can let users "buy" lengths of time within that period. That might be a bit difficult to let them have, e.g., 2 hours during that period and that period only. If they are issued with a bunch of CP vouchers then they could go on a splurge and use them all in 1 day. Or if you give them out daily, the user can save them one day and use them the next. Administratively you would have to give them 2 hours worth of vouchers each day which expire at the end of that day…

Yes, that will allow that traffic out from the phones on the LAN on those ports. But like I said I would suggest just opening all ports for one phone as a test if you're still have problems. Steve

SG300# SG300#configure SG300(config)#vlan database SG300(config-vlan)#default-vlan vlan 99 New Default VLAN ID will be active after save configuration and reboot device. SG300(config-vlan)#exit SG300(config)#interface vlan 99 SG300(config-if)#ip address 192.168.99.2 255.255.255.0 {gateway address} SG300(config-if)#end SG300#wr reboot (with "reload")

Google "Unix command line tutorial" and get started from there. Do notice that many of the examples you'll find assume that you are using a shell and the webgui command line is not a shell. Commands such as cd(1) don't do what you expect from the webgui command line because each invocation of a command using the webgui is a separate process. If you're serious about learning the UNIX command line I suggest that you don't do your learning on pfSense, set up a VirtualBox virtual machine with FreeBSD 10.3 (or 11.0 if you like) instead.

well. I'll try what you suggest

I read on another thread that Privoxy is not officialy supported under pfSense. So I just installed  it on my LInux box instead.

@johnpoz So what do you suggest I should do ?

I found out that Intel has huge problems with their C2000 Atom CPUs due to a bug with the B0 Stepping. As i'm using a Supermicro A1SRi-2758F, this could be the issue, but i don't know exactly. Can someone explain, if the error on the screenshot on my previous post could be related to this?

Verizon forums on DSL Reports is probably were you'll get answers for this.

Well, not an academic issue as its the primary firewall for my home office and it seems silly to limit bandwidth below a certain rate when the equipment (not to mention paying for it) should be able to handle it. That being said, within 4hrs of the initial post, the firewall killed again, without artificially saturating with a speedtest.  Additional testing with hard setting the rate to 1000 didn't seem to have an effect.  Something over 100mb/s and obviously less than 1000mb/s kills the thing. At this point, reviewing my old notes and logs from a while back… and actually forum posts here.  The original WAN port was bad, so with the current symptoms and it not seeming to be a pfsense issue, pretty sure the old IBM appliance is just giving up the ghost. As such, think it is time to replace... so just going to mark this as solved so folks don't attempt to go down a rabbit hole.

hmmm that is what I was thinking too.. I made the MAC address static and block traffic. I'll check back in a day or so to see if anything turns up.

Not sure what your seeing.. But yeah NO..  Sorry doesn't work that way..