Re: Qualcomm "raw IP" mode (was Re: Huawei E398 cdc/serialmodem-ppp 3G/4G)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bjørn Mork <bjorn@xxxxxxx> writes:

>>  I do see the IPv6 address in the WMC dumps
>> from the WMC port though.  I don't recall ever seeing the IPv6
>> addressing details happening over QMI, but I'd have to do another dump
>> to be sure.  Windows might actually be listenting for RAs on the
>> interface, since ISTR that's officially supported in the 3GPP standards.
>> It's certainly mentioned in the eHRPD stuff for handoff between LTE and
>> EVDO.
>
> So there is a global IPv6 address (or prefix?) assigned?  And you can
> forward IPv6 traffic using it as a source address?
>
> Damn, I need an IPv6 enabled network.  Think I know someone to poke...

Yup, but not too successful just yet.  I got connected and could see
IPv6 addresses using QMI_WDS command 2d (removed the APN from this to
protect the guilty :-):

<= QMUX Header:
<=   len:    0x00bb
<=   sender: 0x80
<=   svc:    0x01
<=   cid:    0x04

<= QMI Header:
<=   Flags:  0x02
<=   TXN:    0x0006
<=   Cmd:    0x002d
<=   Size:   0x00af
<= [0x02] ( 4) 00 00 00 00      SUCCESS - QMI_ERR_NONE
<= [0x10] ( 9) 70 72 6f 66 69 6c 65 31 36       profile16
<= [0x11] ( 1) 03       .
<= [0x17] (33) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00       .................................
<= [0x1d] ( 1) 00       .
<= [0x1f] ( 2) 00 10    ..
<= [0x22] ( 1) 00       .
<= [0x24] ( 1) 00       .
<= [0x25] (17) 2a 02 21 21 00 00 00 04 20 d5 68 81 7e 0e e7 c0 40       *.!!.... .h.~...@
<= [0x26] (17) 2a 02 21 21 00 00 00 04 0c d0 94 91 d2 96 c1 34 40       *.!!...........4@
<= [0x27] (16) 20 01 46 00 00 04 00 00 00 00 00 00 00 01 00 53   .F............S
<= [0x28] (16) 20 01 46 00 00 04 10 00 00 00 00 00 00 01 00 53   .F............S
<= [0x2e] ( 1) 00       .


TLV 0x27 and 0x28 are the correct DNS servers.  And 0x25 and 0x26 are
sane looking addresses for my interface and the gateway (the trailing 40
is just the prefix length).

But I did not get any response from the modem to neither icmp6 RS nor
DHCPv6 solicitations. And configuring the address manually was sort of
cumbersome.  Looks like the modem does proxy neigbour discovery like it
does proxy ARP, and that makes DAD fail...  I had to do 
 "echo 0 >/proc/sys/net/ipv6/conf/wwan2/dad_transmits"
to make the address usable.

We did manage to pick up the packets on the other end, but never
reveived any replies so the link was never fully functional.  I suspect
that this might be related to the address configuration stuff as the
modem also disconnected after a while, like it does with IPv4
connections if you don't run DHCP or call QMI_WDS command 2d.  Note that
this happened even if I did call the latter.

So there are a few bits and pieces to figure out still wrt IPv6 address
configuration. I certainly hope that this doesn't mean that we are
required to use WMC for IPv6....

But the good news is that none of this could possibly require any driver
changes so it's all completely off-topic here ;-)



Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux