Also sprach Veda Narayan
Quoting Jeff Mcadams <jeffm@iglou.com>:
Uhm, yes it does know the username...he did a mon user with the username to get the log, and IPCP occurs after PAP, (you can see the PAP auth ack in the log), so the Arc does indeed know the userid if the drop occured at the time that the ppp log shows.
Nope - It still does not know the user name - the arc uses message passing. So each module has to send the info to the other module to let PPP module to know the user name. CIP tells PPP module about the call, PPP module starts LCP and then informs the radius/user module - this is where the authentication takes place, then radius/user module tells IP about the call to complete IPCP, if the call fails at that point IP does not say call complete - so radius/user will not tell PPP that there is a particular user tried to login. If the IP was nacked or rejected or even if IPCP had taken place for some time before the LCP reject being received - yes then the user name know.
Wow...not sure how you know so much about the internals of the Arc code, but that's impressive. Regardless though, sounds like a bug to me. The *Arc* does know the username...it has already completed PAP...though it might be in the wrong module of the Arc code. In my opinion, if PAP returns with an authentication OK, then the Arc should use that username in whatever logs from that point on. The user may not be authorized to do IP, or the peer may refuse IP, but they are authenticated, so the Arc does know what the userid is and *should* include it in any logs to help diagnose what the problem is. On an only tangentially related note... Anyone know what the deal is with the news server on totalservice? It seems to have been refusing connections for over a day now. Given the shoot-themselves-in-the-foot-concerning-customer-service-what-else-is-new decision by 3Com to forbid participation in this list of techies and others within 3Com (yes, I did confirm this to be the case, to my satisfaction at least), and the totalservice news server software not accepting connections, and continued incredible lameness concerning software contracts; 3Com seems to be actively shutting down every possible avenue of customer support. I guess 3Com really doesn't want customers after all. *sigh* -- Jeff McAdams Email: jeffm@iglou.com Head Network Administrator Voice: (502) 966-3848 IgLou Internet Services (800) 436-4456 - To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.