Wireshark · Wireshark-users: Re: [Wireshark-users] 2 IP addresses on 1 machine

[Juan Perez <jperezsip2008@xxxxxxxxx>]

thank you steve,;
I am using Centos5, the 2 Ips for sure are in the same network. Last octects are: 50 and 51, the network is 48 and the mask is 255.255.255.240.
I will have in production a dedicated machine with 1 IP only, but this is a lab for testing some stuff and both apps have to live in the machine for now.
If I disable eth1 then the app listening in IP 2 does not work properly. As a test, If I disable eth1 and leave eth2 up I can not ping anything from that machine, I have to enable eth1 for the ping to work.

I think that this falls under the realms of the OS more than wireshark. thank you very much guys anyways.

jp





----- Original Message ----
From: Steve Bertrand <steve@xxxxxxxxxx>
To: Community support list for Wireshark <wireshark-users@xxxxxxxxxxxxx>
Sent: Monday, April 20, 2009 11:54:44 AM
Subject: Re: [Wireshark-users] 2 IP addresses on 1 machine

Juan Perez wrote:
> txs Abhik, I had tried that already and the results are the same. also
> the gw would be used for outbound traffic, not inbound right?

If you are truly attempting to use two separate physical interfaces and
put them into the same IP prefix, it will not work the way you expect.

Depending on the OS, the most likely case will be that your PC will
listen for destined to 192.168.1.x/24 on the first interface that was
configured in that subnet.

As a test, disable eth1, and then run tshark on eth2. You should see the
packets end up there at that point.

A q&d physical topology map may help here as well. For instance, are you
running both NICs into a single Layer-2 device? Can you at least post
the last two octets of your real IPs, and include the netmask you are using?

Steve
___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request@xxxxxxxxxxxxx?subject=unsubscribe