3

802.1X provides client-side/front-end port-level authentication (between suplicant and authenticator). RADIUS and Diameter provide back-end authentication (between authenticator and authentication server). Essentially, they are different things. 802.1X is an application while RADIUS/Diameter can potentially provide authentication for various applications. ...


2

Switch1 won't know jack about the network(s) on Switch2 unless you add an appropriate route. But as Win10 is not a router, one should not be routing foreign networks at it. (i.e. sw1's network cannot reach sw2's network through the PC.) The PC should be able to ping either switch, as it has directly connected interfaces in each network. The other devices in ...


1

Your network is a really bad design. In order to route packets between networks, you use a router. In order to bridge frames on the same network, you use a bridge (a switch is a bridge). Your PC is neither a router nor a bridge, so traffic on each side of the PC is confined to that side of the PC.. It may be possible to run a routing or bridging application ...


1

Do not confuse layer-2 interfaces with layer-3 interfaces. Only layer-3 interfaces have ARP tables. The layer-2 interfaces feed the CAM tables, but not the ARP tables. Your switch interface in question is a layer-2 interface based on the configuration you show: interface GigabitEthernet2/0/2 switchport mode access That interface will not have an ARP table. ...


1

For me, Ethernet is a protocol used at layer 2. ... and a large family of protocols for layer 1, yes. Then I started dealing with another type of protocols. Like 802.1x For me it looked like a framework more than a protocol. No. While there are frameworks to simplify handling of 802.1X, it's a protocol. A protocol is a "language" convention ...


Only top voted, non community-wiki answers of a minimum length are eligible