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