From: Krystian Antoni <krystianantoni@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Terrible problem,
Date: Mon, 30 May 2005 19:20:30 +0000 [thread overview]
Message-ID: <258b6f7050530122061b18a2a@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 974 bytes --]
here is my one cent :-)
propably somebody is changing a MAC so you DHCP will grant them specific IP.
u can try nmap them them to see whos behind that MAC (at the moment where
there is only one station turned on). then by using unplug and
seek-the-hacker method u can find from what switch/port he's comming.
if u posses administrable switch it can be much easyier.
if u must verify every user, turn to pptp.
On 5/30/05, Konrad <kcem@tlen.pl> wrote:
>
> Is any way to detect changed MAC adresses?
>
> Someone taught change MACs peoples in my network and I have problems.
>
> E.g. Two computers working on one MAC, and one IP (static ARP and DHCP).
> WinXP is screaming some message... that two computers or more have the
> same IP.
>
> How can I find out who's changed MAC?
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
--
Miłego Dnia
Krystian Antoni
[-- Attachment #1.2: Type: text/html, Size: 1393 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2005-05-30 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 19:20 Krystian Antoni [this message]
2005-05-30 20:42 ` [LARTC] Terrible problem, Peter Surda
2005-05-31 6:47 ` cristian_dimache
2005-05-31 11:17 ` Krystian Antoni
2005-05-31 11:36 ` Sylvain BERTRAND
2005-05-31 12:12 ` cristian_dimache
2005-05-31 14:10 ` Peter Surda
2005-05-31 14:32 ` Sylvain BERTRAND
2005-05-31 15:07 ` Peter Surda
2005-05-31 15:26 ` Sylvain BERTRAND
2005-06-01 5:56 ` cristian_dimache
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=258b6f7050530122061b18a2a@mail.gmail.com \
--to=krystianantoni@gmail.com \
--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.