Re: [v6ops] [*SPAM* Score/Req: 3.9/3.3] Re: [*SPAM* Score/Req: 3.9/3.3] Re: reclassify 464XLAT as standard instead of info

Le 20/09/2017 à 15:38, JORDI PALET MARTINEZ a écrit :
> Don’t know the chipset hardware details.

We cant make statements of functionality if we dont know which platform 
supports it.

> In our trials, they were several models from well know Chinese
> vendors.

Which ones?  Is Balong among them?

> I really doubt chipsets block DHCPv6 messages.

Jordi - I doubted too.  But then I checked.  I worked with operator and 
hw manufacturer.  I got advice from v6ops members.  We issued DHCP 
packets from linux and captured what arrives at PGW.  After months of 
test, I tell it is extremely likely the modem blocks.  Operator informs 
me it is extremely unlikely the BS, SGW and PGW blocks DHCP.  The linux 
does not block anything, it's open source, I checked.

What modems block is the following: std DHCP ports, multicast IP dst 
address of DHCP.  What modems dont block is the following: DHCP packets 
sent on non-std DHCP ports, or on unicast addresses.

There is no open source for these modems.

> You should contact
> those chipset vendors and make sure about that.

YEs, done that.  After discussion I can say that they feel like it's 
good to block it; they sometimes say "because that's the design".  I 
dont know what the design is that, but DHCPv6-PD is certainly not a 
design to block.

I wonder where do the modem manufacturers get the idea that a good 
design is one that does not do DHCP.

Alex
> 
> https://github.com/openwrt-routing/packages/blob/master/nat46/files/464xlat.sh
>
>  Regards, Jordi
> 
> 
> -----Mensaje original----- De: v6ops <v6ops-bounces@ietf.org> en
> nombre de Alexandre Petrescu <alexandre.petrescu@gmail.com> Responder
> a: <alexandre.petrescu@gmail.com> Fecha: miércoles, 20 de septiembre
> de 2017, 10:34 Para: <v6ops@ietf.org> Asunto: Re: [v6ops] [*SPAM*
> Score/Req: 3.9/3.3] Re: reclassify 464XLAT as standard instead of
> info
> 
> 
> 
> Le 20/09/2017 à 15:19, JORDI PALET MARTINEZ a écrit :
>> Google is your friend:
>> 
>> https://android.googlesource.com/platform/external/android-clat/
>> 
>> Same for other questions that you asked before … you can find it
>> also for OpenWRT.
> 
> Jordi, please let me ask again: I would like to ask you which LTE
> modem was inside the LTE router?
> 
> Because the Balong modem in some Huawei smartphones, and some 
> Qualcomm MDM8xxxx series in some IoT devices block DHCPv6 messages.
> 
> OpenWRT is an OS, not a  modem.  An OS runs on many kinds of modems. 
> Some modems block DHCP altogether.
> 
> You cant just redirect me to OpenWRT.
> 
> Alex
> 
>> 
>> Regards, Jordi
>> 
>> 
>> -----Mensaje original----- De: v6ops <v6ops-bounces@ietf.org> en
>> nombre de Alexandre Petrescu <alexandre.petrescu@gmail.com> 
>> Responder a: <alexandre.petrescu@gmail.com> Fecha: miércoles, 20 de
>> septiembre de 2017, 9:55 Para: Erik Kline <ek@google.com> CC:
>> "v6ops@ietf.org" <v6ops@ietf.org> Asunto: Re: [v6ops] reclassify
>> 464XLAT as standard instead of info
>> 
>> No need to stress terms like billions; that's what modem
>> manufacturers put on the market too routinely.  Maybe we can talk
>> trillions of IoT devices.  Maybe we can use the SI prefixes, like
>> exa, or peta.
>> 
>> That aside, I would like to ask you whether the CLAT src on Android
>> is something I could look at?
>> 
>> Alex
>> 
>> Le 20/09/2017 à 08:03, Erik Kline a écrit :
>>> There seem to be some misconceptions flying around here.
>>> 
>>>> Well, I dont think 464XLAT is deployed anywhere else than on
>>>> cellular. These are the big numbers that the Original Poster
>>>> talked about: miliions of users - they are on cellular.
>>> 
>>> 464xlat is a client-side bit of code (the NAT64+DNS64 in the
>>> network is the "other half").  It is primarily implemented in
>>> mobile devices, and primarily in Android, to be more specific.
>>> 
>>> As such, the number of 464xlat capable nodes is numbered in the
>>> /billions/.
>>> 
>>> There are also some wifi (and wired) networks that are IPv6-only
>>> with NAT64+DNS64; mobile networks aren't the only ones.
>>> 
>>> NAT64+DNS64 is easily the single most successful IPv6 transition 
>>> technology on the planet ([a] if one excludes "dualstack", [b]
>>> queue the Sean Spicer jokes).  464xlat can help ease things on
>>> the client side, but it's not the only way to do it (cf. iOS).
>>> 
>> 
>> _______________________________________________ v6ops mailing list 
>> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>> 
>> 
>> 
>> 
>> ********************************************** IPv4 is over Are you
>> ready for the new Internet ? http://www.consulintel.es The IPv6
>> Company
>> 
>> This electronic message contains information which may be
>> privileged or confidential. The information is intended to be for
>> the exclusive use of the individual(s) named above and further
>> non-explicilty authorized disclosure, copying, distribution or use
>> of the contents of this information, even if partially, including
>> attached files, is strictly prohibited and will be considered a
>> criminal offense. If you are not the intended recipient be aware
>> that any disclosure, copying, distribution or use of the contents
>> of this information, even if partially, including attached files,
>> is strictly prohibited, will be considered a criminal offense, so
>> you must reply to the original sender to inform about this
>> communication and delete it.
>> 
>> 
>> 
>> _______________________________________________ v6ops mailing list 
>> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
>> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 
> 
> 
> 
> ********************************************** IPv4 is over Are you
> ready for the new Internet ? http://www.consulintel.es The IPv6
> Company
> 
> This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the exclusive
> use of the individual(s) named above and further non-explicilty
> authorized disclosure, copying, distribution or use of the contents
> of this information, even if partially, including attached files, is
> strictly prohibited and will be considered a criminal offense. If you
> are not the intended recipient be aware that any disclosure, copying,
> distribution or use of the contents of this information, even if
> partially, including attached files, is strictly prohibited, will be
> considered a criminal offense, so you must reply to the original
> sender to inform about this communication and delete it.
> 
> 
> 
> _______________________________________________ v6ops mailing list 
> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
> 