On 28/05 I added the IPv6 configuration, emailed yourself confirming the /64 assigned to the interface Gi0/1/1 ...

I believe that confirms that Daisy are in fact working the way AAISP did.

The writer specifically says the 2300 is a /64 within the the /56. In the same way as my /56s on AAISP were within my overall /48. At initial setup time they only "activated" the single subnet of my /48, and Daisy seem only to gave activated the 2300 /64.

However, the rest of the reply from them is just pathetic. Particularly "we reserve/route a /56 on our core and configure a /64 on your LAN interface". But that line also confirms they have only configured a /64, the 2300 one. The rest of your 23ff is "reserved" for if you require another subnet or subnets.

It may mean you can use the 2301 subnet if you wish, (as the other posters believe you can), and may work once you have the 2300 one working, but I reiterate that you need to get what they specify working before trying to go beyond it . A step at a time.

People already using IPv4 blocks will know why they want them, and the reasons they have those will be real. The only one I know of is having internet servers at home accessible from outside, but not wanting them on your own LAN.

There is also the Internet Of Things rapidly approaching, where segregating domestic devices on a different subnet isn't necessary for things to work, but could save a lot of time diagnosing local faults without needing to disable access on other subnets.

Re your own setup, see what I said about your two screenshots in the post you replied to. Particularly the router IPv6 address.

What the two 2001:xxx:xxx:101::35: lines are about I have no idea unless they are to do with the leased line connection itself to their system, for any management they may need to do. (I expect you know your first "xxxx" after the 2001 identifies Daisy as the CP). Seeing as they haven't previously mentioned them as having anything to do with user-configuration I almost wonder if the writer is just trying to be rude "clever".

Just another thing that if you don't know about it can help a lot, and assuming you are using Windows. Click the Windows key and when the menu pops up type Command prompt. (It will come up offering the app you want after a few characters).

In the black window type
ipconfig /all
and press Return

This will not "do" or alter anything. It will list all the connections your computer is seeing, with their IPv4, IPv6 and Temp addresses. This sort of thing:

