Home › Forums › Linux Support › Networking ›

How to support 50K IPv6 addresses on a single machine?

Feb 02, 2010  By cksen
 in

Hi,

Does anyone know if there is any way to configure 50K "virtual" IPv6 addresses on loopback device in Linux?
The aim is not to add all 50K IPv6 addresses one by one on the loopback/ETH device which will probably mess up the ip table on the system.
In IPv4, I am able to achieve that by specifying the IP address subnet on loopback device (e.g: "ip addr add 10.1.0.0/16 dev lo").
The same command does not seem to work the same way for IPv6. It only adds a single IPv6 address on loopback device and it automatically adds an "unreachable route" entry on the ipv6 route table for that IPv6 network prefix.

The reason I need this is because I am working on an application which tries to simulate 50K IPv6 addresses on a single Linux box.
The kernel version I am currently using is RHEL 2.6.9.55.

Any help would be greatly appreciated!!

Thanks!

Kai

‹ How to change MAC address in Ubuntu permanantly DHCP client ›

Not that easy FredR

Matt's picture
Submitted by Matt (not verified) on Tue, 04/20/2010 - 16:55.

FredR - I am looking into doing the exact same thing, with simulating thousands of IPv6 addresses on the system without having to create all the addresses, and most importantly so the system doesn't have the overhead of maintaining all of the IP addresses. In IPv4, it is possible to define a subnet on the loopback device in the way that Kai mentioned in his original post. That would allow all IP's from 10.1.0.0 --> 10.1.255.255 to be usable by the system... this is the same thing that I'm looking to accomplish with IPv6... basically to define a usable subnet on the loopback for IPv6, not just a script to generate all the IPv6 addresses as aliases...

any ideas?

Thanks,
Matt

maybe....

brandon's picture
Submitted by brandon on Thu, 02/18/2010 - 12:17.

for ip in {yourRangeOfIp}
do sudo /sbin/ifconfig lo inet6 add 2607:f0d0:1002:11::${ip}/64
done

might work

This seems pretty easy. Pick

FredR's picture
Submitted by FredR on Thu, 02/18/2010 - 10:19.

This seems pretty easy. Pick a real interface (eth0 for example). Write a script that adds subinterfaces to eth0 with your ipv6 addresses.

eth0.0 = 1st ipv6 address
eth0.1 = 2nd ipv6 address

and so on. Or you could use the iproute2 "ip" command to add several IPv6 addresses to a single interface:

/sbin/ip addr add 2001:470:X:XXX::XXXX:XXXX:17/64 dev eth0

Chances are, if the addresses are in the same subnet, you won't modify your host's routing table at all. In the above example, ::17 and ::18 would fall under the same /64 subnet.

-- FLR or flrichar is a superfan of Linux Journal, and goofs around in the LJ IRC Channel

Webcast
More Resources
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers

Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.

Learn More

Sponsored by AMD

White Paper
More Resources
Red Hat White Paper: Using an Open Source Framework to Catch the Bad Guy

Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6

Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.

Learn more about catching the bad guy in this free white paper.

Learn More

Sponsored by DLT Solutions