@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.

First thank you for the prompt reply on this issue, here are the interface driver of em0 for both firewalls: [Release 1.2.3] sysctl dev.em.0.%desc dev.em.0.%desc: Intel(R) PRO/1000 Network Connection 6.9.6 [Release 2.0 RC1) sysctl dev.em.0.%desc dev.em.0.%desc: Intel(R) PRO/1000 Legacy Network Connection 1.0.3

Did you hook up a serial cable and use terminal? The embedded variant doesn't use a GUI on the machine itself.

I have the same issue moving from an old November build to RC-1 and an em interface.

Just download the ISO file, burn it and install it on a PC. It will probably just work. I've never ran pfSense on anything but normal PC's (and laptops). Here is the Hardware Compatibility List: http://www.pfsense.org/index.php?option=com_content&task=view&id=46&Itemid=51

There might be good reason that your system is using a 1GB image. For instance some newer "2GB" cards are not big enough to fit the 2gb image. Or it could be, like me, that who ever wrote the card couldn't be bothered to write a 2gb image since it takes so damn long over a usb 1 connection!  :P There's no real disadvantage to using a 1gb image and it's guaranteed to fit. Steve

@dds: Any other idea Howto install pfsense on soekris net4801? In theory the following should work (though I have no experience with that board): write the pfSense embedded (or nanoBSD) image to a compact flash of at least 1GB on another PC and then put the compact flash card in the CF slot on the motherboard and then boot. http://doc.pfsense.org/index.php/Installing_pfSense provides more details.

Thank you for help.l

I found a solution: /etc/rc.conf_mount_rw rm -fr perl5/ /etc/rc.conf_mount_ro It would be better if packages would uninstall cleanly. Kind regards,

Well, i will try without the traffic shaping features, when i do this i will post the solution, another thing there is the possibility for example of installing pfsense.. and then create a bootable cd that contains my preconfigured pfsense install??

Hi, Yes its true I didnt set up the original box ;) Yes its going to have static IP but I need it to take over the IPs the box in production has. So I need to set it up on a different IP initially so I can play around with it and "duplicate" the rules/settings/options. Once that is done Im planning to change the IPs to the production IPs and just neatly shut down the old box, jack in tp cables in the new box and start it up. :) Anywho. Your answers has given me enough information to go on and I think I can start messing around with this now. Thanks for the help!