@victorhooi: In this case, it is just a simple ADSL2+ modem - Billion 5200 SRD modem - it cost just $27 from MSY…lol. Sorry, last time I looked there didn't seem to be many "just" modems. Many of the cheap boxes advertised as modems seemed to be modem/routers. @victorhooi: I've just changed from pfSense 2.0.1 to pfSense 2.1-BETA0, so I might give it a shot under that. It's a shame there isn't more verbose logging on why exactly the connection is failing, apart from a "timeout"…hmm. Your other post on DHCP on the Hacom suggested to me there was a problem in the communication between the modem/router and Hacom. Perhaps if that has been cleared up with pfSense 2.1 you might find PPPoE on pfSense 2.1 works. @victorhooi: Is there any way to increase verbosity of logging somewhere? Or some other diagnostics I can run from pfSense, such as trying the PPPoE negotiation manually from the console? Or would a packet capture help somewhere? Not even sure how to do that under FreeBSD…lol? You can do a packet capture by running tcpdump in a shell session or from the web GUI: Diagnostics -> Packet Capture. Depending on what you are looking for, a packet capture on either the ppp interface (pppoe0) or the physical interface (em0?) or both might be useful. @victorhooi: What other setups are you guys using for working PPPoE? I have use the configuration described in http://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall so I can access the modem web server from my home network on the other side of the pfSense box. This has been occasionally useful for troubleshooting.

heya, The DHCP client in this case is a Billion 5200 ADSL2+ modem. In this case, I restarted pfSense, and it seemed to work, sort of. Sometimes it'd work fine. Otherwise, if I I started it up, and then plug in the DHCP-serving modem, the WebConfigurator would sometimes become unresponsive - and even the VGA console on the server wouldn't respond to keystrokes. Since I couldn't get in via the web interface, console, or SSH, I didn't really have a way to retrieve /var/log/system.log  ???. However, the pfSense server would still respond to pings. Anyhow, I've ended up trying out pfSense 2.1-BETA0, and that seems to work ok with DHCP. Cheers, Victor

heya, Turns out it was actually a bad DOM SATA module =(. I emailed Hacom, and they said they had a bad batch of 8GB DOM chips…sigh. I wish they'd said that earlier. Anyhow, they're sending out a 64GB SDD to replace it =) - I'm using a spare Intel SSD I had lying around until then. It was just a bit confusing getting those error messages, and it being linked to a missing HDD - it didn't seem the most intuitive leap...lol. But then, hey, I've probably just been spoilt by Ubuntu and Arch installers...haha. Thanks all for your help =). Cheers, Victor

reboot has solved the problem :) thanks for support

Thanks, Ill setup and take to location in a few hours for testing.  Ill let you know.

Under diagnostics -> Backup/Restore … click on backup config and save it wherever you like.

OpenNTPD is gone from 2.0.2 and 2.1. It's ntp.org's daemon now on both.

@GullMoli: I'm quite slow when it comes to linux and working around in the shell environment so I'm having some trouble with this. pfSense is based on FreeBSD which is very similar to Linux in some aspects and quite different in other aspects. @GullMoli: (I cant figure out how to edit that file, or even get to it :l) How you tried the pfSense GUI function Diagnostics -> Edit File?

Hello guys, I´m having the same issue to upgrade. The packages to be removed are the original ones? I mean the "1.2.3-relaese packages", because the "Installed packages" I have none. Thanks. Jorge Eston

What you are describing is like you seeing only one NIC.

Ehh. I was just hoping  ;). While that wasn't my biggest concern, I'm glad to hear that I'm able to make changes and still reboot the device(retaining those changes). I just got my ALIX in the mail today…unfortunately, dumb me left my null modem cable at work...and now I'm hungry so there's no way I'm going back tonight! THANKS for the info though!

From the trouble shooting link, the below is what cured my install! Thanks 8) Try using multiple partitions, one small one (~4GB) for / and another for /usr using the rest of the disk.

There are many ways to get in, even adding a rule on the CLI… http://doc.pfsense.org/index.php/I_locked_myself_out_of_the_WebGUI,_help!

@Alan87i: If I run the upgrade too the july 6 snap do you think it will work or die? You mean 2.0.1 RELEASE? Normally, backup your settings and then updgrade. Take a look on packages topic to see if there is any current issue with packages you use.

thanks for your reply