All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alfred Vahau <Alf.Vahau@upng.ac.pg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Personal Firewalls
Date: Tue, 11 Jan 2005 14:39:41 +0000	[thread overview]
Message-ID: <41E3E52D.2050808@upng.ac.pg> (raw)
In-Reply-To: <41E1F504.2010201@upng.ac.pg>



Peter Surda wrote:

> Alfred Vahau wrote:
>
>> Thanks for the reply. This is the practice at present. We block off 
>> one IP and another pops up.
>> At times, quite a few of them appear. We suspect that some of these 
>> guys are disgruntled ex-employees
>> who have unauthorized access or are accessing the network with the 
>> help of other staff.
>
>
> Aha, so you suspect malicious intent and not only accidental 
> behaviour. In that case you shouldn't expect that some other internal 
> information found on the problematic computers is valid either.

We have not dismissed malicious intent. However, the chances of it 
happening is quite remote. Rather the fight is against network abuse.
In line with the core objectives of our institution, there are sites 
which are defined as unproductive. It is the access to these sites for which
strange ip addresses spring up, some of which are within our IP range, 
for which the logs do not provide very much information on the
identify of the user.

>
> 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.
>
Thanks for this pointer. This option looks viable and will pursue this.

>> alfred,
>
>
> Yours sincerely
> Peter Surda

alfred,

> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/


-- 
Perl is my reason for following the Sun;


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2005-01-11 14:39 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 [this message]
2005-01-11 14:42 ` Alfred Vahau
2005-01-31 18:14 ` Alfred Vahau

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=41E3E52D.2050808@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.