DHCPv6 rfc3315 support on Jolla

Question

28

DHCPv6 rfc3315 support on Jolla

asked 2014-01-07 21:57:40 +0200

Sailor

8053 ●81 ●106 ●124

Some environments use DHCPv6 but there is no support on SailfishOS for this.

I would like to have support not just for autoconfiguration but also for dhcpv6 which would help in enterprise environments to get IPv6 connectivity.

edit retag flag offensive close delete

Comments

I found out a interesting fact. It seems like Jolla is requesting a dhcpv6 address but does not assign it:

Jan 12 15:10:46 dhcp dhcpd: DHCPREQUEST for 192.168.0.11 (192.168.0.242) from 50:56:a8:01:24:94 via eth0
Jan 12 15:10:46 dhcp dhcpd: DHCPACK on 192.168.0.11 to 50:56:a8:01:24:94 via eth0
Jan 12 15:10:47 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 45435, transaction ID 0x35B55300
Jan 12 15:10:47 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546
Jan 12 15:10:48 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 50925, transaction ID 0x35B55300
Jan 12 15:10:48 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546
Jan 12 15:10:50 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 47162, transaction ID 0x35B55300
Jan 12 15:10:50 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546
Jan 12 15:10:55 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 34034, transaction ID 0x35B55300
Jan 12 15:10:55 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546

Sailor ( 2014-01-16 12:44:34 +0200 )edit

Ok I see Jolla is trying to connect to ipv6.jolla.com with it's link-local address which is not very successful ;).

20:04:31.620082 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 88) fe80::5054:ff:feef:dfce > fe80::5256:a8ff:fe01:2494: [icmp6 sum ok] ICMP6, destination unreachable, length 88, beyond scope 2406:da00:ff00::36e1:47c7, source address fe80::5256:a8ff:fe01:2494

Sailor ( 2014-01-16 21:06:55 +0200 )edit

Ok, in the config for the wlan which uses IPv6 DHCP the connman config includes the settings for dhcpv6 but the ip address gets not assigned to my interface but routes are installed correctly.

IPv6.method=auto
IPv6.privacy=disabled
IPv6.DHCP.DUID=000100011a48bd675056a8012494
IPv6.DHCP.LastAddress=<prefix>:1::fffd

Sailor ( 2014-01-17 18:02:42 +0200 )edit

Now I found some errors in journcalctl:

Jan 18 16:03:33 jolla connmand[833]: Set IPv6 host route error (Invalid argument)
Jan 18 16:03:36 jolla connmand[833]: Set IPv6 host route error (Invalid argument)
Jan 18 16:03:39 jolla connmand[833]: Set IPv6 host route error (Invalid argument)
Jan 18 16:03:42 jolla connmand[833]: Set IPv6 host route error (Invalid argument)

Sailor ( 2014-01-18 17:13:02 +0200 )edit

2

I have found out that everytime I delete the entire network from the connman directory and readd it via GUI. DHCPv6 is working but if I connect the next time it's not working anymore.

Sailor ( 2014-01-18 17:17:47 +0200 )edit

