Gene Heskett <gene.heskett@xxxxxxxxxxx> writes:
> Because here, everything is on a 192.168.x.x address, fixed using host files
> for dns resolution.
I've got both local IPv4 addresses and IPv6 addresses in my /etc/hosts
file. Works just fine. As for added complexity, it isn't really any
more complex than adding a few config lines. The rest is automatic.
In a lot of ways it is much simpler than IPv4 because folks learned
from their IPv4 mistakes and realized how important it was for IPv6 to
automatically configure itself.
> Anything that doesn't resolve locally gets sent to 192.168.X.1,
> which is a dd-wrt install which handles all the PPPoE stuffs to
> connect me to my adsl account. A max of 4 live machines here
> certainly doesn't need the complexity of ipv6.
>
> That is all I get from vz, and I have doubts they have anything setup that
> would forward an ipv6 query to my ipv4 address their quasi-dhcp issues.
I run openwrt here, but assume dd-wrt is similar. I bet it possible
to have dd-wrt router automatically forward all ipv6 addresses to the
global tun6to4 gateways. One wouldn't even need to have one's linux
box (or boxes) establish a tunnel. That way everything on your
ethernet gets a working IPv6 address. I believe this is also what
Apple's WIFI hocky-puck ("airport") routers do.
-wolfgang
--
Wolfgang S. Rupprecht http://www.full-steam.org/ (ipv6-only)
You may need to config 6to4 to see the above pages.
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
