Congrats. Looks like I forgot to warn you about leaving only and only the installation HDD hooked up to the surrogate computer.  Otherwise, the boot time options will try and find the previous mounting point (non-ad0) when you transfer it.

well i had to punch in the dns servers by hand now its been up and running for 2 days

Well I know it can run on a PIII but this IBM server already required a number of manual modifications to make it work so my worry is it will be even worse on 2.0 Just because an old version worked on something does not mean it will on a new on. At some point all things hit EOL and they dont make drivers for or write the software to talk to it properly. I am in hopes someone with the exact model (x330) can confirm it works ehe. This is a critical box but I really would like to upgrade the firewall.

It's an unsupported controller. Trying to talk Dell into swapping it out for a supported one.

Everything looks okay. What about option under Advanced? Some new stuff you can disable. The webgui rule dont work and I have compared against one rule that works and it looks fine. So why dont it work?

@dreamslacker: Try Ebay.  You are probably stuck on getting a Single GBe NIC and having to use VLANs with an appropriate switch. The RB250GS is a good choice for the switch.  Check in on Lowyat forums to find out more details on the configuration since a lot of TM UniFi users use it for connecting their own routers along with the IPTV STB. For the NIC, I'd recommend getting the Intel PT Gigabit adapter. True indeed, maybe i rather get this RB250GS switch and run it ADSL-> Pfsense -> RB250GS ->  Workstations/ laptop  , but how about connecting through wifi such as iphone /Acryan ?

Nice one.  :) You should be aware, however, that even after disabling swap you will still be waring out your usb stick pretty quickly. You should really be using either embedded or Nano, that would restrict which packages you can use though. Steve

Hello everyone I returned to report that I had a small evolution in my problem but is not complete The solution would be a dirty at the time of mountroot> I apply the command msdosfs: ​​da0s1 to automate or do I insert the file loarder.conf set vfs.root.mountfrom=msdosfs:da0s1 set vfs.root.mountfrom.options=rw An important detail and make the iso image extracted at the root of the pendrive This will load normally but still a problem occurs later on Trying to mount root from msdosfs:ad0s1a ___ ___/ f \ / p ___/ Sense _/      _/ Welcome to pfSense 2.0 RC1  … Mounting filesystems... done. Creating symlinks......done. Launching the init system... At this point it freezes completely stopped what can be done?

This topic is old.  However folks seeing problems should check this document out: http://doc.pfsense.org/index.php/Boot_Troubleshooting

@stephenw10: @Sleeps: However the wireless is still working as an access point (Even though it's in bridge mode) That's weird. Can you actually connect to it? The wireless chipset in the modem will probably continue to operate with whatever values it was last given but it shouldn't send any packets anywhere. If you power up a separate wireless access point without connecting it to a wired network you can still connect to it but obviously it doesn't actually do anything. You could probably set you CM back to router mode, disable the wireless part and then set it back to bridge mode. Steve Yes it's possible to connect,even though I removed the antenna i can still see the wireless connection (secured) in the Wireless utility.  I tried resetting the router to go back to router mode and it's not possible - not a problem. Sleeps

Thanks Jimp, It just happen that the re-installation is not done yet when I checked the snort and squid status. So it's all good now.

pfSense has a squid package which can be installed after you have the base system installed.

You can restore a full 1.2.3 config onto 2.0, sure.

In web GUI: Interfaces -> (assign) click on Bridges tab, click on "+" to add a bridge, select the interfaces you want, etc etc.

Then something on 10.0.0.20 isn't responding. It could be any number of things: 10.0.0.20 doesn't use the pfSense box as its gateway 10.0.0.20 is dropping the traffic (local firewall?) 10.0.0.20 isn't configured to allow resolving DNS for 127.16.4.6 so the query is dropped 10.0.0.20 is sending the traffic back by some other path (check its routing table) etc, etc, etc.

That's usually the best procedure, upgrade the secondary, try it out for a bit, and then upgrade the primary if it went well.