11:52 a.m.
Dear Sir,
My name is Keng Soon Goh, and I am working for Hughes Network Systems. We are Service
Provider for satellite company, and one of our client was having problem accessing to your
websites through IPv6 address. When I run DNS lookup, I noticed three IPv6 addresses as
below.
nslookup -q=aaaa www.fedoraproject.org
Server: 172.27.0.9
Address: 172.27.0.9#53
Non-authoritative answer:
www.fedoraproject.org canonical name = wildcard.fedoraproject.org.
wildcard.fedoraproject.org has AAAA address 2001:4178:2:1269::fed2
wildcard.fedoraproject.org has AAAA address 2607:f188::dead:beef:cafe:fed1
wildcard.fedoraproject.org has AAAA address 2610:28:3090:3001:dead:beef:cafe:fed4
Authoritative answers can be found from:
fedoraproject.org nameserver = ns02.fedoraproject.org.
fedoraproject.org nameserver = ns04.fedoraproject.org.
fedoraproject.org nameserver = ns05.fedoraproject.org.
fedoraproject.org nameserver = ns-sb01.fedoraproject.org.
We noticed that one of your IPv6 address 2001:4178:2:1269::fed2 cannot browse either http
or https, but the other two are working fine. Can you take a look on this ipv6 address? In
addition, the traceroute seems to stop at Level3 cloud, and I think it is the problem with
this address.
Router#traceroute
Protocol [ip]: ipv6
Target IPv6 address: 2607:f188::dead:beef:cafe:fed1
Source address: 2001:5B0:210B:1:1:1:1:1
Insert source routing header? [no]:
Numeric display? [no]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Priority [0]:
Port Number [0]:
Type escape sequence to abort.
Tracing the route to 2607:F188::DEAD:BEEF:CAFE:FED1
1 2001:5B0:21FF:FFFA::100 1 msec 1 msec 1 msec
2 2001:1900:2100::D9D 1 msec 1 msec 1 msec
3 2001:1900:4:1::279 13 msec 14 msec 14 msec
4 2001:1900:4:1::61 21 msec 27 msec 21 msec
5 2001:1900:1A:7::7 22 msec 23 msec
2001:1900:1A:5::7 23 msec
6 2001:470:0:203::1 25 msec 23 msec 25 msec
7 2001:470:0:16A::2 39 msec 35 msec 39 msec
8 2001:504:13::40A 31 msec 31 msec 30 msec
9 2607:F130::3 36 msec 30 msec 30 msec
10 2607:F130:0:B::2 30 msec 30 msec 30 msec
11 2607:F188::DEAD:BEEF:CAFE:FED1 !A !A !A
Router#traceroute
Protocol [ip]: ipv6
Target IPv6 address: 2001:4178:2:1269::fed2
Source address: 2001:5B0:210B:1:1:1:1:1
Insert source routing header? [no]:
Numeric display? [no]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Priority [0]:
Port Number [0]:
Type escape sequence to abort.
Tracing the route to 2001:4178:2:1269::FED2
1 2001:5B0:21FF:FFFA::100 1 msec 1 msec 1 msec
2 2001:1900:2100::D9D 1 msec 0 msec 0 msec
3 2001:1900:4:1::13E 1 msec 1 msec 1 msec
4 2001:1900:4:1::142 12 msec 12 msec 12 msec
5 2001:1900:4:1::32 13 msec
2001:1900:4:1::2E 12 msec 12 msec
6 2001:1900:4:1::36 36 msec 36 msec 35 msec
7 2001:1900:4:1::1D 37 msec 107 msec 37 msec
8 2001:1900:4:1::22 57 msec 60 msec 57 msec
9 2001:1900:4:1::F1 70 msec 57 msec 58 msec
10 2001:1900:4:1::105 63 msec 64 msec 63 msec
11 2001:1900:4:1::D5 82 msec
2001:1900:4:1::DD 62 msec
2001:1900:4:1::D5 63 msec
12 2001:1900:6:1::15 141 msec 140 msec 142 msec
13 2001:1900:5:1::12A 143 msec
2001:1900:5:1::12E 141 msec 140 msec
14 2001:1900:5:1::215 152 msec 150 msec 150 msec
15 2001:1900:5:1::25E 156 msec 157 msec 156 msec
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Destination not found inside max hopcount diameter.
Router#traceroute
Protocol [ip]: ipv6
Target IPv6 address: 2610:28:3090:3001:dead:beef:cafe:fed4
Source address: 2001:5B0:210B:1:1:1:1:1
Insert source routing header? [no]:
Numeric display? [no]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Priority [0]:
Port Number [0]:
Type escape sequence to abort.
Tracing the route to 2610:28:3090:3001:DEAD:BEEF:CAFE:FED4
1 2001:5B0:21FF:FFFA::100 1 msec 2 msec 1 msec
2 2001:1900:2100::D9D 2 msec 1 msec 1 msec
3 2001:1900:4:1::279 14 msec 14 msec 14 msec
4 2001:1900:12:2::D 14 msec 14 msec
2001:1900:12:1::D 14 msec
5 2001:1900:4:3::276 14 msec 14 msec 14 msec
6 2001:504:D::BD 76 msec 30 msec 31 msec
7 * * *
8 * * *
9 * * *
10 2001:468:1:60::1 188 msec 83 msec 83 msec
11 2610:28:3090:23::2 89 msec 87 msec 89 msec
12 2610:28:3090:3001:DEAD:BEEF:CAFE:FED4 !A !A !A
Thanks.
Keng Soon
10:16 a.m.
On Mon, 25 Feb 2013 12:52:32 -0500
Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
Dear Sir,
My name is Keng Soon Goh, and I am working for Hughes Network
Systems. We are Service Provider for satellite company, and one of
our client was having problem accessing to your websites through IPv6
address. When I run DNS lookup, I noticed three IPv6 addresses as
below.
...snip...
We noticed that one of your IPv6 address 2001:4178:2:1269::fed2
cannot browse either http or https, but the other two are working
fine. Can you take a look on this ipv6 address? In addition, the
traceroute seems to stop at Level3 cloud, and I think it is the
problem with this address.
...snip...
This address is working fine for me from here.
Perhaps it was a transitory error?
Can you confirm it's working now?
kevin
10:44 a.m.
Kevin,
Thanks for quick response. I still having problem. I went to different
location with different upstream providers of our network, and I was not
able to browse through this IPv6 address. I am not sure what you say
"working fine for me from here". Are you testing internally or somewhere
outside of your network? Remember that you have three different Web
Hosting location, and it might using the other two. Is there any of your
firewall blocking Hughes IPv6 subnet? Hughes IPv6 subnet is 2001:5B0::/32
le /49.
Thanks.
Keng Soon
On 2/26/13 11:16 AM, "Kevin Fenzi" <kevin(a)scrye.com> wrote:
On Mon, 25 Feb 2013 12:52:32 -0500
Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
> Dear Sir,
>
> My name is Keng Soon Goh, and I am working for Hughes Network
> Systems. We are Service Provider for satellite company, and one of
> our client was having problem accessing to your websites through IPv6
> address. When I run DNS lookup, I noticed three IPv6 addresses as
> below.
...snip...
> We noticed that one of your IPv6 address 2001:4178:2:1269::fed2
> cannot browse either http or https, but the other two are working
> fine. Can you take a look on this ipv6 address? In addition, the
> traceroute seems to stop at Level3 cloud, and I think it is the
> problem with this address.
...snip...
This address is working fine for me from here.
Perhaps it was a transitory error?
Can you confirm it's working now?
kevin
11:20 a.m.
On Tue, 26 Feb 2013 11:44:55 -0500
Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
Kevin,
Thanks for quick response. I still having problem. I went to different
location with different upstream providers of our network, and I was
not able to browse through this IPv6 address. I am not sure what you
say "working fine for me from here". Are you testing internally or
somewhere outside of your network? Remember that you have three
different Web Hosting location, and it might using the other two. Is
there any of your firewall blocking Hughes IPv6 subnet? Hughes IPv6
subnet is 2001:5B0::/32 le /49.
I am testing from my home connection that specific ipv6 ip. ;)
There's no ipv6 blocks that I know of in place. ;(
kevin
--
% ping6 -c 5 2001:4178:2:1269::fed2
PING 2001:4178:2:1269::fed2(2001:4178:2:1269::fed2) 56 data bytes
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=1 ttl=51 time=194 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=2 ttl=51 time=202 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=3 ttl=51 time=200 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=4 ttl=51 time=197 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=5 ttl=51 time=206 ms
--- 2001:4178:2:1269::fed2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 194.611/200.279/206.694/4.213 ms
% wget --no-check-cert https://[2001:4178:2:1269::fed2]/ -O /dev/null
--2013-02-26 10:19:47-- https://[2001:4178:2:1269::fed2]/
Connecting to [2001:4178:2:1269::fed2]:443... connected.
WARNING: certificate common name ‘*.fedoraproject.org’ doesn't
match requested host name ‘2001:4178:2:1269::fed2’. HTTP request sent,
awaiting response... 302 Found Location:
https://apps.fedoraproject.org/ [following] --2013-02-26 10:19:48--
https://apps.fedoraproject.org/ Resolving apps.fedoraproject.org
(apps.fedoraproject.org)... 2001:4178:2:1269::fed2,
2607:f188::dead:beef:cafe:fed1,
2610:28:3090:3001:dead:beef:cafe:fed4, ... Connecting to
apps.fedoraproject.org
(apps.fedoraproject.org)|2001:4178:2:1269::fed2|:443... connected. HTTP
request sent, awaiting response... 200 OK Length: 1755 (1.7K)
[text/html] Saving to: ‘/dev/null’
100%[==========================================================>]
1,755 --.-K/s in 0s
2013-02-26 10:19:49 (18.3 MB/s) - ‘/dev/null’ saved [1755/1755]
3:53 p.m.
Kevin,
I worked with Level3 and they told me their client or your upstream
provider is the one blocking 2001:5B0::/32 le /49. Below is the traceroute
from them. When I traceroute I stopped at 2001:1900:5:1::25E. I believe
your upstream provider is RIPE Network. Can you work with them on this?
Thanks.
Keng
Level3
1 vl-11.car2.SaltLakeCity1.Level3.net (2001:1900:4:1::13E) 0 msec 0 msec 0
msec
2 vl-4043.edge3.Denver1.Level3.net (2001:1900:4:1::142) 12 msec 72 msec
12 msec
3 vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 12 msec 12 msec
vl-4080.edge6.Denver1.Level3.net (2001:1900:4:1::2E) 16 msec
4 vl-4042.edge1.Chicago2.Level3.net (2001:1900:4:1::36) 36 msec 36 msec
76 msec
5 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1D) 36 msec 108 msec
36 msec
6 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 56 msec 56 msec
56 msec
7 vl-4080.car1.NewYork2.Level3.net (2001:1900:4:1::F1) 56 msec 60 msec
56 msec
8 vl-4061.edge2.Washington1.Level3.net (2001:1900:4:1::105) 64 msec 60
msec 80 msec
9 vl-4080.edge1.Washington1.Level3.net (2001:1900:4:1::D1) 60 msec
vl-4081.edge1.Washington1.Level3.net (2001:1900:4:1::D5) 64 msec
vl-4083.edge1.Washington1.Level3.net (2001:1900:4:1::DD) 96 msec
10 vl-4086.edge3.Paris1.Level3.net (2001:1900:6:1::15) 144 msec 144 msec
140 msec
11 vl-4080.edge4.Paris1.Level3.net (2001:1900:5:1::12A) 144 msec 140 msec
140 msec
12 vl-4060.edge3.Frankfurt1.Level3.net (2001:1900:5:1::215) 148 msec 152
msec 152 msec
13 vl-4043.car1.Munich1.Level3.net (2001:1900:5:1::25E) 296 msec 212 msec
216 msec
14 2001:1900:5:2:2::303 156 msec 160 msec 164 msec
15 te9-2-c1.net.muc2.internetx.de (2001:4178:1::12) 332 msec 164 msec 160
msec
16 2001:4178:2:1269::FED2 !A !A !A
Hughes
Tracing the route to 2001:4178:2:1269::FED2
1 2001:5B0:21FF:FFFA::100 2 msec 2 msec 2 msec
2 2001:1900:2100::D9D 3 msec 1 msec 1 msec
3 2001:1900:4:1::13E 1 msec 0 msec 1 msec
4 2001:1900:4:1::142 12 msec 12 msec 12 msec
5 2001:1900:4:1::32 12 msec 12 msec
2001:1900:4:1::2E 12 msec
6 2001:1900:4:1::36 115 msec 37 msec 37 msec
7 2001:1900:4:1::1D 37 msec 36 msec 37 msec
8 2001:1900:4:1::22 57 msec 57 msec 56 msec
9 2001:1900:4:1::F1 58 msec 57 msec 57 msec
10 2001:1900:4:1::105 63 msec 62 msec 84 msec
11 2001:1900:4:1::D1 62 msec *
2001:1900:4:1::D5 83 msec
12 2001:1900:6:1::15 142 msec 141 msec 141 msec
13 2001:1900:5:1::12A 143 msec
2001:1900:5:1::12E 140 msec 140 msec
14 2001:1900:5:1::215 150 msec 151 msec 152 msec
15 2001:1900:5:1::25E 358 msec 342 msec 341 msec
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
On 2/26/13 12:20 PM, "Kevin Fenzi" <kevin(a)scrye.com> wrote:
On Tue, 26 Feb 2013 11:44:55 -0500
Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
> Kevin,
>
> Thanks for quick response. I still having problem. I went to different
> location with different upstream providers of our network, and I was
> not able to browse through this IPv6 address. I am not sure what you
> say "working fine for me from here". Are you testing internally or
> somewhere outside of your network? Remember that you have three
> different Web Hosting location, and it might using the other two. Is
> there any of your firewall blocking Hughes IPv6 subnet? Hughes IPv6
> subnet is 2001:5B0::/32 le /49.
I am testing from my home connection that specific ipv6 ip. ;)
There's no ipv6 blocks that I know of in place. ;(
kevin
--
% ping6 -c 5 2001:4178:2:1269::fed2
PING 2001:4178:2:1269::fed2(2001:4178:2:1269::fed2) 56 data bytes
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=1 ttl=51 time=194 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=2 ttl=51 time=202 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=3 ttl=51 time=200 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=4 ttl=51 time=197 ms
64 bytes from 2001:4178:2:1269::fed2: icmp_seq=5 ttl=51 time=206 ms
--- 2001:4178:2:1269::fed2 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 194.611/200.279/206.694/4.213 ms
% wget --no-check-cert https://[2001:4178:2:1269::fed2]/ -O /dev/null
--2013-02-26 10:19:47-- https://[2001:4178:2:1269::fed2]/
Connecting to [2001:4178:2:1269::fed2]:443... connected.
WARNING: certificate common name Œ*.fedoraproject.org¹ doesn't
match requested host name Œ2001:4178:2:1269::fed2¹. HTTP request sent,
awaiting response... 302 Found Location:
https://apps.fedoraproject.org/ [following] --2013-02-26 10:19:48--
https://apps.fedoraproject.org/ Resolving apps.fedoraproject.org
(apps.fedoraproject.org)... 2001:4178:2:1269::fed2,
2607:f188::dead:beef:cafe:fed1,
2610:28:3090:3001:dead:beef:cafe:fed4, ... Connecting to
apps.fedoraproject.org
(apps.fedoraproject.org)|2001:4178:2:1269::fed2|:443... connected. HTTP
request sent, awaiting response... 200 OK Length: 1755 (1.7K)
[text/html] Saving to: Œ/dev/null¹
100%[==========================================================>]
1,755 --.-K/s in 0s
2013-02-26 10:19:49 (18.3 MB/s) - Œ/dev/null¹ saved [1755/1755]
10:29 a.m.
On Tue, 26 Feb 2013 16:53:08 -0500
Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
Kevin,
I worked with Level3 and they told me their client or your upstream
provider is the one blocking 2001:5B0::/32 le /49. Below is the
traceroute from them. When I traceroute I stopped at
2001:1900:5:1::25E. I believe your upstream provider is RIPE Network.
Can you work with them on this?
yeah, I will ask our provider there to see if there is anything they
can do or problem they can see.
Thanks for your report again.
Thanks.
Keng
kevin
--
Level3
1 vl-11.car2.SaltLakeCity1.Level3.net (2001:1900:4:1::13E) 0 msec 0
msec 0 msec
2 vl-4043.edge3.Denver1.Level3.net (2001:1900:4:1::142) 12 msec 72
msec 12 msec
3 vl-4081.edge6.Denver1.Level3.net (2001:1900:4:1::32) 12 msec 12
msec vl-4080.edge6.Denver1.Level3.net (2001:1900:4:1::2E) 16 msec
4 vl-4042.edge1.Chicago2.Level3.net (2001:1900:4:1::36) 36 msec 36
msec 76 msec
5 vl-4067.car1.Chicago1.Level3.net (2001:1900:4:1::1D) 36 msec 108
msec 36 msec
6 vl-4061.car2.NewYork2.Level3.net (2001:1900:4:1::22) 56 msec 56
msec 56 msec
7 vl-4080.car1.NewYork2.Level3.net (2001:1900:4:1::F1) 56 msec 60
msec 56 msec
8 vl-4061.edge2.Washington1.Level3.net (2001:1900:4:1::105) 64 msec
60 msec 80 msec
9 vl-4080.edge1.Washington1.Level3.net (2001:1900:4:1::D1) 60 msec
vl-4081.edge1.Washington1.Level3.net (2001:1900:4:1::D5) 64 msec
vl-4083.edge1.Washington1.Level3.net (2001:1900:4:1::DD) 96 msec
10 vl-4086.edge3.Paris1.Level3.net (2001:1900:6:1::15) 144 msec 144
msec 140 msec
11 vl-4080.edge4.Paris1.Level3.net (2001:1900:5:1::12A) 144 msec 140
msec 140 msec
12 vl-4060.edge3.Frankfurt1.Level3.net (2001:1900:5:1::215) 148 msec
152 msec 152 msec
13 vl-4043.car1.Munich1.Level3.net (2001:1900:5:1::25E) 296 msec 212
msec 216 msec
14 2001:1900:5:2:2::303 156 msec 160 msec 164 msec
15 te9-2-c1.net.muc2.internetx.de (2001:4178:1::12) 332 msec 164 msec
160 msec
16 2001:4178:2:1269::FED2 !A !A !A
Hughes
Tracing the route to 2001:4178:2:1269::FED2
1 2001:5B0:21FF:FFFA::100 2 msec 2 msec 2 msec
2 2001:1900:2100::D9D 3 msec 1 msec 1 msec
3 2001:1900:4:1::13E 1 msec 0 msec 1 msec
4 2001:1900:4:1::142 12 msec 12 msec 12 msec
5 2001:1900:4:1::32 12 msec 12 msec
2001:1900:4:1::2E 12 msec
6 2001:1900:4:1::36 115 msec 37 msec 37 msec
7 2001:1900:4:1::1D 37 msec 36 msec 37 msec
8 2001:1900:4:1::22 57 msec 57 msec 56 msec
9 2001:1900:4:1::F1 58 msec 57 msec 57 msec
10 2001:1900:4:1::105 63 msec 62 msec 84 msec
11 2001:1900:4:1::D1 62 msec *
2001:1900:4:1::D5 83 msec
12 2001:1900:6:1::15 142 msec 141 msec 141 msec
13 2001:1900:5:1::12A 143 msec
2001:1900:5:1::12E 140 msec 140 msec
14 2001:1900:5:1::215 150 msec 151 msec 152 msec
15 2001:1900:5:1::25E 358 msec 342 msec 341 msec
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
On 2/26/13 12:20 PM, "Kevin Fenzi" <kevin(a)scrye.com> wrote:
>On Tue, 26 Feb 2013 11:44:55 -0500
>Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
>
>> Kevin,
>>
>> Thanks for quick response. I still having problem. I went to
>> different location with different upstream providers of our
>> network, and I was not able to browse through this IPv6 address. I
>> am not sure what you say "working fine for me from here". Are you
>> testing internally or somewhere outside of your network? Remember
>> that you have three different Web Hosting location, and it might
>> using the other two. Is there any of your firewall blocking Hughes
>> IPv6 subnet? Hughes IPv6 subnet is 2001:5B0::/32 le /49.
>
>I am testing from my home connection that specific ipv6 ip. ;)
>
>There's no ipv6 blocks that I know of in place. ;(
>
>kevin
>--
>% ping6 -c 5 2001:4178:2:1269::fed2
>PING 2001:4178:2:1269::fed2(2001:4178:2:1269::fed2) 56 data bytes
>64 bytes from 2001:4178:2:1269::fed2: icmp_seq=1 ttl=51 time=194 ms
>64 bytes from 2001:4178:2:1269::fed2: icmp_seq=2 ttl=51 time=202 ms
>64 bytes from 2001:4178:2:1269::fed2: icmp_seq=3 ttl=51 time=200 ms
>64 bytes from 2001:4178:2:1269::fed2: icmp_seq=4 ttl=51 time=197 ms
>64 bytes from 2001:4178:2:1269::fed2: icmp_seq=5 ttl=51 time=206 ms
>
>--- 2001:4178:2:1269::fed2 ping statistics ---
>5 packets transmitted, 5 received, 0% packet loss, time 4002ms
>rtt min/avg/max/mdev = 194.611/200.279/206.694/4.213 ms
>
>% wget --no-check-cert https://[2001:4178:2:1269::fed2]/ -O /dev/null
>--2013-02-26 10:19:47-- https://[2001:4178:2:1269::fed2]/
>Connecting to [2001:4178:2:1269::fed2]:443... connected.
> WARNING: certificate common name Œ*.fedoraproject.org¹ doesn't
>match requested host name Œ2001:4178:2:1269::fed2¹. HTTP request
>sent, awaiting response... 302 Found Location:
>https://apps.fedoraproject.org/ [following] --2013-02-26 10:19:48--
>https://apps.fedoraproject.org/ Resolving apps.fedoraproject.org
>(apps.fedoraproject.org)... 2001:4178:2:1269::fed2,
>2607:f188::dead:beef:cafe:fed1,
>2610:28:3090:3001:dead:beef:cafe:fed4, ... Connecting to
>apps.fedoraproject.org
>(apps.fedoraproject.org)|2001:4178:2:1269::fed2|:443... connected.
>HTTP request sent, awaiting response... 200 OK Length: 1755 (1.7K)
>[text/html] Saving to: Œ/dev/null¹
>
>100%[==========================================================>]
>1,755 --.-K/s in 0s
>
>2013-02-26 10:19:49 (18.3 MB/s) - Œ/dev/null¹ saved [1755/1755]
>
9:26 a.m.
On Wed, 27 Feb 2013 09:29:38 -0700
Kevin Fenzi <kevin(a)scrye.com> wrote:
On Tue, 26 Feb 2013 16:53:08 -0500
Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
> Kevin,
>
> I worked with Level3 and they told me their client or your upstream
> provider is the one blocking 2001:5B0::/32 le /49. Below is the
> traceroute from them. When I traceroute I stopped at
> 2001:1900:5:1::25E. I believe your upstream provider is RIPE
> Network. Can you work with them on this?
yeah, I will ask our provider there to see if there is anything they
can do or problem they can see.
Thanks for your report again.
Can you try again now?
Our network provider at that site says they have fixed the issue. ;)
kevin
9:47 a.m.
Kevin,
It works now. Do you know what was the root cause?
Thanks.
Keng
On 2/28/13 10:26 AM, "Kevin Fenzi" <kevin(a)scrye.com> wrote:
On Wed, 27 Feb 2013 09:29:38 -0700
Kevin Fenzi <kevin(a)scrye.com> wrote:
> On Tue, 26 Feb 2013 16:53:08 -0500
> Keng Soon Goh <KengSoon.Goh(a)hughes.com> wrote:
>
> > Kevin,
> >
> > I worked with Level3 and they told me their client or your upstream
> > provider is the one blocking 2001:5B0::/32 le /49. Below is the
> > traceroute from them. When I traceroute I stopped at
> > 2001:1900:5:1::25E. I believe your upstream provider is RIPE
> > Network. Can you work with them on this?
>
> yeah, I will ask our provider there to see if there is anything they
> can do or problem they can see.
>
> Thanks for your report again.
Can you try again now?
Our network provider at that site says they have fixed the issue. ;)
kevin
4075
days inactive
4078
days old
websites@lists.fedoraproject.org
7 comments
2 participants
participants (2)
-
Keng Soon Goh -
Kevin Fenzi