qpimd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [qpimd-users] Interface mismatch: recv PIM pkt from 192.168.1.6 to


From: Everton Marques
Subject: Re: [qpimd-users] Interface mismatch: recv PIM pkt from 192.168.1.6 to 224.0.0.13 on fd=12: recv_ifindex=4 (eth2) sock_ifindex=3 (eth1)
Date: Wed, 15 Apr 2009 18:46:03 -0300

Hi,

On Wed, Apr 15, 2009 at 4:22 AM, Andrew Lunn <address@hidden> wrote:
> 2009/04/15 08:06:07 PIM: Scheduling READ event on IGMP socket fd=11
> 2009/04/15 08:06:07 PIM: Recv IP IGMP pkt size=56 from 192.168.1.1 to 
> 224.0.0.22 on fd=13 on ifindex=3 (sock_ifindex=4)
> 2009/04/15 08:06:07 PIM: Interface mismatch: recv IGMP pkt from 192.168.1.1 
> to 224.0.0.22 on fd=13: recv_ifindex=3 (eth1) s
> ock_ifindex=4 (eth2)
>
> I used tcpdump to look at the packets. They are on the correct
> interface, so this looks like a pimd problem. These packets are on
> eth1, so recv_ifindex (eth1) is correct and sock_ifindex=4 (eth2) is
> wrong.

Yes, I currently face the same behavior here, however it does not prevent the
correct multicasting for me. Of course, it should be tackled at some point.
I've added it as an entry to the TODO list.

Are you able to test with the following tarball? The major change is a
functional
maintenance strategy for the RPF cache. There are several minor corrections,
including a fix for the self-neighboring effect you pointed out.

http://download.savannah.nongnu.org/releases-noredirect/qpimd/qpimd-0.145.tar.gz

Cheers,
Everton




reply via email to

[Prev in Thread] Current Thread [Next in Thread]