So yes, the /64 setup is correct and you can successfully connect a laptop. From you previous posts you indicated that from the UDMP console you do have internet access (ping, traceroute work), so why are they saying it doesn't?

They don't seem to understand how IPv6 works, the issue has nothing to do with the UDMP - any device of yours routing the other IPv6 subnets would face the same issue.

In reply to a post by pluralist:

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? The UDMP is to ipv6.google.com, for example

Is there a setting on the UDM Pro to respond or not to incoming IPv6 pings? If there is, have you allowed them?
Not that I'm aware of, what would that be called on another vendors device?

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).Ok will do, however, when I connect that way I have to set a static IP on my laptop and anything from 2001:xxx:xxx:2300::2 - 2001:xxx:xxx:2300::ffff works

Have you tried my suggested change to the IPv6 Address in that setup page where I recommended ::1 not ::2?
Yes, it didn't work, the Router (cisco) address has to be 2001:xxx:xxx:2300::1 and and UDMP address can't be the same.

In reply to a post by tdw42:

So yes, the /64 setup is correct and you can successfully connect a laptop. From you previous posts you indicated that from the UDMP console you do have internet access (ping, traceroute work), so why are they saying it doesn't? I'm not sure but think I've clarified my situation in my email reply.

They don't seem to understand how IPv6 works, the issue has nothing to do with the UDMP - any device of yours routing the other IPv6 subnets would face the same issue. My problem is that they understand it more than I do, so when I get a phone call, I can't argue my case.

Have you told them that the UDMP is a router, and so requires the recursive static route.

The UniFi UDM/USG block ICMP/ICMPv6 from WAN by default which is discouraged as it breaks things such as path MTU discovery. Under Settings, Routing & Firewall on the Firewall, Rules IPv6 tab for the WAN LOCAL interface create a rule with Rule Applied = After predefined rules, Action = Accept, IPv6 Protocol = ICMPv6, IPv6 ICMP Type Name = Echo Request (Classic UI, it may be different in the new UI). This can be repeated for other ICMP types e.g. Destination Unreachable, Packet Too Big

In reply to a post by JESC77:

Traceroute from https://network-tools.webwiz.net/traceroute.htm to 2001:xxx:xxx:23aa::4fb automatically assigned to my laptop (tried configuring the LAN with 23aa for the hell of it).

1 1 ms 2a00:85c0:1::2
2 5 ms 2001:1900:5:2:2:0:8:7d75
3 5 ms 2001:1900:2::3:159
4 6 ms 2001:1900:5:2:2::2a5e
5 9 ms 2001:b98:1:1::ff3e:b0
6 12 ms 2001:b98:300:101::35:2
7 Timeout Unknown Host did not respond to ping

Cheers

When you were speaking to their engineer. Did you mention the above?

Seem to me they think if your laptop is directly connected to the Cisco all is hunky dory but it isn't is it. Therein lies your line of questioning to them that proves that their routing in is broken.

In reply to a post by tdw42:

Have you told them that the UDMP is a router, and so requires the recursive static route. I assumed he did but will double check.

The UniFi UDM/USG block ICMP/ICMPv6 from WAN by default which is discouraged as it breaks things such as path MTU discovery. Under Settings, Routing & Firewall on the Firewall, Rules IPv6 tab for the WAN LOCAL interface create a rule with Rule Applied = After predefined rules, Action = Accept, IPv6 Protocol = ICMPv6, IPv6 ICMP Type Name = Echo Request (Classic UI, it may be different in the new UI). This can be repeated for other ICMP types e.g. Destination Unreachable, Packet Too Big I've created those rules but still can't ping the UDMP.

In reply to a post by Pheasant:

In reply to a post by JESC77:

Traceroute from https://network-tools.webwiz.net/traceroute.htm to 2001:xxx:xxx:23aa::4fb automatically assigned to my laptop (tried configuring the LAN with 23aa for the hell of it).

1 1 ms 2a00:85c0:1::2
2 5 ms 2001:1900:5:2:2:0:8:7d75
3 5 ms 2001:1900:2::3:159
4 6 ms 2001:1900:5:2:2::2a5e
5 9 ms 2001:b98:1:1::ff3e:b0
6 12 ms 2001:b98:300:101::35:2
7 Timeout Unknown Host did not respond to ping

Cheers

When you were speaking to their engineer. Did you mention the above? I emailed him all the traceroutes I've done when on the call.

Seem to me they think if your laptop is directly connected to the Cisco all is hunky dory but it isn't is it. Therein lies your line of questioning to them that proves that their routing in is broken. They do know that I can't make it work through the UDMP.

Are you unequivocally saying that because my laptop works when connected to the cisco, it is not proof of correct configuration on Daisys network?

Edited by JESC77 (Thu 29-Jul-21 09:35:06)

I just created a new firewall rule, ICMPv6 on WAN Local and can now traceroute to my UDMP. Could that mean that their config is correct?


Hop Time IP Address Hostname Country
1 0 ms 2a00:85c0:1::2
2 5 ms 2001:1900:5:2:2:0:8:7d75
3 13 ms 2001:1900:2::3:159 l
4 5 ms 2001:1900:5:2:2::2a5e
5 8 ms 2001:b98:1:1::ff3e:b0
6 12 ms 2001:b98:xxx:101::35:2
7 12 ms 2001:b98:xxx:2300::2

This person had a similar problem to me and was able to resolve it by using the link local address of the router in front of his UDMP, could that be my solution?
https://community.ui.com/questions/UDM-Pro-with-Stat...

Well done. It's a step a right direction. At least now the WAN side of the UDM Pro is responding to external ping and traceroute.

Not sure that Ubiquity Community posting is going to help - Daisy have said they don't support DHCPv6 / Prefix Delegation from their network/gear so its down to ensuring that static routing for your subnets have been correctly setup on the Cisco WAN interface to your box - which from what I have read they claim they have been.

Have you tested now to see if you can get a route out from the LAN, laptop etc connected behind the UDM Pro can you ping6 out?