From: Evgeni Gechev <etg@setcom.bg>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip conflict with proxy arp
Date: Tue, 29 Oct 2002 17:33:59 +0000 [thread overview]
Message-ID: <marc-lartc-103591450721682@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103587435607275@msgid-missing>
Rohan Almeida wrote:
> HI,
> I've got a proxy arp setup with iptables and tc.
>
> on eth0 i have a route to 172.16.2.0/24 network
> on eth1 is the LAN of 172.16.1.0/24 network
>
> I have enabled proxy arp on both interfaces.
> Now accordingly, the interface will respond
> to all ARP requests for which it has a route to.
>
> Noy my setup is such, that a user on the LAN,
> would like to have an ip from the 172.16.2.0/24 network.
>
> But unfortunately, when he tries to allocate an
> ip like 172.16.2.1 he gets an ip conflict.
>
> I also know why he is getting it!
> But is there any way out of this??
>
> Something like, tell the linux server to respond for
> ARP requests for the 172.16.2.0/24 network but at the
> same time if a machine is trying to use an ip for itself,
> then it should not respond.
>
> Help!
>
> --
> arc_of_descent
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Just add a route to 172.16.2.1/32 on eth1.
But you should add such route not only for escaping the ip conflict.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-10-29 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-29 6:52 [LARTC] ip conflict with proxy arp Rohan Almeida
2002-10-29 17:33 ` Evgeni Gechev [this message]
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=marc-lartc-103591450721682@msgid-missing \
--to=etg@setcom.bg \
--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.