that doesn't seem to matter … its a appears to be a general issue: https://forum.pfsense.org/index.php?topic=111108.msg626013#msg626013

And my problem remains the same!

I've also heard of people on other systems using scripts that ping a target and when the ping goes high, it starts to clamp down on the traffic shaper. Because traffic shaping is almost only useful if you're the slowest link. If your ISP is not giving you enough bandwidth, then that is no longer true.

I can't think of why this happened but I reformatted the disk and reinstalled pfsense. Worked like a charm!

Packet capture at the client to see where the web traffic is actually going. I suspect that only some of the traffic is going through the tunnel, such as maybe DNS and that is the WAN traffic being seen.  But the web traffic is using the local internet connection instead of the tunnel.

Attached is another screenshot of the log. Could there be anything other than the firewall that could be causing the problems I'm running into? [image: log3.png] [image: log3.png_thumb]

No, not possible with just standard NAT. The reason is that PF has no means to inspect the payloads of the data packets that are flowing trough the packet filter, to do redirections based on the destination hostname part of the HTTP headers you'd have to know what's inside those payloads.

What does pfsense have to do with a switch port?  Come on think for a couple of seconds here..  How does pfsense tell the switch not to negotiate a connection "lights" on the switch?? "the printer refuses to accept any connection" Well again No Lightly No Worky!!! Is your printer 10/100 while your switch port is hard coded GIG?  You get NO Lights at all, not even a flicker when you first plug in the cord??  But your saying this printer works on another switch?  And your saying other stuff works when you plug it into the port on the switch printer doesn't work on? What is the printer, what is the switches involved.  What is the cable your using.  You changed cables right?

@artooro: For the record we have found the source of this issue, some of the code that was written for a linux environment doesn't seem to run quite as well on freebsd so we'll issue an update for users asap. And Mothra as a preview-release early tester we will personally contact and verify with you that the fix is working. Interestingly I didn't see this issue on my virtual machine. Thanks! Top notch service as usual ;) Update fixed the issue.

Thanks Jorge I stepped through the suggestions in your posted links, and nothing seemed to work until I got to Traffic Shaping.  The Traffic Shaping had been done on the original installation, so of course the speeds were off ! I reran the Wizard and tweaked it a bit, and voila - I get to keep this old box for a while longer. Appreciate the tips, they were right on :) Regards

YES!!! that worked..i logged in as admin and was able to make changes. Now to configure my group to be allowed to makes changes too.

@georgeman: https://atxfiles.pfsense.org/mirror/downloads/ Or any of the other mirrors. Still, I would suggest to troubleshoot the issue and get it fixed (if due to a bug) Thanks, i've been troubleshooting the issue for 2 weeks now and whilst i'm pretty sure it's a bug and will present it shortly, I need to get a working solution for my customer asap.

@cmb: That ATA error is likely because the drive is dying. Guessing it'll probably come back, might just not be hitting the part of the disk that's problematic post-reinstall for some reason. Maybe next power cycle or some future power cycle it comes back. Check SMART on the drive, though it being clean isn't necessarily indicative of no issue. I couldn't even check it, it has a output/input parse error. I believe my HDD died on it unfortunately. Every time I shut it down and try booting it backup I get a ton of errors and now when I tried turning it on I got kernel not found. I'm gonna replace the HDD/SATA cable and see what happens.

On #2, this is RRD objecting to time running backwards. The first timestamp is recent (May 10th), while the second timestamp is from back in January. It may be that the current time has not yet been set after boot. I see this happen with power cycling systems that do not have a battery backed clock. It goes away once NTP is synchronized.

up

Hello Fahim, Do your PPP logs give you any idea of the problem? can you post them here? Mike.

@coxhaus: I can run packet captures if it would help? Yes that would be telling. Filter on the IP of the TV.

Race conditions!