-=> On 12-31-19 20:07, Terry Roati wrote to Tony Langdon <=-

 TR> I was expecting that you would have setup IPv6 in the router and it
 TR> would have handled the IPv4 stuff as well.

You forget, I've had native IPv6 for _years_, so nothing needed to be done to
accommodate the IPv6 transport on my end.  It was the other end of the link
that upgraded their server, allowing me to switch to using IPv6 to carry the
tunnel.

 TL> Again, state your assumptions.

 TR> If running windows, did you have tochange the hosts file?

Windows on...?  And I again don't understand the relevance here.  Again, you
need to state yur assumptions.

The infrastructure here runs Linux, though there are a number of Windows
machines running as desktops.  This one also doubles as a file server for
nodelist processing, allowing me to update the nodelist data for my othernets
locally, but using the Linux boxes to do the automated processing.

 TL> Given that they have owned Internode, who have been offering IPv6
 TL> officially (i.e. not a trial) since 2011, and had it on a trial for
 TL> some time before then.

 TR> That's the mystery, however I get the impression that not all of IInet
 TR> supports IPv6 also based on what I have read in Whirlpool.

Yeah, it's been years.

 TL> Anyway, my network setup is fairly complex with several networks
 TL> running on the same wire.  The main router only handles the single
 TL> static IPv4 and the /56 from Internode.  There are a couple of other
 TL> networks in play.

 TR> Your setup does seem fairly complex but I am sure you have a reason for
 TR> this.

Yes, I participate in a lot of IP networks. :D

 TR> I just want to run a simple network of 3 PC's, NVR and a NAS. IPv6 will
 TR> allow me to run more domains which is about it.

Domains for what?  Web servers don't need IPs for extra domains.


... Klingons--the Harley riders of the universe
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux