#20453: Multicast IPv6 ICMP packets are dropped by built-in RT5350 switch, 
breaking
neighbour discovery
------------------------------------+----------------------------------
 Reporter:  tom@…                   |      Owner:  developers
     Type:  defect                  |     Status:  new
 Priority:  normal                  |  Milestone:  Chaos Calmer (trunk)
Component:  base system             |    Version:  Trunk
 Keywords:  IPv6 multicast, Ralink  |
------------------------------------+----------------------------------
 The problem I have encountered is basically the exact same thing as
 described in this previous ticket: https://dev.openwrt.org/ticket/15448
 except that it is happening in a different platform. In my case, I am
 using the RT5350F CPU with built in switch. The driver for the switch is
 the file called <openwrt-
 root>/target/linux/ramips/files/drivers/net/ethernet/ralink/esw_rt3052.c

 I am attaching a one-line-modified version that corrects the problem by
 configuring one register in the CPU differently. Also, I am attaching a
 screen capture of the relevant datasheet section. Basically, I have set
 bits 18 to 24 to zeros to enable IPv6 multicast packets to make it to the
 CPU.

 Here is the section I changed:
 // The following modification by Tom Rodinger
 //      .reg_initval_fct2       = 0x00d6500c,  // old value
         .reg_initval_fct2       = 0x000e500c,  // fixed value to allow
 IPv6 multicasts to get to the CPU

 Finally, the attached Wireshark screenshot shows that after the fix, the
 correct neighbour advertisement response is invoked by a neighbour
 solicitation message.

 I believe that this bug affects a number of variants from Ralink that all
 use this same switch driver. Hopefully you can integrate this fix into
 trunk.

--
Ticket URL: <https://dev.openwrt.org/ticket/20453>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets

Reply via email to