What can I do to give more information ?

Maybe some info on the setup of the client's that can't connect also are the using the same ISP.
basically what do they have common.

Excellent.  Thank you very much for the reply. I'll give it a shot tomorrow. I didn't think it was anything I was doing wrong.

@keylevel:

I've installed 1.2.3-RC3 on an Alix 3D3 (updated 3C3) and have had exactly the same problem.

I found that selecting the "no acpi" boot allowed the system to boot.

I then set the power management mode in the BIOS to APM and then re-installed (not sure if that was needed, but I changed the install media as well). This also boots ok.

Confirmed ! This solves the issue, alix3c3 boots right up with BIOS power management set to APM.

(I'll test on the 1c1 and 1d1 later and confirm whether fix works on those boards as well)

Thanks !

You're welcome. Glad it was such an easy fix  8)

No idea, probably, if HUP entails rereading the config file.

100% cpu usage is due to device polling so disabled that and solved it

–edit--
one more finding:
if i disable traffic shaper everything works like a charm but with it enabled, doesnt

--edit--
if wireless is bridged to LAN and if u need to have traffic shaping rules for wireless then packet in interface to select will be WAN as usual but out interface needs to be LAN (due to wireless being bridged to LAN) or opt1 (wireless) ?

--edit--
above question is relevant if traffic shaping is possible on bridged interface

hmm https dont wanna work with RC1 kernel.gz =(

this is impossible.  packets are not going to magically go from the WAN to your PC unless pfsense was set up to send them there.  either these are faked, or there is some trojan running on your PC which is letting stuff in (maybe something else, but no idea right now.)  or maybe a hacked zombie pc on your LAN which is spoofing the packets?  easy way to tell is to run tcpdump on the wan interface of the pfsense and see if you see those packets coming in at all.

To be frank I also had a downtime a few days ago.
I was getting device timeout messages for a while and AP was gone.
After rebooting my wireless clients and playing a bit with the AP settings it was back on (there isn't something specific that fixed it though).
Like I said I run the official 1.2.3RC3.
On the plus side stuck beacons are much more rare now but this device timeout is causing the same issue so I am happy the devs returned to 7.2 driver as it was better in that respect :)
To sum it up I guess we should just wait for 2.0 with 8.0 and hope drivers are better there.

thanks alot that corrected the issue

I tohught i checked that box  ??? but i guess i didnt

HAPPY THANKSGIVING PFSENSE!!!

here is the screenshot

Untitleds.jpg
Untitleds.jpg_thumb

Nice one pre made image thanks :)

I was having problems getting FreeDOS to boot.

Thanks Covex.
I used to backup my configuration file, and restore it.
Now i installed pfsense nanobsd and configured it by hand, just like the 1.2 version.
Now it all works.

Thanks again

@Papa:

Then what possible problem am I having because I can assure you I would love to take IPsec over PPTP. I can connect just fine if I try it internally, but the moment I leave my network and attempt it from the LAN, it fails.

Probably not forwarding all the required protocols and ports. Which you require will differ depending on what you're forwarding to and how that device is configured.

Is there a workaround?

I'm installing an ALIX w/microdrive over Thanksgiving and I'd like to set it up with the full install.

EDIT – Just use the "simple" install.  The kernel installation screen shows up in that mode!

I updated that page. The information it had was very, very out of date.

I reported that bug back in January 2008 - it's on the old cvstrac system here.

I'm not sure that it's going to get fixed now, as unless I'm mistaken, all this code will be replaced by the new traffic shaper in 2.0.

Last I heard, we're just waiting on FreeBSD to drop a Security Advisory and issue a patch for a vulnerability (OpenSSL, I think.)