6 Aug
2013
6 Aug
'13
5:04 a.m.
I think the lack of multicast support in some Linux kernel builds
makes the Perl rip44d fail for some users.
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.
If you're having problems with rip44d not receiving RIP packets, and
you're not one of those having a NAT/DMZ router of some sort in front
of the gateway, please check if your kernel has multicast enabled:
http://unix.stackexchange.com/questions/25872/how-can-i-know-if-ip-multicas…
I can probably add raw socket support to rip44d, mimicking what Marius
did in his C version, to work around it, if this is indeed a problem.
One alternative is to run the C daemon on those systems, of course!
- Hessu, OH7LZB
On Tue, Aug 6, 2013 at 2:08 AM, Brian Rogers <n1uro(a)n1uro.ampr.org> wrote:
On Sat, 2013-08-03 at 11:46 +0300, Marius Petrescu
spake:
I added an option to use raw sockets instead of
multicast to the daemon.
This is needed on systems that do not support multicast properly.
On system where it works, there is no need to upgrade.
Thank you Marius - it's definately now doing what it needs to do! Good
job! With my 10 yr old system running a P-III I'm lucky to have a circa
2009 setup running. I don't know why on earth though this 2.6 kernel
doesn't support multicast.