@stephenw10: It's not the same, you don't get some of the benefits of running Nano. Youc an choose to move /tmp and /var to ramdrives in the advanced options which gets you the limited writes. (mounting -noatime also  :-\ I'd have to check). Ahhh.. I thought there may be more to the nanobsd image. Is there some reason you need more space than the 4G Nano image gives you? Steve Not really, other than the feeling I am using the space I paid for :p.  Guess I will be using the nanobsd image. thanks.

Not necessarily. Do you have a complete list of specs? What exact images are you trying to load? What error is shown? (if any) Some quick Googling seems to show some issues with this model and *BSD. Some workarounds might be: disabling ACPI in the BIOS. Using the F12 boot media selection to specify the boot device which seems to pass more useful info to the OS. Steve

Where are you pinging from? Try pinging from the Diagnostics: Ping: page in the webgui. Try pinging from the pfSense console. Please give the exact error given if the ping fails. Are your public IP, gateway and DNS servers all in the same subnet? Steve

It should be supported by the iwn(4) driver in FreeBSD 10 but that means only in pfSense 2.2 alpha. It will not work in pfSense 2.1.4 (current). Edit: Looks like I was wrong, it will work to some extent in 2.1.4 but it's reported not to work in access point mode. Also the FreeBSD 10 man page reports only station and monitor mode so you could be out of luck if you want to use it as an access point. Steve

Just to add my experience Every fiber service switch I have ever connected to has required me to force the interface settings in pfsense.  The always connect half duplex and sometimes the wrong speed if I leave it to auto-negotiate.  Most likely the settings are 100baseTX / full duplex [image: 2014-07-14_171531.jpg] [image: 2014-07-14_171531.jpg_thumb]

Both vi and ee are available in the shell.

No. The EFM is on a fixed IP range. But yes, existing connection is PPPoE. Good idea on the config file,also on the opening a port. Thanks for the suggestions

As stated here: https://forum.pfsense.org/index.php?topic=78713.0 Issue is fixed. I just upgraded my Firebox from 2.1.3 -> 2.1.4, using auto-upgrade (gui-easy-way), and all is fine! Thanks for the fix guys! :)

That's caused by a hardware bug or failure. If the system works with other OSes (which may have software workarounds for hardware bugs where FreeBSD 8.3 does not in this case), then a BIOS upgrade is the best next step as it may fix it.

the CD isn't easy to modify, not really a practical option. CD+config on USB flash would work. The memstick image is more practical to mount, could potentially embed the config into a memstick load and then have only a single USB flash drive.

same over here :-) The problems seem to be fixed ^^

OK, I just tested it again. What works: Windows + Putty + Native serial port What doesn't: Windows + Hyperterminal + Native serial port Linux + gtkterm + USB converter This can cause quite some frustration for newcomers like me. Has the root cause ever been investigated ? In any case, thanks for your help and your work!

@stephenw10: I've been in situations where, following a power outage or equipment failure, I'm unable to access a device that would have been trivial had it had a fixed IP written on the outside of the device. I would always avoid fixed IPs for most devices though. When I hit that situation, I enable DHCP in pfSense (opening up a single DHCP pool) and let the device connect and find the DHCP address from there. Then disable DHCP once I get everything back to normal. I also like to set Servers and other Core devices to Static to avoid those types of Issues. A little more work but helps on hairy days!

Which peplink router? Why use another router at all? pfSense can probably do it all. Steve

Thanks!

That’s a very helpful diagnostic, and I will no longer suspect the Embedded edition! Given your input Phil, and now that I have an alternative pfSense appliance at my client site, I am going to completely re-install pfSense on my first device to see if the PPPoE problem is magically fixed by a fresh re-install.  I anticipate that a re-install will not fix the problem, but I want to put a nail in that coffin because it may be suggested or requested by a pfSense developer. Out of curiosity Phil, what is the make of the WAN interface on your problematic unit (e.g., Intel, Broadcom, etc.)?  I may be overlooking this information in your PPP log.

Rebooted modem, everything seems to be working now.