Kevin Katz wrote:
> Routing Table.....by Redhat setup
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> *.*.*.196 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
> *.*.*.197 0.0.0.0 255.255.255.255 UH 0 0 0 eth2
> *.*.*.198 0.0.0.0 255.255.255.255 UH 0 0 0 eth3
> *.*.*.194 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
> *.*.*.192 0.0.0.0 255.255.255.192 U 0 0 0 eth0
> *.*.*.192 0.0.0.0 255.255.255.192 U 0 0 0 eth1
> *.*.*.192 0.0.0.0 255.255.255.192 U 0 0 0 eth2
> *.*.*.192 0.0.0.0 255.255.255.192 U 0 0 0 eth3
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 *.*.*.193 0.0.0.0 UG 0 0 0 eth0
> Hardware
>
> eth0 Link encap:Ethernet HWaddr 00:E0:81:10:26:52
> inet addr:*.*.*.194 Bcast:*.*.*.255 Mask:255.255.255.192
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:319502 errors:0 dropped:0 overruns:0 frame:0
> TX packets:761159 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:11 Base address:0xef80
>
> eth1 Link encap:Ethernet HWaddr 00:10:4B:30:71:9A
> inet addr:*.*.*.196 Bcast:*.*.*.255 Mask:255.255.255.192
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:357558 errors:0 dropped:0 overruns:0 frame:0
> TX packets:8040 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:10 Base address:0xdc00
>
> eth2 Link encap:Ethernet HWaddr 00:50:04:71:4D:20
> inet addr:*.*.*.197 Bcast:*.*.*.255 Mask:255.255.255.192
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:63509 errors:0 dropped:0 overruns:0 frame:0
> TX packets:7217 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:9 Base address:0xd880
>
> eth3 Link encap:Ethernet HWaddr 00:10:4B:30:63:AE
> inet addr:*.*.*.198 Bcast:*.*.*.255 Mask:255.255.255.192
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:13768 errors:0 dropped:0 overruns:0 frame:0
> TX packets:634 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> Interrupt:5 Base address:0xd800
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3924 Metric:1
> RX packets:15246 errors:0 dropped:0 overruns:0 frame:0
> TX packets:15246 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
I'm sorry but this is my first time to see this kind of notation(
*.*.*.196 )
in the routing table. What actual network or subnet address does
*.*.*.196
have? If these addresses are on the same network or subnet, i think you
don't need
*.*.*.192. So you better remove them out unless it is dynamically
discovered(RIP).
Same also with the IP address configured for each interface.
> With this particular setup, almost all traffic, both incomming and
> outgoing, goes through either eth0 or eth1....and what I found, if an arp
> "who-has" request came in for eth3, whose named is www, Linux would reply
> "www is at 00:E0:81:10:26:52" or "www is at 00:10:4B:30:71:9A", when it
> should have replied, "www is at 00:10:4B:30:63:AE"
ARP packets are sent broadcast on the network or subnet. If you have
multiple interfaces attached
on the same network(why?), then they would receive the same ARP packet.
In this case it doesn't matter
which of the interfaces the ARP packet arrived. When the linux-box
receives an ARP request packet, it
simply look the hardware address of the IP address in the ARP packet in
its arp-table. If a hardware
address is found, the linux-box sends back an ARP reply containing the
harware address of the requested
IP address, otherwise is does nothing. I may suggest you configure your
interfaces specifying the
complete IP address (e.g. ifconfig eth0 172.28.52.111 255.255.255.0 gw
172.28.52.91), otherwise i don't
have a clue.
Hope this help.
bunal!
---
Ronnel P. Maglasang
Software Design Eng'ng Department voice : 340-0451
NEC Technologies Phils., Inc. fax : 340-0457
PEZA, Lapulapu City e-mail:
[EMAIL PROTECTED]
Philippines
KNOWLEDGE IS CONTAGIOUS... PASS IT ON...
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
