Check any port forwards you may have configured: http://doc.pfsense.org/index.php/Why_does_enabling_NAT_Reflection_break_web_surfing%3F

I seem to have isolated the problem to the UDMA settings of my CF. After looking arount in the web, I suspect that I must change something in the boot.conf to enable (or set) UDMA2 for this CF. The problem is .. how do i do something like that ?

It was actually McAfee personal firewall causing the issue. I thought I had it configured to accept incoming ICMP but somehow it got reset when I changed my LAN network configuration. I was looking for the root cause to be harder than it was. I guess that's what you get when trying to troubleshoot at 2:00am on a few hours sleep. I am a N00B when it comes to packet sniffing technologies. I love the features of PFSENSE so far. After reading I'm taking this dumb mistake to learn how to use tcpdump to analyse where my packets drop. I also ordered the "PFSENSE definitive guide" from Amazon. Should be coming in today. Hopefully it can help me understand how to securely setup my DMZ. Regards,

The console option to set the WAN IP is only on 2.0, but it's there now. May as well do pfctl -d/pfctl -e rather than involving the PHP shell, a lot less hoops to jump though for the same effect :-)

ok, rookie mistake…i got it. here is how it was setup before i tried to mess with pfsense internet------isp gateway------router(LAN-192.168.1.1 WAN-173.xxx.xxx.33)---------(wifi router in my office- 192.168.2.1) this is how it was setup once i decided to mess with pfsense internet------isp gateway------router(192.168.1.1 WAN-173.xxx.xxx.33)--------------WAN nic of pfsense 173.xxx.xxx.41 this is how it is connected now (i forgot about the first router) internet------isp gateway-------------------------WAN nic of pfsense 173.xxx.xxx.41 sometimes it is easy to miss the easy problems.

Hum…  ::) ...all packages are availables. Don't need full install... Next time I'll check before post... Sorry

Hello, I've just finish to copy an img to a CF (from Debian) no problems… dd if=pfSense-1.2.3-RELEASE-4g-nanobsd.img of=/dev/sdg 7827687+0 enregistrements lus 7827687+0 enregistrements écrits 4007775744 octets (4,0 GB) copiés, 3947,2 s, 1,0 MB/s

There aren't any automated conversion scripts out there, but usually it isn't that difficult to go through and convert by hand into the GUI. You can probably drop a lot of that length by proper use of aliases and such.

Any ideas?

A good chance is that there was a NIC duplex mismatch, which causes the packet errors you see and screws your perfomance to the wall.

When it's ready  :) Hopefully sometime before the end of the year. PPTP/GRE NAT issues are still there, I'm not sure if there is still a chance they'll be addressed or not.

thanks everyone for the input i will go ahead with the 1.2.3 until I'm more familiar with pfsence.

Thanks for reporting back. Bit of a trap that auto-detect and the firewire interfaces.