What would happen is, when certain users logged in, they'd be given an IP
address by the portmaster, that wasn't that address they ended up with.
Here's an example of one user...
User logs in using trumpet winsock, gets a line like this from the
portmaster:
"PPP Session Established from (206.72.196.25) to (206.72.196.56)"
Then the normal } } } { } PPP characters.
Normally trumpet would come back with MY IP ADDRESS IS, but in this case,
depending on which time you tried, it either DID NOT, or it would come
back with a different address that wasn't 56.
Our logs from the portmaster would show the user coming in on .41, and
saying "dest ppp03.berkshire.net" which is 206.72.196.41...
Show session on the portmaster would still come up as ppp03, even though
it originaly spit out 206.72.196.56 which points to another pppXX hostname.
We tried running radius with debug, and we watched as each user logged
in. It would start to assign the IP address, gripe about an "unknown
request type 61" send an ACK and then repeat a couple of steps before
finally accepting the user.
Hope this isn't too vague, the debug was going to screen and not a file,
so I don't have an exact copy.
-Jason
---
oooooo o o oo o o--o | Jason Hatch
oo o o oo oo o--o | System Administrator, B e r k s h i r e N e t
oo o o oo o o | email: zone@berkshire.net phone: (413) 442-7805
oooooo o o oo o o--o | You toucha my Sparc, I breaka you face.