Date: Thu, 10 Jan 2002 00:33:56 -0500 From: "Joe & Fhe Barbish" <barbish@a1poweruser.com> To: "Brian Somers" <brian@freebsd-services.com> Cc: "FBSD Questions" <questions@FreeBSD.ORG> Subject: RE: How to setup dialin to server and them callback orginal dialin caller Message-ID: <LPBBIGIAAKKEOEJOLEGOIEOPCLAA.barbish@a1poweruser.com> In-Reply-To: <200201100426.g0A4Q6S24964@hak.lan.Awfulhak.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian
OK so I leave every thing the way it is but change the incoming section like
this.
incoming:
allow users barbish bob
enable pap
accept dns
set ifaddr 10.0.0.1 10.0.0.74 255.255.255.255
set callback cbcp
set cbcp
set log +cbcp
set redial 3 1
set device /dev/cuaa2 /dev/cuaa1
set speed 115200
set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
\"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT"
Now I need to understand the flow of things.
When the win98 box calls the dialin modem on the FBSD box, getty senses &
answers the call, makes the connection, tells the winbox it wants pap and
asks for id/pw, whatever is entered is checked against ppp.secret, at a
match ppp sees the callback phone number and hangs up the phone. Now the
modem that just answered the inbound call is free to dial out using the
callback phone number from ppp.secert. On the winbox when FBSD hung up the
dial window jumped up and asked if the user wants to dial again. The user
should just close the dialer window. The modem on the winbox must already
have the ats=1 turned on for auto answer. FBSD does it's callback and the
modem on the winbox picks up. FBSD does not request pap logon again or
anything. The winbox is all ready logged on from the first call in. If this
is not how it works then please explain the correct flow of events.
Thanks
Joe
-----Original Message-----
From: owner-freebsd-questions@FreeBSD.ORG
[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Brian Somers
Sent: Wednesday, January 09, 2002 11:26 PM
To: Joe & Fhe Barbish
Cc: Brian Somers; FBSD Questions; brian@freebsd-services.com
Subject: Re: How to setup dialin to server and them callback orginal dialin
caller
> Brian
> I did like you said and ran a test. I dialed in ok like
> always but the callback did not happen. To get right to
> the point of making it function, you need to see what I
> have configured. To that ends I have included my ppp.conf
> and ppp.secret files with a ppp.log from my last test.
> Please give it a once over and see if you can identify
> what's wrong? Cuua2 is the dial in and callback device.
> My ppp.conf is heavyly commented for the jr people who work
> for me supporting this work enviroment.
>
> Thanks Joe
[.....]
> ppp.log of the test
>
> Jan 9 22:55:52 gateway ppp[378]: Phase: Using interface: tun0
> Jan 9 22:55:52 gateway ppp[378]: Phase: deflink: Created in closed state
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: default: set speed 115200
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: default: set timeout 0
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: default: disable pred1
> deflate lqr
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: default: deny pred1
deflate
> lqr
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: incoming: enable pap
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: incoming: accept dns
> Jan 9 22:55:52 gateway ppp[378]: tun0: Command: incoming: set ifaddr
> 10.0.0.1 10.0.0.74 255.255.255.255
[.....]
You're invoking ppp with the incoming profile rather than with the
callback-server profile. You should run
ppp -direct callback-server
from the ppplogin script.
The callback-server profile should also have a better ``set dial''
command - perhaps the one from your dialisp profile. The current set
dial will only wait 10 seconds for CONNECT.
The callback-server profile's first line is ``load''ing an
non-existent profile. I suspect it should say ``load incoming'' so
that it does things like ``allow users'' and ``set ifaddr'' etc.
[.....]
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: deflink: RecvConfigReq(2)
state
> = Req-Sent
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: ACCMAP[6] 0x000a0000
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: MAGICNUM[6] 0x0336d0d8
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: PROTOCOMP[2]
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: ACFCOMP[2]
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: CALLBACK[3] CBCP
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: deflink: SendConfigRej(2)
state
> = Req-Sent
> Jan 9 22:55:55 gateway ppp[378]: tun0: LCP: CALLBACK[3] CBCP
[.....]
This is the bit that goes wrong - ppp rejects the callback request
because it hasn't seen a ``set callback'' line....
Cheers.
--
Brian <brian@freebsd-services.com> <brian@Awfulhak.org>
http://www.freebsd-services.com/ <brian@[uk.]FreeBSD.org>
Don't _EVER_ lose your sense of humour ! <brian@[uk.]OpenBSD.org>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?LPBBIGIAAKKEOEJOLEGOIEOPCLAA.barbish>