From owner-freebsd-questions Tue Aug 1 5:57:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from goblin.apana.org.au (goblin.apana.org.au [203.3.126.3]) by hub.freebsd.org (Postfix) with ESMTP id E659037B6F7 for ; Tue, 1 Aug 2000 05:56:54 -0700 (PDT) (envelope-from dougy@gargoyle.apana.org.au) Received: (from uucp@localhost) by goblin.apana.org.au (8.8.8/8.8.8) id WAA15394; Tue, 1 Aug 2000 22:31:20 +1000 (EST) (envelope-from dougy@gargoyle.apana.org.au) Received: from dougy.apana.org.au(203.3.126.131), claiming to be "DOUGY" via SMTP by goblin.apana.org.au, id smtpdK15392; Tue Aug 1 22:31:01 2000 Message-ID: <000801bffbb4$e3117380$837e03cb@DOUGY> From: "Doug Young" To: "Alexander Derevyanko" Cc: References: <005701bffaf0$eb23a4e0$837e03cb@DOUGY> <3985A720.D6B9FAC7@pc759.cs.msu.su> Subject: Re: FreeBSD to FreeBSD dialin configuration Date: Tue, 1 Aug 2000 22:34:49 +1000 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0004_01BFFC08.B37E25B0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0004_01BFFC08.B37E25B0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0005_01BFFC08.B37E25B0" ------=_NextPart_001_0005_01BFFC08.B37E25B0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable So, please, increase debug level on both sides of you links (not on = mgetty only, but=20 on ppp and pppd), connect once, and send to the maillist complete = debug logs and you=20 configuration files (passwords excluded).=20 Read the logs first, it can be very odd problem.=20 I've attached the mgetty.config, ppp.log & mgetty.cuaa1 log files from = the "server" ..... don't know how to debug ppp or pppd. The dialout = system is running user-ppp and I think the dialin server is running = pppd, although I'm far from certain that its configured properly. I'd = prefer to have user-ppp both ends, however such explanations as exist = about both are far from explicit.=20 =20 =20 ------=_NextPart_001_0005_01BFFC08.B37E25B0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

So, please, increase debug level on both sides of you links (not on = mgetty=20 only, but
on ppp and pppd), connect once, and send to the maillist = complete debug logs and you
configuration files (passwords = excluded).=20
Read the logs first, it can be very odd problem.=20

I've attached the mgetty.config, = ppp.log &=20 mgetty.cuaa1 log files from the "server" ..... don't know how to debug = ppp or=20 pppd. The dialout system is running user-ppp and I think the = dialin=20 server is running pppd, although I'm far from certain that its = configured=20 properly. I'd prefer to have user-ppp both ends, however such=20 explanations as exist about both are far from explicit.

