Folks, I apologize for re-posting a message. I am stuck on this problem. I haven't had a lot of time to work on this. I am attempting to complete my MCSE. It seems that the problems I was having with route and traceroute may have been fixed by the below configuration. I believe that the problem connecting is a pppd problem, and not a diald problem. The setup works, but it always takes two calls, and often more, to establish a working connection. I would appreciate any help. Thanks, Steve ##################Begin original message #########################3 Tony, Thanks for the help. I can't for the life of me figure all this out. I'm just not sure what all the pieces are doing. Here's what I have: I added these lines to the top of the sample diald.conf: -m ppp local 127.0.0.2 remote 127.0.0.3 dynamic connect /ppp-up device /dev/modem speed 38400 modem debug defaultroute crtscts lock mtu 1524 redial-timeout 60 fifo /var/run/diald.ctl ############ end mods to diald.conf ############# My /ppp-up looks like this: #!/bin/sh # # /etc/ppp/ppp-up # # Aufbau einer PPP Verbindung # localip=0.0.0.0 remoteip= device=/dev/modem pppflags="debug" /usr/sbin/pppd connect \ '/usr/sbin/chat -v -f /etc/ppp/ppp.chat' \ $device $pppflags $localip:$remoteip ########### end ppp-up ################# Do I need the $<VAR>s here? Should these variables be sent from the diald.conf? /etc/ppp/options only has "asyncmap 0" ################################33 ppp.chat looks like this: baraba:/etc # cat ppp/ppp.chat ""ATZ OK ATDT2024780571 ABORT "NO CARRIER" ABORT BUSY ABORT "NO DIALTONE" ABORT ERROR CONNECT "" net "" ogin:--ogin: <UID> ssword: <PASSWORD> MTU "" ############## end ppp.chat ##################33 The failed protocol negotiations usually look like this: Aug 13 17:44:48 baraba chat[2169]: Entering PPP Session.^M Aug 13 17:44:48 baraba chat[2169]: IP address is 153.35.91.134^M Aug 13 17:44:48 baraba chat[2169]: MTU -- got it Aug 13 17:44:48 baraba chat[2169]: send (^M) Aug 13 17:44:48 baraba pppd[2162]: Serial connection established. Aug 13 17:44:49 baraba pppd[2162]: Using interface ppp0 Aug 13 17:44:49 baraba pppd[2162]: Connect: ppp0 <--> /dev/modem Aug 13 17:44:49 baraba pppd[2162]: sent [LCP ConfReq id=0x1 <mru 1500> <asyncmap 0x0> <magic 0xf9e4ca81> <pcomp> <accomp>] Aug 13 17:44:52 baraba pppd[2162]: sent [LCP ConfReq id=0x1 <mru 1500> <asyncmap 0x0> <magic 0xf9e4ca81> <pcomp> <accomp>] Aug 13 17:44:53 baraba pppd[2162]: rcvd [LCP ConfReq id=0x1 <mru 1524> <asyncmap 0xa0000> <pcomp> <accomp> < 13 09 03 00 c0 7b 71 ba 18>] Aug 13 17:44:53 baraba pppd[2162]: sent [LCP ConfRej id=0x1 < 13 09 03 00 c0 7b 71 ba 18>] Aug 13 17:44:53 baraba pppd[2162]: rcvd [LCP ConfAck id=0x1 <mru 1500> <asyncmap 0x0> <magic 0xf9e4ca81> <pcomp> <accomp>] Aug 13 17:44:53 baraba pppd[2162]: rcvd [LCP ConfReq id=0x2 <mru 1524> <asyncmap 0xa0000> <pcomp> <accomp>] Aug 13 17:44:53 baraba pppd[2162]: sent [LCP ConfAck id=0x2 <mru 1524> <asyncmap 0xa0000> <pcomp> <accomp>] Aug 13 17:44:53 baraba pppd[2162]: sent [IPCP ConfReq id=0x1 <addr 10.10.10.4> <compress VJ 0f 01>] Aug 13 17:44:53 baraba pppd[2162]: sent [IPXCP ConfReq id=0x1 <network 0> <node 00005cd4f2c2> <router proto 2> <complete>] Aug 13 17:44:53 baraba pppd[2162]: rcvd [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 206.115.156.5>] Aug 13 17:44:53 baraba pppd[2162]: sent [IPCP ConfAck id=0x1 <compress VJ 0f 01> <addr 206.115.156.5>] Aug 13 17:44:53 baraba pppd[2162]: rcvd [LCP ProtRej id=0x3 80 2b 01 01 00 18 01 06 00 00 00 00 02 08 00 00 5c d4 f2 c2 04 04 00 02 06 02] Aug 13 17:44:56 baraba pppd[2162]: sent [IPCP ConfReq id=0x1 <addr 10.10.10.4> <compress VJ 0f 01>] Aug 13 17:44:56 baraba pppd[2162]: rcvd [IPCP ConfNak id=0x1 <addr 153.35.91.134>] Aug 13 17:44:56 baraba pppd[2162]: sent [IPCP ConfReq id=0x2 <addr 153.35.91.134> <compress VJ 0f 01>] Aug 13 17:44:56 baraba pppd[2162]: rcvd [IPCP ConfAck id=0x2 <addr 153.35.91.134> <compress VJ 0f 01>] Aug 13 17:44:56 baraba pppd[2162]: local IP address 153.35.91.134 Aug 13 17:44:56 baraba pppd[2162]: remote IP address 206.115.156.5 Aug 13 17:45:25 baraba diald[2101]: failed to set terminal attributes: Invalid argument Aug 13 17:45:26 baraba diald[2101]: failed to set terminal attributes: Invalid argument Aug 13 17:45:26 baraba diald[2101]: Running connect (pid = 2179). Aug 13 17:45:26 baraba diald[2101]: failed to set terminal attributes: Invalid argument Aug 13 17:45:26 baraba diald[2101]: Running pppd (pid = 2182). Aug 13 17:45:26 baraba diald[2101]: New addresses: local 153.35.91.134, remote 206.115.156.5. Aug 13 17:45:27 baraba pppd[2182]: pppd 2.2.0 started by root, uid 0 Aug 13 17:45:27 baraba pppd[2162]: Modem hangup Aug 13 17:45:27 baraba pppd[2162]: Connection terminated. Aug 13 17:45:27 baraba pppd[2162]: Exit. Aug 13 17:45:27 baraba pppd[2182]: tcsetattr: Invalid argument Aug 13 17:45:27 baraba pppd[2182]: Exit. ############# END /vaar/log/message tail ################### It is interesting to point out that the ethernet address of the box with the modem is listed in the above log. That is 10.10.10.4. The message below seems to be the one that shows the problem: "failed to set terminal attributes: Invalid argument" I have no clue what this means. Any ideas? I can get KPPP to set up a connection every time. but with this cobled together diald attempt at a solution I just get a connection every second or third try. Sometimes it can take several minutes to get an output from the "route" command which shows how devices are connected. It can take forever to run a traceroute as well. What is intersting is that from another box on my network the traceroute will scream. The output of the "route" looks like this. baraba:/etc # route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface baraba.sprintma * 255.255.255.255 UH 0 0 0 dummy0 tnt5.tco2.da.uu * 255.255.255.255 UH 500 0 0 ppp0 127.0.0.3 * 255.255.255.255 UH 2000 0 0 sl0 tnt6.tco2.da.uu * 255.255.255.255 UH 0 0 0 ppp0 10.10.10.0 * 255.255.255.0 U 0 0 122 eth0 loopback * 255.0.0.0 U 0 0 1 lo default * 0.0.0.0 U 500 0 7 ppp0 default 127.0.0.3 0.0.0.0 UG 2000 0 0 sl0 baraba:/etc # ############# END of route table #################### And the if config looks like this. baraba:/etc # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0 UP BROADCAST LOOPBACK RUNNING MTU:3584 Metric:1 RX packets:24 errors:0 dropped:0 overruns:0 TX packets:24 errors:0 dropped:0 overruns:0 dummy0 Link encap:10Mbps Ethernet HWaddr 00:00:00:00:00:00 inet addr:10.10.10.4 Bcast:10.255.255.255 Mask:255.0.0.0 UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 TX packets:0 errors:0 dropped:0 overruns:0 eth0 Link encap:10Mbps Ethernet HWaddr 00:20:AF:28:47:DC inet addr:10.10.10.4 Bcast:10.10.10.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:72621 errors:0 dropped:0 overruns:0 TX packets:68029 errors:0 dropped:0 overruns:0 Interrupt:10 Base address:0x300 ppp0 Link encap:Point-Point Protocol inet addr:153.37.3.219 P-t-P:206.115.156.6 Mask:255.255.0.0 UP POINTOPOINT RUNNING MTU:1524 Metric:1 RX packets:55 errors:0 dropped:0 overruns:0 TX packets:66 errors:0 dropped:0 overruns:0 l0 Link encap:Serial Line IP inet addr:127.0.0.2 P-t-P:127.0.0.3 Mask:255.0.0.0 UP POINTOPOINT RUNNING MTU:1524 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 TX packets:25 errors:0 dropped:0 overruns:0 #################### end of ifconfig output ############### If you or any body else has a clue I would love to hear it. TIA Steve Anthony Schlemmer wrote:
-m ppp local 10.10.10.1 remote 10.10.10.10 dynamic connect /etc/ppp/ppp-up
to diald.conf.
I started the daemon like this: diald /dev/modem defaultroute
Thanks for your help,
Steve
I took the supplied sample diald.conf file from /usr/doc/packages/diald/config and added the following lines to the end of it. I works pretty reliably. Because all of the necessary arguments are in my systems's "/etc/diald.conf" file, I run diald with no runtime arguments at all. This stuff should be fairly boilerplate expect for the "ip-up" and "ip-down" stuff. I use diald on my gateway/firewall system for my home network and have some basic firewall and IP Masquerading stuff setup.
fifo /var/run/diald.ctl mode ppp connect "/bin/sh /etc/ppp/connect" device /dev/ttyS1 speed 115200 modem lock crtscts local 127.0.0.2 remote 127.0.0.3 dynamic defaultroute retry-count 10 redial-timeout 15 first-packet-timeout 300 connect-timeout 120 two-way ip-up /etc/ppp/firewall.rules ip-down /etc/ppp/firewall.reset
If you're having problems generally with the login stuff and you're using "chat" in your connect script, try running "chat" with the "-v" argument which causes verbose output to be sent to the "syslogd" process. You can look at the output in the /var/log/messages file.
Tony
-- Anthony.Schlemmer@gte.net - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
-- [<A HREF="http://counter.li.org"><A HREF="http://counter.li.org</A">http://counter.li.org</A</A>>] S.u.S.E. Linux, www.suse.com I Think, I think I am, Therefore I am, I think? - Graeme Edge of the Moody Blues - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e