On Tue, 27 Oct 2009 10:41:46 -0500
Jack Bates wrote:
> Jeroen Massar wrote:
> > But yes, the network stack itself is a different question, then again,
> > you can just route a /64 into the loopback device and let your apache
> > listen there... (which also allows you to do easy-failover as you ca
Brian Johnson wrote:
>> Last time I checked, and this may have changed, the limit in Linux was
>> around 4096.
>
> So in this circumstance you could route a /116 to the server. COOL!
These days what we might at one point have refered to as a host or
server may actually be a hardware container wi
8 steps in a
worst-case scenario.
The same concept applies to ipv4 cidr as well, but it is less obvious.
William
--Original Message--
From: Adrian Chadd
To: Jeroen Massar
Cc: North American Network Operators Group
Subject: Re: IPv6 could change things - Was: DMCA takedowns of networks
Se
On Tue, Oct 27, 2009 at 02:05:36PM +, Michael Dillon wrote:
> But, when IPv6 is a bit more common, there is no need for virtual
> hosters to share
> a single IP address between several sites. They may as well use a
> unique IPv6 address
> for every single site, even if they are all on the same
> -Original Message-
> From: Ray Soucy [mailto:r...@maine.edu]
> Sent: Tuesday, October 27, 2009 9:45 AM
> To: Jeffrey Ollie
> Cc: North American Network Operators Group
> Subject: Re: IPv6 could change things - Was: DMCA takedowns of
networks
>
> > But do
Once upon a time, Jeffrey Ollie said:
> But do the commonly-used operating systems support adding hundreds or
> thousands of addresses to an interface, and what would the performance
> implications be?
I've got Linux (and even Windows) boxes with several hundred IPs bound
today; I don't see why I
> But do the commonly-used operating systems support adding hundreds or
> thousands of addresses to an interface, and what would the performance
> implications be?
>
> Jeff Ollie
Last time I checked, and this may have changed, the limit in Linux was
around 4096.
In practice though, you also have
Jeroen Massar wrote:
But yes, the network stack itself is a different question, then again,
you can just route a /64 into the loopback device and let your apache
listen there... (which also allows you to do easy-failover as you can
move that complete /64 to a different box ;)
You are still com
On Tue, Oct 27, 2009, Jeroen Massar wrote:
> But yes, the network stack itself is a different question, then again,
> you can just route a /64 into the loopback device and let your apache
> listen there... (which also allows you to do easy-failover as you can
> move that complete /64 to a differen
Jeffrey Ollie wrote:
[..]
> But do the commonly-used operating systems support adding hundreds or
> thousands of addresses to an interface, and what would the performance
> implications be?
Remember that IP addresses are 128bits, while hostnames (the ones for
the "Host:" header in the HTTP query)
On Tue, Oct 27, 2009 at 9:05 AM, Michael Dillon
wrote:
>
> But, when IPv6 is a bit more common, there is no need for virtual
> hosters to share
> a single IP address between several sites. They may as well use a
> unique IPv6 address
> for every single site, even if they are all on the same serve
Michael Dillon wrote:
[..]
> [..] The
> side effect of this is
> that it makes the network operator's tool sharper, and able to knock
> down single sites
> with a /32 ACL.
You actually mean a /128 in the case of IPv6, the /32 would be the
complete ISP...
> For a hosting provider, I would think th
12 matches
Mail list logo
