From: "Dan" <dan@34q.eu>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Routing public IP's through a gateway
Date: Mon, 15 Oct 2007 12:31:25 +0000 [thread overview]
Message-ID: <000f01c80f27$4d636580$e82a3080$@eu> (raw)
In-Reply-To: <200710142307.12127.tim@timg.ws>
Hi,
Sounds to me like you don't actually need to do anything - just enable IP forwarding on the linux machine (the gateway - usually something like echo 1 > /proc/sys/net/ipv4/ip_forward), and point your 202.172.122.7x machines at 202.172.122.74 for their default gateway (which your DHCP server should be passing out as a dhcp option anyway).
Unless I have missed something in the question?
Dan
-----Original Message-----
From: lartc-bounces@mailman.ds9a.nl [mailto:lartc-bounces@mailman.ds9a.nl] On Behalf Of Tim Groeneveld
Sent: 15 October 2007 13:15
To: lartc@mailman.ds9a.nl
Subject: Re: [LARTC] Routing public IP's through a gateway
On Sunday 14 October 2007 11:07:10 pm Tim Groeneveld wrote:
> Greeting all,
>
> I have a bit of a complicated question.
>
> I have two ethernet devices, eth1 and eth2.
>
> eth1 is where my internet comes from. It is in the form of
> 202.172.122.208/29. It has another IP range, 202.172.122.72/29. What I
> want to be able to do is route 202.172.122.72/29 to eth2, so that
> other machines can use those IPs, any ideas on how to do this, I
> cannot work out how to do this.
>
> eth2 has a DHCP server, which only gives out IPs 202.172.122.74 to
> 202.172.122.76.
>
> eth1 is basically just hooked into my internet router, while eth2 is
> hooked into a switch, and will be used for other computers.
>
> If anyone could help me with this setup, I would more then appreciate it.
>
> Thank you very much,
>
> - Tim Groeneveld
>
To extend what I have tried to say further:
My ISP has given me two IP ranges. 202.172.122.208/29 and 202.172.122.72/29.
They are unable to give me any larger IP ranges for some lame excuse, which I am sure was written by the BOfH.
Does your isp route 202.172.122.72/29 to me? Why yes it does. It routes this IP through the gateway 202.172.122.209.
If I want to give a machine an IP in 202.172.122.72/29, this is what I need
> A machine already in the 202.172.122.208/29 IP range.
> ip route add 202.172.122.72/29 via 202.172.122.209 dev eth1
> ifconfig eth1 202.172.122.73 netmask 255.255.255.248 (where on this machine, eth1 is hooked into my router).
What I would like, is a gateway machine, which will use eth2 to provide a gateway for other machines to assign themselves .72/29 IP's, *without* the need of 202.172.122.209 being in the route table.
So, there would be *one* gateway machine. This gateway machine has (already) an IP on both ranges.
> 202.172.122.211 (eth1)
> 202.172.122.74 (eth2)
eth2 would then be connected into a switch, and eth1 into the internet router.
I am not sure if this helps at all, sorry if it does not.
Thanks again,
- Tim G
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-10-15 12:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 13:07 [LARTC] Routing public IP's through a gateway Tim Groeneveld
2007-10-14 20:47 ` Alex Samad
2007-10-15 2:51 ` Mohan Sundaram
2007-10-15 2:59 ` Mohan Sundaram
2007-10-15 12:14 ` Tim Groeneveld
2007-10-15 12:31 ` Dan [this message]
2007-10-15 13:07 ` FW: " Dan
2007-10-15 13:12 ` Tim Groeneveld
2007-10-15 14:10 ` Tim Groeneveld
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='000f01c80f27$4d636580$e82a3080$@eu' \
--to=dan@34q.eu \
--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.