I found out a interesting fact. It seems like Jolla is requesting a dhcpv6 address but does not assign it:
Jan 12 15:10:46 dhcp dhcpd: DHCPREQUEST for 192.168.0.11 (192.168.0.242) from 50:56:a8:01:24:94 via eth0 Jan 12 15:10:46 dhcp dhcpd: DHCPACK on 192.168.0.11 to 50:56:a8:01:24:94 via eth0 Jan 12 15:10:47 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 45435, transaction ID 0x35B55300 Jan 12 15:10:47 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546 Jan 12 15:10:48 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 50925, transaction ID 0x35B55300 Jan 12 15:10:48 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546 Jan 12 15:10:50 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 47162, transaction ID 0x35B55300 Jan 12 15:10:50 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546 Jan 12 15:10:55 dhcp dhcpd: Confirm message from fe80::5256:a8ff:fe01:2494 port 34034, transaction ID 0x35B55300 Jan 12 15:10:55 dhcp dhcpd: Sending Reply to fe80::5256:a8ff:fe01:2494 port 546
Sailor ( 2014-01-16 12:44:34 +0200 )edit
Ok I see Jolla is trying to connect to ipv6.jolla.com with it's link-local address which is not very successful ;).
20:04:31.620082 IP6 (hlim 64, next-header ICMPv6 (58) payload length: 88) fe80::5054:ff:feef:dfce > fe80::5256:a8ff:fe01:2494: [icmp6 sum ok] ICMP6, destination unreachable, length 88, beyond scope 2406:da00:ff00::36e1:47c7, source address fe80::5256:a8ff:fe01:2494
Sailor ( 2014-01-16 21:06:55 +0200 )edit
Ok, in the config for the wlan which uses IPv6 DHCP the connman config includes the settings for dhcpv6 but the ip address gets not assigned to my interface but routes are installed correctly.
IPv6.method=auto IPv6.privacy=disabled IPv6.DHCP.DUID=000100011a48bd675056a8012494 IPv6.DHCP.LastAddress=<prefix>:1::fffd
Sailor ( 2014-01-17 18:02:42 +0200 )edit
Now I found some errors in journcalctl:
Jan 18 16:03:33 jolla connmand[833]: Set IPv6 host route error (Invalid argument) Jan 18 16:03:36 jolla connmand[833]: Set IPv6 host route error (Invalid argument) Jan 18 16:03:39 jolla connmand[833]: Set IPv6 host route error (Invalid argument) Jan 18 16:03:42 jolla connmand[833]: Set IPv6 host route error (Invalid argument)
Sailor ( 2014-01-18 17:13:02 +0200 )edit
I have found out that everytime I delete the entire network from the connman directory and readd it via GUI. DHCPv6 is working but if I connect the next time it's not working anymore.
Sailor ( 2014-01-18 17:17:47 +0200 )edit

Answer 1

12

answered 2014-01-20 11:40:50 +0200

Sailor

8053 ●81 ●106 ●124

updated 2014-01-20 12:06:18 +0200

Please update connman to minimum 1.17 because there (and in 1.16) are fixes for DHCPv6 and we have 1.15. https://connman.net/blogs/patrik/2013/connman-117
https://connman.net/blogs/patrik/2013/connman-116

edit flag offensive delete publish link

Accepted Answer

2

answered 2015-02-04 22:53:45 +0200

Sailor

8053 ●81 ●106 ●124

It looks like it's fixed in the latest update. For me it works now as expected.

edit flag offensive delete publish link

Answer 3

0

answered 2014-02-05 20:56:48 +0200

jr
421 ●6 ●13 ●15

DHCPv6 is started by ConnMan when the network supports it. So one needs radvd (or similar) in the network to send ND_RA_FLAG_MANAGED flag in its router advertisement message, that is the "AdvManagedFlag on" option in radvd configuration.

edit flag offensive delete publish link

Comments

But it's simply not working ;). Only on first try because DAD is failing on second try.

Sailor ( 2014-02-05 21:32:20 +0200 )edit

1

Then connman update to 1.17 or later is needed, it has important dhcpv6 fixes as you have noticed.

jr ( 2014-02-06 01:03:52 +0200 )edit

Answer 4

0

answered 2017-11-02 17:42:32 +0200

Manankanchu

9022 ●42 ●54 ●50

http://www.manankanchu.co...

DHCPv6 access on Jolla phone working without problem.

Trying IPv6 on Jolla tablet (ver. 2.1.2.3) proves it is only working with RA but not with DHCPv6

Anyone an idea why dhcpv6 client is faulty on Jolla tablet ?

edit flag offensive delete publish link

DHCPv6 rfc3315 support on Jolla

Comments

4 Answers

Comments

Question tools

Stats

Related questions

DHCPv6 rfc3315 support on Jolla

Comments

4 Answers

Comments

Question tools

Public thread

Stats

Related questions