From owner-freebsd-questions Sat Feb 12 15:27:30 2000 Delivered-To: freebsd-questions@freebsd.org Received: from alchemy.oven.org (sh-adm2.ksl.co.il [199.203.25.38]) by builder.freebsd.org (Postfix) with ESMTP id 9C5193FC0 for ; Sat, 12 Feb 2000 15:27:23 -0800 (PST) Received: from localhost (mapc@localhost) by alchemy.oven.org (8.9.3/8.9.3) with ESMTP id AAA26083 for ; Sun, 13 Feb 2000 00:28:48 +0200 (IST) (envelope-from roman@xpert.com) X-Authentication-Warning: alchemy.oven.org: mapc owned process doing -bs Date: Sun, 13 Feb 2000 00:28:47 +0200 (IST) From: Roman Shterenzon X-Sender: mapc@alchemy.oven.org To: questions@freebsd.org Subject: User ppp question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've noticed a strange behavior of user-ppp ( PPP(8) ) In the man page is says that: set cd off|seconds[!] Normally, ppp checks for the existence of carrier one second af- ter the login script is complete. If it's not set, ppp assumes that this is because the device doesn't support carrier (which is true for most ``laplink'' NULL-modem cables), logs the fact and stops checking for carrier. ... The same fact is mentioned in /usr/share/examples/ppp/ppp.conf.sample However, I use the following script in /etc/ppp/ppp.conf: default: # # Make sure that "device" references the correct serial port # for your modem. (cuaa0 = COM1, cuaa1 = COM2) # set device /dev/cuaa2 set log Phase Chat LCP IPCP CCP tun command set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK AT&FX4W4 OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 120 set ifaddr 10.0.1.1/0 10.0.1.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns [snip] callback: set phone 8777777 set authkey my_password set ifaddr xx.xx.xx.xx xx.xx.xx.xy 255.255.255.255 add default HISADDR set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATZ OK \ AT&FX4W4 OK ATDT\\T TIMEOUT 60 CONNECT" set login "TIMEOUT 5 \"\" \\r \ Userid:-\\r-Userid: roman word? \\P \ TIMEOUT 15 dialback ++andonemore+ATH0 \ OK \"\" \ TIMEOUT 70 RING ATA \ CONNECT \"\" \ TIMEOUT 10 > ppp" [snip] But, the ppp exits out of the `set login' after the ++ATH0 is issued. The log file tells me this": [snip] Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Received: Password? Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Send: \P Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Expect(15): dialback Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Received: ^M Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Received: Shell dialback Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Send: ++andonemore+ATH0^M Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Expect(15): OK Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Received: 8888888^M Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Received: ^M Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Received: OK^M Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Send: ^M Feb 11 23:22:47 alchemy ppp[61404]: tun0: Chat: Expect(70): RING Feb 11 23:22:48 alchemy ppp[61404]: tun0: Chat: Received: ^M Feb 11 23:22:48 alchemy ppp[61404]: tun0: Chat: Received: OK^M Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: deflink: Carrier lost Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: deflink: Disconnected! Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: deflink: login -> logout Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: deflink: logout -> hangup Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: deflink: Disconnected! Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: deflink: Connect time: 28 secs: 0 octets in, 0 octets out Feb 11 23:22:49 alchemy ppp[61404]: tun0: Phase: total 0 bytes/sec, peak 0 bytes/sec on Fri Feb 11 23:22:49 2000 [snip] And, another question: I didn't notice, is there a way to define -nat as a default option? --Roman Shterenzon, UNIX System Administrator and Consultant [ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message