routes are killing me - how to?

[Bill Fink]

On Thu Nov 7 2002, Stefan Jeglinski wrote:

> 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

Hi Stefan,

The <half-duplex> above may be a problem.  Normally this should be
<full-duplex>.  If the Linux box is full duplex (check "dmesg | grep -i eth"),
this could cause problems.

Another possibility is that there is firewall software running on the
MacOS X box, which could possibly have the symptom of allowing your
real IP address to work, but not work when using a private 192.168.0
IP address.

						-Hope this helps

						-Bill