I'm really unsure then which IP is being used… The issue may be around the wireless adapter I'm using. It's a RNX-N600UBE using the RT3572 chipset plugged-in via USB. It's using the run driver which I load through the boot.conf file I'll disable it and see if the crashes still occur.

What VM software are you attempting to use? What host OS on the computer? What is your goal with this, just to use pfsense to protect and give VPN access to one computer? Are there other computers on the network?

There was a time during 2.1 development when the list showed all addresses (including really external ones) and at that time the Filter [All|Local|Remote] dropdown was added so the user could choose what to display. Then, for whatever reason in some forum discussion… the behaviour was changed back to displaying just local addresses. But I suspect that a "local address" is one on a directly-connected network. I am not familiar with the previous behaviour, but I guess it used to show entries for other bits of private address space that were behind another router on LAN, or across a VPN link or...? I think the ability to show all, regardless of being direct-connected, private intranet or public internet, then filter it, was good. I think it was the "rate" source/binary that has to be modified so it actually spits out all the data. Then the PHP can filter for display as selected by the user.

Then you may need pkg_add, but you would not touch or change anything in the GUI to add those.

It looks like that is actually a sysctl rather than a loader tunable, as such you should be able to add it to the table in System: Advanced: System Tunables: This will mean it gets added to the config file and will survive a firmware update. Steve

I have an ath0 WiFi running inside an Alix2D13 on 2.1-RELEASE at a remote site. It ran various 2.1-RCn and was updated remotely a few times and it has been working. The settings (with SSID and password changed) are in the attached. At that site the power goes off a lot, and it comes back [both power and WiFi :) ] Maybe that will give you some confidence? [image: WiFiA.png] [image: WiFiA.png_thumb] [image: WiFiB.png] [image: WiFiB.png_thumb] [image: WiFiC.png] [image: WiFiC.png_thumb] [image: WiFiD.png] [image: WiFiD.png_thumb]

Hmm… Trying to mount root from ufs:/dev/ad4s1a WARNING: / was not properly dismounted <118>Configuring crash dumps... <118>Using /dev/ad4s1b for dump device. <118>Mounting filesystems... WARNING: R/W mount of / denied.  Filesystem is not clean - run fsck <118>mount: <118>/dev/ad4s1a <118>: <118>Operation not permitted <118>** /dev/ad4s1a <118>** Last Mounted on / <118>** Root file system <118>** Phase 1 - Check Blocks and Sizes <118>PARTIALLY TRUNCATED INODE I=37000242 <118>SALVAGE? yes

Well, today I'm still having the same problem after the clean install and so I tried the sugested solutions withought luck. One thin I noticied is that when the wan interface falls the "Gateway Monitoring Daemon" also stops and could not be started, on the log it says "ALARM: WAN_PPPOE(192.168.153.1) *** down ***" then the problem is that the router can't bring up the wan after a failure. Wel I don't have the necesary knowledge to know what's happening so…..

Aah, very good question. That motherboard has the idiotic Marvell controller, which doesn't work even under windows. I don't know of the top of my head, which SATA ports I have used, but I would guess I connected the HDD to the SATA3 Marvell port… The following output perhaps confirms that? (mind you, I'm running in IDE mode at the moment) $ atacontrol list ATA channel 0:     Master:  ad0 <hitachi hts542580k9sa00="" bbbzc3hp="">SATA revision 1.x     Slave:      no device present ATA channel 1:     Master:      no device present     Slave:      no device present ATA channel 2:     Master: acd0 <tsstcorp cddvdw="" sh-222ab="" sb01="">SATA revision 1.x     Slave:      no device present ATA channel 3:     Master:      no device present     Slave:      no device present</tsstcorp></hitachi>

You just need to assign/configure the WAN, to be able to login in to the Web Interface from the WAN side, and finish the configuration… i have done this way to use a PCI-E Wlan  Card as LAN...

haha - Maybe.  You won't know until you have tried.  If it doesn't work with 2.1, it will be the first time it hasn't worked.  I've done it a number of times before. I'd say back up the settings and try it.  If it fails, THEN do the clean install and restore. If you want to go straight to clean install and restore, thats always good.

The config should be in <drive>:\conf\config.xml Make sure you let the system boot all the way to the menu and use 99 to install, don't press I at the first prompt.</drive>

Thanks alot, this fixed the issue For anyone else trying to manualy fix this issue and your favourite text editor is Notepad, make sure it is not using "Word Wrap" otherwise you wil have issues when copying the code back into Pfsense :)

I assume you mean it still says 'Booting OS….'? That's what you see if no lcd driver has loaded. If it's actually showing some other Watchguard related information it must still be running the Watchguard OS. After you have loaded the lcdproc-dev package you have to go the Services: LCDproc: page and select the driver, screen size and port. Then add some screens in the second page. Then lcdproc should start. Steve

No body reply so I will answer it myself. Lucky me Jim pick up the issue and fixed it Detailed here https://redmine.pfsense.org/issues/3225 It works. Confirmed! Great job Jim!

It must somehow have made an empty tag or similar entry. If you look in the config.xml you will see it, it may have to be manually edited out.

Yep, I do have a backup. Will do the clean install, thanks.

Thanks for your help….upgraded the firmware to .99H from .99 and that did the trick! Once past that I have a baud rate mismatch I needed to correct...the ALix board was set to 38400 while pfSense was set to 9600...Thanks again to all who responded