From: George Alexandru Dragoi <waruiinu@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routable subnet as aliased IP's?
Date: Fri, 04 Feb 2005 13:27:14 +0000 [thread overview]
Message-ID: <3063e50502040527378be5d5@mail.gmail.com> (raw)
In-Reply-To: <1107508803.42033e435a792@mail.norwesters.org>
I think you can just make aliases for all 8 ips (Yes i said 8)
ifconfig eth0:0 100.0.43.152 netmask 255.255.255.255 up
ifconfig eth0:1 100.0.43.153 netmask 255.255.255.255 up
ifconfig eth0:2 100.0.43.154 netmask 255.255.255.255 up
...
ifconfig eth0:7 100.0.43.159 netmask 255.255.255.255 up
On Fri, 4 Feb 2005 01:20:03 -0800, 3ds@norwesters.net
<3ds@norwesters.net> wrote:
> Greetings all!
> I just got a colocated server space and the ISP has given me an IP address and a
> routable /29 subnet. Here's a partial snippet of the info they gave me (with
> the real addressess changed for privacy)
>
> == WAN Address
> Customer IP Address : 100.0.33.14
> Netmask : 255.255.255.248
> Broadcast Address : 100.0.33.15
> Default Gateway : 100.0.33.9
> == Routed Network
> IP Address Type : 100.0.43.152/29 Class-C Subnet
> Number of IP Addrs : 6
> Domain Name : example.net
> Customer IP Addresses : 100.0.43.{153 thru 158}
> Netmask : 255.255.255.248
> Broadcast Address : 100.0.43.159
>
> And they provided this chart:
> -
> |
> | +----------+
> | | Customer |
> |------| Host #1 |
> | .154 | |
> | +----------+
> - WAN - - Subnet - |
> +------+ Net/Mask +----------+ Net/Mask | +----------+
> | ISP | 100.0.33.8 | Customer | 100.0.43.152 | | Customer |
> |Router|---- /29 -----|Colocation|---- /248 ----|------| Host #2 |
> | | .9 .14 | Router | .153 | .155 | |
> +------+ +----------+ | +----------+
> ** REQUIRED ** |
> ** DEVICE ** | +----------+
> | | Customer |
> |------| Host #n |
> | .156 | |
> | +----------+
> |
> -
>
> I have a single server with Fedora Core3 (x86-64 2.6.10-1 kernel) installed, and
> my intent is to use the iproute2 tools to set up aliases for .154, .155, .156,
> etc. and then use IP Virtual Hosts in Apache.
>
> So, to my question. I could get a router for routing the /29 subnet as the ISP
> suggests, but can I use my Linux machine to do this? Can I mount eth0 as
> 100.0.33.14 and then setup the 100.0.43.152-158 as aliases and write the routing
> so that everything works? I have read chapters 3 and 4 of the LARTC, and I
> think it may be possible, but it's just not clicking yet as to how I might be
> able to do this.
>
> And to add one last twist to this... let's say that I can do the above, what if
> I wanted to take one of those IP's from the /29 subnet and route it on to
> another system plugged into my eth1 while maintaining all of the other IP's as
> aliases?
>
> Am I dreaming? Can you help me?
>
> Thanks!
> Ray
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
--
Bla bla
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-02-04 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 9:20 [LARTC] routable subnet as aliased IP's? 3ds
2005-02-04 13:27 ` George Alexandru Dragoi [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=3063e50502040527378be5d5@mail.gmail.com \
--to=waruiinu@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.