Signal 10

[Doug Hardie]

On Dec 9, 2005, at 00:00, Doug Hardie wrote:

> Well, it finally happened again.  This is the packet with the same  
> timestamp as the signal 10 message.  There is no response to it.  I  
> haven't decoded it completely yet, but it appears that the user id  
> is corrupt.  I wonder if something in that field is causing the  
> problem.  I was able to identify the user from the phone number and  
> that user did successfully connect about 6 times earlier today so I  
> don't think its a configuration issue but most likely a line issue  
> (dial-in) causing corruption of the user-id.  The NAS is Ascend and  
> I would have thought it would catch that and not forward junk at us.

Found the problem.  There are several NULLs in that user id.  My  
reading of the RFCs led me to believe there could not be NULLs in  
that field.  Hence I never allowed for that in one of my rlm's.   
Don't understand the signal 10 though.  Normally that kind of problem  
generates a signal 11.