Hi,
This may be a little late response to this problem. But I just had the same
problem and I found a solution. And it wasn't easy to find it either.
The problem is:
Framed-Compression = Van-Jacobsen-TCP-IP,
It should be
Framed-Compression = Van-Jacobson-TCP-IP,
Note the JacobsOn and not JacobsEn. One character out of place!
The fun thing is that this only goes wrong with WindowsNT users. Win95 and
Win98 and others have no problem whatsoever. And the effect is that routing
and ping work but as soon as you connect to a port there isn't anything
comming back....cause the compression is screwed up.
Maybe it might be an idea for Open.com to add an item in the dictionary that
will allow for both the Jacobson and the Jocobsen versions?
Arjen Jansen
Glasshouse Business Network
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Hugh Irvine
> Sent: Friday, November 26, 1999 04:49
> To: Robert Page; Robert Page; [EMAIL PROTECTED]
> Subject: Re: (RADIATOR) Users Cannot Route After Connecting
>
>
>
> Hello Robert -
>
> On Fri, 26 Nov 1999, Robert Page wrote:
> > Greg,
> >
> > I am passing these values and users cannot go anywhere or
> authenticate. one
> > difference in the radius users file that works versus this
> exported one from
> > Plat is in the User-Service-Type attribute.
> >
> > Are you saying I do not need to pass these as a minimum?
> >
> > From Plat and Radiator via exported RADIUS users file:
> >
> > Port-Limit=1,
> > Framed-Protocol=PPP,
> > Framed-Address=255.255.255.254,
> > Framed-Netmask=255.255.255.0,
> > User-Service=Framed-User,
> > Framed-Routing=None,
> > Framed-Compression=Van-Jacobsen-TCP-IP,
> > Framed-MTU=1500,
> > Session-Timeout=21600,
> > Idle-Timeout=900
> >
> > From RADIUS users file that is currently working with
> Livingston 2.1 on
> > Linux:
> >
> > User-Service-Type = Framed-User,
> > Framed-Protocol = PPP,
> > Framed-Address = 255.255.255.254,
> > Framed-Netmask = 255.255.255.255,
> > Framed-Routing = None,
> > Framed-Compression = Van-Jacobsen-TCP-IP,
> > Framed-MTU = 1500
> > Session-Timeout = 21600,
> > Idle-Timeout = 900,
> > Port-Limit=1
> >
>
> This is likely to be your problem. The Radiator dictionary defines
> "Service-Type", not "User-Service" nor "User-Service-Type". This will
> definitely cause problems with the Cisco's, which always
> expect a valid
> "Service-Type" in the reply. Either change your user
> definitions to use
> "Service-Type" (preferred) or add the other definition(s) to
> your dictionary.
>
> hth
>
> Hugh
>
>
> --
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, TACACS+, PAM, external, etc etc on Unix, Win95/8,
> NT, Rhapsody
>
> ===
> Archive at http://www.thesite.com.au/~radiator/
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
