NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Unacceptable Frames received and switch is not forwarding frames to another port
Hello All, I am using Netgear XS708T 8 port 10GB switch( new firmware) and for that switch, I have connected one radar.( multiple in future) For port 1, radar is connected and in port 3 anot...
Hi,
Thank you very much for the details explanation.
It is really helpful.
Yes radar is inhouse developed with MAC address AA:BB:11:22:33:55
Now I need one more help. How can I solve this issue? how can I make the switch to start working( receiving in port 1 and forwarding at port 3).
Thanks in advance
Grüezi hegde
Potentially there is certain data in the frame (like a reserved MAC address, some bits recognized as multicast, something else in the header, ...) not generically switch-able and useable. A dumb switch might forward such frames silently, while a smarter device might refuse. What might work in a data acquisition point-to-point config cold be prohibited in a generic L2 network environment. this will lead to unacceptable frame types and non-forwardable packets.
99.9% not a switch issue - most likely an application design L2 issue working somewhere near or beyond the edges of the standards. This might also lead to the MAC issue mentioned. Is this radar processor some in-house development?
Regards,
-Kurt
Hi,
Thank you very much for the details explanation.
It is really helpful.
Yes radar is inhouse developed with MAC address AA:BB:11:22:33:55
Now I need one more help. How can I solve this issue? how can I make the switch to start working( receiving in port 1 and forwarding at port 3).
Thanks in advance
For a test, can you define the MAC address on the adapter yourself?
I'm under the assumption aa:bb:11 isn't a registered MAC OID for your devices. Play it simple, take your mobile phone, and connect it to your favorite WiFi using a random MAC (Apple names it "private WiFi address"). Slightly change it in the last bits. If it does generate a2:d7:bd:d1:7d:32, change it to a2:d7:bd:d1:7d:33 for a unique MAC different from your mobile, and try this for your device. Does the switch handle the forwarding as expected now?
From wally brain, a little bit tired after long day, can't tell this minute you what might be the effective cause.
Probably somebody from Netgear switch engineering can answer why these packets are not forwarded.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
