Seems like a 200-300 multicast packet/sec on the LAN will cause serious lockups on budget routers. Ive tried both a TRENDNet TEW-633GR and a Linksys WRT54G v4 flashed with DD-WRT. Enabling/disabling multicast in the config makes no difference.
I don't actually want LAN->WAN or LAN->wireless routing just LAN->LAN but I needs wireless->LAN TCP/IP access to manage my headless servers. I actually bought a Linksys SRW2008 to act as a LAN switch as the advertised iGMP snooping feature should have prevented multicast LAN->router traffic. Unfortunately the SRW2008 has badly broken firmware and iGMP snooping doesn't work so it floods all the ports including the one the router is attached to.
It does however have decent vlan support, but no mechanism for coloring the multicast data with a different vlan tag from other traffic. As a work around I am using Linux's vconfig command to create vlan tagged interfaces to let the application tag the data as its published. This works but complicates the system and application config.
Why does a few hundred irrelevant multicast LAN packets/sec have such an impact on these routers? Is there a way to get them to ignore this data?
Alternatively, can anyone recommend a decent gigE iGMP snooping switch that supports 64+ multicast groups?
Would it be possible to measure multicast performance as part of the SmallNetBuilder router/switch tests?
PG.
I don't actually want LAN->WAN or LAN->wireless routing just LAN->LAN but I needs wireless->LAN TCP/IP access to manage my headless servers. I actually bought a Linksys SRW2008 to act as a LAN switch as the advertised iGMP snooping feature should have prevented multicast LAN->router traffic. Unfortunately the SRW2008 has badly broken firmware and iGMP snooping doesn't work so it floods all the ports including the one the router is attached to.
It does however have decent vlan support, but no mechanism for coloring the multicast data with a different vlan tag from other traffic. As a work around I am using Linux's vconfig command to create vlan tagged interfaces to let the application tag the data as its published. This works but complicates the system and application config.
Why does a few hundred irrelevant multicast LAN packets/sec have such an impact on these routers? Is there a way to get them to ignore this data?
Alternatively, can anyone recommend a decent gigE iGMP snooping switch that supports 64+ multicast groups?
Would it be possible to measure multicast performance as part of the SmallNetBuilder router/switch tests?
PG.