From: Alfred Vahau <Alf.Vahau@upng.ac.pg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Personal Firewalls
Date: Mon, 31 Jan 2005 18:14:34 +0000 [thread overview]
Message-ID: <41FE758A.4050805@upng.ac.pg> (raw)
In-Reply-To: <41E1F504.2010201@upng.ac.pg>
>However, there is a possibility if you want to find the computer by
IP, if you use manageable switches. As you know which >IPs are improper,
you can also find the corresponding MAC address passively from the
router's ARP table (or actively by >arping), and the switches will be
able to tell you on which port this MAC is plugged. Then you can e.g.
shutdown the port or >follow the cable to the physical computer location.
Just reporting back on how this went. The above worked beautifully and
the suspect PC has been identified.
Two puzzling aspect which I hope the list will throw some light on is:
1. The ipconfig /all command on Windows returns the description of the
NIC with company A but the MAC address contains the code for company B
according to OUI scheme.
http://standards.ieee.org/regauth/oui/oui.txt
Is this an industry practice?
Both IP and MAC addresses match that of the investigated computer.
2. Our proxy access logs show that sites C and D were heavily accessed.
The browser history shows site shows D being accessed but not a trace of
access to C. I am suspecting an ftp server being used.
Thanks in advance for the help.
alfred,
--
Perl -
"... making the easy jobs easy,
without making the hard jobs impossible."
'The Camel', 3ed
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-31 18:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 3:22 [LARTC] Personal Firewalls Alfred Vahau
2005-01-10 9:39 ` Peter Surda
2005-01-10 18:33 ` Alfred Vahau
2005-01-10 18:47 ` David Hough
2005-01-10 19:47 ` Peter Surda
2005-01-11 14:28 ` Alfred Vahau
2005-01-11 14:39 ` Alfred Vahau
2005-01-11 14:42 ` Alfred Vahau
2005-01-31 18:14 ` Alfred Vahau [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41FE758A.4050805@upng.ac.pg \
--to=alf.vahau@upng.ac.pg \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.