The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
Please vote in the Forum Structure Poll. Polling will close at 2PM EST on January 21, 2025.
Going IPv6
Nakatomi2010
Registered User regular
Registered User regular
So, I've been contemplating for some time switching from IPv4 to IPv6 within my network for educational purposes, and I think I'm going to pull the trigger. Obviously I've got to make sure the dumb devices on my network, such as my BluRay players and Wii can support it, but ultimately it's probably giong to happen.
I have a Verizon router which currently pushes all of it's functions into a Netgear router. The Netgear router is doing DHCP. I don't want the Verizon router to be involved in this process, I'm going to consider it my fall back router and will probably keep it IPv4 and connect any devices that have issues to it. The Netgear WNR3500 however is what I'd like to continue segmenting my network.
I'm doing this to get a Microsoft Cert (70-642) which seems to have quiet a bit to do with IPv6 configuring, so I was going to spin up a server 2008 box and have it do the addressing.
If I turn off DHCP on the Netgear, it'll still have it's firewall kicking off right? I'd just have to reconfigure the ports to the newer IPv6 IPs.
Or will I need to segment the network again and keep a dedicated IPv6 line behind the server?
Make sense? If not, just let me know I'll try to explain it better.
Thanks.
I have a Verizon router which currently pushes all of it's functions into a Netgear router. The Netgear router is doing DHCP. I don't want the Verizon router to be involved in this process, I'm going to consider it my fall back router and will probably keep it IPv4 and connect any devices that have issues to it. The Netgear WNR3500 however is what I'd like to continue segmenting my network.
I'm doing this to get a Microsoft Cert (70-642) which seems to have quiet a bit to do with IPv6 configuring, so I was going to spin up a server 2008 box and have it do the addressing.
If I turn off DHCP on the Netgear, it'll still have it's firewall kicking off right? I'd just have to reconfigure the ports to the newer IPv6 IPs.
Or will I need to segment the network again and keep a dedicated IPv6 line behind the server?
Make sense? If not, just let me know I'll try to explain it better.
Thanks.
Check out me building my HTPC (NSF56K) (Updated 1-10-08)
Movie Collection
Foody Things
Holy shit! Sony's new techno toy!
Wii Friend code: 1445 3205 3057 5295
Movie Collection
Foody Things
Holy shit! Sony's new techno toy!
Wii Friend code: 1445 3205 3057 5295
Nakatomi2010 on
0
Posts
However - some questions to consider:
1) Does the Netgear even support IPv6? More specifically, does the router support IPv6->4 tunneling? I'm making an assumption that your ISP is not providing native IPv6 connectivity for you, so if you expect to get these devices out onto the internet, you will need something to handle the IPv6->4 translation.
2) If it does, you may want to check that its firewall services work with IPv6 traffic. Not sure why it wouldn't (especially since inbound requests would come in with an IPv4 address), but it's something to check.
3) Is it possible to disable IPv6 "DHCP" on the Netgear? It may by default assume you want to use stateless autoconfiguration, and I'm not sure if it will allow you to disable this.
If you want to go a simpler method, you could configure an IPv6 tunnel (http://ipv6.he.net/ provides free tunnel broker services) on the server in question. You should then be able to route all IPv6 traffic through the server and out the tunnel while keeping your legacy devices on the IPv4 network without making any topology changes..