qpimd-users
[Top][All Lists]
Advanced

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

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


From: Andrew Lunn
Subject: [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 09:22:36 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

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.

eth0      Link encap:Serial Line IP  
          NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:256 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:5 

eth1      Link encap:Ethernet  HWaddr FE:FE:00:00:01:01  
          inet addr:192.168.1.1  Bcast:192.168.1.3  Mask:255.255.255.252
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:125 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:10216 (9.9 KiB)  TX bytes:8834 (8.6 KiB)
          Interrupt:5 

eth2      Link encap:Ethernet  HWaddr FE:FE:00:00:01:02  
          inet addr:192.168.1.5  Bcast:192.168.1.7  Mask:255.255.255.252
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:18 errors:0 dropped:0 overruns:0 frame:0
          TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:994 (994.0 b)  TX bytes:4796 (4.6 KiB)
          Interrupt:5 

eth10     Link encap:Ethernet  HWaddr 7A:02:C9:C1:65:BF  
          inet addr:192.168.41.253  Bcast:192.168.41.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:35 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:6017 (5.8 KiB)  TX bytes:0 (0.0 b)
          Interrupt:5 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

pimd.conf contains

interface eth1
 ip pim ssm
 ip igmp

interface eth2
 ip pim ssm
 ip igmp

I tried adding eth0, but that made no difference.

At startup it logs:

2009/04/15 08:06:06 PIM: Quagga 0.99.11 pimd 0.144 starting, VTY interface at 
port TCP 2611
2009/04/15 08:06:06 PIM: PIM_MOTD_VERSION: adding pimd version to default MOTD
2009/04/15 08:06:06 PIM: PIM_ZCLIENT_DEBUG: zclient debugging is supported, 
mode is OFF (see option -Z)
2009/04/15 08:06:06 PIM: PIM_CHECK_RECV_IFINDEX_SANITY: will match socket 
ifindex against recv ifindex
2009/04/15 08:06:06 PIM: PIM_USE_QUAGGA_INET_CHECKSUM: using Quagga's builtin 
checksum
2009/04/15 08:06:06 PIM: zclient update contacting ZEBRA daemon at socket UNIX 
/usr/local/run/zserv.api
2009/04/15 08:06:06 PIM: pim_zebra_init: zclient update socket initialized
2009/04/15 08:06:06 PIM: zclient_lookup_sched_now: zclient lookup immediate 
connection scheduled
2009/04/15 08:06:06 PIM: zclient_lookup_new: zclient lookup socket initialized
2009/04/15 08:06:06 PIM: zclient_lookup_connect: FIXME blocking connect: 
zclient_socket_un()
2009/04/15 08:06:06 PIM: pim_zebra_if_add: eth0 index 2 flags 128 metric 1 mtu 
1500 operative 0
2009/04/15 08:06:06 PIM: pim_zebra_if_add: eth1 index 3 flags 69699 metric 1 
mtu 1500 operative 1
2009/04/15 08:06:06 PIM: pim_zebra_if_address_add: eth1 connected IP address 
192.168.1.1/30
2009/04/15 08:06:06 PIM: Socket fd=11 joined group 224.0.0.1 on interface 
address 192.168.1.1
2009/04/15 08:06:06 PIM: Socket fd=11 joined group 224.0.0.22 on interface 
address 192.168.1.1
2009/04/15 08:06:06 PIM: Creating IGMP socket fd=11 for address 192.168.1.1 on 
interface eth1
2009/04/15 08:06:06 PIM: Scheduling READ event on IGMP socket fd=11
2009/04/15 08:06:06 PIM: Querier 192.168.1.1 scheduling 31-second (startup) 
TIMER event for IGMP query on fd=11
2009/04/15 08:06:06 PIM: Socket fd=12 joined group 224.0.0.13 on interface 
address 192.168.1.1
2009/04/15 08:06:06 PIM: Scheduling READ event on PIM socket fd=12
2009/04/15 08:06:06 PIM: Scheduling 1241 msec triggered hello on interface eth1
2009/04/15 08:06:06 PIM: pim_zebra_if_add: eth2 index 4 flags 69699 metric 1 
mtu 1500 operative 1
2009/04/15 08:06:06 PIM: pim_zebra_if_address_add: eth2 connected IP address 
192.168.1.5/30
2009/04/15 08:06:06 PIM: Socket fd=13 joined group 224.0.0.1 on interface 
address 192.168.1.5
2009/04/15 08:06:06 PIM: Socket fd=13 joined group 224.0.0.22 on interface 
address 192.168.1.5
2009/04/15 08:06:06 PIM: Creating IGMP socket fd=13 for address 192.168.1.5 on 
interface eth2
2009/04/15 08:06:06 PIM: Scheduling READ event on IGMP socket fd=13
2009/04/15 08:06:06 PIM: Querier 192.168.1.5 scheduling 31-second (startup) 
TIMER event for IGMP query on fd=13
2009/04/15 08:06:06 PIM: Socket fd=14 joined group 224.0.0.13 on interface 
address 192.168.1.5

           Andrew




reply via email to

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