Windows 10: Converting to IPV6 - how do I set up Local LAN addresses

Hi there

ISP is migrating to IPV6 shortly. I'm going to bite the bullet and try to convert LAN adresses to IPV6 -- not sure how to do this Google isn't totally helpful on this either.

I believe for the switch over period one can use something like a NAT64 gateway for access to both IPV4 and IPV6 systems.

I've set the DNS's in the router to use Google;s public DNS64 which are :

2001:4860:4860::6464
2001:4860:4860::64

My Routers IPV6 menu suggests I use default link as gateway

2001:0db8:0:f101::1

This works so far on Internet

Google's public DNS64 returns IPV4 addresses as "pseudo" ipv6 ones which

I've set the router to IPV4/IPV6 dual stack.

I'm stuck on what I should use on the local LAN though. I've only got 1 Linux computer now with Internet access -should be up to 4 - 6 windows machines, plus 3 android phones plus an amazon fire TV box, 2X Linux NAS servers and a smart TV.

The amazon TV works as does the smart TV but I haven't a clue about the local computers.

I can only access the NAS box now from another Linux VM an -- Windows machines just don't get a look in.

This is only a test --I can revert back but eventually this will have to work and I've a bit of free time today to play with this.

BTW take a note of ALL settings before playing with any of this type of stuff as it will an impossible job to get it all back again if it doesn't work.

Would appreciate help from Gurus.

Router is IPV6 capable - no probs there.





Cheers
jimbo

:)

 

MWS: starting server using WLAN not working

That's a perfectly valid IPv6 address.

 

Windows 10 hosted network hotspot problem

No luck. I responded to Robert Aldwinckle December 8, 2017 post as well. Here is some further info:

Windows IP Configuration

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : home

Link-local IPv6 Address . . . . . : fe80::886e:36dc:69c1:12fc%6

IPv4 Address. . . . . . . . . . . : 192.168.1.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.1.1
Wireless LAN adapter Wireless Network Connection:
Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : home
Wireless LAN adapter Local Area Connection* 12:
Connection-specific DNS Suffix . :

Link-local IPv6 Address . . . . . : fe80::4887:ee04:5578:bd52%8

IPv4 Address. . . . . . . . . . . : 192.168.137.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :
Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:208f:3239:9bf7:8c5a

Link-local IPv6 Address . . . . . : fe80::208f:3239:9bf7:8c5a%15

Default Gateway . . . . . . . . . : ::

The wireless LAN adapter doesn't have a default gateway. Is that normal?

Thank you.

 

Is your router set to DHCP6 on the lan side you probably have DHCP4 set properly already , I know mine was set to not configured or something like that.

 

They should be doing Dual Stack, since they will still have to run IPv4. ATT uses a 6rd Tunnel. Took some many tries to get it to work with my Cisco RV-320 gateway.

 

You don't have to do anything with your LAN - you can carry on using IP4.

 

Actually you do for those router/gateway units that use Dual Stack and you connect to the outside world through a DMZ or Passthrough mode on your provider's gateway. Otherwise it will just be IPv4 traffic from your side to the outside world.

 

Hi there

Fine -- everything working again now on LAN and IPV6 test on outside working + access to IVP6 and IVP4 sites. It will be a while before the whole hog goes IPV6 100% -- so the dual stack is just fine.

I think I made it more complex than it actually was -- case of "R.T.F.M" !!!!!!

Cheers
jimbo