On 1/2/19 10:10 AM, Lee Howard wrote:
DHCPv6 is fine.
Jordi did a panel a year ago at APNIC where he browbeat vendors about
supporting transition mechanisms. The summary is that they said they
have code, they just don't want to ship everything, because it's more to
maintain.
On 1/2/19 7:59 AM, Brandon Martin wrote:
On 1/2/19 7:37 AM, Mikael Abrahamsson wrote:
Yes, we're buying devices from a vendor that uses OpenWrt as base for
their operating system. We're using this one currently:
https://www.intenogroup.com/products/gateways/eg400/
We remotely manage it
On Wed, 2 Jan 2019, Brandon Martin wrote:
Out of curiosity, what do you use to terminate the MAP/LW4o6 tunnels/encaps
to the public Internet? Plenty of options here, of course, especially at the
traffic rates I'm moving. I'm just curious what others' experiences have
been as these are still
On 1/2/19 7:37 AM, Mikael Abrahamsson wrote:
Yes, we're buying devices from a vendor that uses OpenWrt as base for
their operating system. We're using this one currently:
https://www.intenogroup.com/products/gateways/eg400/
We remotely manage it using Netconf/YANG from our NMS so we can do
On Wed, 2 Jan 2019, Brandon Martin wrote:
On 12/14/18 11:51 AM, Mikael Abrahamsson wrote:
We use this to configure LW4o6 tunnels using DHCPv6. This is already
present in OpenWrt via the MAP package. It supports both MAP-E and LW4o6.
So I guess you're deploying "RG" style CPE routers to your
On 12/14/18 11:51 AM, Mikael Abrahamsson wrote:
We use this to configure LW4o6 tunnels using DHCPv6. This is already
present in OpenWrt via the MAP package. It supports both MAP-E and LW4o6.
So I guess you're deploying "RG" style CPE routers to your customers
that you've loaded OpenWRT onto?
On Fri, 14 Dec 2018, Brandon Martin wrote:
Are there any (draft, standard, or otherwise) defined mechanisms for
indicating to customer-provided devices that they should configure IPv6 to
IPv4 transition mechanisms such as MAP, 4rd, 464XLAT, etc. and providing the
configuration details
-Mensaje original-
De: NANOG en nombre de Brandon Martin
Fecha: viernes, 14 de diciembre de 2018, 17:20
Para: "nanog@nanog.org"
Asunto: Auto-configuring IPv6 transition mechanisms on customer devices
Are there any (draft, standard, or otherwise) defined mechanisms for
Are there any (draft, standard, or otherwise) defined mechanisms for
indicating to customer-provided devices that they should configure IPv6
to IPv4 transition mechanisms such as MAP, 4rd, 464XLAT, etc. and
providing the configuration details thereof?
I'm not aware of any. It seems like this
9 matches
Mail list logo
