I wish I could point out the source of your problem, but frankly, this
latest report leaves me stumped. I am particularly puzzled by this
combination of items:
(this from your latest e-mail)
ip route show (SuSE):
192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2
default via 192.168.1.254 dev eth0
and (this from the attachment to your prior e-mail)
SuSE#>ping -c 1 192.168.1.254
PING 192.168.1.254 (192.168.1.254) from 192.168.1.2 : 56(84) bytes
of data.
From 192.168.1.2: icmp_seq=1 Destination Host Unreachable
From 192.168.1.2 icmp_seq=1 Destination Host Unreachable
Since the SuSE host (192.168.1.2) has a route to the network that contains
192.168.1.254, I don't understand why it reports "Destination Host
Unreachable". Perhaps someone else here can spot whatever I am overlooking.
But I've run out of ideas. Sorry.
At 05:10 AM 10/7/02 -0400, Quan Si Kwon wrote:
>Thanks again for the speedy response!
>
>Okay! the routing tables of the Bering and SuSE hosts are as follows:
>
>ip route show (Bering):
>65.95.176.1 dev ppp0 proto kernel scope link src 65.95.176.89
>192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254
>default via 65.95.176.1 dev ppp0
>
>ip route show (SuSE):
>192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.2
>default via 192.168.1.254 dev eth0
>
>
>The oddity of the Win2K host's routing table is probably because of the
>gateway for DFE-538TX (192.168.72.77) was 192.168.1.10, the IP of the
>other card (DFE-530TX). Here I thought the two cards in the Win2K host are
>in different subnet: 192.168.72.77/24 and 192.168.1.10/24, I must route
>all traffic from 192.168.72.0/24 via 192.168.72.77/24 using
>192.168.1.10/24? I have since changed both cards' gateway to 192.168.1.254
>and come up the following results using ping and route print:
>
>ping -c 2 192.168.1.254:
>Pinging 192.168.1.254 with 32 bytes of data:
>Request timed out.Request timed out.
>Ping statistics for 192.168.1.254: Packets: Sent = 2, Received = 0,
>Lost = 2 (100% loss),Approximate round trip times in
>milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
>route print:
>===========================================================================
>Interface List
>0x1 ........................... MS TCP Loopback interface
>0x1000003 ...00 05 5d f5 f9 bf ...... D-Link DFE-530TX PCI Fast Ethernet
>Adapter
>0x1000004 ...00 50 ba 5b dc 86 ...... D-Link DFE-538TX 10/100 Adapter
>===========================================================================
>===========================================================================
>Active Routes:
>Network Destination Netmask Gateway Interface Metric
> 0.0.0.0 0.0.0.0 192.168.1.254 192.168.72.77 1
> 0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.10 1
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.10 192.168.1.10 1
> 192.168.1.10 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.1.255 255.255.255.255 192.168.1.10 192.168.1.10 1
> 192.168.72.0 255.255.255.0 192.168.72.77 192.168.72.77 1
> 192.168.72.77 255.255.255.255 127.0.0.1 127.0.0.1 1
> 192.168.72.255 255.255.255.255 192.168.72.77 192.168.72.77 1
> 224.0.0.0 224.0.0.0 192.168.1.10 192.168.1.10 1
> 224.0.0.0 224.0.0.0 192.168.72.77 192.168.72.77 1
> 255.255.255.255 255.255.255.255 192.168.1.10 192.168.1.10 1
>Default Gateway: 192.168.1.254
>===========================================================================
>Persistent Routes:
> None
--
-------------------------------------------"Never tell me the odds!"--------
Ray Olszewski -- Han Solo
Palo Alto, California, USA [EMAIL PROTECTED]
-------------------------------------------------------------------------------
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html
