Re: NAS Port always 0

Tom Murphy wrote: I put in some debugging code there to spit out the ifname and devname. For some reason, they are both blank. I'm using openl2tpd and that may Hmm be messing up the reporting of the ppp interface, but, my question is this: At the time the RADIUS authentication is being

Re: NAS Port always 0

Tom Murphy wrote: Hi, I'm using a linux box as the NAS. PPP connections come in and get fed to radiusclient which in turn contacts a FreeRADIUS 1.1.3 server. Some of the PPP connections are dynamic, most are static. I did set up ippool properly in FreeRADIUS, but it dishes out only 2 IP

Re: NAS Port always 0

Hi Phil, On 06/12/06, Phil Mayers wrote: Certainly if the NAS-Port isn't being set correctly, ippool won't work. Yeah it doesn't seem to like that the NAS-Port is always zero. Is there a way to tell the pppd-radius plugin, or, radiusclient to use a different NAS Port when it sends the

NAS Port always 0

Hi, I'm using a linux box as the NAS. PPP connections come in and get fed to radiusclient which in turn contacts a FreeRADIUS 1.1.3 server. Some of the PPP connections are dynamic, most are static. I did set up ippool properly in FreeRADIUS, but it dishes out only 2 IP addresses. Doing some

Re: NAS Port always 0

Tom Murphy wrote: Doing some searching around, I discovered this is because the Nas-Port is always 0 (as evidenced by the radius log files). So it will only send those two addresses out because it thinks the same user is logging on each time? Yes. Is there a way to tell the pppd-radius