Timeline for How does a Layer 2 Switch know which port is a neighboring switch port and which port is connected to a host?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 24, 2018 at 13:03 | comment | added | jonathanjo | a) Host replying to more than one MAC address could be a router with HSRP or similar; b) Swapping hosts on an interface might not clear the MAC address table entry (depends on medium), the cache timeout is normally short (~10 sec) but can be long (first router I tried allowed 1 million seconds, approx 11.6 days). | |
| Sep 24, 2018 at 12:40 | comment | added | Henrik supports the community | Or a computer replying to more than one MAC address for some reason. | |
| Sep 24, 2018 at 10:35 | history | edited | JFL | CC BY-SA 4.0 |
edited body
|
| Sep 24, 2018 at 10:11 | comment | added | JFL | @NinjaBug Right. It can also be a hub of course (increasingly rare) or a WiFi access point - which is functionally equivalent to a switch. | |
| Sep 24, 2018 at 10:05 | vote | accept | Ninja Bug | ||
| Sep 24, 2018 at 10:05 | comment | added | Ninja Bug | There is a one-to-one correspondence between hosts and ports in the access link right? I mean if a port is assigned only one MAC address, it may be a host or a switch, but if "more than one" MAC addresses are assigned to a port, it is "definitely" connected to a virtual or physical switch? | |
| Sep 24, 2018 at 10:01 | history | answered | JFL | CC BY-SA 4.0 |