@jimp:

Still the same issue as before with a relative link starting with /

Now if you used ../index.php, that might be ok.

ok, I made it… and pushed all the files in my clone... (also the ones for LCDProc, sorry but I thought that a "commit" was enough)...

Can you please merge the changes in the main repository?

@stens:

I'm not using squid or any proxy. Have configured pfsense to do QoS and traffic limiting.

Did you add a rule to queue ICMP traffic into an unrestricted or high priority queue?

If not, it (ICMP) could end up in a queue that drops packets when overloaded, leading you to think that there are link latency issues when it is just the traffic shaper doing it's job.

I used to get this, albeit with an actual cable WAN connection until I added a rule to queue ICMP traffic into qACK (highest priority, non-bandwidth limited).

Yes this helps.
Thanks.

DON'T WORK. DON'T WORK.  :'(

From the description it seems like a bug that was fixed in em(4) driver just lately.
Upgrade to the latest snapshot that has the fixes in and test with it.

I tried again from scratch.
Now it works.
I wasn't even able to do firewall rules on ovpn tunnels. Now they match correctly.
I tried to remember what I've done the previous time.
The problem was probably related to a misleading tutorial that suggested to assign a new interface to ovpns1. I tried this conf but it didn't work. I rolled back, but I think that the conf has been hopeless corrupted.
Thank you, you've been precious!

Hi
Thank you for help,
I am in transparent proxy.
Tab: Common ACL: I am using ext url redirect
blacklist tab is working well now.
but Squidguard seems not block sites in blacklist database.

In brief, they filtered all web traffic but not block

I look in every details of settings of Squid and Squidguard but can not find reason. Before I use the version build  in Mar, it is OK

Hope you can help

I will have to check that, but it is a 19" rack mount appliance box with a low end video onboard (vga) card.

I just physically checked the box and to my embarrassment the box only has 1Gb of RAM in it .. must have been high when I built it hehehe :)

Hi Guys,
Just back in the door after a long long day.

Well it's all up and running and have learned a precious lesson.

After many phonecalls with the ISP and digging about on forums I got up, walked away from the desk and got some fresh air. I decided to go back to basics.

First up, check the cat5 cabling. Whilst checking it, (by pinging the LAN and WAN interfaces) with a direct connection to my laptop, I found I couldn't ping the WAN interface. I thought, gotcha!! There must be a problem with the cable. Swapped it out, same with the replacement cable. Then I started looking at the WAN NIC. This was a Broadcom NetXtreme Gigabit integrated with the motherboard. Remember, I thought I had got it working the previous day so it must be compatible. Went to the Free BSD compatability hardware list. It had lots of Broadcom NetXtreme cards all in the Broadcom NetXtreme II family but not the original. I was gutted. I was sure I had checked it beforehand and remember I was more concerned about the Sundance (ST201) card, that is supported. So in the end I didn't use the motherboard NIC but put in another Sundance (ST201) card and hey presto!! All up and running and no speed degradation.

I feel frustrated, tired and more than a little bit stupid….grrr!!

Anyone else reading this post....check the hardware compatibility list. Save yourself some blood sweat and tears ;-)

Have ammended the original posting accordingly.

Thanks for the help anyway guys.

Kind Regards,
Niall

Might be related to this…

http://redmine.pfsense.org/issues/1407

Can you draw me a schema or describe the router1 and router2?
How are they connected to each other(switch, direct cable, carp)?

Thanks alot!

Are the ports opened by UPnP?

That would be up to the UPnP client to close them out.

Oh that. I'm working on the builders. That isn't the server being down.

I had to do a ports rebuild on there and we're working on some patches now. The way you said it was like the snapshot server was down, not that the build had stopped. I knew the build stopped, I did it. :-)

That is the updaters directory, not the snapshot directory. The amd64 full update is right there (latest.tgz)

You are probably expecting this URL instead:

http://snapshots.pfsense.org/FreeBSD_RELENG_8_1/amd64/pfSense_HEAD/updates/?C=M;O=D

The URL that ends in .updaters is a special directory used for auto update. It only has the most current update in it. The other URL contains past updates as well.