Who is connected to network
Hi All, Is there a way to see who is connected to your network. Say if you have a wireless network and you need to know if someone got it right to get onto your network. How do you monitor that and how do you prevent it? Even on a normal network how could you monitor who is connected to your network? Regards _____________________________________________________________________ For super low premiums, click here http://www.dialdirect.co.za/quote
it clown wrote:
Hi All,
Is there a way to see who is connected to your network.
Say if you have a wireless network and you need to know if someone got it right to get onto your network.
How do you monitor that and how do you prevent it?
Even on a normal network how could you monitor who is connected to your network?
Doesn't "w" or "who" does it? Martin
On 09:11 Wed 05 Jan , it clown wrote:
Hi All,
Is there a way to see who is connected to your network.
Say if you have a wireless network and you need to know if someone got it right to get onto your network.
How do you monitor that and how do you prevent it?
Even on a normal network how could you monitor who is connected to your network?
Regards
I'll address the 2nd question: Your wireless network needs to be set up to accept *only* your card's MAC address as well as any member of the family. That prevents anyone else from piggy-backing. ...CH
On Wednesday 05 January 2005 16:11, C Hamel wrote:
On 09:11 Wed 05 Jan , it clown wrote:
Hi All,
Is there a way to see who is connected to your network.
Say if you have a wireless network and you need to know if someone got it right to get onto your network.
How do you monitor that and how do you prevent it?
Even on a normal network how could you monitor who is connected to your network?
Regards
I'll address the 2nd question: Your wireless network needs to be set up to accept *only* your card's MAC address as well as any member of the family. That prevents anyone else from piggy-backing.
Not too sure if this works for wireless cards to, but you can reassign the MAC address on some network cards. For wireless you want to _also_ enable WEP, with a good secret. A big long hex one like my mate has. He also does some trick whereby you won't see the AP by default. You have to have the correct settings to start or the AP is invisible to you. Don't ask me how he's done it, I don't know. As to a fixed network, it very much depends on your architecture: Hub: Listen for traffic in promiscuous mode. Switch: Tend to offer a special port (RMON) or other facilities for snooping. Some will also allow you to restrict access based on MAC address too, but it is probably open to the same dodge mentioned above. -- Steve Boddy
He also does some trick whereby you won't see the AP by default. You have to have the correct settings to start or the AP is invisible to you. Don't ask me how he's done it, I don't know.
most decent aps have the ability to turn off ssid broadcast. that way people will (should) only be able to find your ap if they already know it exists. one thing to watch out for is users of mircosoft's zero-config in xp. it has issues with finding aps with the ssid broadcast turned off even if the settings are already there. if possible, use the manufacturers drivers/config in windows as they don't have the same problem. -- trey NOTE: All responses to this address *not* from the list go straight to /dev/null
On Thursday 06 January 2005 10:09, Trey Gruel wrote:
He also does some trick whereby you won't see the AP by default. You have to have the correct settings to start or the AP is invisible to you. Don't ask me how he's done it, I don't know.
most decent aps have the ability to turn off ssid broadcast. that way people will (should) only be able to find your ap if they already know it exists. one thing to watch out for is users of mircosoft's zero-config in xp. it has issues with finding aps with the ssid broadcast turned off even if the settings are already there. if possible, use the manufacturers drivers/config in windows as they don't have the same problem.
-- trey
NOTE: All responses to this address *not* from the list go straight to /dev/null
What does the command look like that sends unwanted things to /dev/null ? Thanks, Jerome
The Thursday 2005-01-06 at 20:33 -1000, Susemail wrote:
NOTE: All responses to this address *not* from the list go straight to /dev/null
What does the command look like that sends unwanted things to /dev/null ?
I could do very easily that with procmail... Mail to my list address { :0f * ^X-Mailinglist: suse-linux-e | /usr/bin/formail -bfi "Reply-To:suse-linux-e@suse.com" :0 a: $HOME/Mail/lists/suse-linux-e ... other lists ... :0: * ^TO_suse-linux-e@suse.com $HOME/Mail/lists/in_dups ... :0: $HOME/Mail/lists/in_elresto } Just substitute the last folder with /dev/null and you have it. -- Cheers, Carlos Robinson
it clown wrote:
Hi All,
Is there a way to see who is connected to your network.
Say if you have a wireless network and you need to know if someone got it right to get onto your network.
How do you monitor that and how do you prevent it?
Even on a normal network how could you monitor who is connected to your network?
Depending on what you're looking for, there's Kismet or Ethereal.
James Knott wrote:
it clown wrote:
Hi All,
Is there a way to see who is connected to your network.
Say if you have a wireless network and you need to know if someone got it right to get onto your network.
How do you monitor that and how do you prevent it?
Even on a normal network how could you monitor who is connected to your network?
Depending on what you're looking for, there's Kismet or Ethereal.
I use "last" and "netstat -a". Regards Sid. -- Sid Boyce .... Hamradio G3VBV and Keen Flyer =====ALMOST ALL LINUX USED HERE, Solaris 10 SPARC is just for play=====
participants (9)
-
C Hamel -
Carlos E. R. -
it clown -
James Knott -
Martin Deppe -
Sid Boyce -
Stephen Boddy -
Susemail -
Trey Gruel