In reply to a post by tdw42:

The lowest address within each subnet prefix (the interface identifier set to all zeroes) is reserved as the "subnet-router" anycast address, try setting the LAN address to 2001:xxxx:xxxx:2301::1/64 instead of 2001:xxxx:xxxx:2301::/64

Unfortunately, this didn't work.

Thanks.

In reply to a post by pluralist:

In reply to a post by tdw42:

In reply to a post by pluralist:

Another minor point is that on your lan you should no longer see fe80 addresses. These are now "deprecated", meaning they are being phased out and shouldn't be used. The correct equivalent is fc00.

Completely incorrect.
...
You may be thinking of the fec0::/10 site-local address range which was deprecated in 2004 as what comprised a "site" was open to interpretation causing confusion. These should not be used.

You are right, except I wasn't thinking about fec0::/10. don't recall ever seeing that. I may have simply mis(speed)read something where fe80 v fc00 was being discussed. In particular wrt the 192.168.n.n of IPv4.

Thanks for pointing it out. The OP does need to get the right information.

Can you recap what info I need to get, please?

Thank you.

A lot has been said by many of us. So a recap is difficult.

All I can recommend at the moment is that you forget about the 2301. Just use the 2300, which should appear automatically in your LAN if things are set up correctly. As should one or other or several fe80s or fc00s.

It isn't impossible that the info you have from Daisy is slightly incorrect, possibly the person writing it making a mistake like I've made a few. Though most of what I've posted has not been challenged - as it's right .

I keep harking back to:

Provided to me by Daisy:

The IPv6 Range 2001:xxx:xxx:2300::/56 has been routed to port Gi0/1/0 (Vlan100, port currently in use by your IPv4 network) & Gi0/1/1 (Vlan100, port currently free) on the Cisco 1111-8P router. Please configure your network with the following details:

Gateway IP: 2001:xxx:xxx:2300::1/64

Usable IP's: 2001:xxx:xxx:2300::2 - 2001:xxx:xxx:2300:ffff:ffff:ffff:ffff

That quote has internal inconsistences. For the whole of the /56 to have been routed, i.e. available, the usable IP's would be "2001:xxx:xxx:2300::2 - 2001:xxx:xxx:23ff:ffff:ffff:ffff:ffff", so you could put anything you liked after the final "23". The "2300" at the end of the availables suggests to me a /64 has actually been routed. Not the /56 as stated.

Even if I'm wrong, the fact your using 2301 is not what they say is usable. So my recommendation throughout not just at the start of this post has been not to try 2301 until you get 2300 working. You definitely should not be specifying it within the 2300 LAN. The 2301 would be a different /64 subnet within the /56, though possibly with the same 2300 gateway.

PS: Let's see how wrong I'm shown to be with that little lot. Though I cannot be wrong in recommending to first get things working with no mention at all of 2301 in your setup .

Edit: The DHCP for your LAN in your router should be using the range Daisy specified as available, the full range of 2300 starting with "2". "1" being the external address of your router.

Edited by pluralist (Sat 24-Jul-21 16:02:18)

There is a difference between connecting an endpoint (the PC) and a router (the UDM Pro).

The WAN setup on the UDM Pro appears correct as the OP can successfully traceroute to an external site, the last hop of the traceroute to the UDM Pro likely fails due to the default firewall rules.

The UDM Pro will require a unique /64 on each interface, as would any router, it is not possible to use the same 2001:xxxx:xxxx:2300::/64 subnet on both WAN and LAN interfaces. Using 2001:xxxx:xxxx:2300::2/64 as the WAN address and 2001:xxxx:xxxx:2301::1/64 as the LAN address is perfectly valid.

As you say the Information from Daisy is contradictory, and I believe the issue is that they need to route the /56, or some subset thereof, to the UDM Pro WAN address. A traceroute to an address in any other subnet (so 2001:xxxx:xxxx:2301::1/64 to 2001:xxxx:xxxx:23ff::1/64) may or may not provide some information.

In reply to a post by jpm:

Have Daisy said what they are expecting the next-hop address to be for your /56 from the perspective of their router? Usually how I'd expect to see this configured is (ignoring VRRP to keep things simple):

ISP interface configured to 2300::1/64
Your firewall configured to 2300::2/64

The ISP then has a route in their network that the next-hop for 2300::/56 is 2300::2/64 so that traffic can actually get back to you.

If they've just stuck a /64 on an interface and given you a 'usable range' as if it's IPv4 networking then that won't work. I've had this discussion with ISPs a fair amount so it can get frustrating but normally someone who works there knows what you're after.

If the OP is able to raise a ticket to arrange a telecon with Daisy 2nd /3rd level support team responsible for configuring their customer addressing then that may be the most expedient way for both of them to walk through the config. Whilst both on the line, hopefully they can both cross check everything and get things moving.

You never know there may be an “ah ha” moment during which Daisy discover an error has been made on their side or some routing not been correctly configured….

Do you think I should ask for a /48 when I ask them to check their config (again)?

There’s no harm in it. It may be ‘force’ them to recheck the config. So from that perspective no bad thing.

In reply to a post by JESC77:

Hi, I hope this is useful.

Traceroute from https://network-tools.webwiz.net/traceroute.htm to Cisco
1 0 ms 2a00:85c0:1::2
2 6 ms 2001:1900:5:2:2:0:8:7d75
3 5 ms 2001:1900:2::3:159
4 5 ms 2001:1900:5:2:2::2a5e
5 8 ms 2001:xxx:1:1::ff3e:b0
6 12 ms 2001:xxx:xxx:2300::1

Traceroute from https://network-tools.webwiz.net/traceroute.htm to UDMP
1 0 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 7 ms 2001:xxx:1:1::ff3e:b0
6 12 ms 2001:xxx:xxx:101::35:2
7 Timeout Unknown Host did not respond to ping

From UDMP SSH
traceroute to ipv6.google.com (2a00:1450:4009:815::200e), 30 hops max, 72 byte packets
1 2001:xxx:xxx:2300::1 0.722 ms 0.592 ms 0.461 ms
2 2001:xxx:300:101::35:1 5.748 ms 6.417 ms 6.109 ms
3 2001:xxx:1:1::ff40:dc 5.805 ms 5.860 ms 5.962 ms
4 2001:xxx:1:40:1525:3b41:1:2 6.587 ms 6.645 ms 6.561 ms
5 2a00:1450:8125::1 5.877 ms * *
6 * 2001:4860:0:1::5378 5.954 ms 2001:4860:0:1::248e 5.874 ms
7 * 2001:4860:0:1100::f 7.301 ms 2001:4860:0:1100::10 6.801 ms
8 lhr35s11-in-x0e.1e100.net (2a00:1450:4009:815::200e) 6.390 ms 5.881 ms *

I get no route from the LAN.

Thanks.

The last one I need is a traceroute from outside your network to an address inside the /48 or /56 - one that should be routing via your UDM. This will tell us if Daisy have configured the routing correctly.

He hasn't got a /48.

That's why I said /48 or /56