DropReasons

[Aviv_Kedem]

Our AP's configured with trunk (3 tagged vlans) on eth side and we have about 500 per sec of these dropreasons:

1
DropReason: bc/mc to radio unneeded(218)
SAMPLE:

----------------------------------------------------------------------
Packet 14:
Time: 8:55:39.507589, Len: 127, 802.3, Proto: 0x0800, Vlan: 500, Priority: 0, Ingress: ge1, l3_off: 18, l4_off: 38
DropReason: bc/mc to radio unneeded(218)
802.3: XX-XX-XX-5C-6E-80 > FF-FF-FF-FF-FF-FF, 802.11p pri 0, 802.11q vlan 500, protocol 0x0800
IPv4: XX.XX.2.72 > XX.XX.3.255, proto UDP, IPv4 length 109, DSCP 0, Id 0, DF
UDP: ports 9956 > 9956, data length 89
----------------------------------------------------------------------

Why should I see this kind of dropreasons?

2
DropReason: non-[port] member vlan(205)
Why should I see the dropped packets from the vlans that NOT configured on ge1 switchport configuration ?

Thanks,

Aviv Kedem

[Daren_Ellis]

Hi Aviv,

We want to forward as little unessary traffic into the air as possible.
The firewall will drop certain traffic (Mainly broadcast multicast) that should not be forwarded into the air.
Which is why we always recommend that the firewall and Proxy arp always be enabled.

In regard to question 2:

You are most likely trunking and on the L2 side you might be allow vlans that are not configured on the WiNG device.
In this case you will need to prune the traffic, only allow (from the L2 switch) vlans that are maps/configured on the APs Ge1 port(s).

[Alona]

All the queues in the radio h/wso radios are faster. It's effecient anymore to query the h/w queues for status.

[Aviv_Kedem]

Any suggestions?

[Aviv_Kedem]

Any ideas?

Thanks