@wallabybob:

I've come to think (possibly quite erroneously) of the buttons like this:
"Save updates the configuration file. Apply processes the relevant section of the configuration file so the recent changes are also made to the running configuration."

Hence one generally shouldn't see an Apply unless a Save button has been previously clicked.

That's how it works.

Not sure if it's related to load but what's happening is your WAN NIC is losing link with whatever it's plugged into. Maybe your modem is rebooting under high load, or you have a bad cable or bad modem or bad NIC (probably not).

No, squid and squidGuard are add-on packages available through the packages menu.  Keep in mind that they are not developed by the pfSense developers themselves (usually) and may be in differing states of development or functionality.  Before putting any package into production it will be a very good idea to test it heavily.  Check the packages forum for more information on which packages work well.

Hi again

Take a look at my old thread:
http://forum.pfsense.org/index.php/topic,32805.0.html

I fixed redmine and closed the ticket. Thanks for the update.  :)

your welcome :-) I had the same issue with i first tried 2.0

@mikeisfly:

I would check under you wan rules to make sure you are not blocking Private networks.

Thank's for opening my eye's, that was the Prob!!!

I'll later check to put the ALIX in a DMZ on the WRAP to ease port forwarding…

Greetz
Mirco

Its a great idea, and I do use dnsomatic from time to time, however the site (including the list of supported services) hasn't been touched in years, and I needed several other services (including one custom designed one) to be automatically updated.

thanks :)

Ok Now I think I got it ,,,, case of too much info . Not enough coffee!
This way works
Thanks

nat2.0works.JPG
nat2.0works.JPG_thumb

For anyone who might encounter with this problem, I tried to replicate it on another machine by installing 1.2 and upgrading to the same snapshot and packages. The second machine worked flawlessly although it had fewer interfaces and firewall rules. I will post if I find anything when I try to work on the original machine.

adios

Like Jimp said, pfsense can load just a touch slower than other installations. What may have been happening before is the previous installations you used before (linksys/netgear/m0n0 etc…) would boot up before your computer gave up trying to get an IP and assigned itself the 169 address. Once your machine gets that 169 address, it gives up trying to get an IP, thus you have to release/renew.

Maybe you can increase how long your PC tries to get an IP through a registry tweak if this concerns you. Otherwise turn the pfsense box on first, give it a 30 second head start and then turn the PC on. Or leave the pfsense box on 24/7 :-)

@scrotyballbags:

Thanks, this helps, but why does it only do this with PfSense?  The router I was using before would be ok when restarted while my PC was on…

I haven't been able to get it to work and I have been working on it the last few days. There is one person ermal who had created this post a while back http://forum.pfsense.org/index.php/topic,2718.180.html

I followed those instructions but was unsuccessful.

HI and thanks,

I foun another thread and a reply from you about my other problem
"HOSTAP mode not supported"

http://forum.pfsense.org/index.php/topic,31000.0.html

I will give this a try next week. thx

perfect, bandwidthd is ok now. thanks jimps.

today, after an update to 2.0-BETA5 (amd64) built on Fri Feb 18 05:19:03 EST 2011 the relus.debug is updated as expected… ???

@Brutal:

It also doesn't matter whether the hw.igb.num_queues is set for 2 or 4.

I suspect that it will matter if you have "enough" cores or "enough" cards.

Looks like the mbuf clusters.  What does that mean?  The system is currently connected to a 10/100 unmanaged switch (did it on a gig switch also) with 2 VoIP phones and 1 laptop.