05-02-2011 05:20 AM - edited 03-06-2019 04:52 PM
Hi all,
I am working on a dot1x setup.
We would like to authenticate devices through dot1x.
I have configured the config below on a access port. Reauthentication on the radius server is set on 60min.
interface FastEthernet1/1
switchport access vlan 10
switchport mode access
authentication port-control auto
authentication periodic
authentication timer reauthenticate server
dot1x pae authenticator
dot1x timeout quiet-period 3
dot1x timeout tx-period 5
spanning-tree portfast
What happens if someone disconnects port fa 1/1 and branches a hub in this port and reconnects the device on the hub. I suppose the device will reauthenticate without problem. Maybe we'll see a port down error in the log.
Now imagine the following scenario.
Someone branches an illegal pc on the hub and sniffs the traffic. He disconnects the device and spoofs the mac address on his illegal pc. Will this pc have access to the network until the reauthentication timer expires? Why not?
Is there a possibility to prevent this? (lowering reauthentication timer will probably create more traffic flow).
Port-security maximum 1? If this is configurable on a dot1x port?
Anyone ideas?
Thanks,
Best Regards,
Joris
Solved! Go to Solution.
05-02-2011 05:39 AM
Same concept applies. I've updated the link above to one for a 3750. Refresh and try it again.
Please rate helpful posts.
05-02-2011 05:55 AM
Yes, this is a possibility.
The vulnerability that is mitigated by port security still leaves a vulnerability due to the nature of it's function. Port security works to protect by using MAC addresses that it detects attempting to communicate. With that said, if a port is connected to a switch with a configured SPAN port (or even a connected TAP) this traffic sniffing would go undetected because the attacker listens but doesn't actively speak or communicate out.
It's not by any stretch perfect, but it's a good deterrent.
Please rate helpful posts.
05-02-2011 05:30 AM
Port security is the solution.
This is one of the issues with 802.1x that is a problem. Once a port is authenticated using 802.1x then the port is available for use. Assuming the hub was connected prior to auth, then another could connect to the switch after auth and communicate on the network. The only multi-authentication mechanism with Cisco's implementation of 802.1x is an IP Phone based solution.
Port security is the stop-gap solution for the vulnerability in port authenticaiton behavior.
Message was edited by: Antonio Knox
05-02-2011 05:34 AM
Hi Antonio,
What do we do when we do not have a Nexus setup?
If I'm informed correctly a security port cannot be a dot1x port. Can we configure dot1x and port-security on a 3750 or 4500 environment?
Thanks,
Joris
05-02-2011 05:39 AM
Same concept applies. I've updated the link above to one for a 3750. Refresh and try it again.
Please rate helpful posts.
05-02-2011 05:50 AM
Thanks Antonio,
Is there a possibility that the illegal connected pc does not generate traffic and does not trigger the port-security?
eg. professional hacking programs...
Thanks,
Joris
05-02-2011 05:55 AM
Yes, this is a possibility.
The vulnerability that is mitigated by port security still leaves a vulnerability due to the nature of it's function. Port security works to protect by using MAC addresses that it detects attempting to communicate. With that said, if a port is connected to a switch with a configured SPAN port (or even a connected TAP) this traffic sniffing would go undetected because the attacker listens but doesn't actively speak or communicate out.
It's not by any stretch perfect, but it's a good deterrent.
Please rate helpful posts.
05-02-2011 05:59 AM
Thanks Antonio.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide