[TriLUG] IPv6 addressing question
Matt Flyer via TriLUG
trilug at trilug.org
Wed Oct 10 16:39:11 EDT 2018
Dear Trilug,
I have a production (Linode) server running a couple of hosts.
Recently I established HughesNet service for my parents in a rural
location where cable is not available, cell service is spotty, and DSL
is highly questionable. I noticed that HughesNet tries to use IPv6
instead of IPv4 - kudos to them.
However, I noticed that i could not connect to my hosts from the
HughesNet. The problem was that there was an IPv6 address assigned
that Apache wasn't listening on. I fixed that, but as I am running two
(SSL) hosts, I quickly ran into the SNI bull spit and allocated the
IPv6 address to one host.
I asked Linode for a second IPv6 address and they gave me a /64 block.
Yes thats 18,446,744,073,709,551,616 addresses and I want ONE.
I have been trying to understand how to use the IPv6 addresses and it
is about as clear as mud.
I know that my pool is: 2600:3c03::f03c:91ff:fe69:a6aa / 64
I took a guess at the /etc/network/interfaces file for the IPv6 and
came up with this:
iface eth0 inet6 static
address 2600:3c03::f03c:91ff:fe69:a6aa::1/64
gateway fe80::1
up ip addr add 2600:3c03::f03c:91ff:fe69:a6aa::2/64 dev eth0 label
eth0:1
down ip addr del 2600:3c03::f03c:91ff:fe69:a6aa::2/64 dev etho0 label
eth0:1
Basically there are two interfaces, eth0 and eth0:1 which listen on
different addresses and a similar block exists for the IPv4
configuration respectively.
My question to the group is, given the address pool, am I assigning the
addresses correctly with the ::1/64 and ::2/64 labels or am I missing
the boat here?
As it is a production server, I would like to avoid doing a reboot to
apply these settings only to have it crash and go off line, so I
thought I would ask the gurus who have been working with IPv6 first.
Thank You in advance.
More information about the TriLUG
mailing list