After getting the PM talking PPP for a Framed-User account, our next step is
making it dial back, which is how our ordinary Dialback-Login-User accounts
work for security reasons.
Observing point 11 of the 3.3.2b3 relase notes:
11.Support has been added for Dialback PPP users which were
authenticated using PAP or CHAP.
we assumed lack of this new support was the cause of our previous dialback
attempt, and loaded it into our PM. Results unchanged (symptoms after setup).
My test setup looks like this:
- A Radius entry like this:
# Cameron Simpson
xx1 Password = "xxxx"
User-Service-Type = Dialback-Framed-User,
Framed-Protocol = PPP,
Framed-Address = 255.255.255.254,
Framed-Netmask = 255.255.255.255,
Framed-Routing = None,
Framed-Compression = Van-Jacobsen-TCP-IP,
Framed-MTU = 1500,
Dialback-No = "0,xxx-xxxx"
xx2 Password = "xxxx"
User-Service-Type = Dialback-Login-User,
Login-Host = xxx,
Login-Service = Telnet,
Dialback-No = "0,xxx-xxxx"
- We're using PAP authentication, which worked fine for Framed-User
accounts. As you will see, we don't get to try it with Dialback-Framed
users.
Symptoms:
Dialing in to the xx2 account works fine - it prompts me for login and
password, says "Dialback Accepted", hangs up and rings me back, and I login
in again just fine.
Dialing in to the xx1 account isn't so smooth.
I dial in, get a prompt, give it xx1 and the password, it says "Dialback..."
(hmm, a textually different response) and hangs up, but it doesn't ring me
back.
Is there something obvious I'm missing in the setup? Something non-obvious?
- Cameron Simpson
cameron@research.canon.com.au, DoD#743
http://www.dap.csiro.au/~cameron/
-- Intel: only half of "intelligence". - David White <david@research.canon.com.au>