mping discovery error on centos...

Issues related to configuring your network
maheshv76
Posts: 7
Joined: 2017/05/08 05:21:39

Re: mping discovery error on centos...

Post by maheshv76 » 2017/05/11 18:04:03

How to avoid binding it to loopback interface?

do we need to do ifconfig eth0 and get the IP address ? COnfigure the xml file to include the IP address directly instead of environmental variable.

bind_addr="196.40.0.5" break_on_coord_rsp="true"
ip_ttl="2 for scenario 1 and

bind_addr="196.40.0.6" break_on_coord_rsp="true"
ip_ttl=2 for scenario 2.

thanks for the quick response, would appreciate it.

ethereal is not able to find the network packets.

mahesh.

aks
Posts: 3073
Joined: 2014/09/20 11:22:14

Re: mping discovery error on centos...

Post by aks » 2017/05/12 22:08:39

How to avoid binding it to loopback interface?
Quite simple really, don't bind to 127.0.0.1/8. Bind to the "real" interfaces.
do we need to do ifconfig eth0 and get the IP address
Eh? The IP addresses can be displayed with ip addr sh (ifconfig is so depreciated now).
COnfigure the xml file to include the IP address directly instead of environmental variable.
Well that depends on the application, if the the launch of the application can read the specific environmental variables that the vendor says they will read. If there are no environment variables specified with the launch then the application will only inherit environment variables of the thing that launches it (usually systemd or init, in CentOS 7, systemd). When troubleshooting it is often wise to be explicit and not to rely on something (that you can eb specific about) being done by some other program (that you may or may not understand).

I do not see any of:
bind_addr="196.40.0.5" break_on_coord_rsp="true"
ip_ttl="2 for scenario 1 and

bind_addr="196.40.0.6" break_on_coord_rsp="true"
ip_ttl=2 for scenario 2.
in the configuration files you've posted (and that would really help with context). Are you leaving details out? That's not a good way to ask for help! Please post the complete configuration if you are!
ethereal is not able to find the network packets.
Ethereal is so over, it's now wireshark (and has been for quite some time now, I'm thinking about 10 years now, it was a commercial conflict with Gerald .. now how's that for name dropping!). If you are really using etheral, then I would be surprised it works at all! You can also use the nifty tcpdump program. If you can't see the packets on the wire (assuming all "normal" networking scenarios), then the packets, in all probability, are not going onto the wire.

Post Reply