THUFIR HAWAT wrote:
On 7/10/05, Michael Schwendt <mschwendt.tmp0501.nospam@xxxxxxxx> wrote:
On Mon, 11 Jul 2005 04:09:40 +0200, Alexander Dalloz wrote:
...
According to the current routing table, both eth0 and eth1 point to
network 192.168.0.0, which is a problem for traffic that is supposed
to reach eth1.
...
well, I don't know why it works, but it does :)
I pinged caladan from the arrakis D-Link NIC with the following
setup:
from arrakis:
[root@arrakis init.d]#
[root@arrakis init.d]# date
Mon Jul 11 12:27:44 IST 2005
[root@arrakis init.d]# whoami
root
[root@arrakis init.d]# pwd
/etc/init.d
[root@arrakis init.d]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
192.169.1.0 * 255.255.255.0 U 0 0 0 eth0
[root@arrakis init.d]# ./network restart
Shutting down interface eth0: [ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Disabling IPv4 packet forwarding: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth1: [ OK ]
[root@arrakis init.d]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
192.169.1.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1
Your routing table has changed (for the better). eth0 and eth1 are now
in separate subnets, with appropriate routes.
eth0 for 192.168.1.0/24
eth1 for 192.169.0.0/24
[root@arrakis init.d]# ping 192.168.0.3
PING 192.168.0.3 (192.168.0.3) 56(84) bytes of data.
64 bytes from 192.168.0.3: icmp_seq=0 ttl=128 time=1.59 ms
64 bytes from 192.168.0.3: icmp_seq=1 ttl=128 time=0.481 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=128 time=0.472 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=128 time=0.487 ms
64 bytes from 192.168.0.3: icmp_seq=4 ttl=128 time=0.467 ms
--- 192.168.0.3 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4010ms
rtt min/avg/max/mdev = 0.467/0.699/1.590/0.445 ms, pipe 2
[root@arrakis init.d]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:E6:A0:24:27
inet addr:192.169.1.2 Bcast:192.169.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:e6ff:fea0:2427/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:4718 (4.6 KiB)
Interrupt:5 Base address:0xd400
eth1 Link encap:Ethernet HWaddr 00:0D:88:37:FA:22
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:88ff:fe37:fa22/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:182 errors:13 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22954 (22.4 KiB) TX bytes:6884 (6.7 KiB)
Interrupt:5 Base address:0xd000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:139 errors:0 dropped:0 overruns:0 frame:0
TX packets:139 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:13021 (12.7 KiB) TX bytes:13021 (12.7 KiB)
[root@arrakis init.d]#
from caladan:
C:\>ping 192.168.0.2
Pinging 192.168.0.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>ping 192.168.0.1
Pinging 192.168.0.1 with 32 bytes of data:
Reply from 192.168.0.1: bytes=32 time<10ms TTL=64
Reply from 192.168.0.1: bytes=32 time<10ms TTL=64
Reply from 192.168.0.1: bytes=32 time<10ms TTL=64
Reply from 192.168.0.1: bytes=32 time<10ms TTL=64
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\>
C:\>ipconfig /all
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : CALADAN
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI
For Complete PC Management NIC (3C905C-TX)
Physical Address. . . . . . . . . : 00-50-DA-68-8C-B2
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Monday, July 11, 2005 4:33:23
AM
Lease Expires . . . . . . . . . . : Monday, July 18, 2005 4:33:23
AM
C:\>
I have no idea why that works, but it does :)
Me neither. What's the output of "netstat -rn" on caladan?
Paul.
