Re: [PATCH] lanstreamer: IBM LanStreamer and failing multicast reception

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

 



Bjørn Mork <bjorn@xxxxxxx> writes:

> The problem is that this command also make the Cisco routers
> *transmit* the OSPF IP multicasts as layer 2 multicasts, which don't
> show up at canardo.  They do however show up at the other Cisco router
> (so they can still establish an OSPF neighbourship with eachother),
> and also on a ibmtr_cs PCMCIA card I've got.  I've not yet tried
> quagga over the PCMCIA card, but will do that as soon as I get a
> chance.

As expected.  This is from quagga running on my laptop with tr0 being
the 3c389 card:

obelix# sh ip ospf neighbor 

Neighbor ID     Pri   State           Dead Time   Address         Interface           RXmtL RqstL DBsmL
192.168.14.68     1   Full/DR         00:00:38    10.4.0.1        tr0:10.4.0.3        0     0     0
192.168.14.1      1   Init/DROther    00:00:39    10.4.0.2        tr0:10.4.0.3        0     0     0
192.168.14.67     1   Full/Backup     00:00:36    10.4.0.5        tr0:10.4.0.3        0     0     0


The two neighbours that are up are the two Cisco 2612 routers, while
the third neighbour, which is permanent in Init state, is quagga on
the lanstreamer box.

And tcpdump does of course show multicast packets from all 4 sources:

obelix:/etc/quagga# tcpdump -nevv -s4000 -itr0
tcpdump: listening on tr0, link-type IEEE802 (Token ring), capture size 4000 bytes
21:20:47.747545 10 40 00:a0:4c:08:71:81 c0:00:00:04:00:00 110: LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 26617, offset 0, flags [none], length: 88) 10.4.0.5 > 224.0.0.5: OSPFv2, Hello (1), length: 68 [len 56]
21:20:48.781721 10 40 00:a0:24:f9:d5:ef c0:00:00:04:00:00 100: Single-route Forward (2052) LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 63957, offset 0, flags [none], length: 76) 10.4.0.3 > 224.0.0.5: OSPFv2, Hello (1), length: 56
        Router-ID: 10.4.0.3, Backbone Area, Authentication Type: none (0)
        Options: [External]
          Hello Timer: 10s, Dead Timer 40s, Mask: 255.255.255.248, Priority: 1
          Designated Router 10.4.0.1, Backup Designated Router 10.4.0.5
          Neighbor List:
            192.168.14.68
            192.168.14.1
            192.168.14.67
21:20:48.782284 18 40 00:a0:24:f9:d5:ef c0:00:00:04:00:00 100: Single-route Forward (2052) LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 63957, offset 0, flags [none], length: 76) 10.4.0.3 > 224.0.0.5: OSPFv2, Hello (1), length: 56
        Router-ID: 10.4.0.3, Backbone Area, Authentication Type: none (0)
        Options: [External]
          Hello Timer: 10s, Dead Timer 40s, Mask: 255.255.255.248, Priority: 1
          Designated Router 10.4.0.1, Backup Designated Router 10.4.0.5
          Neighbor List:
            192.168.14.68
            192.168.14.1
            192.168.14.67
21:20:49.274715 18 40 00:0c:01:65:95:81 c0:00:00:04:00:00 110: LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 10762, offset 0, flags [none], length: 88) 10.4.0.1 > 224.0.0.5: OSPFv2, Hello (1), length: 68 [len 56]
21:20:50.346607 18 40 08:00:5a:fd:42:bf c0:00:00:04:00:00 88: Single-route Forward (2052) LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 25903, offset 0, flags [none], length: 64) 10.4.0.2 > 224.0.0.5: OSPFv2, Hello (1), length: 44
        Router-ID: 192.168.14.1, Backbone Area, Authentication Type: none (0)
        Options: [External]
          Hello Timer: 10s, Dead Timer 40s, Mask: 255.255.255.248, Priority: 1
          Designated Router 10.4.0.2
