Am Mo, den 11.07.2005 schrieb THUFIR HAWAT um 13:57: > 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 :) Attention! You changed something! > I pinged caladan from the arrakis D-Link NIC with the following > setup: > [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 Hope you face the different IP/Net of eth0. And be aware that this is NO private IP address space IP. It is a public net: $ whois 192.169.1.0 [Querying whois.arin.net] [whois.arin.net] OrgName: RGnet, LLC OrgID: RGNETI-1 Address: 5147 Crystal Springs Drive NE City: Bainbridge Island StateProv: WA PostalCode: 98110 Country: US NetRange: 192.169.0.0 - 192.169.1.255 CIDR: 192.169.0.0/23 NetName: PSG169 NetHandle: NET-192-169-0-0-1 Parent: NET-192-0-0-0-0 NetType: Direct Assignment NameServer: PSG.COM NameServer: NS0.REM.COM Comment: RegDate: 2005-04-12 Updated: 2005-04-12 192.168.1.0/24 for eth0 should work too and uses the private address space. > 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 eth0 now sits in a different net than eth1 and different than your previous setup. > [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 > 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 Can't work as the IP isn't existing in your network. > I have no idea why that works, but it does :) I think I you know now. > -Thufir Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 14:03:41 up 15 days, 20:55, load average: 0.21, 0.30, 0.38
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
