@nothing: A/A is just another source of problems made up by the jews to save money buying cheaper hardware  :P Hahahha….  ;D

Also remember to turn off password protected sharing in Windows 7 or Vista if that is what you are using for sharing.

Easiest solution is on the interface tab (LAN for instance) you should have a pre-existing rule allowing internet, if you click the green arrow it will turn grey, indicating that rule is now "off" - essentially blocking interwebz for that interface. [image: AR9rOYo.png] **When I say "pre-existing" I mean to say a rule you created to allow internet traffic. Most people usually have something like * * * * *  meaning allow everything. I don't think pfsense creates such an internet rule for you automatically, just anti-lockout rules.

@stephenw10: The i350 has been well tested under 2.1, there are many reports of successfully using that card if you search the forum. I've never used one myself though.  ;) Steve Works just fine. I've got an I350-T4 in my system at home and I'm about to add a pair of boxes at work which each have 12 ports of I350. They're great NICs. Low power and fast.

After more testing this has nothing to do with pfSense.  It has something to do with having 2 IPs in DNS.

thanks mate! you saved my exam of networks!

I'm guessing that the high interrupt rate is because of a high packet rate.  You can probably confirm that with an RRD graph. When your first connect the switches together they have to learn which mac addrs are on which ports.  When they have to forward a packet and don't know which port the traffic belongs to then the switch will flood the packet to all ports (or all ports in that vlan).  That kind of storm should subside pretty quickly as the switch learns.  I have seen instances where I've had to clear the mac address table in both switches. If by connecting those switches together you have also created a loop in your network then you may need to run spanning tree on your switches.

The Gateway dashboard element shows the percentage of loss based on ICMP echo requests to your default gateway (by default).  You could try changing the IP address that you use for monitoring, under System -> Routing on the Gateways tab, you would edit your gateway to change this setting. If I were in your shoes, I'd ping the ISP's default gateway and then show them the statistics from ping.  You can do this in pfSense under Diagnostics -> Ping.  Assuming that you allow ICMP echo requests on your WAN port, they should be able to ping you too and see the loss for themselves.

I'm not sure exactly what you are trying to do or what gear you have available, could you do a quick drawing of your hardware and connections and post it?

@chpalmer: Is gitsync advisable at this point? Hasn't broken my lab setup yet…  :D Not advisable, but not known to be broken.

1. If you have good enough hardware, that should be fine 2. Squid package will do that 3. Captive Portal can handle that 4. Not possible. Network storage does not belong on a firewall.

Then get with the times already and upgrade :-) It's not an unreasonable restriction these days. The function that script calls only exists on 2.1. Sure it could be done on 2.0.x but it means copying a bunch of code and a lot of extra work.