Wireless LAN adapter WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8822BE 802.11ac PCIe Adapter
Physical Address. . . . . . . . . : 5C-BA-EF-B3-79-FF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd24:fb65:5fe3:3300:68aa:1ef9:2660:c64(Preferred)
Temporary IPv6 Address. . . . . . : fd24:fb65:5fe3:3300:90f8:a8ee:44a9:7cc1(Preferred)
Link-local IPv6 Address . . . . . : fe80::68aa:1ef9:2660:c64%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.8.150(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 July 2021 18:45:00
Lease Expires . . . . . . . . . . : 28 July 2021 17:16:43
Default Gateway . . . . . . . . . : 192.168.8.1
DHCP Server . . . . . . . . . . . : 192.168.8.1
DHCPv6 IAID . . . . . . . . . . . : 89963247
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-13-4B-F4-F8-0D-AC-20-11-9B
DNS Servers . . . . . . . . . . . : fe80::26fb:65ff:fe5f:e333%8
192.168.8.1
NetBIOS over Tcpip. . . . . . . . : Enabled

The directly attached static route (ipv6 route 2001:xxx:xxx:2300::/56 Vlan100) is useless here, you need them to add a recursive static route.

Not being familiar with how Cisco routers handle overlapping addresses and subnets (as the 2001:xxx:xxx:2300::/64 subnet is part of the larger 2001:xxx:xxx:2300::/56) I'd suggest asking for just some of the /56 to be routed to the UDMP WAN address, e.g. ipv6 route 2001:xxx:xxx:2310::/60 2001:xxx:xxx:2300::2/64 which would route 16 of the subnets (2001:xxx:xxx:2310::/64 to 2001:xxx:xxx:231f::/64) to the UDMP.

In reply to a post by Pheasant:

Think it would be useful to get an output from the UDM of the IPv6 routes and routing tables. Can you get that from the CLI/shell commands?

Can various devices connected the LAN ping6 each other and the UDM?

I can only get the IPv4 routing table, will continue to look into it though.

I'll attempt to ping6 some other devices when on site tomorrow.

In reply to a post by pluralist:

On 28/05 I added the IPv6 configuration, emailed yourself confirming the /64 assigned to the interface Gi0/1/1 ...

I believe that confirms that Daisy are in fact working the way AAISP did.

The writer specifically says the 2300 is a /64 within the the /56. In the same way as my /56s on AAISP were within my overall /48. At initial setup time they only "activated" the single subnet of my /48, and Daisy seem only to gave activated the 2300 /64.

However, the rest of the reply from them is just pathetic. Particularly "we reserve/route a /56 on our core and configure a /64 on your LAN interface". But that line also confirms they have only configured a /64, the 2300 one. The rest of your 23ff is "reserved" for if you require another subnet or subnets.

It may mean you can use the 2301 subnet if you wish, (as the other posters believe you can), and may work once you have the 2300 one working, but I reiterate that you need to get what they specify working before trying to go beyond it . A step at a time. I believe I do have it working, when my laptop is plugged into the cisco with a static IPv6 address of 2001:xxx:xxx:2300::2

People already using IPv4 blocks will know why they want them, and the reasons they have those will be real. The only one I know of is having internet servers at home accessible from outside, but not wanting them on your own LAN.

There is also the Internet Of Things rapidly approaching, where segregating domestic devices on a different subnet isn't necessary for things to work, but could save a lot of time diagnosing local faults without needing to disable access on other subnets.

Re your own setup, see what I said about your two screenshots in the post you replied to. Particularly the router IPv6 address. I'm pretty sure that in. the UDMP WAN settings "Router" should be 2001:xxx:xxx:2300::1, if it's anything else, I cant ping out from the the UDMP.

What the two 2001:xxx:xxx:101::35: lines are about I have no idea unless they are to do with the leased line connection itself to their system, for any management they may need to do. (I expect you know your first "xxxx" after the 2001 identifies Daisy as the CP). Seeing as they haven't previously mentioned them as having anything to do with user-configuration I almost wonder if the writer is just trying to be rude "clever".

Just another thing that if you don't know about it can help a lot, and assuming you are using Windows. Click the Windows key and when the menu pops up type Command prompt. (It will come up offering the app you want after a few characters).

In the black window type
ipconfig /all
and press Return

This will not "do" or alter anything. It will list all the connections your computer is seeing, with their IPv4, IPv6 and Temp addresses. This sort of thing:

Wireless LAN adapter WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8822BE 802.11ac PCIe Adapter
Physical Address. . . . . . . . . : 5C-BA-EF-B3-79-FF
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : fd24:fb65:5fe3:3300:68aa:1ef9:2660:c64(Preferred)
Temporary IPv6 Address. . . . . . : fd24:fb65:5fe3:3300:90f8:a8ee:44a9:7cc1(Preferred)
Link-local IPv6 Address . . . . . : fe80::68aa:1ef9:2660:c64%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.8.150(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 July 2021 18:45:00
Lease Expires . . . . . . . . . . : 28 July 2021 17:16:43
Default Gateway . . . . . . . . . : 192.168.8.1
DHCP Server . . . . . . . . . . . : 192.168.8.1
DHCPv6 IAID . . . . . . . . . . . : 89963247
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-13-4B-F4-F8-0D-AC-20-11-9B
DNS Servers . . . . . . . . . . . : fe80::26fb:65ff:fe5f:e333%8
192.168.8.1
NetBIOS over Tcpip. . . . . . . . : Enabled

I'm using a Mac but here's my ifconfig output if it's useful at all.

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
Jays-MBP-3:~ jaycockerill$ ifconfig
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether 8c:85:90:1b:32:7f
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (<unknown type>)
status: inactive
en3: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 82:80:e9:45:20:01
media: autoselect <full-duplex>
status: inactive
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 82:80:e9:45:20:00
media: autoselect <full-duplex>
status: inactive
en4: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 82:80:e9:45:20:05
media: autoselect <full-duplex>
status: inactive
en2: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
options=460<TSO4,TSO6,CHANNEL_IO>
ether 82:80:e9:45:20:04
media: autoselect <full-duplex>
status: inactive
bridge0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=63<RXCSUM,TXCSUM,TSO4,TSO6>
ether 82:80:e9:45:20:00
Configuration:
id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
ipfilter disabled flags 0x0
member: en1 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 7 priority 0 path cost 0
member: en2 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 9 priority 0 path cost 0
member: en3 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 6 priority 0 path cost 0
member: en4 flags=3<LEARNING,DISCOVER>
ifmaxaddr 0 port 8 priority 0 path cost 0
nd6 options=201<PERFORMNUD,DAD>
media: <unknown type>
status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
options=400<CHANNEL_IO>
ether 0e:85:90:1b:32:7f
media: autoselect
status: inactive
awdl0: flags=8902<BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1484
options=400<CHANNEL_IO>
ether fa:03:e3:95:cd:68
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: inactive
llw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=400<CHANNEL_IO>
ether fa:03:e3:95:cd:68
nd6 options=201<PERFORMNUD,DAD>
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::db14:98c5:c453:721b%utun0 prefixlen 64 scopeid 0xe
nd6 options=201<PERFORMNUD,DAD>
utun1: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
inet6 fe80::a8d5:ddbb:8ead:7282%utun1 prefixlen 64 scopeid 0xf
nd6 options=201<PERFORMNUD,DAD>
utun2: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::8b09:3921:9b3a:d7c3%utun2 prefixlen 64 scopeid 0x10
nd6 options=201<PERFORMNUD,DAD>
utun3: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::94fd:b39a:29a5:f512%utun3 prefixlen 64 scopeid 0x11
nd6 options=201<PERFORMNUD,DAD>
utun4: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::895a:8e24:5b10:d0cc%utun4 prefixlen 64 scopeid 0x12
nd6 options=201<PERFORMNUD,DAD>
utun5: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::27ad:5962:7497:8600%utun5 prefixlen 64 scopeid 0x13
nd6 options=201<PERFORMNUD,DAD>
utun6: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::2868:3424:eb1:9d54%utun6 prefixlen 64 scopeid 0x14
nd6 options=201<PERFORMNUD,DAD>
utun7: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::ec0e:f6b6:c678:8a70%utun7 prefixlen 64 scopeid 0x15
nd6 options=201<PERFORMNUD,DAD>
utun8: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::22c2:5dd4:a19e:94b3%utun8 prefixlen 64 scopeid 0x18
nd6 options=201<PERFORMNUD,DAD>
utun9: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1380
inet6 fe80::e416:d0f0:269b:711a%utun9 prefixlen 64 scopeid 0x19
nd6 options=201<PERFORMNUD,DAD>
en5: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ether ac:de:48:00:11:22
inet6 fe80::aede:48ff:fe00:1122%en5 prefixlen 64 scopeid 0x4
nd6 options=201<PERFORMNUD,DAD>
media: autoselect
status: active
en8: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
options=6467<RXCSUM,TXCSUM,VLAN_MTU,TSO4,TSO6,CHANNEL_IO,PARTIAL_CSUM,ZEROINVERT_CSUM>
ether 00:e0:4c:68:05:b3
inet6 fe80::c3f:6e5a:3068:6ccb%en8 prefixlen 64 secured scopeid 0x1b
inet 10.10.1.201 netmask 0xfffffe00 broadcast 10.10.1.255
inet6 2001:xxx:xxx:2301::4fb prefixlen 64 dynamic
nd6 options=201<PERFORMNUD,DAD>
media: autoselect (1000baseT <full-duplex>)
status: active

In reply to a post by tdw42:

The directly attached static route (ipv6 route 2001:xxx:xxx:2300::/56 Vlan100) is useless here, you need them to add a recursive static route.

Not being familiar with how Cisco routers handle overlapping addresses and subnets (as the 2001:xxx:xxx:2300::/64 subnet is part of the larger 2001:xxx:xxx:2300::/56) I'd suggest asking for just some of the /56 to be routed to the UDMP WAN address, e.g. ipv6 route 2001:xxx:xxx:2310::/60 2001:xxx:xxx:2300::2/64 which would route 16 of the subnets (2001:xxx:xxx:2310::/64 to 2001:xxx:xxx:231f::/64) to the UDMP.

Thanks, I think I'll send this in reply to Daisy, can anyone think of anything else pertinent to add?

In reply to a post by JESC77:

int Vlan100
ipv6 address 2001:xxx:xxx:2300::1/64
!
ipv6 route 2001:xxx:xxx:2300::/56 Vlan100

It looks like for some reason they've configured the /56 route as a directly attached route. In everything I've set up the ipv6 route line would read:

ipv6 route 2001:xxx:xxx:2300::/56 2001:xxx:xxx:2300::2

As in, it's saying everything in the /56 is accessible via your UDM.

Can you packet capture the WAN side of your UDM? If you ping an address within the /56 but not inside the /64 assigned to the WAN interface itself then you should see those pings. If you don't then the route isn't configured correctly.

Edit: I see this is what tdw42 suggested already.

Edited by jpm (Tue 27-Jul-21 21:55:53)

In reply to a post by tdw42:

The directly attached static route (ipv6 route 2001:xxx:xxx:2300::/56 Vlan100) is useless here, you need them to add a recursive static route.

Not being familiar with how Cisco routers handle overlapping addresses and subnets (as the 2001:xxx:xxx:2300::/64 subnet is part of the larger 2001:xxx:xxx:2300::/56) I'd suggest asking for just some of the /56 to be routed to the UDMP WAN address, e.g. ipv6 route 2001:xxx:xxx:2310::/60 2001:xxx:xxx:2300::2/64 which would route 16 of the subnets (2001:xxx:xxx:2310::/64 to 2001:xxx:xxx:231f::/64) to the UDMP.

In other words, I think what you are saying is that the Cisco box is basically not able to determine the next hop simply using the Vlan100 interface as the destination. By adding the recursive route with the /60 you are effectively adding a proper next hop.

Why though only specify a subset of the /56 ?

Edit: I see that jpm has posted as I was scribing. oops 😂😀

Edited by Pheasant (Tue 27-Jul-21 22:10:48)

In reply to a post by jpm:

In reply to a post by JESC77:

int Vlan100
ipv6 address 2001:xxx:xxx:2300::1/64
!
ipv6 route 2001:xxx:xxx:2300::/56 Vlan100

It looks like for some reason they've configured the /56 route as a directly attached route. In everything I've set up the ipv6 route line would read:

ipv6 route 2001:xxx:xxx:2300::/56 2001:xxx:xxx:2300::2

As in, it's saying everything in the /56 is accessible via your UDM.

Can you packet capture the WAN side of your UDM? If you ping an address within the /56 but not inside the /64 assigned to the WAN interface itself then you should see those pings. If you don't then the route isn't configured correctly.

Edit: I see this is what tdw42 suggested already.

I can ping 2001:b98:301:2300:: from the UDMP.

I received a phone call from the same lead engineer that sent me the last email today, he insists that their configuration is correct as is proved by my laptop working when plugged into their cisco. They provide many customers with working IPv6 using the same setup as mine. He said that recursive routing is very specialised and unnecessary in my situation.
Then received the email below:

As suggested we allocate /56 for yourself on our core and route this to site. We understand you will not need that many IPv6’s addresses/subnet’s, so we allocate a /64 (1 IPv6 network) to your LAN and also still route the /56 to the back of this LAN so you are able to utilise any IPv6 addresses you wish within the /56 (even outside of the /64 configured). That is the reason for the route you questioned.

When you connect a laptop to the same part of your LAN as the Ubiquity controller and configure the laptop with the IPv6 configuration I provided you are able to gain external Internet facing IPv6 connectivity, however when you connect your Ubiquity to the same part of your LAN and configure it (as you’ve advised) to the same details you can’t gain external Internet facing IPv6 connectivity via the diagnostic console of the device and can’t hit or get past the gateway, meaning the issue is 100% the configuration on the Ubiquity or another factor on the Ubiquity.

Unfortunately we can’t support that. I would suggest to continue with Ubiquity support, advise them the exact scenario stated above, the exact configuration you’ve added at which point they can’t say it’s not an issue with their kit.

My reply:
To clarify my situation:
I can only get IPv6 connectivity when my laptop is plugged directly it Gi0/0/0 on your Cisco.
When my laptop is connected to the UDM Pro, with the UDM Pro plugged into Gi0/0/0, it doesn’t matter if I set a static IP on my laptop or it is assigned one with DHCPv6, it doesn’t work. The UDM Pro does has IPv6 connectivity as I can ping6 when logged in with SSH.

When you say the UDM Pro as IPv6 connectivity because you can ping6 when looged in with SSH, what exactly do you mean? IIRC you pinged it from the Cisco?

What is sending the ping to what address?

Is there a setting on the UDM Pro to respond or not to incoming IPv6 pings? If there is, have you allowed them?

For a further diagnostic, another thing that occurred to me about you getting IPv6 connectivity from your laptop when you plug it into the Cisco, instead of you pinging anything please go onto the tbb Main Site and set up a BQM with the IP address it detects. It should be the IP address of your laptop. (Remember it takes a few minutes for anything useful to show up on the graph).

Have you tried my suggested change to the IPv6 Address in that setup page where I recommended ::1 not ::2?