Bob, thanks for explaining in detail WHAT is going on before suggesting HOW to fix it!
'route' seems to reveal the problem -- I have 3 clips attached (plus 2 from 'routetrace'). Interestingly, while pppd is running, a restart of eth0 shows: "RTNETLINK answers: File exists" My kppp 2.4.1 was set to its defaults: * default gateway, and * assign default route to this gateway When I began to educate myself about how to add/del entries in the routing table, I realized that the modem user has to be root in order to do this (not very elegant - running a cron job as root every minute to check things isn't that elegant either) ... so I'll sleep over it unless you have a straight forward suggestion ............................... Horst. AT BOOT: Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 STARTING PPP BEFORE KILLING ETH0: Destination Gateway Genmask Flags Metric Ref Use Iface 206.163.184.195 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 (the failing routetrace clip follows below) RE-STARTING ETH0 WHILE PPP IS WORKING: Destination Gateway Genmask Flags Metric Ref Use Iface 206.163.184.193 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 206.163.184.193 0.0.0.0 UG 0 0 0 ppp0 (currently I don't have another box on my (non-existing)LAN to check if eth0 is really working) Since you asked for routetrace, while not working: 1 192.168.1.11 2997.988 ms !H 2999.786 ms !H 2999.924 ms !H and with a working connection: 1 206.163.184.193 137.643 ms 129.836 ms 129.904 ms 2 206.163.184.222 129.897 ms 129.941 ms 131.053 ms 3 206.163.183.229 130.869 ms 127.891 ms 129.974 ms 4 157.238.26.161 129.896 ms 140.073 ms 129.771 ms 5 129.250.55.117 170.058 ms 149.834 ms 159.950 ms 6 129.250.30.145 189.935 ms 169.899 ms 149.913 ms 7 129.250.3.37 159.997 ms 160.124 ms 139.687 ms 8 129.250.9.58 169.927 ms 169.998 ms 199.837 ms 9 144.232.6.118 159.998 ms 139.878 ms 139.941 ms 10 160.81.36.90 142.231 ms 147.606 ms 150.078 ms 11 207.189.191.9 159.768 ms 159.930 ms 160.000 ms 12 207.189.137.45 179.888 ms 159.963 ms 169.909 ms ####################################################### On Mon, 26 Nov 2001, Bob Miller wrote: > Horst Lueck wrote: > > > QUESTION: > > Which process/conf-file is responsible for directing a request for an > > external connection to ppp0, while, lets say 'ping 192.168.1.xxx' goes > > through eth0 ? > > (I have tried subnet mask 255.255.255.0 and 255.255.0.0) > > Hi, Horst. > > Whenver the kernel has an outgoing IP packet to send, it looks in its > routing table. You can view the routing table type by typing > "/sbin/route -n". > > Here's what it shows on my workstation. > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use Iface > 192.168.0.4 0.0.0.0 255.255.255.255 UH 0 0 0 eth0 > 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 > 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo > 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 > > That's not very interesting, because my workstation only has one > network interface, eth0. When I send a packet, the kernel looks for > the routing table that best matches the packet's destination address > and sends the packet through the listed interface to the listed > gateway, or directly to the destination if there is no gateway. > > The line with Destination 0.0.0.0 and Genmask 0.0.0.0 is known as the > Default Route. Whenever a packet doesn't match any of the other > routing table entries, it is sent through the Default Route. In my > routing table above, the Default Route is the last line. > > If I sent a packet to 207.189.137.45, the only match would be the > default route, and the packet would be sent through eth0 to the > gateway, 192.168.0.1. > > If I sent a packet to 192.168.0.44, the best match would be the third > line (Destination = 192.168.0.0, Genmask = 255.255.255.0), so the > packet would be sent directly to 192.168.0.44 through eth0. > > If you look at your routing table while your PPP link is up, I think > you'll see that the default route (destination 0.0.0.0, Genmask > 0.0.0.0) points through eth0 to some gateway on the 192.168.0.X > network. > > So what should you do? In my version of kppp (warning, I run a very > old version of KDE), there is a panel on the edit dialog called > "Gateway". There is a checkbox on that panel labeled "Assign the > Default Route to this Gateway". I would check that box. Then redial > your ISP. > > But that's for kppp 1.6.22. I don't know how the current version > works. > > If that doesn't solve your problem, please write back with the output > of "/sbin/route -n" and "/sbin/traceroute -n 207.189.137.45". > > -- > Bob Miller K<bob> > kbobsoft software consulting > http://kbobsoft.com [EMAIL PROTECTED] >
