Just to note it is very common to have multiple interfaces going to the same switch especially when talking about an enterprise class one like the 6509. I would suspect that the would connect to separate VLANs although it can work fine on the same VLAN but that's generally bad practice. There are also of course teaming configurations where you have multiple interfaces connecting to the same swtich for throughput or redundancy but thats not what we are discussing here.<br>
<br>--j<br><br><div class="gmail_quote">On Tue, Feb 17, 2009 at 10:00 PM, John Gateley <span dir="ltr"><<a href="mailto:tclug@jfoo.org">tclug@jfoo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Venkat Chandra wrote:<br>
> auto eth0<br>
> iface eth0 inet static<br>
> address 10.19.175.242<br>
</div><div class="Ih2E3d">> gateway 10.19.175.241<br>
><br>
</div><div class="Ih2E3d">> auto eth1<br>
> iface eth1 inet static<br>
> address 192.168.164.2<br>
</div> > ...<br>
<div class="Ih2E3d">> The network cables from these two interfaces terminate on a Cisco 6509<br>
> switch.<br>
<br>
</div>This is bizarre. Why are both cables going to the same switch?<br>
Can you get another switch and create two "proper" sub-nets, one<br>
for the 10.x segment and one for the 192.x segment? Then make sure<br>
routing on the host is set up properly so that replies get routed<br>
to the right interface?<br>
<div class="Ih2E3d"><br>
> I can run tcpdump on the<br>
> interfaces separately and I can see ICMP Requests coming in on both the<br>
> interfaces but only one of the interfaces responds with an ICMP Reply.<br>
<br>
</div>An explicit dump would be interesting, and in particular to see if an<br>
ICMP request comes in the 192 interface and the reply goes out the 10.x<br>
interface.<br>
<br>
I'm not an expert, but what you are doing here seems prone to problems<br>
at best, and flat out wrong at worst.<br>
<font color="#888888"><br>
j<br>
</font><div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota<br>
<a href="mailto:tclug-list@mn-linux.org">tclug-list@mn-linux.org</a><br>
<a href="http://mailman.mn-linux.org/mailman/listinfo/tclug-list" target="_blank">http://mailman.mn-linux.org/mailman/listinfo/tclug-list</a><br>
</div></div></blockquote></div><br>