[SOLVED][Fix included in 17.7.1] PPPOE Crash

Started by jwe, August 10, 2017, 02:13:23 AM

Previous topic - Next topic
Quote from: franco on August 24, 2017, 08:37:45 AM
In the provider field, simply fill with "ac4.nue3\", the trailing backslash is important. The Host-Uniq field must be empty.

I dont have the provider field in my web-interface. Is there an option to make it visible?
(Looked in Interfaces/Point-to-Point/Devices(Interface type=pppoe))

Quote from: alexdupre on August 24, 2017, 08:42:20 AM
Since blocking one AC seems to have fixed the issue, it'd be interesting to see if blocking the another one produces the same result.

It seems like the 2nd AC is only showing up after the session to the first AC is established.
This might be because the original router from my ISP is building a second pppoe session for voice and i assume that the second AC is for the voice connection. So i cant test using only the second AC as it is not responding to my PADI. It sends its PADO always about 1 second after the session with AC(1) is established.

I'll have the new test image up and running this evening... The check that Alex proposed seems to be a very likely fix so you don't necessarily have to try something else for the moment. :)

FWIW, the "provider" input field is under your [WAN] interface configuration, oddly enough not under the PPPoE device itself. I've been meaning to hollow out the device settings so that only the bare minimum is there and everything else can be configured from the interface configuration itself.


Cheers,
Franco


Quote from: franco on August 26, 2017, 10:05:40 AM
The new image is here:

https://pkg.opnsense.org/snapshots/OPNsense-17.7-test3-OpenSSL-vga-amd64.img.bz2


Cheers,
Franco

Hi Franco,

this seems to work, but as i did not always see the other AC,
and i cant load the img into my hyper-v to watch network traffic via wireshark, it would be nice if someone else can confirm this work.

Or - if you have some time for it- you could create the test image as an iso...

Hyper-v really sucks not beeing able to load img's :(

I'd be happy to test it, too. But I need a serial image for my apu2.


Works great for me!  :D Thanks guys!

For everybody else stumbling upon this (and google):
My apu2 was stuck in a bootloop (rebooting after configuring interfaces).
When I unplugged the pppoe cable it booted fine but re-plugging it caused the whole system to crash.
I've done this with `tail -f /var/log/syslog` where I just found a "kernel panic 12" hexdump.

The test3 image fixed it.

Hi,

I confirm that everything is working fine here with the test3 image. Thanks guys!!


Regards,

Thanks for testing. I'll update the patch and push for merging it in standard FreeBSD installation.

Otherwise confirmed as well, thanks again to everyone for the help in tracking this down and Alex for the quick fix.

This will be in 17.7.1 this week. :)


Cheers,
Franco

Very nice!

Thanks for all the help, patches and images.


jwe, will you mark it solved? Thanks!



Updating from 17.1 still wants to go to 17.7 first. Is this fix included in 17.7? If not, then the firewall will crash and will not be able to update. How to work around this so that 17.1 machines can be updated?