Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
02-02-2012, 08:25 AM
|
#1
|
|
LQ Newbie
Registered: Oct 2007
Location: Guatemala
Distribution: Slackware
Posts: 3
Rep:
|
How to disconnect a client
In a nutshell: how can I disconnect a client that connects to my network using dhcp?
I can pinpoint the lease/IP the client gets via dhcpd and with it, the MAC address. Using this information only, how can I disconnect the client from my network? (just disconnect, not banish forever)
|
|
|
|
02-02-2012, 08:32 AM
|
#2
|
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 42,706
|
what does "disconnect" mean? Ideally you'd connect to the switch they are connected to an shut down that port. You can put out fake arps for their IP address so they can't do much, but outside of a physical sense, there really is no such thing as disconnecting them. They aren't connected to the network in any way other than physically. It's not like there is a connection to a service like AD which makes their world pretty limited if domain membership was revoked.
|
|
|
|
02-02-2012, 10:45 AM
|
#3
|
|
Member
Registered: Nov 2005
Distribution: Fedora, Redhat
Posts: 372
Rep: 
|
I agree with Chris.
I think the only reliable way to prevent someone from accessing your network is to implement IEEE 802.1x. That would be an awful amount of work and expense. Every other measure you take could be subverted.
I assume (because of the DHCP reference) that the client is somewhere within your premises? I'd have security escort them from the building. 
|
|
|
|
02-02-2012, 10:50 AM
|
#4
|
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 42,706
|
Everytime I hear someone say they are "logged on to the network" I want to strangle them. 802.1x notwithstanding.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 05:48 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|