Lasse Brandt <[email protected]> wrote in <[email protected]>:
la> 1) Is the hosting provider actually forcing me to do something "bad" la> og plain wrong? In that situation normally you get an IP address in the /59 network to communicate with the gateway router from ISP. An IP address in your /64 network cannot directly communicate with an address in /59. If you do not have the /59 address, I think using link-local address is the easiest way. As long as the gateway works correctly, you can get its link-local address by using the following command: % ping6 ff02::2%re0 PING6(56=40+8+8 bytes) fe80::XXXX:XXXX:XXXX:XXXX%re0 --> ff02::2%re0 16 bytes from fe80::YYYY:YYYY:YYYY:YYYY%re0, icmp_seq=0 hlim=64 time=0.525 ms 16 bytes from fe80::YYYY:YYYY:YYYY:YYYY%re0, icmp_seq=1 hlim=64 time=0.312 ms ^C Note that "XXXX:.." is your address on re0, and "YYYY:.." is the gateway's. You do not need any configuration like assigning 2a01:... address into re0 or static routes before performing this ping. At least one router replies to this and displays its link-local address. After that, you can add the default route to it: # route add -inet6 default fe80::YYYY:YYYY:YYYY:YYYY%re0 and configure your /64 address (2a01:...) to re0. -- Hiroki
pgpdo1CO9Ghlo.pgp
Description: PGP signature
