Re: [omping] Always got a "omping: Multiple local interfaces match parameters" error
Hangbin Liu napsal(a):
On Thu, 2011-07-07 at 09:48 +0200, Jan Friesse wrote:
> Hi Hangbin,
> can you please rerun omping with -vvv parameter? This will give you a
> lot of debug messages and this should help us to identify problem.
>
> But if not bug, it really looks like you have multiple NICs with same IP
> (ether 10.16.40.142 or 10.16.42.40).
>
Jan,
With "-vvv" find the reason . I add a br0 on eth0 , so there is a
fe80::62eb:69ff:feba:c932 on both eth0 and br0 . delete the fe80 addr on
eth0 and omping going on well .
Great, but one extra question. Did you had 10.16.40.142 on eth0 and br0
too, or not? Because if not, and omping was complaining, it is bug.
Btw. which version are you using?
But I can't got any response msg from other remote hosts except
from
myself. Doesn't understand multicast clearly , can you tell me why ?
Thanks.
Ok, so basic usage is following.
Let's say you want to test connection between two computers (what you
probably want) with IP 10.16.40.142 and 10.16.42.40
Only thing you must to is to run
omping 10.16.40.142 10.16.42.40
on both of computers. This is because normal ping is handled by OS (in
other words you have server running all the time) but ssmping (protocol
used by onping) is not running by OS, so you must run server (omping is
behaving both as client and server)
/* without bridge , just an eth0 */
# omping 10.16.40.142 10.16.42.40
10.16.42.40 : waiting for response msg
10.16.42.40 : waiting for response msg
10.16.42.40 : waiting for response msg
10.16.42.40 : waiting for response msg
10.16.42.40 : waiting for response msg
^C
10.16.42.40 : response message never received
So here on 10.16.42.40 omping is not running.
# omping 10.16.40.142 224.0.0.1
224.0.0.1 : waiting for response msg
224.0.0.1 : waiting for response msg
224.0.0.1 : waiting for response msg
224.0.0.1 : waiting for response msg
^C
224.0.0.1 : response message never received
This is really bug and omping should complain, because 224.0.0.1 is
multicast address.
# omping 10.16.40.142 10.16.40.142
10.16.40.142 : waiting for response msg
10.16.40.142 : joined (S,G) = (*, 232.43.211.234), pinging
10.16.40.142 : unicast, seq=1, size=69 bytes, dist=0, time=0.014ms
10.16.40.142 : multicast, seq=1, size=69 bytes, dist=0, time=0.024ms
I'm wondering that this works, but ... ya it make sense. Since omping
0.0.2 same effect gives you omping 10.16.40.142. This is good for
testing local firewall, because at least on Fedora/RHEL you will never
get multicast reply with default firewall on.
Regards,
Honza