On 01/09/15 12:01, Fraser McGlinn wrote:
On 01/09/15 06:04, steve wrote:
The server is remote, on the interwebs, and running CentOS6, which
does not offer NAT for IPv6. I'm hosting https://www.greengecko.co.nz
there over IPv4, but the IPv6 copy of the site is on the physical
server due to not being able to redirect.
I suppose I could just proxy it...
I'm not following what the problem is here - you can just have a prefix
that is routed to you and you can assign that on the VM Bridge,
otherwise just bridge the physical NIC to the virtual.
You need to get out of the idea of NAT for v6. It doesn't exist, and it
never will.
Remember in v6 land, you don't need to have global unicast addressing on
every interface, you can route over the link-local addressing
(fe80::/10). As long as the end to end v6 is global unicast it all works
fine.
If you can more clearly define your problem, and hopefully it will make
more sense to the list.
Cheers,
Fraser
I obviously am missing something here.
To rephrase.
What are the steps necessary to publish a KVM guest to the internet
using IPv6?
The server has a /120 allocation, which I have been using from 1 upwards
and have a dozen or more in use. How should I configure the server -
without bridging eth0: - to accomplish this, and what subnet will be
made available to the client??
Cheers,
Steve
--
Steve Holdoway BSc(Hons) MIITP
http://www.greengecko.co.nz
Linkedin: http://www.linkedin.com/in/steveholdoway
Skype: sholdowa
_______________________________________________
Linux-users mailing list
[email protected]
http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
