Hi, On Thu, 18 Aug 2011 13:11:19 +0200 Andre Keller <a...@list.ak.cx> wrote: > Am 18.08.2011 07:51, schrieb YASUOKA Masahiko: >> npppd supports `LNS' only and it supports `compulsory tunnel' (or >> `accept dialin'). So currently npppd can become `R3' on above picture >> but it can not become `R2'. >> >> To enable `accept-dialin' on npppd, please add below line to >> npppd.conf. >> >> l2tp.accept_dialin: true > > is there radius support for npppd? (looking in the sourcecode shows that > a least some radius parts are implemented)
Yes. Latest version of usr.sbin/npppd/HOWTO_PIPEX_NPPPD.txt includes sample setting of radius like below: # RADIUS authentication / accounting #auth.radius.realm_list: radius #auth.radius.realm.server.address: 127.0.0.1:1812 #auth.radius.realm.server.secret: hogehoge #auth.radius.realm.acct_server.address: 127.0.0.1:1813 #auth.radius.realm.acct_server.secret: hogehoge #realm.radius.concentrate: tun0 > If there is support can some documentation about usage be found anywhere? Not yet. The configuration part of `npppd' will be re-written with OpenBSD parse.y style. Then npppd.conf(7) will be provided after that. Thanks, --yasuoka
