As a follow-up, I changed the plain <Realm> clause to <Realm DEFAULT> and
it now works. I was able to reproduce it by dialing in with
[EMAIL PROTECTED] (not a real realm) and it froze. However when I make the
above change and dial in again I just get a no such user but it doesn't
bomb out.
I guess I have to have a <Realm DEFAULT> clause after all. I probably
missed it in the manual, so apologies to all.
Steve
------------------------------------------------------
Steve Suehring
Voyager.net Network Operations Systems Engineer
------------------------------------------------------
---------- Forwarded message ----------
Date: Wed, 29 Dec 1999 22:30:04 -0600 (CST)
From: Steve Suehring <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Ouch, server died
Hello-
I don't think I broke it. :)
We've got a rather simple configuration going, just one realm = xxx.net
and a <Realm> clause for people without the @xxx.net realm
attached. Should I also have a Realm DEFAULT too?
Tonight someone decided to dial up with the Internet Connection Wizard
from Microsoft. This killed the server apparently.
Here's some of the info. Mike or Hugh, I can send the hex from the packet
to you as well if you'd like.
Steve
*** Received from xxx.xxx.xxx.xxx port xxxx ....
Code: Access-Request
Identifier: 117
Authentic: ~<8>wp<172>c<164><15><182>SB" T<219><25>
Attributes:
User-Name = "[EMAIL PROTECTED]"
User-Password =
"<189><230><165>lC<127>E<127><11><189><129>z<251><170><2
36>%"
NAS-IP-Address = xxx.xxx.xxx.xxx
NAS-Port = 1541
Acct-Session-Id = "100930874"
Wed Dec 29 21:38:07 1999: DEBUG: Check if Handler Realm=voyager.net should
be used to handle this request
Wed Dec 29 21:38:18 1999: INFO: Server started
------------------------------------------------------
Steve Suehring
Voyager.net Network Operations Systems Engineer
------------------------------------------------------
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
