From: Anatoly Muliarski <x86ever@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: nat bypass
Date: Mon, 28 Jun 2010 20:49:50 +0300 [thread overview]
Message-ID: <AANLkTinxapgkJ0pc8RdrPJ2Mikmn0H4JpdMYgeP4Dwvb@mail.gmail.com> (raw)
In-Reply-To: <AANLkTil_H1QeaCHQYhMjVRFiLwtqF9yLAJZ9BWecOIDW@mail.gmail.com>
2010/6/28 ratheesh k <ratheesh.ksz@gmail.com>:
> Hi,
>
> A -------> R ------->S
>
> I have a linux machine A is connected to Linux machine R . Machine R
> is having two network interfaces and acting as a router .
> It has a dhcp server running . It will assign ip in 192.168.1.0/24
> subnet to all machine connected on lan side ( A is connected also in
> lan side ) . Wan side of R is connected to HTTP server S . There is
> also a DHCP server running on S to assign ip in 10.232.18.0/24 subnet
> . Is there any way , in which NAT should be bypassed to get ip from
> DHCP server running on S . My question is : How can A will get an ip
> from 10.232.18.0/24 pool ip .?
> ebtables is an option ? How can we make it ?
> Is there any other optimal way ?
>
Suppose you achieve your goal and A got an IP from S pool.
But there appear another problem - what about routing?
Presumably you should track leased IP and dynamically bridge packets
to/from it - and it looks rather complicated.
--
Best regards
Anatoly Muliarski
next prev parent reply other threads:[~2010-06-28 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 10:13 nat bypass ratheesh k
2010-06-28 14:02 ` Grant Taylor
2010-06-28 17:49 ` Anatoly Muliarski [this message]
2010-06-30 2:37 ` Simon Horman
2010-06-30 9:24 ` ratheesh k
2010-06-30 12:05 ` Stephen Clark
2010-06-30 9:54 ` Mart Frauenlob
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=AANLkTinxapgkJ0pc8RdrPJ2Mikmn0H4JpdMYgeP4Dwvb@mail.gmail.com \
--to=x86ever@gmail.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).