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.

Thanks. Looking for the info in the wrong place… I will scribble that link into my pfsense book for when I forget about it next time.  ::)

@stephenw10: This looks to have been fixed this morning. The updaters URL now contains the correct images.  :) Yes, the images should all be OK now. cmb made some changes and put the correct images in place.

Issue has been resolved: https://github.com/pfsense/pfsense/commit/7b15d22967a9f9fefe7b8b11fa2d68c762c55219 Applied it via System Patches and rebooted, problem gone. Thanks to the pfSense team!

Thank you Jimp

The RoadWarrior connections will, but the site-site connections absolutely need it to be able to complete their connections. Note that I'm assuming (what a terrible thing to do  ::) ) that the site-site conx's are all pfSense based clients, manually configured.  The RoadWarriors are installed via the appropriate Client Export Utility entry. With those caveats, I believe everything I've stated to this point describes the operation of OpenVPN under pfSense (I'm certainly willing to be proven wrong of course).  ;)

@dgcom: I perfectly understand implications of this particular issue, and yes - it is not just a matter of replacing openssl executable… What I am saying is that recompiling everything is not very efficient. But, I guess, you know your product :) … @dgcom: shouldn't build system be smart enough to recompile only if dependencies changed? the build system is, but the system is packaged in a way that is a forklift upgrade on every update. We're exploring ways to update differently (such that updates are more like freebsd-update), but even here there are impacts that you might not imagine. PBIs are dead after 2.2, btw. @dgcom: I, personally, do not run anything, based on recent versions of openssl - except pfSense. this is probably mistake at this point.

Thanks Jason