From: Denys <nuclearcat@nuclearcat.com>
To: lartc@vger.kernel.org
Subject: Re[2]: [LARTC] Terrible problem,
Date: Tue, 31 May 2005 12:39:54 +0000 [thread overview]
Message-ID: <908984853.20050531153954@nuclearcat.com> (raw)
Dear Krystian
Or even maybe better pppoe :)
> for user verification pptp can be used. its free :-)
> On 5/31/05, cristian_dimache@rtanet.ro
> <cristian_dimache@rtanet.ro > wrote:
> Yes, I have this problem too. And I came up with two ideas: one money
> comsuming, one time consuming.
> Money comsuming: get management switches everywhere, and limit MAC
> learning per port. My network amounts to 500+ stations, over a preety wide
> area (all on ethernet), costs evaluated at 30.000$. Rather expensive, ha?
> Time consuming: get into every windows workstation a program that alows
> network connection if MAC is unchanged from the one stored localy in an
> encrypted file.
> Boss evaluated my ideas, and, guess what? I am now working on the program
> described above.
> It will be publicly available, of course...
>> On Mon, 30 May 2005 20:41:20 +0200 Konrad <kcem@tlen.pl> wrote:
>>
>>>Is any way to detect changed MAC adresses?
>> I have been working on this for some time. You can try the current
>> version:
>> http://shurdeek.routehat.org/tmp/dhcpwatch2.pl
>>
>> (please don't ask how it works, I'm pretty busy now :-)).
>>
>>>Someone taught change MACs peoples in my network and I have problems.
>> Yeah I know, I have seen this too.
>>
>>>E.g. Two computers working on one MAC, and one IP (static ARP and DHCP).
>> Exactly.
>>
>>>WinXP is screaming some message... that two computers or more have the
>>>same IP.
>> Actually this happens when people use the same IP but a *different* MAC.
>>
>> Yours sincerely,
>> Peter
>> _______________________________________________
>> LARTC mailing list
>> LARTC@mailman.ds9a.nl
>> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
С уважением,
Denys mailto:nuclearcat@nuclearcat.com
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-05-31 12:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=908984853.20050531153954@nuclearcat.com \
--to=nuclearcat@nuclearcat.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.