21:20:57.747515 10 40 00:a0:4c:08:71:81 c0:00:00:04:00:00 110: LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 26622, offset 0, flags [none], length: 88) 10.4.0.5 > 224.0.0.5: OSPFv2, Hello (1), length: 68 [len 56]
21:20:58.782425 10 40 00:a0:24:f9:d5:ef c0:00:00:04:00:00 100: Single-route Forward (2052) LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 63958, offset 0, flags [none], length: 76) 10.4.0.3 > 224.0.0.5: OSPFv2, Hello (1), length: 56
        Router-ID: 10.4.0.3, Backbone Area, Authentication Type: none (0)
        Options: [External]
          Hello Timer: 10s, Dead Timer 40s, Mask: 255.255.255.248, Priority: 1
          Designated Router 10.4.0.1, Backup Designated Router 10.4.0.5
          Neighbor List:
            192.168.14.68
            192.168.14.1
            192.168.14.67
21:20:58.782988 18 40 00:a0:24:f9:d5:ef c0:00:00:04:00:00 100: Single-route Forward (2052) LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 63958, offset 0, flags [none], length: 76) 10.4.0.3 > 224.0.0.5: OSPFv2, Hello (1), length: 56
        Router-ID: 10.4.0.3, Backbone Area, Authentication Type: none (0)
        Options: [External]
          Hello Timer: 10s, Dead Timer 40s, Mask: 255.255.255.248, Priority: 1
          Designated Router 10.4.0.1, Backup Designated Router 10.4.0.5
          Neighbor List:
            192.168.14.68
            192.168.14.1
            192.168.14.67
21:20:59.275348 18 40 00:0c:01:65:95:81 c0:00:00:04:00:00 110: LLC, dsap SNAP (0xaa), ssap SNAP (0xaa), cmd 0x03, IP (tos 0xc0, ttl   1, id 10764, offset 0, flags [none], length: 88) 10.4.0.1 > 224.0.0.5: OSPFv2, Hello (1), length: 68 [len 56]




Bjørn


PS. I would have posted this earlier if I didn't have to crawl into
the closet with my laptop to do the testing.  But I just can't get the
3c389 card working with the very old ISA-PCMCIA bridge in canardo. It
just bugs out with:

Linux Kernel Card Services
  options:  [pci] [cardbus] [pm]
Intel ISA PCIC probe: 
  Vadem VG-468 ISA-to-PCMCIA at port 0x3e0 ofs 0x00, 1 socket
    host opts [0]: none
    ISA irqs (scanned) = 3,14,15 polling interval = 1000 ms
cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x1f0-0x1f7 0x370-0x37f 0x3f0-0x3ff 0x4d0-0x4d7
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0a00-0x0aff: clean.
cs: memory probe 0x0d0000-0x0dffff: clean.
ibmtr_cs: RequestWindow: Resource in use
Uninitialised timer!
This is just a warning.  Your computer is OK
function=0x00000000, data=0x0
 [<c01237d1>] check_timer_failed+0x61/0x70
 [<c0123b2a>] del_timer+0x1a/0x90
 [<d0cec71d>] ibmtr_detach+0x4d/0xa0 [ibmtr_cs]
 [<d0ccbae6>] unbind_request+0xc6/0xd0 [ds]
 [<d0ccc220>] ds_ioctl+0x360/0x5f0 [ds]
 [<c028100a>] preempt_schedule+0x2a/0x50
 [<d082dffc>] unix_dgram_sendmsg+0x46c/0x560 [unix]
 [<c021569d>] sock_sendmsg+0x9d/0xc0
 [<c016f615>] iget_locked+0xa5/0xd0
 [<c0184756>] proc_get_inode+0x116/0x150
 [<c0280dc8>] schedule+0x2b8/0x4d0
 [<c01370a7>] filemap_nopage+0x207/0x3a0
 [<c021542c>] sockfd_lookup+0x1c/0x80
 [<c0216cf8>] sys_sendto+0xe8/0x100
 [<c0145f30>] handle_mm_fault+0xe0/0x180
 [<c0116fec>] do_page_fault+0x35c/0x56d
 [<c01a8042>] copy_from_user+0x42/0x70
 [<c0127f37>] sys_rt_sigaction+0x87/0xc0
 [<c02175a3>] sys_socketcall+0x143/0x260
 [<c0167bec>] sys_ioctl+0x11c/0x280
 [<c010603b>] syscall_call+0x7/0xb


But this is most likely a PCMCIA resource problem and offtopic here.
I've had similar experiences with other cards in this bridge.  Just
wanted to explain the delay
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux