PROTECTED] - (843-953-7770)
-Original Message-
From: 802.11 wireless issues listserv
[mailto:[EMAIL PROTECTED] On Behalf Of Karyn
Williams
Sent: Monday, February 07, 2005 4:58 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Would anyone like
for those un-configured PCs.
Regards,
Frank
-Original Message-
From: Philippe Hanset [mailto:[EMAIL PROTECTED]
Sent: Monday, February 07, 2005 9:45 AM
To: Frank Bulk
Cc: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: RE: [WIRELESS-LAN] Wireless Identification Tools
Frank,
We have
:[EMAIL PROTECTED]
Sent: Monday, February 07, 2005 9:45 AM
To: Frank Bulk
Cc: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: RE: [WIRELESS-LAN] Wireless Identification Tools
Frank,
We have no problem detecting them (we use the RAD function in our APs which
detects Ad-Hoc as well)!
We have problems
: Monday, February 07, 2005 4:58 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Would anyone like to recommend an inexpensive directional attennae ?
--
Karyn Williams
Network Services Manager
California Institute of the Arts
[EMAIL PROTECTED
To: Frank Bulk
Cc: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Allow me to throw some oil on this hot topic:
I was saying: we rarely have rogue APs in places were we provide decent
free wireless coverage...well...
I forgot one issue though: Ad-Hoc
for Cisco), but seems to be OK in
general.
Thanks.
-jcw
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
From: Donald Gallerie [EMAIL PROTECTED]
Date: Fri, 4 Feb 2005 16:49:18 -0500
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Reply-To: 802.11 wireless issues listserv
Would anyone like to recommend an inexpensive directional attennae ?
--
Karyn Williams
Network Services Manager
California Institute of the Arts
[EMAIL PROTECTED]
http://www.calarts.edu/network
**
Participation and subscription information for this EDUCAUSE Constituent Group
discussion
A way that we have found to be useful and does NOT require us walking
down the hallways is looking for the TTL in the packets. You just need
to know how many router hops is the destination away from where you are
capturing the traffic and subtract it from the default TTL value. For NT
4 and
-Original Message-
From: Philippe Hanset [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 05, 2005 12:39 PM
To: Frank Bulk
Cc: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Allow me to throw some oil on this hot topic:
I was saying: we rarely have rogue
, 2005 7:18 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
We take a similar tact, but use the idea of tracking the IP address
reported
by an internal campus web server to a specific location.
(Which we need to do for virus outbreaks anyway) Because
Simple tools can go a long way towards finding where these devices are-
- Join the rogue network if possible, then just browse to
www.whatismyip.com to see what the public IP in use is, then go track
it down if it's in your domain
- Better yet, if no change from default settings has been made,
@LISTSERV.EDUCAUSE.EDU
Subject: [WIRELESS-LAN] Wireless Identification Tools
In an effort to better identify rogue access points, can any of you
recommend tools that would make the physical and network pinpointing of
WAPs
a bit easier. We have identified a number of rogues but cannot
ascertain
exactly where
Airmagnet laptop or handheld will work.
At 02:16 PM 2/4/2005, you wrote:
In an effort to better identify rogue access points, can any of you
recommend tools that would make the physical and network pinpointing of WAPs
a bit easier. We have identified a number of rogues but cannot ascertain
Philippe Hanset wrote:
Don,
A trick that I have been willing to test for a long time would be
to join the Rogue AP, send traffic to a know sniffing host
in that same layer2 network.
This will reveal the Wired MAC address of the AP.
Then search for that MAC on your wired side and disable the port.
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
From: Jeff Wolfe [EMAIL PROTECTED]
Date: Fri, 4 Feb 2005 15:53:26 -0500
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Reply-To: 802.11 wireless issues listserv
WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Return-Path: [EMAIL PROTECTED
) 766-2984
-Original Message-
From: John Watters [mailto:[EMAIL PROTECTED]
Sent: Friday, February 04, 2005 2:15 PM
To: WIRELESS-LAN@LISTSERV.EDUCAUSE.EDU
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
Where can we find a good list of the MAC address ranges for wireless
access
] Wireless Identification Tools
In an effort to better identify rogue access points, can any of you
recommend tools that would make the physical and network pinpointing of WAPs
a bit easier. We have identified a number of rogues but cannot ascertain
exactly where they are. We have tried getting
John Watters wrote:
Where can we find a good list of the MAC address ranges for wireless access
points? If I just look
by manufacturer (see http://standards.ieee.org/regauth/oui/index.shtml) I do
not see a distinction
between their access points their NICs, switches, routers, and other network
: [WIRELESS-LAN] Wireless Identification Tools
Philippe Hanset wrote:
Don,
A trick that I have been willing to test for a long time would be to
join the Rogue AP, send traffic to a know sniffing host in that same
layer2 network.
This will reveal the Wired MAC address of the AP.
Then search
Subject: Re: [WIRELESS-LAN] Wireless Identification Tools
We take a similar tact, but use the idea of tracking the IP address reported
by an internal campus web server to a specific location.
(Which we need to do for virus outbreaks anyway) Because we use VLAN's it's
a little tedious to search all
Michael Dickson wrote:
Using port security tends to open a can of worms with faculty and TA's
who use hubs in overcrowded offices. Also, it does not defend against
rogue AP's or other devices doing NAT, as only a single mac is seen on
the switch.
And not running it opens a security can of worms
Yantis, Jonathan Lindsey wrote:
Sometimes that is the case and sometimes not. I think what Jeff was
saying is that they connected to the AP with a client and then pinged a
Not necessarily. You can snarf it off the beacon, even if it is closed.
device or something along those lines to get the
22 matches
Mail list logo
