Thanks Tom for the answer earlier, that did the trick.
On another topic, I'm not sure if all my AddToReply messages are
going out to the remote client. Here is what I have setup:
AddToReply Idle-Timeout = "1200"
AddToReply Session-Timeout = "28800"
AddToReply Framed-Compression = "Van-Jacobson-TCP-IP"
AddToReply Framed-MTU = 1500
AddToReply Framed-Routing = None
AddToReply Framed-Netmask = 255.255.255.255
And here is what the trace output shows:
*** Sending to xxx.xxx.xxx.xxx port 50218 ....
Code: Access-Accept
Identifier: 143
Authentic: <252><217>l]-<230><d@`:<26><254><217><132><3>
Attributes:
User-Service = 2
Framed-Protocol = 1
Framed-Netmask = 255.255.255.255
Do you think they are going out, but not showing up or are they not
being sent? I can't see them on the remote end since that is not
my server.
The logins are working, but these are the attributes that were
requested by the remote end. They run a managed modem pool
for us.
Thanks,
John Kicklighter
Internet 2xtreme
Date sent: Wed, 9 Jun 1999 13:14:36 +1000
From: tom minchin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Copies to: [EMAIL PROTECTED]
Subject: Re: (RADIATOR) RewriteUserName help needed
> On Tue, Jun 08, 1999 at 07:37:36PM -0700, [EMAIL PROTECTED] wrote:
> > Another issue with adding realm names at the end of each
> > username with the <Client> clause, multiple logins cannot be
> > enforced between POPs since each POP has it's own realm name.
> > If the same username logs attempts to login to the same POP
> > twice, that should work though. If I could strip off the realm name
> > before any <AuthBy> clauses in the realm, this would solve both
> > problems I believe. Since I'm not very good at regular expressions
> > in perl, can someone show me how to truncate a username based
> > on the '@' ?
> >
>
> There's an example in the manual: RewriteUsername s/^([^@]+).*/$1/
>
> [EMAIL PROTECTED]
>
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
