Hi,
I have a dual port NIC, and I would like to run ping from port A (eth2) to port B (eth3) on same NIC card, using Linux RH5.3 I run:
ping -I eth2 <eth3-ip>
and I don't receive and pong.
It appears that when an ARP request received on eth3 (I used tcpdump) the system decides not to answer the ARP request, apparently because it's sent from a local IP and it doesn't allow you to "query yourself".

Any ideas how can I make this work? I want to test connectivity between port A and port B (not necessarily ping), how can I do that?

Thanks for your help,
Ali.

Hi Ali,

Thats some wierd behavior, just tested it myself... the only thing I noticed was that it was being logged as a martian, maybe there was no response because it thought the packet was spoofed ?

cheers,

kbp

Thanks kbp,
Yeah it's odd, I also think it's kind of IP layer security that prevents the ARP modules from answering the ARP request. I tried to disable all security services (firewall, iptables, selinux, sysctl) but didn't succeed to make it work. I even tried to trick the ARP table and set a manual entry for port B so the ping will not initiate ARP request (and will send ICMP echo directly) but the arp table won't let me set an entry of an IP that I own.

Any other ideas?

You could try mucking about with kernel/network tuning stuff in /etc/sysctl.conf, I thought it might have been source routing related. I had a little play but didnt have that much time available, good luck

kbp

I would suggest using arping and tcpdump/wireshark for this test.

kbp, already tried playing with sysctl, it didn't help.
TimothyEBaldwin, that would work, but I wanted to show a real connection like ping-pong (or other application) rather than sniffing packets on port B.

Thanks guys.
Ali;

Why?

I think network namespaces can be used to do this.

Well?