![what is netgear switch mac address prefix what is netgear switch mac address prefix](https://www.netguardstore.com/images/Switches/Managed-Switches/M4300/M4300-24XF.png)
![what is netgear switch mac address prefix what is netgear switch mac address prefix](https://vignette.wikia.nocookie.net/hitm/images/5/57/Swtich%2C_network%2C_netgear%2C_8-port.jpg)
After time, the switches learn their local topology from who talks to them. The Bridge in the middle and switch A do the same thing.
![what is netgear switch mac address prefix what is netgear switch mac address prefix](https://med.greatecno.com/232093/netgear-gs324-unmanaged-gigabit-ethernet-10-100-1000-black.jpg)
On the return trip, from host 2 to host 1, switch B says, I know that MAC, it came in on this port, so it's going out that port. Host 2 says, hey that is my MAC and processes the packet. The bridge sees it, doesn't know where it goes to and forwards it to all ports except the one it came from, it also records the sending MAC it it's bridge address table. When Host 1 transmits a packet to Host 2, Switch A has no idea where it goes based on the dest MAC, so it sends the packet to all ports except the one it came from, it also records the sending MAC in it's bridge address table. On the A switch there is a host 1 and on switch B a host 2. Let's assume that your transparent bridge is plugged into two switches A and B. If the physical layer addresses are compatible, the packet is transmitted intact. You have two physical segments, so the bridge DOES put its MAC address in otherwise the switches won't know where to forward the packet since they can't learn about devices on the other segment. I was referring to a transparent bridge, something I honestly have not seen in a decade. It sounds like some device is either intentionally or accidentally responding to arp requests with spurious information.Īs frennzy states above, arp -d * and trying to ping the addresses while watching with wireshark might tell you something. The other thing you can to is run wireshark filtering on that mac address and seeing what sort of traffic is coming from that mac address. That will at least tell you the mfg of the device that is causing havoc.ĭo any of those three IPs respond when you ping them? If not then you've got quite the mystery and without a management interface on your switches you're going to have a heck of a time find the port that they are plugged into. I don't think your switches have anything to do with this. Server2 even after it was changed to DHCP is still showing that IP.Īre the MAC address entries not timing out.Īll server traffic should be going through the Dell switch but maybe may drop is on the Netgear since I have a VoIP phone, but I can't get into the Netgear to see the MAC table. The funny thing is Server1 hasn't had that IP for months. Netgear PoE switch 192.168.1.14 - mystery MAC address A Server2's IP is 192.168.1.19 - mystery MAC address A Server1's IP is 192.168.1.9 - mystery MAC address A Now pay attention: I check the arp table: Very suspicious, everything looks great, no incoming traffic, like someone squeezed the IP hose, and 1 ping and it dies. I did check the logs, everything looks amazing clean, not an RDP client issue.Įarlier in the week Server2 with an IP of 192.168.1.19 which has been working well and fine for a good while starts having the same issue. 100-.200, everything is happy for the next few months. I changed it to DHCP and it picks up an address in. I ping it and get 1 returned packet and the rest are lost. I couldn't figure out the issue, reset the connection, the usual network troubleshooting. A few months ago it started losing network connectivity in that the DBA who RDPs (I know, I know) into it was having problems maintaining a connection, it has became very slow over RDP. Server1 used to have an IP of 192.168.1.9. I am sorry I am not explaining everything very well.