ipv6 and NAT in multi machine networks

[pixel fairy]

so the IETF apparently hates NAT. but i cant see any other way to make "little internets" (multi machine networks with dns, mail, web or whatever servers you need to test with) that also have access to the real internet (for example to download packages).

building it all (a repo with said packages etc) is just a rediculous amount of work even with configuration mangement. maybe a docker compose file would work here as docker is pretty quick.

service proxies are obviously restrictive

so what to do to make an ipv6 only playground not sealed off from the outside? nat66?

ive done the v4 version to, mostly to test vpn, web and mail servers. has anyone done this in v6?

[Alvaro Miranda Aguilera]

hello.

If your home network have ipv6, that usually mean that you can create a VM with a bridge interface and everybox in your place will have a real ipv6.

now, if you don't want to do that, is where things go funny.

but vagrant + bridge + ipv6 dhcp runs fine.

Alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/061ed61e-0268-486d-aed9-df5267848ae2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[pixel fairy]

yes, i have ipv6 at home. but just adding all those machines to the lan isnt what i want. usually i have something like this,

internet--laptop--vagrant_isp---some_vagrant_server

                                            \--vagrant_router--other_vagrant_machines

and it gets more complex from there, for example testing vpn setups, or modeling existing networks. in all cases i only need "isp" or "backbone" to route to the real world while keeping all those other networks separate.