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..

@markn62: Does the Vlan adapter need its MTU adjusted from 1500 to 1528 to tag packets or is it done behind the curtain? Not 100% sure but never had to do it with any of my setups. @markn62: Does the dedicated parent adapter need to be created and enabled No. I usually leave the parent alone since I avoid having tagged and untagged traffic on the same interface. When I started this (mixing T & U) was strictly a no-go. Nowadays it is supposed to be ok - but I still don't feel comfortable with it. @markn62: If both a Lan2 & Vlan adapter are needed for the Vlan adapter to tag packers properly, what should the parent adapter's MTU be set too 1500 or 1528? not needed, don't mess with it.

If a burst of bandwidth is a problem, then traffic shaping may be in order. But it would be nice to know what is causing it. Tricom_2 shows a reduced mirror of the incoming bandwidth, indicating something like ACK packets. If this is the case, then it's a TCP stream.

If you try to sniff the packets then all you'll see is encrypted data.  You can look at Squid and SquidGuard logs to try to get any information but I think you'll be sniffing the LAN and WAN ports instead.

Hello Do you have the opportunity to test with a computer on each interface (PC on WAN - pfsense - PC on LAN) and have some iperf or similar tests between the two PCs  (in passthrough and in firewalled configuration) ?

Put some rules on them.. Unlike lan opt interfaces have no rules when created so no access.