route syntax
Jeff Vian
jvian10 at charter.net
Mon Jul 11 15:41:37 UTC 2005
On Mon, 2005-07-11 at 04:57 -0700, THUFIR HAWAT wrote:
> On 7/10/05, Michael Schwendt <mschwendt.tmp0501.nospam at arcor.de> 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 at arrakis init.d]#
> [root at arrakis init.d]# date
> Mon Jul 11 12:27:44 IST 2005
> [root at arrakis init.d]# whoami
> root
> [root at arrakis init.d]# pwd
> /etc/init.d
> [root at 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
You now show eth1 as IP 192.168.0.0 network and 192.168.1.0 network on
eth0. Thus the NICs are on different subnets and it works as designed.
> [root at 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 at 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
> [root at 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 at 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 at 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 :)
>
>
> anyhow, I'm now satisfied that the D-Link NIC works under
> linux. I've already satisfied myself that the built-in
> NIC works under linux.
>
> I'm off to setup masquerading, as per
> http://www.tldp.org/HOWTO/Masquerading-Simple-HOWTO/intro.html>.
> The only wrinkle is that I'm using an asus wl-330g w-fi
> network adapter,
> <http://usa.asus.com/prog/spec.asp?m=WL-330g&langs=09>,
> and while it can be configured from linux it's easier
> to configure it from windows 2000, since arrakis is dual
> boot.
>
> so, I'll configure the asus adapter for arrakis from
> windows 2000. The adapter, I assume, will have to
> connect to the D-Link NIC because that's the NIC
> it connects to under windows.
>
> Anyhow, thank you for the help with this thread and
> many previous :)
>
>
> -Thufir
>
More information about the fedora-list
mailing list