IP Cloud on iPv6

Hi,

I’m having issues on IP Cloud with IPv6. The public IPv6 does not get updated.

/ip cloud print
  ddns-enabled: yes
  ddns-update-interval: 1m
  update-time: yes
  public-address: 201.27.181.165
  public-address-ipv6: 2804:431:b799:39ca::8
  dns-name: axxxxxxxxxxx.sn.mynetname.net
  status: updated

This is my IPv6:

/ipv6 address print  
  Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local 
   #      ADDRESS                                     FROM-POOL INTERFACE                   ADVERTISE
   0  G 2804:431:c7f2:df3f::/64                    pool-ipv6 bridge                      yes

The IPv4 address is correct.

I tried forcing update, having a 1 min as DDNS update interval and nothing made the IPv6 address show correctly.
How should I get this resolved?


Thank you

Безымянный.png
Screenshot_1.png
You shoud request both adress and prefix in dhcp-v6-client

In IP Cloud you see IP address of the router

That somehow depends on ISP. In my case, router requests only prefix (but has add-default-route=yes set), stores received prefix into pool (ISP is giving out /56 prefixes). Then it assigns IPv6 address from pool to LAN interface. At this moment it’s got 3 IPv6 interfaces, only one is routable:

> /ipv6 address print
Flags: X - disabled, I - invalid, D - dynamic, G - global, L - link-local
 #    ADDRESS                                     FROM-POOL   INTERFACE                                                     ADVERTISE
 0  G 2a01:xx:yy:zz::1/64                         pool-ipv6   bridge                                                        yes
 1 DL fe80::6c3b:6bff:fe97:256f/64                            bridge                                                        no
 2 DL fe80::6e3b:6bff:fe97:256f/64                            ether1                                                        no

And yet IP cloud has both IPv6 and IPv4 addresses:

$ host <serial>.sn.mynetname.net
<serial>.sn.mynetname.net has address 89.xxx.yyy.zzz
<serial>.sn.mynetname.net has IPv6 address 2a01:xx:yy:zz::1

Seems like OP has it more or less exactly the same. Which makes me think there might be some intermittent problem with his router updating IP cloud DNS.

In case it matters: my router is running ROS 6.48.3