From: Alfred Vahau <Alf.Vahau@upng.ac.pg>
To: lartc@vger.kernel.org
Subject: [LARTC] Personal Firewalls
Date: Mon, 10 Jan 2005 03:22:44 +0000 [thread overview]
Message-ID: <41E1F504.2010201@upng.ac.pg> (raw)
Hello,
Our ISP provides a firewall and NAT services for our Intranet.
However, within the Intranet, there appear to be personal firewalls
around some anonymous PCs. The IP addresses of these PCs can
be detected by our network monitoring tool.
The identity of the user however remains anonymous.
Are there any tools that can be used to penetrate the personal firewall
and reveal the identity of the users? All our IP addresses fall within
specific ranges and the existence of these addresses are against the
policies on computer usage.
Thanks for any pointers,
Alfred Vahau
IT Services
Uni. PNG
--
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2005-01-10 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 3:22 Alfred Vahau [this message]
2005-01-10 9:39 ` [LARTC] Personal Firewalls 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
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=41E1F504.2010201@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.