> On Saturday 10 March 2001 01:33, Kitabjian, Dave wrote:
> > I was reading the writeup on this interesting feature:
> >
> > "ServerHasBrokenPortNumbers
> >
> > "Some Radius servers (GRIC on NT in particular) exhibit broken
> > behaviour in that the reply does not come from the same UDP
> port that the
> > request was sent to! "
> >
> > We have a similar sounding problem, but from some of our
> Radius CLIENTS:
> >
> > Fri Mar 9 09:26:08 2001: DEBUG: Packet dump:
> > *** Received from 207.201.82.17 port 1646 ....
> > Code: Accounting-Request
> >
> > All (but one) of our NASes are reaching us on ports
> 1812/1813, and those
> > ports were always reflected in the "*** Received from..."
> lines in our
> > Debug 4 logfile. That was all with USR gear. Now that we've
> added Cisco
> > gear, they are often showing 1645/1646, like in the above
> logfile clipping
> > EVEN THOUGH they are actually communicating to Radiator on
> ports 1812/1813!
> >
> > Any idea what the reason for that is, and if it has
> anything to do with the
> > ServerHasBrokenPortNumbers issue?
> >
>
> You can do some experiments with radpwtst to see what port
> numbers it uses
> for its own end of its communications with Radiator (on my
> box its 1028).
"True, true" (if I can quote a popular Budweiser commercial.
> In theory a client can
> use any UDP
> port number it likes for its own end of the communication,
> and in fact it is
> rarely the same port number as the server end. ...
Oh...but isn't the logfile showing the SERVER's port rather than the
CLIENT's port? I guess I always assumed it was the server's port.
> Why do you say that the above is causing difficulty?
Just that, in the past, (I thought) I had used the:
*** Received from 207.201.82.17 port 1646 ....
entries in the logfile to confirm which NASes were communicating with me on
the new ports, so I could tell when it was safe to turn off the copy of
radiusd listening on the old ports, 1645/1646. But perhaps I was confused...
Dave
:)
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
