From: Nicolas Patik <nicolas.patik@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] clone MAC address
Date: Wed, 17 Nov 2004 02:03:02 +0000 [thread overview]
Message-ID: <7539d99f0411161803326e9907@mail.gmail.com> (raw)
In-Reply-To: <7539d99f04111518002045dad8@mail.gmail.com>
The problem is when there is a problem. =)
When the conection is ok, there is no problem.
When the conection goes down for 'normal' reasons, also it's ok, but
when there are unknown reasons (ISP network problems), they pass the
issue to their network engineers, and there is when my problem starts,
they can find that I am connecting more computers.
That is why I want to clone the MAC.
-Nicolas
On Wed, 17 Nov 2004 00:00:36 +0100, Frank Gruellich <frank@der-frank.org> wrote:
> Hello,
>
> * 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.
>
> What exactly is your problem? For this clone-MAC-feature search the
> manpage of ifconfig for 'hardware address'. It's not supported by all
> NIC drivers, but for most. Do you change your routers from time to
> time? DHCP servers cache MACs and may not offer a second IP number if
> had another interface connected some time ago. They should flush the
> cache after some days. If they don't call them and feign a story about
> a new NIC you bought recently.
>
> HTH,
> regards, Frank.
> ==footnotes=> [1] Ascending TCP sequence numbers, not changed by NAT, you know?
> --
> Sigmentation fault
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
_______________________________________________
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:03 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 [this message]
2004-11-17 2:57 ` Francisco Pereira
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=7539d99f0411161803326e9907@mail.gmail.com \
--to=nicolas.patik@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.