From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to set a host with public IP within a private network?
Date: Tue, 02 Aug 2005 23:58:22 +0000 [thread overview]
Message-ID: <42F0089E.5010003@riverviewtech.net> (raw)
In-Reply-To: <20050802173838.72293.qmail@web32611.mail.mud.yahoo.com>
I think you want to take a look at a bridging router. I would be
tempted to set up a bridge between eth0 and eth1 on the Linux router and
then use ebtables to decide if the traffic should be bridged through or
sent up to the higher layers of the protocol stacks. I have a feeling
that you would have to move all IP addresses from eth0 to br0 (the new
bridge interface). I think you would have a command like this to decide
if an IP needed to be routed or bridged.
ebtables -t broute -A BROUTING -d 5.6.7.201-j ACCEPT
ebtables -t broute -A BROUTING -s 5.6.7.201 -j ACCEPT
ebtables -t broute -A BROUTING -j DROP
An excerpt from the EBTables man page:
*broute*, is used to make a brouter, it has one built-in chain:
*BROUTING*. The targets *DROP* and *ACCEPT* have special meaning in the
broute table. *DROP* actually means the frame has to be routed, while
*ACCEPT* means the frame has to be bridged. The *BROUTING* chain is
traversed very early. It is only traversed by frames entering on a
bridge enslaved NIC that is in forwarding state. Normally those frames
would be bridged, but you can decide otherwise here. The *redirect*
target is very handy here.
Give this a whirl and see if it will do any thing for you. If you need
more specifics just ask.
Grant. . . .
panca sorin wrote:
>Hello! I have the following setup:
>1) a connection to my ISP with a public IP (1.2.3.4)
>with the gateway 1.2.3.1
>2) an allocated IP class with 64 addresses
>(5.6.7.192/26)
>3) two LANs connected through two NICs:
> a) 192.168.0.0/24 on eth1 (192.168.0.1)
> b) 10.0.0.0/24 on eth2 (10.0.0.1)
>
>The IPs from the allocated class are all assigned to
>eth0.
>The networks are SNATed to the external IP and to all
>IPs in the allocated class in a round-robin fashion.
> (-j SNAT --to 1.2.3.4 lowest_IP_in_class
>highest_IP_in_class)
>
>My question is:
>Is it possible to assign one IP from my allocated
>class to an internal machine without changing eth1 or
>eth2 IPs *OR* without adding a subclass of my
>allocated class to eth1 or eth2 in order to give an ip
>to an internal networked machine?
>What command should i give if that setup is possible?
>Desired Network Diagram:
>
> ----------
>/---|Internet|
>| ----------
>|eth0 192.168.0.1 10.0.0.1
>| ---------- eth1 eth2
>\--| Linux |--------------v--------------------v
> | Router | | |
> ---------- | |
> | |
> ------------- | ---------- |
> |192.168.0.2|--------< |10.0.0.2|----<
> ------------- | ---------- |
> . | . |
> . | . |
> . | . |
> --------------- | ------------ |
> |192.168.0.254|-------< |10.0.0.254|--<
> --------------- | ------------
> |
> |
> ----------- |
> |5.6.7.201|-----------<
> -----------
>
>I would de-assign some of the addresses from eth0 to
>re-assign them to locally connected computers...
>
>Thank you in advance for your help!
>
>
>
>
>____________________________________________________
>Start your day with Yahoo! - make it your home page
>http://www.yahoo.com/r/hs
>
>_______________________________________________
>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
next prev parent reply other threads:[~2005-08-02 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 17:38 [LARTC] How to set a host with public IP within a private network? panca sorin
2005-08-02 23:58 ` Grant Taylor [this message]
2005-08-03 10:09 ` xerces8
2005-08-03 10:21 ` panca sorin
2005-08-03 10:23 ` panca sorin
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=42F0089E.5010003@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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.