From: Francisco Pereira <fpereira@lojan.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] clone MAC address
Date: Wed, 17 Nov 2004 02:57:13 +0000 [thread overview]
Message-ID: <419ABE09.4040000@lojan.com> (raw)
In-Reply-To: <7539d99f04111518002045dad8@mail.gmail.com>
Frank Gruellich wrote:
> * Nicolas Patik <nicolas.patik@gmail.com> 16. Nov 04:
>
>>No, I'm not talking about natting ... I'm talking about hidding my
>>computers from my ISP.
>
> Tell me, what's the difference. Can you give some technical description
> for this 'hiding' you are talking about?
>
>>.. or .... are you telling me that the problem with my linux box is
>>about bad firewall rules?
>
> No. 'Firewall rules' are a matter of layer 3, MACs and their so called
> cloning belong to layer 2.
>
>>Right now with my linux box doing NAT they can find that I have others
>>computers connected.
>
> Contradicting to Chris they can. But trust me, they won't. Finding
> hosts behind a NAT router is very difficult and involves the collection
> of huge amounts of traffic.[1] After all, it will not work for any OSs.
It's no so dificult, at least in some cases.
p0f (passive OS fingerprint) uses a technique (that has some
limitations) to detect masqueraded hosts, it have to sniff all the
traffic but not collect it.
http://lcamtuf.coredump.cx/p0f.shtml
Regards,
Francisco.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-11-17 2:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-16 2:00 [LARTC] clone MAC address Nicolas Patik
2004-11-16 18:15 ` Stef Coene
2004-11-16 19:29 ` Nicolas Patik
2004-11-16 19:46 ` Chris Bennett
2004-11-16 23:00 ` Frank Gruellich
2004-11-17 2:03 ` Nicolas Patik
2004-11-17 2:57 ` Francisco Pereira [this message]
2004-11-17 16:22 ` Nicolas Patik
2004-11-17 22:05 ` Chris Bennett
2004-11-18 19:36 ` Stef Coene
2004-12-18 20:53 ` sandr8
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=419ABE09.4040000@lojan.com \
--to=fpereira@lojan.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.