Date: Wed, 9 Jul 1997 11:59:43 -0400 (EDT) From: dave@ns.systemresc.com To: questions@freebsd.org Subject: Help DCD Message-ID: <Pine.BSI.3.95.970709115901.6295A-100000@ns.systemresc.com>
next in thread | raw e-mail | index | archive | help
Hello I have been learning and running two freebsd boxes in Buffalo and Niagara Falls for dialup ppp access to the internet. I also use one BSDI box. The one in the falls is giving me alot more problem and mainly it is mgetty or the way I have it configured. The problem is if someone drops carrier. Mgetty resetts the modem but it doesn't kill the dialup scriptthat they used to log on with. I have not been able to setup pap so I use pppd in the script started by the user dialing into the system. Here are some of the files for my system I will show you a log file that I think that problem lies with DCD. The &C1 sets the modem to watch for carrier between the two modems and if dropped then mgetty resetts the modem and it does that but not the process it is running so no one else can log in on that modem and when it is the first one in the hunt group the system is virtual shutdown. The info file on mgetty said it could be the cables are too long or because we are using a flat cable. Is this why or possible, that the log shows the warning about DCD being low. The other files I'm including in this file are my ttys and my ppp.conf that I would like to get to work with pap. I tried using just getty but could not even get it to give me a login in prompt just garabage characters and I tried all sorts of things before going to mgetty. Please help me, with any infomation or where I could go for more help. David G. Hazelton dave@systemresc.com <<<<PART OF THE CUAC0 LOG FILE>>>>> 07/07 20:34:54 ac0 mgetty: official release 1.0.0 07/07 20:34:54 ac0 check for lockfiles 07/07 20:34:54 ac0 locking the line 07/07 20:34:58 ac0 send: ATS0=0Q0&C1&D3&K3[0d] 07/07 20:34:58 ac0 waiting for ``OK'' ** found ** 07/07 20:34:58 ac0 waiting... 07/07 21:34:58 ac0 checking if modem is still alive 07/07 21:34:58 ac0 mdm_send: 'AT' -> OK 07/07 21:34:59 ac0 waiting... 07/07 21:44:27 ac0 waiting for ``RING'' ** found ** 07/07 21:44:27 ac0 waiting for ``RING'' ** found ** 07/07 21:44:33 ac0 send: ATA[0d] 07/07 21:44:33 ac0 waiting for ``CONNECT'' ** found ** 07/07 21:44:44 ac0 send: 07/07 21:45:32 ac0 WARNING: starting login while DCD is low! 07/07 21:45:32 ##### data dev=cuac0, pid=566, caller=, conn='', name='', cmd='/usr/bin/login', user='jennie' <<<<THE TTTYS FILE>>>>> console none unknown off secure ttyv0 "/usr/libexec/getty Pc" cons25 on secure ttyv1 "/usr/libexec/getty Pc" cons25 on secure ttyv2 "/usr/libexec/getty Pc" cons25 off secure ttyv3 "/usr/libexec/getty Pc" cons25 off secure #ttyc0 "/usr/libexec/getty vr" dialup on insecure #ttyc1 "/usr/libexec/getty vq" dialup on insecure #ttyc1 "/usr/libexec/getty vr" dialup on insecure cuac0 "/usr/local/sbin/mgetty" unknown on insecure cuac1 "/usr/local/sbin/mgetty" unknown on insecure cuac2 "/usr/local/sbin/mgetty" unknown on insecure cuac3 "/usr/local/sbin/mgetty" unknown on insecure cuac4 "/usr/local/sbin/mgetty" unknown on insecure cuac5 "/usr/local/sbin/mgetty" unknown on insecure cuac6 "/usr/local/sbin/mgetty" unknown on insecure cuac7 "/usr/local/sbin/mgetty" unknown on insecure cuac8 "/usr/local/sbin/mgetty" unknown on insecure cuac9 "/usr/local/sbin/mgetty" unknown on insecure #ttyd1 "/usr/libexec/getty std:9600" unknown on insecure ttyp0 none network ttyp1 none network ttyp2 none network ttyp3 none network ttyp4 none network ttyp5 none network <<<<PPP.CONF>>>>> ################################################################# # # PPP Sample Configuration File # # Written by Toshiharu OHNO # # $Id: ppp.conf.sample,v 1.3.4.3 1996/06/17 09:17:50 jkh Exp $ # ################################################################# # # Default setup. Executed always when PPP is invoked. # #default: #set device /dev/cuaa1 #set speed 38400 #disable lqr #deny lqr #set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" ATE1Q0 OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" # # Example with login script # o From PPP prompt, # ppp> dial simplesite # will automatically dials and perform login procedure. # # ppp> load simplesite # will also load and execute commands, but don't dial. # # o From shell, invoke as # % ppp simplesite # will load commands associated with the label. Use, # ppp> dial # to establish the connection. # #simplesite: #set phone 12345678 #set login "TIMEOUT 5 login:-\\r-login: ppp word: ppp" #set timeout 120 # # Multi-phone example # #multiphone: # set phone 12345678:12345679:12345670:12345671 # set login "TIMEOUT 5 login:-\\r-login: ppp word: ppp" # # If peer requires to use CHAP, don't forget to supply authname and authkey. # # If you'd like to use CHAP to authentication peer, comment out the line # ``enable chap'' below. You also need to prepare /etc/ppp.secret. # # If remote system sends its system name within CHAP packet and it is # found in /etc/ppp.secret, then secret key is taken from the file and # value of authkey is ignored. # #chapsite: #set phone 12345678 #set login "TIMEOUT 5 login:-\\r-login: ppp word: ppp" #deny pap #accept chap # enable chap #set authname MySystemName #set authkey OurSecretKey # # To speak PAP is just similar to CHAP # #papsite: #set phone 12345678 #s#et login "TIMEOUT 5 login:-\\r-login: ppp word: ppp" #deny chap #accept pap # enable pap #set authname MyUserName #set authkey MyPassword # # On demand dialup example # Here, we assume that local side use 192.244.185.226 and # remote side use 192.244.176.44 as their IP address. # You must supply -auto option to invoke PPP. # # ex. % ppp -auto ondemand # #ondemand: #set phone 1234567 #set login "TIMEOUT 5 login:-\\r-login: ppp word: ppp" #set timeout 120 #set ifaddr 192.244.185.226 192.244.176.44 255.255.255.0 #add 0 0 192.244.176.44 # # Another on demand example # If peer assign some IP address for us, and we can't predict it # until we make a connection, use 0 as local side address. # #pmdemend: # set phone 1234567 # set login "TIMEOUT 5 login:-\\r-login: ppp word: ppp" # set timeout 120 # set ifaddr 0 192.244.176.44 255.255.255.0 #add 0 0 192.244.176.44 # # Example to validate incoming user with CHAP # Invod as ``ppp -direct users'' from login script. User's system name # and secret-key must be registered into /etc/ppp.secret. # IP address assigned to peer is registered in ppp.secret, then that # value is used and value in ``ifaddr'' command has no effect. # #users: #disable pap # enable chap # enable proxy # set authname ppp-server # set ifaddr 192.244.176.44 292.244.184.31 # # Example of Callback Request # # Here, we assume that peer will hangup the line and initiates a callback # after successful authentication. We simply use chat script capability # and wait for a "NO CARRIER" response from our modem. # # % ppp callback # #callback: #set phone 0312345678 #set login "ABORT NO\\sCARRIER TIMEOUT 5 login:-\\r-login: MyName word: MySecret TIMEOUT 20 DUMMY" #set debug phase chat #dial #quit # # Example for PPP/TELNET and PPP/TCP. Read doc for further details # #ppptelnet: # set escape 0xff #ppptcp: # set device 192.244.191.33:2400 default: set debug phase lcp chat set timeout 0 cuac00: set ifaddr 207.198.60.226 207.198.60.254 255.255.255.224 enable proxy cuac01: set ifaddr 207.198.60.226 207.198.60.253 255.255.255.224 enable proxy cuac02: set ifaddr 207.198.60.226 207.198.60.252 255.255.255.224 enable proxy cuac03: set ifaddr 207.198.60.226 207.198.60.251 255.255.255.224 enable proxy cuac04: set ifaddr 207.198.60.226 207.198.60.250 255.255.255.224 enable proxy cuac05: set ifaddr 207.198.60.226 207.198.60.249 255.255.255.224 enable proxy cuac06: set ifaddr 207.198.60.226 207.198.60.248 255.255.255.224 enable proxy cuac07: set ifaddr 207.198.60.226 207.198.60.247 255.255.255.224 enable proxy cuac08: set ifaddr 207.198.60.226 207.198.60.246 255.255.255.224 enable proxy cuac09: set ifaddr 207.198.60.226 207.198.60.245 255.255.255.224 enable proxy papcuac00: enable pap enable passwdauth set ifaddr 207.198.60.226 207.198.60.254 255.255.255.224 enable proxy papcuac01: enable pap set ifaddr 207.198.60.226 207.198.60.253 255.255.255.224 enable proxy papcuac02: enable pap set ifaddr 207.198.60.226 207.198.60.252 255.255.255.224 enable proxy papcuac03: enable pap set ifaddr 207.198.60.226 207.198.60.251 255.255.255.224 enable proxy papcuac04: enable pap set ifaddr 207.198.60.226 207.198.60.250 255.255.255.224 enable proxy papcuac05: enable pap set ifaddr 207.198.60.226 207.198.60.249 255.255.255.224 enable proxy papcuac06: enable pap set ifaddr 207.198.60.226 207.198.60.248 255.255.255.224 enable proxy papcuac07: enable pap set ifaddr 207.198.60.226 207.198.60.247 255.255.255.224 enable proxy papcuac08: enable pap set ifaddr 207.198.60.226 207.198.60.246 255.255.255.224 enable proxy papcuac09: enable pap set ifaddr 207.198.60.226 207.198.60.245 255.255.255.224 enable proxy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSI.3.95.970709115901.6295A-100000>