Subject: Re: [44net] 44Net Digest, Vol 2, Issue 159 From: sp2lob sp2lob@tlen.pl Date: 10/06/2013 12:43 AM
To: AMPRNet working group 44net@hamradio.ucsd.edu
Hello Rob et al,
In my system I've similar setup.
- tun0 - tunnel to my JNOS
- tunl0 - tunnel to AMPRNet
Both have assigned same IP - 44.165.2.2 I do not observe anything suspicious.
What kind of issue do you encounter, please?
Best regards. Tom - sp2lob
Tom,
Check this: cat /proc/net/igmp
Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 1 V3 010000E0 1 0:00000000 0 3 tunl0 : 2 V3 090000E0 1 0:00000000 0 010000E0 1 0:00000000 0 4 net0 : 1 V3 010000E0 1 0:00000000 0
As you can see, the 224.0.0.9 address is at the tunl0 interface. When I start the daemon after the net0 interface is created (tun0 in your case) the address gets added to net0 only, and not to tunl0. Therefore the daemon does not receive the 224.0.0.9 multicasts (only 224.0.0.1 which everyone gets).
I don't know what the algorithm is to select the interface when there are multiple interfaces with the same address. It looks like it picks the one with the highest index. The function to add a multicast address cannot specify the interface directly.
Rob
Hello Rob et al,
Quote: "...by default mcast routes will be associated with an interface the kernel picks (usually the first to come up)."
There is something what you're looking for, I believe. Small, nifty & powerfull program to install: *smcroute*
The *smcroute* http://www.cschill.de/smcroute/ utility provides a command line interface to manipulate the multicast routing tables via a method other than *mrouted*.
Before:
root@lts:~# cat /proc/net/igmp Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 2 V2 010000E0 1 0:00000000 1 4 tunl0 : 1 V3 010000E0 1 0:00000000 0 root@lts:~#
To *join* multicast group:
root@lts:~# smcroute -j eth0 224.0.0.9
After:
root@lts:~# cat /proc/net/igmp Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 3 V2 090000E0 1 1:0000002D 1 010000E0 1 0:00000000 1 4 tunl0 : 1 V3 010000E0 1 0:00000000 0 root@lts:~#
To *leave* multicast group:
root@lts:~# smcroute -l eth0 224.0.0.9
Give some feedback after you check this feature, please.
Best regards. Tom - sp2lob
Hello Rob et al,
Quote: "...by default mcast routes will be associated with an interface the kernel picks (usually the first to come up)."
There is something what you're looking for, I believe. Small, nifty & powerfull program to install: *smcroute*
The *smcroute* http://www.cschill.de/smcroute/ utility provides a command line interface to manipulate the multicast routing tables via a method other than *mrouted*.
Before:
root@lts:~# cat /proc/net/igmp Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 2 V2 010000E0 1 0:00000000 1 4 tunl0 : 1 V3 010000E0 1 0:00000000 0 root@lts:~#
To *join* multicast group:
root@lts:~# smcroute -j eth0 224.0.0.9
After:
root@lts:~# cat /proc/net/igmp Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 3 V2 090000E0 1 1:0000002D 1 010000E0 1 0:00000000 1 4 tunl0 : 1 V3 010000E0 1 0:00000000 0 root@lts:~#
To *leave* multicast group:
root@lts:~# smcroute -l eth0 224.0.0.9
Give some feedback after you check this feature, please.
Best regards. Tom - sp2lob
Hello Rob et al,
Quote: "...by default mcast routes will be associated with an interface the kernel picks (usually the first to come up)."
There is something what you're looking for, I believe. Small, nifty & powerfull program to install: *smcroute*
The *smcroute* http://www.cschill.de/smcroute/ utility provides a command line interface to manipulate the multicast routing tables via a method other than *mrouted*.
Before:
root@lts:~# cat /proc/net/igmp Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 2 V2 010000E0 1 0:00000000 1 4 tunl0 : 1 V3 010000E0 1 0:00000000 0 root@lts:~#
To *join* multicast group:
root@lts:~# smcroute -j eth0 224.0.0.9
After:
root@lts:~# cat /proc/net/igmp Idx Device : Count Querier Group Users Timer Reporter 1 lo : 1 V3 010000E0 1 0:00000000 0 2 eth0 : 3 V2 090000E0 1 1:0000002D 1 010000E0 1 0:00000000 1 4 tunl0 : 1 V3 010000E0 1 0:00000000 0 root@lts:~#
To *leave* multicast group:
root@lts:~# smcroute -l eth0 224.0.0.9
Give some feedback after you check this feature, please.
Best regards. Tom - sp2lob
Rob,
By mistake unnecessary link http://www.cschill.de/smcroute/ got pasted into previous e-mail.
For instance, on Debian like systems apt-get install smcroute will suffice.
Best regards. Tom - sp2lob
Rob et al,
It appears that multicast routing isn't compiled in the Raspbian kernel 3.6.11+, at least mine.
Therefore smcroute _will not_ work - pity...
Best regards. Tom - sp2lob
Hello Tom,
So following the recommendations here - http://unix.stackexchange.com/questions/25872/how-can-i-know-if-ip-multicast... , your RPi image doesn't have Multicast in your kernel? Strange.. my RPi "Linux rpi 3.6.11+ #474 PREEMPT Thu Jun 13 17:14:42 BST 2013 armv6l GNU/Linux" kernel has it.
--David
On 10/08/2013 06:20 AM, sp2lob wrote:
(Please trim inclusions from previous messages) _______________________________________________ Rob et al,
It appears that multicast routing isn't compiled in the Raspbian kernel 3.6.11+, at least mine.
Therefore smcroute _will not_ work - pity...
Best regards. Tom - sp2lob
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
-
David Ranch -
Rob Janssen -
sp2lob -
sp2lob＠tlen.pl