I too am interested in this. I use a tunnel through Sixxs and I assign IPv6
addresses using radvd. I have radvd, aiccu, DNS, DHCP (v4 only) and IPv6
routing all running on a CentOS 6.5 server. All of my servers and
workstations are able to ping6 to outside targets, and anything with a browser
installed can open ipv6.google.com.
So far I have figured out that you have to run TWO instances of DHCP. One
instance issues IPv4 and the other issues IPv6. I have not gone so far as
to actually set up a second instance of DHCP.
My main questions revolve around getting internal IPv6 addresses updated into
the DNS server. Radvd won't do it. DHCPv6 seems to be deprecated though it
would probably work.
My ISP is AT&T DSL. They say they offer IPv6, but I found out recently that it
is really a 6rd tunnel. My Zoom router knows how to deal with IPv6 but not
6rd. Therefore I have nothing to gain by switching from Sixxs.
Within the 6 months or so I expect Google Fiber to become available to me.
That changes everything ... Or nothing!
Bill Gee
On Wednesday, October 01, 2014 03:13:34 Ashley M. Kirchner wrote:
> I'm completely confused here and I'm hoping someone here has a setup
> they're willing to share, or help me configure things on my end.
>
> My connectivity is through Comcast, who unfortunately, does not offer ipv6
> in my area. My connection goes like this:
> Comcast -> Motorola Surfboard Cable Router -> CentOS 6.5 server
>
> The CentOS server is multi-homed and manages the internal 192.168.x.x
> network by offering DHCP and firewall service (NATting and others.) DNS
> lookups are going to Comcast's servers.
>
> I have an IPV6 tunnel through Hurricane Electric (www.tunnelbroker.net).
> The tunnel is configured and is up and running on the CentOS server. I can
> ping several IPV6 addresses from it just fine:
>
> ping6 -n ipv6.google.com
> PING ipv6.google.com(2607:f8b0:400f:801::1006) 56 data bytes
> 64 bytes from 2607:f8b0:400f:801::1006: icmp_seq=1 ttl=53 time=109 ms
> 64 bytes from 2607:f8b0:400f:801::1006: icmp_seq=2 ttl=53 time=109 ms
> 64 bytes from 2607:f8b0:400f:801::1006: icmp_seq=3 ttl=53 time=106 ms
> ^C
> --- ipv6.google.com ping statistics ---
> 3 packets transmitted, 3 received, 0% packet loss, time 2436ms
> rtt min/avg/max/mdev = 106.905/108.723/109.756/1.317 ms
>
>
> What I'd like to do now is have DHCP offer ipv6 addresses as well. Problem
> is, I don't know how to configure it properly using the information given
> to me by Hurricane. I have my client address which is what the CentOS
> tunnel interface is. Then I have a routed /64 and /48 prefix which I *think*
> is what I'm supposed to use for my internal network (according to their
> info popup window) but I don't know how to configure DHCPd to use that and
> then route through the ipv6 interface.
>
> So does anyone here have a tunnel from HE and are using DHCP on an internal
> network handing out ipv6 addresses? Any suggestions of how to configure
> dhcpd6.conf?
>
> Thanks all.
> Ash
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
