ublox with ipv6
Thomas Schäfer
tschaefer at t-online.de
Tue Jun 8 19:53:38 UTC 2021
Hi,
I am not sure, if I asked it already. ModemManager gets all information about
IPv6, but it ignores them.
I made a successful IPv6 (dual stack) test with a combination of
NetworkManager/ModemManager and some manual commands.
I used version 1.14.8. (the latest in tumbleweed)
I haven't compiled the master version.
I attached the full mm debug log. But in reality only these line were
interesting:
ModemManager[3506]: <debug> [1623177383.777935] [modem0/ttyACM1/at] device
open count is 2 (close)
ModemManager[3506]: <debug> [1623177383.778026] [modem0/ttyACM1/at] <--
'<CR><LF>+CGEV: ME PDN ACT 5<CR><LF>'
ModemManager[3506]: <info> [1623177383.778131] [modem0] mobile equipment
request to activate context (cid 5)
ModemManager[3506]: <debug> [1623177383.778221] [modem0/ttyACM1/at] -->
'AT+UIPADDR=5<CR>'
ModemManager[3506]: <debug> [1623177384.037245] [modem0/ttyACM1/at] <--
'<CR><LF>+UIPADDR:
5,"usb0:4","10.212.96.155","255.255.255.0","",""<CR><LF><CR><LF
>OK<CR><LF>'
ModemManager[3506]: <debug> [1623177384.037492] [modem0/bearer0] (u-blox) IPv4
gateway address retrieved: 10.212.96.155
ModemManager[3506]: <debug> [1623177384.037537] [modem0/bearer0] (u-blox)
gathering IP and DNS information for PDP context #5...
ModemManager[3506]: <debug> [1623177384.037594] [modem0/ttyACM1/at] device
open count is 3 (open)
ModemManager[3506]: <debug> [1623177384.037657] [modem0/ttyACM1/at] device
open count is 2 (close)
ModemManager[3506]: <debug> [1623177384.037727] [modem0/ttyACM1/at] -->
'AT+CGCONTRDP=5<CR>'
ModemManager[3506]: <debug> [1623177384.052348] [modem0/ttyACM1/at] <--
'<CR><LF>+CGCONTRDP: 5,6,"internet.telekom.MNC001.MCC262.GPRS","'
ModemManager[3506]: <debug> [1623177384.053180] [modem0/ttyACM1/at] <--
'10.212.96.100.255.255.255.255","10.212.96.100","10.74.210.210","10.74.210.211","0.0.0.0","0.0.0.0",
0<CR><LF>'
ModemManager[3506]: <debug> [1623177384.053371] [modem0/ttyACM1/at] <--
'+CGCONTRDP: 5,6,"internet.telekom.MNC001.MCC262.GPRS","'
ModemManager[3506]: <debug> [1623177384.054811] [modem0/ttyACM1/at] <--
'42.1.5.152.185.1.249.22.0.1.0.1.106.104.189.236.255.255.255.255.255.255.255.255.255.255.255.255.255.255.255.255","42.1.5.152.185.1.249.22.0.1.0.1.106.104.189.236","42.1.5.152.7.255.0.0.0.16.0.116.2.16.2.16","42.1.5.152.7.255.0.0.0.16.0.116.2.16.2.17","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0","0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0",
0<CR><LF>'
ModemManager[3506]: <debug> [1623177384.055091] [modem0/ttyACM1/at] <--
'<CR><LF>OK<CR><LF>'
ModemManager[3506]: <debug> [1623177384.055319] [modem0/bearer0] (u-blox) IPv4
address retrieved: 10.212.96.100
ModemManager[3506]: <debug> [1623177384.055415] [modem0/bearer0] (u-blox) IPv4
subnet retrieved: 255.255.255.255
ModemManager[3506]: <debug> [1623177384.055468] [modem0/bearer0] (u-blox)
primary DNS retrieved: 10.74.210.210
ModemManager[3506]: <debug> [1623177384.055509] [modem0/bearer0] (u-blox)
secondary DNS retrieved: 10.74.210.211
ModemManager[3506]: <debug> [1623177384.055552] [modem0/bearer0] (u-blox)
finished IP settings retrieval for PDP context #5...
ModemManager[3506]: <debug> [1623177384.055618] [modem0/wwp0s20u1/net] port
now connected
ModemManager[3506]: <debug> [1623177384.055663] [modem0/bearer0] connected
ModemManager[3506]: <info> [1623177384.055883] [modem0] state changed
(connecting -> connected)
The gateway settings are a little bit strange, but it works.
"The default route should be created toward a fake
IPV6 address on the same network in order to forward the internet traffic on the
USB link."
So IP address, gateway and DNS-resolvers worked.
MTU is Ok. Speedtests were Ok too.
Regards,
Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ublox-modem-ipv6-dualstack-test.tar.xz
Type: application/x-xz-compressed-tar
Size: 42956 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20210608/711acf26/attachment-0001.bin>
More information about the ModemManager-devel
mailing list