16
17.7 Legacy Series / Re: [NOT-SOLVED,WTF!?] PPPOE Crash
« on: August 21, 2017, 10:00:07 pm »Ok, so we need to roll back on that patch and start asking the authors for help in solving this mystery.
The older kernel will work for 17.7 if you can install it:
# opnsense-update -ikr 17.1.9 -n "17.1\/sets"
# /usr/local/etc/rc.reboot
The working image is also ok to install. The kernels are the same and upgrades will work as soon as 17.7.1 is out.
Cheers,
Franco
Okay.. what are the next steps now?
Are you contacting the author?
Edit:
I could reproduce the problem on my main PC within a hyper-v VM running pfsense 17.7
I also captured the packages with wireshark if it could help futher identify the problem.
But this makes the problem hardware-independent, as my main pc has an intel nic, mobo from gigabyte
Edit2:
I did some research on the patch at https://reviews.freebsd.org/D9270 (as far as my knowledge is going...)-
It seems like it not only patched/added the host-uniq feature but also added some additional parsing for the PADM messages.
As i can see in ng_pppoe_rcvdata_ether(), the way how a NULL PADI tag gets treated changed dramatically, before they called
Code: [Select]
CTR1(KTR_NET, "%20s: PADI w/o Service-Name",__func__);
LEAVE(ENETUNREACH);
but now they just to some new indroduced
Code: [Select]
if (tag==NULL)tag=&sntag;
which i would assume to be the problem.