6 Aug
2013
6 Aug
'13
9:39 p.m.
Double check your reverse path filtering setting? It is now on by default
on newer kernels
This drove me nuts until I figured it out because I could see the multicast
announcements when running tcpdump on the
tunnel interface, but rip44d didn't see them.
In ubuntu look in /etc/sysctl.conf for "rp_filter" settings.
-Neil
On Tue, Aug 6, 2013 at 6:56 AM, Brian Rogers <n1uro(a)n1uro.ampr.org> wrote:
> (Please trim inclusions from previous messages)
> _______________________________________________
> Hello Hessu (and list)
>
> On Tue, 2013-08-06 at 13:04 +0300, Heikki Hannikainen spake:
> > I think the lack of multicast support in some Linux kernel builds
> > makes the Perl rip44d fail for some users.
>
> That's not the case here though. Multicast is enabled and the interfaces
> are also running multicast. I am however behind a NAT router (even
> though it should be moot since I do hear the broadcasts). I'm just
> completely at a loss on my specific issue. netstat -g shows:
>
> tunl0 1 224.0.0.251
> tunl0 1 all-systems.mcast.net
>
> and ifconfig tunl0 shows:
> tunl0 Link encap:IPIP Tunnel HWaddr
> inet addr:44.88.0.9 Mask:255.255.255.0
> UP RUNNING MULTICAST MTU:1480 Metric:1
>
>
> > Linux 2.6 certainly supports multicast, it's been in the kernel for a
> > long while (at least in kernel 1.2 it was there, and probably before
> > that). Some distributions apparently haven't compiled in the multicast
> > code.
>
> I'm using the stock kernel for the distro. If an error popped up for me
> I'd at least know where to look... but since there was no error, nothing
> ever was logged, it simply acted "deaf". Netcat verfied for me that the
> port was indeed open to the interface as well.
>
> If you wish to make a switch to enable raw sockets I'll be willing to
> test it for you.
>
> --
> 73 de Brian Rogers - N1URO
> email: <n1uro(a)n1uro.ampr.org>
> Web: http://www.n1uro.net/
> Ampr1: http://n1uro.ampr.org/
> Ampr2: http://nos.n1uro.ampr.org
> Linux Amateur Radio Services
> axMail-Fax & URONode
> AmprNet coordinator for:
> Connecticut, Delaware, Maine,
> Massachusetts, New Hampshire,
> Pennsylvania, Rhode Island,
> and Vermont.
>