t;WISPA General List" <wireless@wispa.org>
> Sent: Tuesday, October 25, 2016 9:01:51 PM
> Subject: Re: [WISPA] IPV6 deploymernt
> Art,
> So I know of two solid methods that could solve your problem. Neither are
> super
> awesome and both would involve NAT.
> 1. I
ttp://tanjiwireless.com/<http://tanjiwireless.com/>
From: wireless-boun...@wispa.org <wireless-boun...@wispa.org> on behalf of Tim
Way <t...@way.vg>
Sent: Tuesday, October 25, 2016 6:01:51 PM
To: WISPA General List
Subject: Re: [WISPA] IPV6 dep
Art,
So I know of two solid methods that could solve your problem. Neither are
super awesome and both would involve NAT.
1. IPv6 only to the client with NAT64 and DNS64 to handle IPv4 only
connectivity
2. IPv4 CGN Shared Address Space, RFC 6598 100.64.0.0/10, and IPv6 Global
Unicast running in
Tim,
So we are an IPV4 ISP not able to get any more IPV4 address space. We have
IPV6 working in office, and on server network.
I have working windows and linux IPV6 only configured machines but
obviously they can only access IPV6 capable web sites and such.
But we will need to start assigning
Dual stack is a different architecture than having two separate networks
running with one running IPv4 and one running IPv6. To connect the two
disparate networks you would need to perform address family translation
(NAT64). In dual-stack it will prefer IPv6 when available, minus happy
eyeballs,
Any out there successfully deployed dual stack network can share what
equipment used for pure ipv6 access to ipv4 networks?
--
Arthur Stephens
Senior Networking Technician
Ptera Inc.
PO Box 135
24001 E Mission Suite 50
Liberty Lake, WA 99019
509-927-7837
ptera.com |
facebook.com/PteraInc |
