|
whois service
![[ru]](/s/countries/ru.gif) Shadow Hawkins on Wednesday, 29 May 2013 09:18:13
Whois service does not work for me when the server has IPv6 address (I use jwhois).
Is it blocked? Other services work well through SixXS.
whois service
You will need to provide quite a bit more details than that. Output of commands, possible traceroutes etc would be very useful.
One suggestion though, the best whois client is the one made by Marco d'Itri, aka the standard 'whois' in for instance Debian.
whois service
Shadow Hawkins on Thursday, 30 May 2013 05:34:56
This time I used 'whois' client.
1. 'whois google.com' request (it fails)
$ whois google.com
Whois Server Version 2.0
Domain names in the .com and .net domains can now be registered
with many different competing registrars. Go to http://www.internic.net
for detailed information.
Timeout.
# tcpdump -i br0 port 43
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on br0, link-type EN10MB (Ethernet), capture size 65535 bytes
09:20:23.309243 IP6 2a02:578:5002:8062::2.45394 > 2001:502:8c25:1060::74.nicname: Flags [S], seq 2279589557, win 14400, options [mss 1440,sackOK,TS val 21030281 ecr 0,nop,wscale 7], length 0
09:20:23.371703 IP6 2001:502:8c25:1060::74.nicname > 2a02:578:5002:8062::2.45394: Flags [S.], seq 124300190, ack 2279589558, win 5312, options [mss 1340,sackOK,TS val 3191166073 ecr 21030281,nop,wscale 7], length 0
09:20:23.371735 IP6 2a02:578:5002:8062::2.45394 > 2001:502:8c25:1060::74.nicname: Flags [.], ack 1, win 113, options [nop,nop,TS val 21030297 ecr 3191166073], length 0
09:20:23.371767 IP6 2a02:578:5002:8062::2.45394 > 2001:502:8c25:1060::74.nicname: Flags [P.], seq 1:14, ack 1, win 113, options [nop,nop,TS val 21030297 ecr 3191166073], length 13
09:20:23.432737 IP6 2001:502:8c25:1060::74.nicname > 2a02:578:5002:8062::2.45394: Flags [.], ack 14, win 42, options [nop,nop,TS val 3191166136 ecr 21030297], length 0
09:20:23.432760 IP6 2001:502:8c25:1060::74.nicname > 2a02:578:5002:8062::2.45394: Flags [P.], seq 1:190, ack 14, win 42, options [nop,nop,TS val 3191166136 ecr 21030297], length 189
09:20:23.432828 IP6 2a02:578:5002:8062::2.45394 > 2001:502:8c25:1060::74.nicname: Flags [.], ack 190, win 121, options [nop,nop,TS val 21030312 ecr 3191166136], length 0
2. animatsuri.org request (it succeeds)
09:33:18.077826 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [S], seq 1162672375, win 14600, options [mss 1460,sackOK,TS val 21223973 ecr 0,nop,wscale 7], length 0
09:33:18.251600 IP 199.15.84.131.nicname > 192.168.1.2.37078: Flags [S.], seq 3880239850, ack 1162672376, win 1460, options [mss 1300,nop,wscale 0,nop,nop,TS val 4092505448 ecr 21223973,sackOK,eol], length 0
09:33:18.251635 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [.], ack 1, win 115, options [nop,nop,TS val 21224017 ecr 4092505448], length 0
09:33:18.251682 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [P.], seq 1:17, ack 1, win 115, options [nop,nop,TS val 21224017 ecr 4092505448], length 16
09:33:18.426529 IP 199.15.84.131.nicname > 192.168.1.2.37078: Flags [.], seq 1:1289, ack 17, win 3916, options [nop,nop,TS val 4092505622 ecr 21224017], length 1288
09:33:18.426547 IP 199.15.84.131.nicname > 192.168.1.2.37078: Flags [P.], seq 1289:1449, ack 17, win 3916, options [nop,nop,TS val 4092505622 ecr 21224017], length 160
09:33:18.426551 IP 199.15.84.131.nicname > 192.168.1.2.37078: Flags [.], seq 1449:2737, ack 17, win 3916, options [nop,nop,TS val 4092505622 ecr 21224017], length 1288
09:33:18.426621 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [.], ack 1289, win 137, options [nop,nop,TS val 21224060 ecr 4092505622], length 0
09:33:18.426628 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [.], ack 1449, win 157, options [nop,nop,TS val 21224060 ecr 4092505622], length 0
09:33:18.426631 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [.], ack 2737, win 180, options [nop,nop,TS val 21224060 ecr 4092505622], length 0
09:33:18.426649 IP 199.15.84.131.nicname > 192.168.1.2.37078: Flags [FP.], seq 2737:3045, ack 17, win 3916, options [nop,nop,TS val 4092505622 ecr 21224017], length 308
09:33:18.426755 IP 192.168.1.2.37078 > 199.15.84.131.nicname: Flags [F.], seq 17, ack 3046, win 200, options [nop,nop,TS val 21224060 ecr 4092505622], length 0
09:33:18.599825 IP 199.15.84.131.nicname > 192.168.1.2.37078: Flags [.], ack 18, win 3916, options [nop,nop,TS val 4092505796 ecr 21224060], length 0
3. If I try to make google.com request in my VPN connection (it only has IPv4, also a success)
09:23:21.363938 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [S], seq 878126169, win 14600, options [mss 1460,sackOK,TS val 21074795 ecr 0,nop,wscale 7], length 0
09:23:21.580765 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [S.], seq 1706403489, ack 878126170, win 5792, options [mss 1368,sackOK,TS val 989745144 ecr 21074795,nop,wscale 7], length 0
09:23:21.580792 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 1, win 115, options [nop,nop,TS val 21074849 ecr 989745144], length 0
09:23:21.580848 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [P.], seq 1:14, ack 1, win 115, options [nop,nop,TS val 21074849 ecr 989745144], length 13
09:23:21.797051 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], ack 14, win 46, options [nop,nop,TS val 989745361 ecr 21074849], length 0
09:23:21.798017 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [P.], seq 1:190, ack 14, win 46, options [nop,nop,TS val 989745361 ecr 21074849], length 189
09:23:21.798077 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 190, win 123, options [nop,nop,TS val 21074903 ecr 989745361], length 0
09:23:21.799305 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], seq 190:1546, ack 14, win 46, options [nop,nop,TS val 989745363 ecr 21074849], length 1356
09:23:21.799352 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 1546, win 146, options [nop,nop,TS val 21074903 ecr 989745363], length 0
09:23:22.014565 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], seq 1546:2902, ack 14, win 46, options [nop,nop,TS val 989745578 ecr 21074903], length 1356
09:23:22.014588 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], seq 2902:4258, ack 14, win 46, options [nop,nop,TS val 989745578 ecr 21074903], length 1356
09:23:22.014614 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 2902, win 168, options [nop,nop,TS val 21074957 ecr 989745578], length 0
09:23:22.014627 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 4258, win 191, options [nop,nop,TS val 21074957 ecr 989745578], length 0
09:23:22.014935 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], seq 4258:5614, ack 14, win 46, options [nop,nop,TS val 989745579 ecr 21074903], length 1356
09:23:22.014960 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 5614, win 213, options [nop,nop,TS val 21074957 ecr 989745579], length 0
09:23:22.015528 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], seq 5614:6970, ack 14, win 46, options [nop,nop,TS val 989745579 ecr 21074903], length 1356
09:23:22.015542 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 6970, win 236, options [nop,nop,TS val 21074958 ecr 989745579], length 0
09:23:22.230414 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [P.], seq 6970:8326, ack 14, win 46, options [nop,nop,TS val 989745794 ecr 21074957], length 1356
09:23:22.230468 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 8326, win 259, options [nop,nop,TS val 21075011 ecr 989745794], length 0
09:23:22.231174 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], seq 8326:9682, ack 14, win 46, options [nop,nop,TS val 989745794 ecr 21074957], length 1356
09:23:22.231208 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [.], ack 9682, win 281, options [nop,nop,TS val 21075011 ecr 989745794], length 0
09:23:22.231355 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [FP.], seq 9682:10313, ack 14, win 46, options [nop,nop,TS val 989745794 ecr 21074957], length 631
09:23:22.231466 IP 10.0.15.209.37718 > 199.7.54.74.nicname: Flags [F.], seq 14, ack 10314, win 302, options [nop,nop,TS val 21075011 ecr 989745794], length 0
09:23:22.278345 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [S], seq 3878482810, win 14600, options [mss 1460,sackOK,TS val 21075023 ecr 0,nop,wscale 7], length 0
09:23:22.447174 IP 199.7.54.74.nicname > 10.0.15.209.37718: Flags [.], ack 15, win 46, options [nop,nop,TS val 989746011 ecr 21075011], length 0
09:23:22.492359 IP 64.124.14.21.nicname > 10.0.15.209.56853: Flags [S.], seq 4129808631, ack 3878482811, win 5840, options [mss 1368], length 0
09:23:22.492384 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [.], ack 1, win 14600, length 0
09:23:22.492427 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [P.], seq 1:13, ack 1, win 14600, length 12
09:23:22.711029 IP 64.124.14.21.nicname > 10.0.15.209.56853: Flags [.], ack 13, win 5840, length 0
09:23:22.713892 IP 64.124.14.21.nicname > 10.0.15.209.56853: Flags [.], seq 1:1369, ack 13, win 5840, length 1368
09:23:22.713904 IP 64.124.14.21.nicname > 10.0.15.209.56853: Flags [F.], seq 2585, ack 13, win 5840, length 0
09:23:22.713947 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [.], ack 1369, win 16416, length 0
09:23:22.713954 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [.], ack 1369, win 16416, length 0
09:23:22.714846 IP 64.124.14.21.nicname > 10.0.15.209.56853: Flags [P.], seq 1369:2585, ack 13, win 5840, length 1216
09:23:22.714894 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [.], ack 2586, win 19152, length 0
09:23:22.714973 IP 10.0.15.209.56853 > 64.124.14.21.nicname: Flags [F.], seq 13, ack 2586, win 19152, length 0
09:23:22.930037 IP 64.124.14.21.nicname > 10.0.15.209.56853: Flags [.], ack 14, win 5840, length 0
4. ping and traceroute
64 bytes from 2001:502:8c25:1060::74: icmp_seq=8 ttl=52 time=61.0 ms
64 bytes from 2001:502:8c25:1060::74: icmp_seq=9 ttl=52 time=60.6 ms
^C
--- 2001:502:8c25:1060::74 ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8034ms
rtt min/avg/max/mdev = 60.610/60.955/61.533/0.428 ms
traceroute to 2001:502:8c25:1060::74 (2001:502:8c25:1060::74), 30 hops max, 80 byte packets
1 runesave.xtsubasa.org (2a02:578:5002:8062::1) 0.367 ms 0.596 ms 0.734 ms
2 broker (2a02:578:5002:62::1) 2.401 ms 2.617 ms 2.620 ms
3 ruled01.sixxs.net (2a02:578:5001:2::2) 2.618 ms 2.617 ms 2.615 ms
4 2a02:578:5001:2::1 (2a02:578:5001:2::1) 2.985 ms 2.987 ms 2.987 ms
5 2a02:578:1:24::1 (2a02:578:1:24::1) 3.422 ms 3.560 ms 3.678 ms
6 2a02:578:1:33::2 (2a02:578:1:33::2) 15.416 ms 15.128 ms 15.053 ms
7 2a02:578:1:20::1 (2a02:578:1:20::1) 42.797 ms 2a02:578:1:1b::1 (2a02:578:1:1b::1) 44.074 ms 2a02:578:1:20::1 (2a02:578:1:20::1) 42.052 ms
8 30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1) 42.777 ms 44.562 ms 42.042 ms
9 r1-gi2-0-13.ipv6-fo.fra1.verisign.com (2001:7f8::1cae:0:1) 45.273 ms 43.684 ms 43.651 ms
10 xe-1-3-0.r1.bb-fo.lon3.vrsn.net (2620:0:5050:fa01::105) 60.036 ms 59.318 ms 60.278 ms
11 xe-1-1-0.r1.edge-fo.lon3.vrsn.net (2620:0:5050:fa02::66) 58.646 ms 58.653 ms 59.740 ms
12 2001:502:8c25:13ff::2 (2001:502:8c25:13ff::2) 59.724 ms 58.870 ms 58.266 ms
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
whois service
Looks a lot like MTU issues.
You might want to try a tracepath6 to figure out if the MTU makes sense along the path.
whois service
Shadow Hawkins on Thursday, 30 May 2013 06:32:46
My local MTU is 1500.
MTU on my router (it has SixXS static tunnel configured) is 1280.
tracepath6 output:
1?: [LOCALHOST] 0.023ms pmtu 1500
1: runesave.xtsubasa.org 0.688ms
1: runesave.xtsubasa.org 0.601ms
2: runesave.xtsubasa.org 0.576ms pmtu 1280
2: broker 2.084ms
3: ruled01.sixxs.net 2.120ms asymm 2
4: 2a02:578:5001:2::1 2.493ms asymm 3
5: 2a02:578:1:24::1 3.107ms asymm 4
6: 2a02:578:1:33::2 14.303ms asymm 5
7: 2a02:578:1:23::2 43.711ms asymm 6
8: 30gigabitethernet4-3.core1.fra1.he.net 44.303ms asymm 7
9: r1-gi2-0-13.ipv6-fo.fra1.verisign.com 42.529ms
10: xe-1-3-0.r1.bb-fo.lon3.vrsn.net 62.001ms asymm 9
11: xe-1-1-0.r1.edge-fo.lon3.vrsn.net 59.976ms
12: xe-1-1-0.r2.edge-fo.lon3.vrsn.net 58.919ms asymm 11
13: ??? 58.347ms asymm 11
14: no reply
<I skipped here>
31: no reply
Too many hops: pmtu 1280
Resume: pmtu 1280
Is this normal?
whois service
Shadow Hawkins on Thursday, 30 May 2013 06:35:43
I forgot to mention that MTU in SixXS control panel is also 1280.
whois service
Pavel Volkov wrote:
I forgot to mention that MTU in SixXS control panel is also 1280.
You could try, if possible, configuring a higher MTU on both sides, but it looks a lot like the remote network is not sending back ICMP Packet Too Bigs and/or dropping them when receiving them.
I'll see if I can reach somebody from Verisign to fix their network, if they make this silly mistake here they likely did it in other places.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 29 May 2013 14:12:25
Posting is only allowed when you are