routes are killing me - how to?

Jer_57 yellowdog-general@lists.terrasoftsolutions.com
Thu Nov 7 15:13:01 2002


Can you do a "netstat -rn" on both machines and post the results.  This will help clear up a lot of the confusion I think.

jer

> 
> From: Stefan Jeglinski <jeglin@4pi.com>
> Date: 2002/11/07 Thu PM 04:55:47 EST
> To: yellowdog-general@lists.terrasoftsolutions.com
> Subject: Re: routes are killing me - how to?
> 
> >You will not have any success with masquerading until you have this issue
> >resolved.
> 
> Agreed. On the Linux box I have:
> 
> eth0      Link encap:Ethernet  HWaddr 00:00:C5:53:8E:45 
>            inet addr:192.168.0.1  Bcast:192.168.0.255  Mask:255.255.255.0
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:0 errors:21675 dropped:0 overruns:0 frame:0
>            TX packets:0 errors:309 dropped:0 overruns:0 carrier:918
>            collisions:0
> 
> eth1      Link encap:Ethernet  HWaddr 00:05:9A:20:02:3A 
>            inet addr:63.220.231.132  Bcast:63.220.231.191  Mask:255.255.255.192
>            UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>            RX packets:69453 errors:2 dropped:0 overruns:0 frame:2
>            TX packets:110560 errors:38 dropped:0 overruns:0 carrier:76
>            collisions:0
> 
> eth1 is physically connected to a switch on the public network. eth0 
> is connected to a hub on the private network. the only box on the 
> private network is an OSX box:
> 
> en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>          inet6 fe80::203:93ff:fe48:e26%en0 prefixlen 64 scopeid 0x4
>          inet 192.168.0.222 netmask 0xffffff00 broadcast 192.168.0.255
>          ether 00:03:93:48:0e:26
>          media: autoselect (100baseTX <half-duplex>) status: active
> 
> So it seems to me, the OSX box and the eth0 NIC are on the same 
> subnet. They are physically connected to one another through the hub 
> and nothing else:
> 
> OSX (192.168.0.222) ----- hub ----- (192.168.0.1) eth0
> 
> They cannot ping one another! But before you say that there must be a 
> problem with hardware, consider that using all of the same pieces, 
> this *works*:
> 
>                +---------------------------------+
>                |  +---------------------------+  |
>                +  |                           |  |
>               hub | +-----------------------+ |  |
> OSX          |   | |                       | |  |
> 63.220.231.x-+   +-+ eth0 (63.220.231.162) | |  |
>                     |                       | +-hub--dslmodem (63.220.231.129)
>                     |                       |   | |
>                     | (63.220.231.132) eth1 +---+ +
>                     |                       |     |
>                     +-----------------------+     |
>                                                   |
>                   other 63.220.231.128/26 IPs ----+
> 
> 
> 
> 
> Stefan Jeglinski
> _______________________________________________
> yellowdog-general mailing list
> yellowdog-general@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-general
>