REPLY: 2:280/5555 616a9a21
MSGID: 2:5005/49 616ab362
CHRS: CP866 2
TZUTC: 0700
TID: hpt/fbsd 1.9.0-cur 2019-12-05
Dear Michiel,

16 Oct 21 11:23, you wrote to me:

 VS>> Those of you lucky to have a *native* IPv6 connection from your
 VS>> ISP, could you please share what network topology your ISP
 VS>> offers. E.g.

 VS>> 3. A /64 for the link and a /56 for your devices

 MV> I think #3 comes closest.

Thanks for replying.

 MV> I am not sure about the /64 for the link. The only visible part of the
 MV> link is the IPv6 WAN address of the router. It is outside the /56
 MV> assigned to the user, the link may just use a /128.

Do you see the WAN address of the router in the `traceroute -6` output?

 MV> The modem/router supplied by the ISP assigns one /64 for the LAN and
 MV> another /64 for the guest network. More /64 out  of the /56 can be
 MV> obtained by connecting extra routers.

Very little flexibility IMHO. Can you at least assign a static IPv6 address
within the LAN /64?

 MV> For IPv6 one must use the modem/router from the provider. When the
 MV> modem/router from the provider is set in bridge mode, the connection
 MV> becomes IPv4 only.

This looks very similar to what I've heard from a Rostelecom representative.
This probably means that the IPv6 is not really "native" and there is some
kind of tunnel terminated at the provider-owned CPE.

Victor Sudakov, VAS4-RIPE, VAS47-RIPN
--- GoldED+/BSD 1.1.5-b20170303-b20170303
 * Origin: Ulthar (2:5005/49)
SEEN-BY: 1/123 30/0 50/109 80/1 90/1 105/81 120/340 123/131 154/10
SEEN-BY: 221/1 6 226/30 227/702 229/424 426 428 550 664 700 240/1120
SEEN-BY: 240/5832 249/206 317 400 261/38 280/464 5555 282/464 1038
SEEN-BY: 301/0 1 101 113 812 317/3 322/757 342/200 460/58 463/68 467/239
SEEN-BY: 467/888 633/280 712/848 920/1 5000/111 5001/100 5005/49 53
SEEN-BY: 5015/46 5020/715 830 846 1042 2047 2140 4441 5058/104 5064/56
SEEN-BY: 5080/102 5083/1 444
PATH: 5005/49 5020/1042 301/1 229/426