Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I'm having a problem on my cluster and I'm being told that the reason why is that my one of my machines is using V2 while the rest are using V3. I've used the same disks to do all the installs so I don't know how they could be different. I don't see an RPM for IGMP, so how do you upgrade it? Thanks!
It's clear that it says it supports version 3 (V3 near lo). Why eth0 and eth1 use version 2? Good question. Probably it didn't receive proper replies just after boot and made a fallback to version 2. There's a method to force it to version 3 without reboot. Example:
/sbin/sysctl -w net.ipv4.conf.eth0.force_igmp_version=3
/proc/net/igmp should then show V3 for eth0. Use similar command for eth1 and check if it works correctly (you may dump some traffic using tcpdump to see if version 3 is really used).
Nope, I don't think that you need an upgrade. You have version 3 support (at least it's saying so). I'm wondering if you have experience with ethereal or any other sniffer? It may be a good idea to run one between the hosts and see what's comming in just before reboot (especially: see IGMP version used).
Snort is not a sniffer (well..it can work as a sniffer, but that would be an overkill). I recommend ethereal (graphical). It also has console mode. But that's a nice tool for analyzing the trace file on your desktop machine. To get the traffic you can just use tcpdump. The command will be something like
tcpdump -i eth0 -w output.log
Use the right interface name for the one you want to sniff on. When you think it's done stop tcpdump (ctrl+c) and copy the file to your desktop machine when you can look into it.