@stlpaul:

From my icd2 investigation:

User call icd dbus method to "activate connection" (via status menu network list). icd will read list of plugins (from gconf) for that connection and start calling activate method of each plugin. But icd does not call next plugin until current does not tell icd "method call success" or "method call failed". if failed then icd deactivate connection and show error message - it will not try to continue.

ipv4 plugin method waiting for dbus signal DHCP connected which is sent via dbus-send from udhcpc script. ipv6 plugin method waiting for dbus signal DHCP6 connected which is sent again via dbus-send from dhcp-wide (v6).

both ipv4 and ipv6 support static ip address assign (from gconf key) and then dhcp client is not spawned and plugins tell immediately to icd "method success".

so ipv4 only network has problem that ipv6 plugin always fail if is not has static ip address config. I do not know correct gconf key for ipv6 plugin, so I workaround is: udhcpc script will send to icd dbus signal DHCP connected and DHCP6 too.

for (dhcp) ipv6 only networks workaround: when udhcpc timeout it send DHCP (v4) connected too, so icd spawn dhcp-wide v6 (thinks that ipv4 is already up). if dhcp-wide v6 will timeout, then it send DHCP6 disconned signal to icd and icd will disconnect network.

So for radvd ipv6 networks possible solution would be: if ipv6 address is assigned to wlan0 interface send both DHCP and DHCP6 connected dbus signal. icd then mark connection as connected. (dhcp v4 and dhcp v6 clients will be still running on background, but this could not be problem... they are small so no memory eating)