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?
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.
