Re: first attempt to run UUCP; failed
Eugene Sevinian writes: Hi all, I am trying to connect 2 Debian machine, via uucp. I am not sure that I will find answer in this mailing list, Sorry about that, I was clouding the issue with my previous answer. OK, you will need to setup UUCP on both machines. One of the machine will have to become the primary and the other machine will need to become the secondary. The primary's job will be to collect UUCP mail from other sites and to pass that mail to your ISP. The secondary machine will become the leaf site and will gather mail from local users to pass on to the primary via UUCP. The primary can still gather mail from it's local users as well. The point of this arrangement is that the primary will monitor it's UUCP port for incoming UUCP connections while the secondary will (via cron) periodically call the primary and exchange mail/programs. Should you add more machine to your virtual network, they will also in turn call the primary as well for UUCP connections. UUCP connectivity can be more sophisticated than my simple example. But in any case, one or more machine must listen for incoming connections while one or more machines do the initial talking. -- -= Sent by Debian 1.3 Linux =- Thomas Kocourek KD4CIK @[EMAIL PROTECTED]@westgac3.dragon.com Remove @_@ for correct Email address --... ...-- ... -.. . -.- -.. - -.-. .. -.-
Re: first attempt to run UUCP; failed
On Thu, Dec 03, 1998 at 03:20:54AM +0400, Eugene Sevinian wrote: 54.54 1060) Calling system spyur (port ttyS2) 54.54 1060) DEBUG: fcsend: Writing ATZ\r sleep 55.56 1060) DEBUG: icexpect: Looking for 3 OK\r 55.56 1060) DEBUG: icexpect: Got \r\nATZ\r\r\nOK\r (found it) 55.56 1060) DEBUG: fcsend: Writing sleep ATM0L0E1Q0\r sleep 57.60 1060) DEBUG: icexpect: Looking for 3 OK\r 57.60 1060) DEBUG: icexpect: Got \nATM0L0E1Q0\r\r\nOK\r (found it) 57.60 1060) DEBUG: fcsend: Writing ATDP \D 562635\r 57.60 1060) DEBUG: icexpect: Looking for 7 CONNECT 57.61 1060) DEBUG: icexpect: Got \nATDP562635\r\r\nNO CARRIER 50.95 1060) DEBUG: icexpect: Found 10 NO CARRIER Perhaps your delay is not long enough between dialing and connecting -- especially since you are pulse dialing, which is quite slow. I can't remember how you increase it exactly though, it's been some time since I played with this stuff. Hamish -- Hamish Moffatt VK3TYD [EMAIL PROTECTED], [EMAIL PROTECTED] Latest Debian packages at ftp://ftp.rising.com.au/pub/hamish. PGP#EFA6B9D5 CCs of replies from mailing lists are welcome. http://hamish.home.ml.org
Re: first attempt to run UUCP; failed
Eugene Sevinian writes: Hi all, I am trying to connect 2 Debian machine, via uucp. I am not sure that I will find answer in this mailing list, however I will try to discribe the problem shortly. At the very initial stage of communication chat script is getting NO CARRIER and exit. At the same time I use this line by minicom without problem, so it seems that the phone line is ok. I think that sometihng is wrong with uucp configuration. Hope, there are UUCP gury around here, who will help me to understand what is going on. Here is the debug info from client side: 54.54 1060) Calling system spyur (port ttyS2) 54.54 1060) DEBUG: fcsend: Writing ATZ\r sleep 55.56 1060) DEBUG: icexpect: Looking for 3 OK\r 55.56 1060) DEBUG: icexpect: Got \r\nATZ\r\r\nOK\r (found it) 55.56 1060) DEBUG: fcsend: Writing sleep ATM0L0E1Q0\r sleep 57.60 1060) DEBUG: icexpect: Looking for 3 OK\r 57.60 1060) DEBUG: icexpect: Got \nATM0L0E1Q0\r\r\nOK\r (found it) 57.60 1060) DEBUG: fcsend: Writing ATDP \D 562635\r 57.60 1060) DEBUG: icexpect: Looking for 7 CONNECT 57.61 1060) DEBUG: icexpect: Got \nATDP562635\r\r\nNO CARRIER 50.95 1060) DEBUG: icexpect: Found 10 NO CARRIER 50.95 1060) ERROR: Chat script failed: Got NO\sCARRIER 50.95 1060) DEBUG: fconn_close: Closing connection 50.96 1060) DEBUG: fcsend: Writing sleep sleep +++ sleep sleep ATM0H\r 59.03 1060) DEBUG: Call failed: 2 (Dial failed) 59.04 1087) DEBUG: usysdep_detach: Forked; old PID 1060, new pid 1087 59.04 1087) DEBUG: fsysdep_get_work_init: Found C.NVMzzTJAAAOl 59.04 1087) DEBUG: fconn_open: Opening port ACU (default speed) Thanks for any tips, Sure thing - 1) turn off the command echo option of the modem. UUCP does not like having the command echoed back. 2) assuming that your modem has 2 memories for parameter storage, use one of the memories for parameters for UUCP, and one for ordinary connectivity. Use minicom to setup the UUCP memory slot and adjust your script to load that memory into the modem's working registers. If you wish, you can Email me your configuration files (with the account password information blanked out). I also need to know if you are using Taylor or HDB mode of operation. The configuration is different depending on which you want to use. -- -= Sent by Debian 1.3 Linux =- Thomas Kocourek KD4CIK @[EMAIL PROTECTED]@westgac3.dragon.com Remove @_@ for correct Email address --... ...-- ... -.. . -.- -.. - -.-. .. -.-
first attempt to run UUCP; failed
Hi all, I am trying to connect 2 Debian machine, via uucp. I am not sure that I will find answer in this mailing list, however I will try to discribe the problem shortly. At the very initial stage of communication chat script is getting NO CARRIER and exit. At the same time I use this line by minicom without problem, so it seems that the phone line is ok. I think that sometihng is wrong with uucp configuration. Hope, there are UUCP gury around here, who will help me to understand what is going on. Here is the debug info from client side: 54.54 1060) Calling system spyur (port ttyS2) 54.54 1060) DEBUG: fcsend: Writing ATZ\r sleep 55.56 1060) DEBUG: icexpect: Looking for 3 OK\r 55.56 1060) DEBUG: icexpect: Got \r\nATZ\r\r\nOK\r (found it) 55.56 1060) DEBUG: fcsend: Writing sleep ATM0L0E1Q0\r sleep 57.60 1060) DEBUG: icexpect: Looking for 3 OK\r 57.60 1060) DEBUG: icexpect: Got \nATM0L0E1Q0\r\r\nOK\r (found it) 57.60 1060) DEBUG: fcsend: Writing ATDP \D 562635\r 57.60 1060) DEBUG: icexpect: Looking for 7 CONNECT 57.61 1060) DEBUG: icexpect: Got \nATDP562635\r\r\nNO CARRIER 50.95 1060) DEBUG: icexpect: Found 10 NO CARRIER 50.95 1060) ERROR: Chat script failed: Got NO\sCARRIER 50.95 1060) DEBUG: fconn_close: Closing connection 50.96 1060) DEBUG: fcsend: Writing sleep sleep +++ sleep sleep ATM0H\r 59.03 1060) DEBUG: Call failed: 2 (Dial failed) 59.04 1087) DEBUG: usysdep_detach: Forked; old PID 1060, new pid 1087 59.04 1087) DEBUG: fsysdep_get_work_init: Found C.NVMzzTJAAAOl 59.04 1087) DEBUG: fconn_open: Opening port ACU (default speed) Thanks for any tips, Eugene Sevinian CRD, YerPhI, 375036, Armenia Phone: 374-2-344873
