With my cable provider it can take several hours to update changes and the connection becomes active again, just leave it connected and switched on overnight.
If its the mac address causing the problem you can enter the old mac on the WAN interface of pfsense box.

Yes, I reached the bootloader and was even able to use the menu option to reboot. But that's how far it went no pfsense unless the serial cable was not connected during the first 2/3 minutes, and also only on the 4801 box the 5501 had no problem at all.

Sorry for late reply - yes I adjusted fstab as specified. But, as you say - it appears that Seagate Microdrives have problems… However, would be very interesting to know what lies behind this mystery...

doesent it say after hd install

admin
pfsense
if i recall correct ;)

So that would be a 'yes'.

It just looked odd to me, just wanted to make sure it wasn't something weird.

Yep, we're about to release 1.2.2 to address this and 3 other items.

Thanks all for your help, I bit the bullet and got a USB to serial cable.

I had to downgrade (re-flash) to 1.2.0 to have a system that was accessible. Is their any word on a fix for this? The pfSense is installed on a Dell GX240 system. I've had the 1.2.0 version installed for about 10 months now with no troubles and I'm happy with it however I like to have up to date software installed.

I'm not sure what you mean. I am using a USB->RS232 adapter because my Thinkpad does not have a serial interface. It seems to work without problems with a single Intel NIC, but not with the dual one.

I have verified that the card itself is okay. I even exchanged it for another Intel dual NIC with a different PCI bridge chip, but that didn't work either. My guess is that the Neoware BIOS is crap and does not set up the IRQs properly or something.

It's annoying because otherwise the Neoware might be an excellent and very cheap router, if only it wasn't held back by the on-board Realtek NIC.

If you can get your hands on a CF-card with wearleveling this would work too.
But cards with wearleveling are a bit more expensive than normal cards.

Also i think some of the ALIX boards have a connector to connect a 2.5" HD.

The default image is too small to autoupgrade and will run out of space during the upgrade process.

The only way I've found to upgrade an embedded install is to reflash. A console upgrade may work if your image has been expanded to something larger than the default 128MB.

Hi,
you are right because mpd.conf done by 1.2.0, 1.2.1 and 2.0 are the same for my configuration, but only in 1.2.1 mpd kill connection with options i had reported.
All my installation are fresh in the same hardware with only a first configuration of wan to try this problem (also i try to update 1.2.0 but is the same).
I think mpd in 1.2.1 have something different from other and i'm sure that, without:

set ipcp ranges 0.0.0.0/0 0.0.0.0/0
        set ipcp enable req-pri-dns
        set ipcp enable req-sec-dns

my adsl with 1.2.1 works.
Is also sure that:

set ipcp enable req-sec-dns

are useful if i don't allow my pfsense to overwrite dns with pppoe dns (general setup), and is sure that:

set ipcp ranges 0.0.0.0/0 0.0.0.0/0

return a:

[pppoe] IPCP: peer address cannot be zero

and then ipcp kill my connection.

Marco Chiavacci

@jahonix:

Nope, it IS upgradable.

Thank you, that's relief ;-)

Michael

Thank you very much that was it

thanks again

Okay I have successfully installed to a CF card using the hacom image, and it works well now :)

Thanks to Bao from hacom who really guided me with lots of suggestions.

It works! Thank you again jahonix.

Thanks