Hi guys, I want report about bug found:
incorrect AVP type 6,8... You can say stupid idiod why you didn't changed as you need Of course I did - after change from 0 to 1 my routers started works but ... (always exist this f@cking "but") all windows clients stopped So I clossed possibility to connect of 90% clients - not so good fo me. So question: what I can do threre ?
Kind regards
P.s. xl2tpd works with routers and windows clients at same time - so there no such type of issue ...
Incorrect AVP type 6,8
Re: Incorrect AVP type 6,8
use avp_permissive=1 in l2tp section
accel-ppp.conf
and info from accel wiki http://accel-ppp.org/wiki/doku.php?id=k ... ct_by_l2tp
accel-ppp.conf
Code: Select all
[l2tp]
avp_permissive=1
Look at logs, if you see something like
its because zyxel's client doesn't conform rfc:Code: Select all
[2012-01-18|09:16:02]: warn: l2tp: incorrect avp received (type=7, M=0, must be 1)
Anyway you can solve it by modifying accel-ppp's l2tp dictionary:Code: Select all
The Host Name AVP, Attribute Type 7, indicates the name of the issuing LAC or LNS. This name should be as broadly unique as possible; for hosts participating in DNS [RFC1034], a hostname with fully qualified domain would be appropriate. This AVP MUST NOT be hidden (the H-bit MUST be 0). The M-bit for this AVP MUST be set to 1. The Length of this AVP is 6 plus the length of the Host Name.
open install_prefix/share/accel-ppp/l2tp/dictionary.rfc2661
2. find line ATTRIBUTE Host-Name 7 string M=1 3. clear M=1 4. save file and restart accel-ppp If it still doesn't connect search the log for messages like warn: l2tp: incorrect avp received (type=7, M=0, must be 1), its maybe other attributes are incorrect too so you can modify l2tp dictionary for it.
Re: Incorrect AVP type 6,8
Thanks helped issue on f@cked missing mschap in my TP-LInk router!