On Tue, 18 Dec 2001, Christoph Simon wrote: > On Tue, 18 Dec 2001 14:27:20 -0500 (EST) > mok2 <mok2@xxxxxxxxxxxxxxxxx> wrote: > > > Destination Gateway Genmask Flags Metric Ref Use Iface > > 166.50.32.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 > > 176.30.3.192 0.0.0.0 255.255.255.192 U 0 0 0 eth2 > > 10.2.2.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 176.30.3.193 0.0.0.0 UG 0 0 0 eth2 > > > > eth2 Link encap:Ethernet HWaddr > > inet addr:176.30.3.38 Bcast:176.30.3.255 Mask:255.255.255.192 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:98373 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:116675 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:1015 > > RX bytes:76086367 (72.5 Mb) TX bytes:97127829 (92.6 Mb) > > > > ppp0 Link encap:Point-to-Point Protocol > > inet addr:166.50.33.32 P-t-P:166.50.32.1 Mask:255.255.255.255 > > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > > RX packets:4 errors:1 dropped:0 overruns:0 frame:0 > > TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 > > RX bytes:40 (40.0 b) TX bytes:61 (61.0 b) > > > > the gw with the lowest metric determines which connection will work.. > > i cannot add in both gw and make both connections work at the same time.. > > > > that is my problem.. > > If you try to access 166.50.32.1/32, ppp0 will be used. If you try to > access 10.2.2.0/24, eth0 will be used. In all other cases, eth2 will > be used. This should just work. What do you expect to work and > doesn't? BTW, normally there is no explicit route for lo; the kernel > does know how to deal with the loop back. > i cannot access 166.50.33.32 from the outside