------=_NextPart_001_0005_01BFFC08.B37E25B0-- ------=_NextPart_000_0004_01BFFC08.B37E25B0 Content-Type: application/octet-stream; name="mgetty.cuaa1" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="mgetty.cuaa1" 01/21 22:09:40 aa1 mgetty: experimental test release 1.1.21-Jul24 01/21 22:09:40 aa1 check for lockfiles 01/21 22:09:40 aa1 checklock: stat failed, no file 01/21 22:09:40 aa1 locking the line 01/21 22:09:40 aa1 makelock(cuaa1) called 01/21 22:09:40 aa1 do_makelock: lock='/var/spool/lock/LCK..cuaa1' 01/21 22:09:40 aa1 lock made 01/21 22:09:41 aa1 tio_get_rs232_lines: status: RTS CTS DSR DTR 01/21 22:09:41 aa1 lowering DTR to reset Modem 01/21 22:09:41 aa1 tss: set speed to 38400 (113000) 01/21 22:09:41 aa1 tio_set_flow_control( HARD ) 01/21 22:09:41 aa1 waiting for line to clear (VTIME), read: 01/21 22:09:41 aa1 send: A 01/21 22:09:41 aa1 select returned 1 01/21 22:09:41 aa1 checking lockfiles, locking the line 01/21 22:09:41 aa1 makelock(cuaa1) called 01/21 22:09:41 aa1 do_makelock: lock='/var/spool/lock/LCK..cuaa1' 01/21 22:09:41 aa1 lock not made: lock file exists (pid=1242) 01/21 22:09:41 aa1 lock file exists (dialout)! 01/21 22:09:41 aa1 lockfile found, pid=1242 01/21 22:09:41 aa1 utmp + wtmp entry made 01/21 22:09:41 aa1 lockfile found, pid=1242TS0=0Q0&D3&C1[0d] 01/21 22:09:41 aa1 waiting for ``OK'' 01/21 22:09:41 aa1 got: ATS0=0Q0&D3&C1[0d] 01/21 22:09:41 aa1 CND: ATS0=0Q0&D3&C1[0d][0a]OK ** found ** 01/21 22:09:42 aa1 waiting for line to clear (VTIME), read: [0d][0a] 01/21 22:09:43 aa1 removing lock file 01/21 22:09:43 aa1 waiting... ------=_NextPart_000_0004_01BFFC08.B37E25B0 Content-Type: application/octet-stream; name="mgetty.config" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="mgetty.config" =0A= =0A= # *** Configuring for port cuaa1 ***=0A= =0A= =0A= # - `debug (mgetty)' =0A= # This sets the amount of logging `mgetty' will do. A good value is=0A= # 4, more details are seen with `5', and `9' is really noisy. Try=0A= # it! The log data is written to the file `/tmp/log_mg.cuaxx'.: [4] =0A= # - `fax-id'=0A= # This sets the fax station ID used in fax mode to identify your=0A= # site to the caller (usually this is simply your fax phone number).=0A= # : [00 00 000000] =0A= # - `speed'=0A= # Specify, as integer value, the port speed to use. Default is=0A= # 38400. If the given speed is not valid, `mgetty' complains loudly =0A= # and exits.: [38400] =0A= # - `switchbd'=0A= # Some modems, mainly Rockwell chipsets, switch to 19200 bps when=0A= # entering fax mode. Others may need other speed switches (but I=0A= # know none). If your modem is Rockwell based, try `switchbd 19200'=0A= # if fax reception doesn't work. (*Warning:* if this is set wrongly,=0A= # fax reception will definitely fail. For most sane modems, you do=0A= # *not need* this.). Set speed or `0': =0A= # - `direct' =0A= # Tells mgetty that it is running on a direct line. Mgetty won't try=0A= # to initialize any modem, nor will it wait for `RING'. It will just=0A= # wait for any character, and then output the issue file and login=0A= # prompt. This option is used if you want to connect to machines via=0A= # nullmodem cable.: [NO] =0A= # - `blocking' =0A= # Tells mgetty to open the device in `blocking' mode, that is, the=0A= # `open()' system call won't succeed until carrier detect is set.=0A= # This is set if `mgetty' is called as `getty'. I'm not sure whether=0A= # it's very useful, but I include it for completeness: [NO] =0A= # - `port-owner'=0A= # If set, mgetty will `chown' the tty line to the given username (you=0A= # can specify a string or an integer uid, but the integer must be=0A= # valid). This is highly recommended for security purposes: only=0A= # give port access to those users you trust not to misuse your modem=0A= # lines!: [uucp] =0A= # - `port-group' =0A= # If set, mgetty will `chgrp' the tty line to this group id (which=0A= # can be given as group name, or as integer gid). If it's not given,=0A= # or not valid, the primary group id of `port-owner' =0A= # will be used.: [uucp] =0A= # - `port-mode'=0A= # Specifies the permissions to `chmod' the device to. =0A= # *Never* make a modem device world-accessible, better use `0660'=0A= # or even `0600'.: [0660] =0A= # - `toggle-dtr'=0A= # Tells mgetty whether it should lower the DTR line upon startup to=0A= # reset modem. Default is `yes', but some (few) modems react=0A= # allergic to that and crash.: [YES] =0A= # - `toggle-dtr-waittime'=0A= # Specifies the time (in ms) to hold the DTR line low.: [500] =0A= # - `data-only'=0A= # Tells `mgetty' to forget about faxing and only use the data part of=0A= # the modem. Default is `false'. You need this if your modem can't=0A= # distinguish incoming fax and data calls.: [NO] =0A= # - `fax-only'=0A= # Tells `mgetty' to put the modem in fax-only mode. You need this if=0A= # your modem can't distinguish incoming fax and data calls, but you=0A= # need fax more important than data; and you need it if you want to=0A= # disable data calls for security reasons (this could be achieved=0A= # via `login.config' as well): [NO] =0A= # - `modem-type'=0A= # Specifies the kind of modem connected to the port. Valid options = are:=0A= # * auto=0A= # Mgetty will detect the modem type itself (which may = occasionally=0A= # be not desirable, or it may fail on old modem equipment).=0A= # * c2.0=0A= # Modem is a CLASS 2.0 fax mode. Works better than class 2, if=0A= # both are available, because its better standardized. Known to=0A= # work with USR and ZyXEL.=0A= # * cls2=0A= # Modem is a CLASS 2 fax modem, mgetty will not try class 2.0.=0A= # * data=0A= # Do not try fax initialization=0A= # There is no way (yet) to tell mgetty to use *only* fax mode and=0A= # refuse data calls with this option, use the `fax-only true'=0A= # statement for that.: [auto] =0A= # - `init-chat' =0A= # Tells mgetty the chat sequence to use for initializing the modem.=0A= # *Warning*: the sequence starts with *expect*, which will in most=0A= # cases be `""' (nothing). This ordering was chosen because UUCP=0A= # does it this way, and I wanted to avoid confusion here.=0A= #=0A= # Example:=0A= #=0A= # "" \d\d\d+++\d\d\dATQ0E1V1H0 OK ATL0M0S0=3D0 OK AT&K3 OK=0A= # init sequence: ["" ATS0=3D0Q0&D3&C1 OK] =0A= # - `force-init-chat'=0A= # In some cases, the modem can get stuck in a mode where it won't=0A= # react to a simple `AT' command. Usually this happens because the=0A= # modem is set to ignore a DTR drop and still has a data connection=0A= # to the other side. If you use a voice modem, it could be stuck in=0A= # voice mode.=0A= =0A= # In these situations, the normal `init-chat' will time out, because=0A= # the modem won't send the proper responses back.=0A= =0A= # To get the modem back into a sane state, you can use the=0A= # `force-init-chat' chat sequence. The default setup will send the=0A= # DLE ETX characters, to get voice modems back to life, and then the=0A= # `(pause)+++(pause)ATH0' sequence to get the modem back from data=0A= # mode to command mode.=0A= =0A= # You could prepend this sequence to `init-chat' (it wouldn't harm),=0A= # but especially the pauses around the +++ sequence makes this=0A= # undesirable slow.: =0A= # - `modem-check-time'=0A= # Some modems have the nasty tendency to crash silently. With this=0A= # option, you tell `mgetty' to check every SECONDS seconds with a=0A= # simple `AT...OK' sequence whether the modem still reacts. If not,=0A= # `mgetty' will restart itself and do a full modem reset.: [3600] =0A= # - `rings' =0A= # Sets the number of `RING' messages to wait for, before mgetty=0A= # picks up the phone. *Warning:* if your modem auto-answers, for =0A= # whatever reason, set this to something *different* than the =0A= # value set with `ATS0=3Dmmm', otherwise the modems autoanswer and =0A= # mgettys manual answer will collide (most modems hang up if a =0A= # command is received during auto-answer): [1] =0A= # - `answer-chat'=0A= # This is the command sequence that is used to answer a phone call.=0A= # Usually you can leave it at the default ` "" ATA CONNECT \c \r ',=0A= # but for some modems you need `ATS0=3D1' in place of `ATA' (ATA not=0A= # allowed). The extra `\r' expect string is needed that the code can=0A= # grab the full CONNECT XYZ\R string. It will work without the \r,=0A= # but then the logging information will be less detailed. *Right now,=0A= # \r won't work at all, it's not implemented yet. Don't use it.*=0A= # : ["" ATA CONNECT \c \r] =0A= # - `answer-chat-timeout' =0A= # During the ANSWER-CHAT, each "expect" string must be seen in the=0A= # time specified here. Default is 80 seconds. This time should be at=0A= # least some 5 seconds longer than the time set with the `ATS7=3D...'=0A= # modem setup command.: [80] =0A= # - `autobauding'=0A= # Some modems switch their DTE line speed to the communication line=0A= # speed after connecting, e.g., after sending `CONNECT 2400', the=0A= # modem switches to 2400 bps. Newer modems usually have a switch to=0A= # "lock" a DTE baud rate, which is strongly recommended. If your=0A= # modem insists on doing this speed switch, setting `autobauding' to=0A= # YES will make mgetty behave accordingly.: [NO] =0A= # - `ringback'=0A= # If you have to put your modem and your telephone on the same phone=0A= # line, you can switch on "ringback" or "ring-twice". This means,=0A= # mgetty won't answer the phone on the first call, but remember the=0A= # call, and pick up on the second call (if it comes in the time=0A= # specified by `ringback-time').: [NO] =0A= # - `ringback-time'=0A= # This setting specifies how much time may pass between the first=0A= # and the second call if "ringback" is active.: [30] =0A= # - `ignore-carrier'=0A= =0A= # If your Modem does not assert the DCD (carrier detect) line, or the=0A= # serial port or cable or serial driver is broken, it is possible=0A= # that `mgetty' or `login' will block after a successful CONNECT=0A= # (that means: everything seems to work, but suddenly nothing is sent=0A= # to the port anymore. Depending on the operating system used, this=0A= # can be before printing the `/etc/issue' file or not before printing=0A= # the `password:' prompt.=0A= =0A= # To work around this, you can switch off the carrier detection in=0A= # software: set `ignore-carrier true'. Default is `false'.=0A= =0A= # *WARNING:* If you use this, your system won't be able to detect=0A= # when a caller just hangs up instead of cleanly logging out. This=0A= # may result in hanging modems, etc.: [false] =0A= # - `issue-file'=0A= # This is the file printed before the login prompt.: [/etc/issue] =0A= # - `prompt-waittime'=0A= # This specifies how long `mgetty' will wait for modem and line to=0A= # settle down (in ms) before printing issue file and login prompt: = [500] =0A= # - `login-prompt'=0A= # This specifies the login prompt that mgetty will output. Some=0A= # special characters in this string (and in the issue file, btw) are=0A= # recognized and replaced by something else:=0A= # * @ system name=0A= # * \n newline=0A= # * \r carriage return=0A= # * \g bell=0A= # * \b backspace (ascii 010)=0A= # * \f form feed (ascii 013)=0A= # * \t TAB=0A= # * \P (and \L) port name (e.g. ttyS0)=0A= # * \C date and time, in "ctime()" format=0A= # * \I Connection string (e.g. 2400/REL)=0A= # * \N (and \U) number of users currently logged in=0A= # * \S Port speed (e.g. 38400)=0A= # * \D current date in dd/mm/yy format=0A= # * \T current time in hh:mm:ss format=0A= # * \DIGIT character with the specified octal code=0A= #=0A= # The maximum lenght of the login prompt is limited to 140=0A= # characters (after expansion).: [@!login: ] =0A= # - `login-time'=0A= # This specifies the maximum time the user can take to log in. If no=0A= # login has occured after that time, `mgetty' will hang up.: [240] =0A= # - `fax-server-file'=0A= # Specifies the fax file(s) that is to be sent if someone else calls=0A= # your modem in *fax polling mode*, that is, the caller *receives* a=0A= # document.=0A= #=0A= # Normally, the file given is a text file, containing the list of G3=0A= # files to send to the calling machine, one file per line. Comment=0A= # lines (starting with "#") are ignored. For backward compatibility,=0A= # `mgetty' does check whether the named file is a G3 file itself, in=0A= # which case this file is sent directly (but then, you can only send=0A= # one page).=0A= =0A= # Not all modems support fax poll *server* mode, I know that the=0A= # ZyXEL and MultiTech do.: =0A= # - `diskspace'=0A= # This setting tells mgetty the minimum amount of disk space (in KB) = that=0A= # has to be available in the fax spool directory for fax reception=0A= # to be allowed.: [1024] =0A= # - `notify'=0A= # This is the address that will get mails if a fax is received. Not=0A= # fully tested.: [faxadmin] =0A= # - `fax-owner'=0A= # If set, mgetty will `chown' the received files to the given = username =0A= # (you can specify a string or an integer uid, but the integer must = be=0A= # valid).: [uucp] =0A= # - `fax-group' =0A= # If set, mgetty will `chgrp' the received files to this group id=0A= # (which can be given as group name, or as integer gid).: [modem] =0A= # - `fax-mode'=0A= # Specifies the permissions to `chmod' the received files.: [0660] =0A= # - `debug (sendfax)' =0A= # controls the amount of information written into the fax log file.=0A= # `0' means "totally silent" (not even errors are written), `9' =0A= # is really noisy. I usually use `3' or `4' in normal use, and `6' =0A= # for debugging.: [4] =0A= # - `modem-init' =0A= # Specifies an `AT...' command that is to be sent to the modem right=0A= # at the *beginning* of all modem talk (even before setting the modem=0A= # into fax mode, so this could be an `ATZ' if you want to reset the=0A= # modem).: =0A= # - `modem-handshake'=0A= # Specifies an `AT...' command that will be sent to the modem at the=0A= # *end* of the modem initialization, right before dialing. *Do not=0A= # use ATZ or such here*, since resetting the modem will switch off=0A= # fax mode.: [AT&H3] =0A= # - `max-tries'=0A= # Specify the maximum number of tries per page if the receiving end=0A= # reports reception errors. If NNN tries do not suffice to=0A= # successfully transmit a page, `sendfax' will give up or simply go=0A= # on, depending on the setting of `max-tries-continue' (see below).=0A= # If this is set to `0', `sendfax' will ignore retransmission=0A= # requests and simply go on.: [3] =0A= # - `max-tries-continue' =0A= # After the maximum number of tries for one page are reached,=0A= # `sendfax' can report an error and abort (`max-tries-continue NO'),=0A= # or go on with the next page (YES).=0A= #=0A= # For "mission critical" faxes, I'd set it to NO, but since the page=0A= # quality is most often quite good even if reported as "page bad",=0A= # the default is YES.: [YES] =0A= # - `speed'=0A= # Set the port speed to use for fax send operations. Usually,=0A= # `38400' is a good choice, but a few dumb modems (for example, some=0A= # based on rockwell chipsets) need `19200' or even `9600'. A few=0A= # modems can go higher, but `sendfax' may not support it, and it may=0A= # not always work.: [38000] =0A= # - `dial-prefix'=0A= # This is the command used for dialing out. Usually this will be=0A= # something simple, as `ATD' or `ATDP', but if you have an unusual=0A= # setup, it could also be something like `ATX0DP0;X4DT' (meaning:=0A= # switch off dial-tone detection, pulse-dial `0', back to command=0A= # mode, switch on dial-tone detection, and go ahead dialing with=0A= # touch tones). The phone number will be sent right after the=0A= # `dial-prefix'.: [ATD] =0A= # - `poll-dir'=0A= # This is used to specify a directory where polled faxes (wheather=0A= # maps and such) are to be saved into. Default is the current=0A= # directory.: [./] =0A= # - `normal-res'=0A= # If set to `yes' or `true' (boolean), `sendfax' won't attempt to=0A= # make a fax connection in "fine resolution" mode. Normally you=0A= # won't need to use that option, since `faxrunq' will set the `-n'=0A= # switch if needed.: [NO] =0A= # - `verbose' =0A= # If set to `yes' or `true', `sendfax' will output progress reports=0A= # on stdout, if set to `no', `sendfax' will only print error and=0A= # warning messages.: [NO] =0A= =0A= # Settings for port cuaa1=0A= # ------------------------=0A= # debug 4=0A= # fax-id 00 00 000000=0A= # speed 38400=0A= # direct NO=0A= # blocking NO=0A= # port-owner uucp=0A= # port-group uucp=0A= # port-mode 0660=0A= # toggle-dtr YES=0A= # toggle-dtr-waittime 500=0A= # data-only NO=0A= # fax-only NO=0A= # modem-type auto=0A= # init-chat "" ATS0=3D0Q0&D3&C1 OK=0A= # modem-check-time 3600=0A= # rings 1=0A= # answer-chat "" ATA CONNECT \c \r=0A= # answer-chat-timeout 80=0A= # autobauding NO=0A= # ringback NO=0A= # ringback-time 30=0A= # ignore-carrier false=0A= # issue-file /etc/issue=0A= # prompt-waittime 500=0A= # login-prompt @!login: =0A= # login-time 240=0A= # diskspace 1024=0A= # notify faxadmin=0A= # fax-owner uucp=0A= # fax-group modem=0A= # fax-mode 0660=0A= # fax-id 00 00 000000=0A= # modem-type auto=0A= # debug 4=0A= # modem-handshake AT&H3=0A= # max-tries 3=0A= # max-tries-continue YES=0A= # speed 38000=0A= # dial-prefix ATD=0A= # poll-dir ./=0A= # normal-res NO=0A= # verbose NO=0A= # OK?: [y] =0A= port cuaa1=0A= debug 9=0A= # fax-id 00 00 000000=0A= speed 38400=0A= direct NO=0A= blocking NO=0A= port-owner uucp=0A= port-group uucp=0A= port-mode 0660=0A= toggle-dtr YES=0A= toggle-dtr-waittime 500=0A= data-only YES=0A= fax-only NO=0A= modem-type data=0A= init-chat "" ATS0=3D0Q0&D3&C1 OK=0A= modem-check-time 3600=0A= rings 1=0A= answer-chat "" ATA CONNECT \c \r=0A= answer-chat-timeout 80=0A= autobauding NO=0A= ringback NO=0A= ringback-time 30=0A= ignore-carrier false=0A= issue-file /etc/issue=0A= prompt-waittime 500=0A= login-prompt @!login: =0A= login-time 240=0A= diskspace 1024=0A= # notify faxadmin=0A= # fax-owner uucp=0A= # fax-group modem=0A= # fax-mode 0660=0A= ------=_NextPart_000_0004_01BFFC08.B37E25B0 Content-Type: application/octet-stream; name="ppp.log" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="ppp.log" Jul 30 20:00:00 bryden newsyslog[15171]: logfile turned over Aug 1 20:33:00 bryden ppp[30425]: Phase: Using interface: tun1=20 Aug 1 20:33:00 bryden ppp[30425]: Phase: deflink: Created in closed = state=20 Aug 1 20:33:00 bryden ppp[30425]: Command: default: set device = /dev/cuaa0 /dev/cuaa1=20 Aug 1 20:33:00 bryden ppp[30425]: Command: default: set speed 38400=20 Aug 1 20:33:00 bryden ppp[30425]: Command: default: set dial ABORT BUSY = ABORT NO\sCARRIER TIMEOUT 5 "" ATE1Q0 OK-AT-OK \dATDT\T TIMEOUT 40 = CONNECT=20 Aug 1 20:33:00 bryden ppp[30425]: Command: POLY: set phone 38627687=20 Aug 1 20:33:00 bryden ppp[30425]: Command: POLY: set login TIMEOUT 10 = gin:-BREAK-gin: XXXXXX word: XXXXXX=20 Aug 1 20:33:00 bryden ppp[30425]: Command: POLY: set timeout 0=20 Aug 1 20:33:00 bryden ppp[30425]: Command: POLY: deny lqr=20 Aug 1 20:33:00 bryden ppp[30425]: Command: POLY: set ifaddr = 203.3.126.129 203.3.126.66 255.255.255.0=20 Aug 1 20:33:00 bryden ppp[30426]: Phase: PPP Started (ddial mode).=20 Aug 1 20:33:01 bryden ppp[30426]: Phase: bundle: Establish=20 Aug 1 20:33:01 bryden ppp[30426]: Phase: deflink: closed -> opening=20 Aug 1 20:33:01 bryden ppp[30426]: Phase: deflink: /dev/cuaa0 is in use=20 Aug 1 20:33:01 bryden ppp[30426]: Phase: deflink: Connected!=20 Aug 1 20:33:01 bryden ppp[30426]: Phase: deflink: opening -> dial=20 Aug 1 20:33:01 bryden ppp[30426]: Phase: Phone: 38627687=20 Aug 1 20:33:01 bryden ppp[30426]: Chat: Send: ATE1Q0^M=20 Aug 1 20:33:01 bryden ppp[30426]: Chat: Expect(5): OK=20 Aug 1 20:33:01 bryden ppp[30426]: Chat: Received: ATE1Q0^M^M=20 Aug 1 20:33:01 bryden ppp[30426]: Chat: Received: OK^M=20 Aug 1 20:33:01 bryden ppp[30426]: Chat: Send: ATDT38627687^M=20 Aug 1 20:33:03 bryden ppp[30426]: Chat: Expect(40): CONNECT=20 Aug 1 20:33:23 bryden ppp[30426]: Chat: Received: ATDT38627687^M^M=20 Aug 1 20:33:23 bryden ppp[30426]: Chat: Received: CONNECT 38400^M=20 Aug 1 20:33:23 bryden ppp[30426]: Phase: deflink: dial -> carrier=20 Aug 1 20:33:24 bryden ppp[30426]: Phase: deflink: /dev/cuaa1: CD = detected=20 Aug 1 20:33:24 bryden ppp[30426]: Phase: deflink: carrier -> login=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Expect(10): gin:=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Received: ^M^M=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Received: = poly.apana.org.au!login:=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Send: XXXXXX^M=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Expect(10): word:=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Received: XXXXXX^M=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Received: Password:=20 Aug 1 20:33:24 bryden ppp[30426]: Chat: Send: XXXXXX^M=20 Aug 1 20:33:24 bryden ppp[30426]: Phase: deflink: login -> lcp=20 Aug 1 20:33:24 bryden ppp[30426]: LCP: FSM: Using "deflink" as a = transport=20 Aug 1 20:33:24 bryden ppp[30426]: LCP: deflink: State change Initial = --> Closed=20 Aug 1 20:33:24 bryden ppp[30426]: LCP: deflink: State change Closed --> = Stopped=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: deflink: LayerStart=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: deflink: SendConfigReq(1) state = =3D Stopped=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: ACFCOMP[2]=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: PROTOCOMP[2]=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: ACCMAP[6] 0x00000000=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: MRU[4] 1500=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: MAGICNUM[6] 0x24a635b6=20 Aug 1 20:33:25 bryden ppp[30426]: LCP: deflink: State change Stopped = --> Req-Sent=20 Aug 1 20:33:29 bryden ppp[30426]: LCP: deflink: SendConfigReq(1) state = =3D Req-Sent=20 Aug 1 20:33:29 bryden ppp[30426]: LCP: ACFCOMP[2]=20 Aug 1 20:33:29 bryden ppp[30426]: LCP: PROTOCOMP[2]=20 Aug 1 20:33:29 bryden ppp[30426]: LCP: ACCMAP[6] 0x00000000=20 Aug 1 20:33:29 bryden ppp[30426]: LCP: MRU[4] 1500=20 Aug 1 20:33:29 bryden ppp[30426]: LCP: MAGICNUM[6] 0x24a635b6=20 Aug 1 20:33:32 bryden ppp[30426]: LCP: deflink: SendConfigReq(1) state = =3D Req-Sent=20 Aug 1 20:33:32 bryden ppp[30426]: LCP: ACFCOMP[2]=20 Aug 1 20:33:32 bryden ppp[30426]: LCP: PROTOCOMP[2]=20 Aug 1 20:33:32 bryden ppp[30426]: LCP: ACCMAP[6] 0x00000000=20 Aug 1 20:33:32 bryden ppp[30426]: LCP: MRU[4] 1500=20 Aug 1 20:33:32 bryden ppp[30426]: LCP: MAGICNUM[6] 0x24a635b6=20 Aug 1 20:33:35 bryden ppp[30426]: LCP: deflink: SendConfigReq(1) state = =3D Req-Sent=20 Aug 1 20:33:35 bryden ppp[30426]: LCP: ACFCOMP[2]=20 Aug 1 20:33:35 bryden ppp[30426]: LCP: PROTOCOMP[2]=20 Aug 1 20:33:35 bryden ppp[30426]: LCP: ACCMAP[6] 0x00000000=20 Aug 1 20:33:35 bryden ppp[30426]: LCP: MRU[4] 1500=20 Aug 1 20:33:35 bryden ppp[30426]: LCP: MAGICNUM[6] 0x24a635b6=20 Aug 1 20:33:38 bryden ppp[30426]: LCP: deflink: SendConfigReq(1) state = =3D Req-Sent=20 Aug 1 20:33:38 bryden ppp[30426]: LCP: ACFCOMP[2]=20 Aug 1 20:33:38 bryden ppp[30426]: LCP: PROTOCOMP[2]=20 Aug 1 20:33:38 bryden ppp[30426]: LCP: ACCMAP[6] 0x00000000=20 Aug 1 20:33:38 bryden ppp[30426]: LCP: MRU[4] 1500=20 Aug 1 20:33:38 bryden ppp[30426]: LCP: MAGICNUM[6] 0x24a635b6=20 Aug 1 20:33:41 bryden ppp[30426]: LCP: deflink: LayerFinish=20 Aug 1 20:33:41 bryden ppp[30426]: LCP: deflink: State change Req-Sent = --> Stopped=20 Aug 1 20:33:41 bryden ppp[30426]: LCP: deflink: State change Stopped = --> Closed=20 Aug 1 20:33:41 bryden ppp[30426]: LCP: deflink: State change Closed --> = Initial=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: Disconnected!=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: lcp -> logout=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: logout -> hangup=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: Disconnected!=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: Connect time: 40 = secs: 1345 octets in, 260 octets out=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: total 40 bytes/sec, peak 289 = bytes/sec on Tue Aug 1 20:33:41 2000=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: hangup -> opening=20 Aug 1 20:33:41 bryden ppp[30426]: Phase: deflink: Enter pause (3) for = redialing.=20 Aug 1 20:33:44 bryden ppp[30426]: Phase: deflink: Redial timer expired. = Aug 1 20:33:44 bryden ppp[30426]: Phase: deflink: /dev/cuaa0 is in use=20 Aug 1 20:33:44 bryden ppp[30426]: Phase: deflink: Connected!=20 Aug 1 20:33:44 bryden ppp[30426]: Phase: deflink: opening -> dial=20 Aug 1 20:33:44 bryden ppp[30426]: Phase: Phone: 38627687=20 Aug 1 20:33:44 bryden ppp[30426]: Chat: Send: ATE1Q0^M=20 Aug 1 20:33:44 bryden ppp[30426]: Chat: Expect(5): OK=20 Aug 1 20:33:50 bryden ppp[30426]: Chat: Expect timeout=20 Aug 1 20:33:50 bryden ppp[30426]: Chat: Send: AT^M=20 Aug 1 20:33:50 bryden ppp[30426]: Chat: Expect(5): OK=20 Aug 1 20:33:50 bryden ppp[30426]: Chat: Received: AT^M^M=20 Aug 1 20:33:50 bryden ppp[30426]: Chat: Received: OK^M=20 Aug 1 20:33:50 bryden ppp[30426]: Chat: Send: ATDT38627687^M=20 Aug 1 20:33:52 bryden ppp[30426]: Chat: Expect(40): CONNECT=20 Aug 1 20:34:09 bryden ppp[30426]: Chat: Received: ATDT38627687^M^M=20 Aug 1 20:34:09 bryden ppp[30426]: Chat: Received: CONNECT 38400^M=20 Aug 1 20:34:09 bryden ppp[30426]: Phase: deflink: dial -> carrier=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: Signal 15, terminate.=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: deflink: Disconnected!=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: deflink: carrier -> logout=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: deflink: logout -> hangup=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: deflink: Disconnected!=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: deflink: Connect time: 26 = secs: 0 octets in, 0 octets out=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: total 0 bytes/sec, peak 0 = bytes/sec on Tue Aug 1 20:34:10 2000=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: deflink: hangup -> closed=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: bundle: Dead=20 Aug 1 20:34:10 bryden ppp[30426]: Phase: PPP Terminated (normal).=20 ------=_NextPart_000_0004_01BFFC08.B37E25B0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message