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

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

 



> I would suggest just putting printk in the driver interrupt handler. 
> Just print out the dest mac of the frame that arrives when an interrupt 
> is asserted.  Of course, if you enabled full packet debug in the driver, 

>that may already be there.  I haven't looked.

Enabling network_monitor will give you the functional address being used
in the /proc/net/streamerN. (I'm away from the source right now, so the
names may be slightly different). 

Multicast over token-ring can be implemented in 3 ways per the RFC, in
order of preference: 
1) Using a specific multicast address
2) Using a functional address
3) Using promiscuous mode

Olympic supports option 2, the 3c359 would do option 1, but I never put
it in as it would be the only card that would, so it supports option 2 
also. ibmtr maybe option 2, but I have a suspicion it uses option 3. 

I believe the same code path was added to the lanstreamer driver and
should work, although the lanstreamer hardware is an often 
bizarre world to be in and doesn't always behave as it should. 

When I added the token ring multicast code to the kernel and drivers, 
the lanstreamer driver didn't exist so I only tested with ibmtr,
olympic and 3c359. 

Mike Phillips
(Still answering the occasional token ring questions) 
-
: 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