New subject: 44Net Digest, Vol 2, Issue 158

5 Oct 2013

...
  Subject:
 Re: [44net] 44Net Digest, Vol 2, Issue 157
 From:
 sp2lob &lt;sp2lob(a)tlen.pl&gt;
 Date:
 10/03/2013 11:03 PM

 To:
 AMPRNet working group &lt;44net(a)hamradio.ucsd.edu&gt;

 Rob,

 I have already answer for you.

 Yes, my Pi is running Raspbian 3.6.11+ #538
 PREEMPT Fri Aug 30 20:42:08 BST 2013 armv6l
 updated&upgraded as often as possible.

 Line from config.gz file you're asking about is as follow:
 #CONFIG_IP_MROUTE is not set

 But here is my AMPRNet tunnel interface:

 tunl0  Link encap:UNSPEC
            inet addr: 44.165.2.2 Mask: 255.255.255.248
            UP RUNNING NOARP MULTICAST MTU:1480 Metric:1

 I've also 3 ax ifces, 3 nr ifces, 1 rose ifce and tun0 ifce from linux to my JNOS.

 Traffic flows in both directions IN&OUT just fine.

 Best regards.
 Tom - sp2lob 
Hi Tom,

Well, that is the same as what I have here except there is no MULTICAST on
my tunl0 interface.   The flag is only there on my eth0 interface.
The kernel is the same version, config of that MROUTE option is also the same.

Did you issue a command to get that MULTICAST on tunl0 switched on?
Or is that supposed to be enabled by the application, rip44d in this case?
I use this:

ip addr add 44.137.40.2/32 dev tunl0
ip link set dev tunl0 up

maybe I need "ip link set dev tunl0 multicast on"?

That could be something to try...   tomorrow I will add that command and change
the ampr-ripd to use multicast socket instead of raw, and reboot to see what happens.

Rob

Re: [44net] 44Net Digest, Vol 2, Issue 158