2.0 might be generally safe to use in that situation, but the only way to know would be to test it out for yourself.
1.2.3 would be the right thing to do for most production networks right now though.
You can upgrade from 1.2.3 to 2.0 when it's released, there shouldn't be any upgrade issues when it's released.
Some time ago I bought a number of USB adapters for note book drives. Some worked with FreeBSD and some didn't. I discovered in the FreeBSD sources there was a table for USB devices with "quirks" and code work arounds for the quirks. The devices that worked used a different chip than the devices that didn't and there was no "quirk" entry for either device.
Suggestion: You try to read the whole external hard drive on a "bare metal" FreeBSD system by a command like```
dd if=/dev/da2 of=/dev/null bs=65536
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.
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.
