Dedikuotam KVM serveriui duotas IPv6 adresas 2a02:7b40:xxxx:xxxx::1 su subnet prefix'u 64.
`ip -6 route`:
2a02:7b40:xxxx:xxxx::/64 via fe80::ffff:1:1 dev eth0 metric 100 pref medium
2a02:7b40:xxxx:xxxx::/64 dev eth0 proto kernel metric 256 pref medium
`ip -6 addr`:
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2a02:7b40:xxxx:xxxx::1/64 scope global
valid_lft forever preferred_lft forever
Tačiau pridėjus naują ip adresą per `ip addr add 2a02:7b40:xxxx:xxxx::2/64 dev eth0`, naujasis IP 2a02:7b40:xxxx:xxxx::2 nėra pasiekiamas iš išorės.
Atrodo, lyg būtų suteiktas 2a02:7b40:xxxx:xxxx::1/128, o ne 2a02:7b40:xxxx:xxxx::1/64.
Ar klaida iv.lt IPv6 route'inimo konfigūracijoje, ar aš pats kažką ne taip darau?
Ačiū.
Komentarai
To pilnai užtektų, jei į serverį būtų route'inamas pilnas 2a02:7b40:xxxx:xxxx::/64 subnet'as, t.y. visi adresai nuo 2a02:7b40:xxxx:xxxx:0000:0000:0000:0000 iki 2a02:7b40:xxxx:xxxx:ffff:ffff:ffff:ffff. Dabar atrodo, kad iš šio /64 subnet'o į serverį route'inamas tik vienintelis 2a02:7b40:xxxx:xxxx:0000:0000:0000:0001 ir iššvaistomi likę galimi 18'446'744'073'709'551'615 adresai
Gal aš kažką ne taip darau pridėdamas papildomą IPv6 serveriui?
Diagnostika
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
inet6 2a02:7b40:xxxx:xxxx::2/64 scope global
valid_lft forever preferred_lft forever
inet6 2a02:7b40:xxxx:xxxx::1/64 scope global
valid_lft forever preferred_lft forever
inet6 fe80::200:3eff:xxxx:xxxx/64 scope link
valid_lft forever preferred_lft forever
2a02:7b40:xxxx:xxxx::/64 dev eth0 proto kernel metric 256 pref medium
2a02:7b40:xxxx:xxxx::/64 via fe80::ffff:1:1 dev eth0 metric 1024 pref medium
PING 2a02:7b40:xxxx:xxxx::1(2a02:7b40:xxxx:xxxx::1) 56 data bytes
64 bytes from 2a02:7b40:xxxx:xxxx::1: icmp_seq=1 ttl=56 time=65.0 ms
PING 2a02:7b40:xxxx:xxxx::2(2a02:7b40:xxxx:xxxx::2) 56 data bytes
From 2001:4048:ffff:2001::2 icmp_seq=1 Destination unreachable: Address unreachable
traceroute to 2a02:7b40:xxxx:xxxx::1 (2a02:7b40:xxxx:xxxx::1), 30 hops max, 80 byte packets
1 2002:4e3a:2374::1 (2002:4e3a:2374::1) 0.358 ms 0.482 ms 0.656 ms
2 2002:c058:6301::1 (2002:c058:6301::1) 34.960 ms 35.123 ms 35.420 ms
3 * * *
4 e0-33.core2.ber1.he.net (2001:470:0:3f8::2) 53.970 ms 56.882 ms 64.158 ms
5 100ge10-2.core1.waw1.he.net (2001:470:0:40::1) 60.784 ms 60.897 ms 61.001 ms
6 100ge5-2.core1.vno1.he.net (2001:470:0:46d::2) 63.686 ms 65.561 ms 61.767 ms
7 2001:470:1:62d::2 (2001:470:1:62d::2) 61.966 ms 62.232 ms 62.494 ms
8 2001:4048:ffff:ffff:ffff:fffd:0:3 (2001:4048:ffff:ffff:ffff:fffd:0:3) 77.615 ms 77.693 ms 81.709 ms
9 2001:4048:ffff:2001::2 (2001:4048:ffff:2001::2) 82.143 ms 78.106 ms 78.311 ms
10 k22-b3-lt1.kvm.serveriai.lt (2a02:7b40:1f0e:b246::1) 69.578 ms 65.835 ms 69.941 ms
11 2a02:7b40:xxxx:xxxx::1 66.615 ms * 66.674 ms
`traceroute 2a02:7b40:xxxx:xxxx::2`
traceroute to 2a02:7b40:xxxx:xxxx::2 (2a02:7b40:xxxx:xxxx::2), 30 hops max, 80 byte packets
1 2002:4e3a:2374::1 (2002:4e3a:2374::1) 0.349 ms 0.481 ms 0.705 ms
2 2002:c058:6301::1 (2002:c058:6301::1) 35.184 ms 35.320 ms 39.379 ms
3 * * *
4 e0-33.core2.ber1.he.net (2001:470:0:3f8::2) 53.817 ms 57.785 ms 64.842 ms
5 100ge10-2.core1.waw1.he.net (2001:470:0:40::1) 61.746 ms 57.544 ms 61.766 ms
6 100ge5-2.core1.vno1.he.net (2001:470:0:46d::2) 63.695 ms 65.711 ms 62.376 ms
7 2001:470:1:62d::2 (2001:470:1:62d::2) 62.762 ms 62.789 ms 67.206 ms
8 2001:4048:ffff:ffff:ffff:fffd:0:3 (2001:4048:ffff:ffff:ffff:fffd:0:3) 82.159 ms 82.303 ms 78.355 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * 2001:4048:ffff:2001::2 (2001:4048:ffff:2001::2) 2081.253 ms !H *