Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Could not grab the file via ....  (Read 5540 times)

owah

  • Newbie
  • *
  • Posts: 6
Could not grab the file via ....
« on: October 06, 2013, 03:24:42 PM »

Hi,

I'm not sure what I'm doing wrong, but I added an AAAA record to my domain:

Code: [Select]
root@caotina:~# dig AAAA ipv6.etienne.pw

; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> AAAA ipv6.etienne.pw
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 365
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 8

;; QUESTION SECTION:
;ipv6.etienne.pw.               IN      AAAA

;; ANSWER SECTION:
ipv6.etienne.pw.        600     IN      AAAA    2a00:bd80:12::e

I'm also able to wget the file from another place:

Code: [Select]
root@ns3369651:~# wget http://ipv6.etienne.pw/hq4yicztn8.txt
--2013-10-07 00:17:44--  http://ipv6.etienne.pw/hq4yicztn8.txt
Resolving ipv6.etienne.pw (ipv6.etienne.pw)... 2a00:bd80:12::e
Connecting to ipv6.etienne.pw (ipv6.etienne.pw)|2a00:bd80:12::e|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5 [text/plain]
Saving to: `hq4yicztn8.txt'

100%[==============================================================================================================================>] 5           --.-K/s   in 0s     

2013-10-07 00:17:44 (695 KB/s) - `hq4yicztn8.txt' saved [5/5]
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: Could not grab the file via ....
« Reply #1 on: October 06, 2013, 03:36:29 PM »

HE doesn't appear to have a route:

Code: [Select]
Connected to route-server.he.net.
Escape character is '^]'.
route-server> sh ipv6 bgp 2a00:bd80::/32
% Network not in table
Logged

owah

  • Newbie
  • *
  • Posts: 6
Re: Could not grab the file via ....
« Reply #2 on: October 06, 2013, 03:38:06 PM »

I guess i'll have to contact HE.NET support regarding this?
« Last Edit: October 06, 2013, 03:41:06 PM by owah »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: Could not grab the file via ....
« Reply #3 on: October 06, 2013, 03:59:47 PM »

Or your provider. They appear to peer fine, just doesn't look like the route is propagating.
Logged

owah

  • Newbie
  • *
  • Posts: 6
Re: Could not grab the file via ....
« Reply #4 on: October 06, 2013, 04:09:12 PM »

hmmmmmm a friend just told me that there apparently is a feud between he.net and cogent regarding ipv6 traffic. and since my provider only offers cogent ipv6... :||||
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: Could not grab the file via ....
« Reply #5 on: October 06, 2013, 04:15:37 PM »

Not certain how Cogent is involved with that address space:

http://bgp.he.net/ip/2a00:bd80::

Neither of those networks are Cogent, and one of them directly IPv6 peers with HE.NET. Like I said, make certain your provider is getting it announced correctly.
« Last Edit: October 06, 2013, 04:23:39 PM by broquea »
Logged

owah

  • Newbie
  • *
  • Posts: 6
Re: Could not grab the file via ....
« Reply #6 on: October 06, 2013, 04:38:08 PM »

http://bgp.he.net/AS51395#_prefixes6

http://bgp.he.net/AS51395#_graph6


Checking the transit provider SOFTplus (my provider) uses you can see that in IPv4 its HE and Cogent and in IPv6 its cogent only. So far ive been able to reach the IPv6 from a multitude of providers.

Anyhow, if i message my provider, what should I specifically ask for?
« Last Edit: October 06, 2013, 04:46:04 PM by owah »
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: Could not grab the file via ....
« Reply #7 on: October 07, 2013, 12:01:50 AM »

http://bgp.he.net/AS51395#_peers

They peer IPv4 with HE. Yell at them to peer on IPv6. Tell them that you cannot reach portions of the internet via the connectivity they sold you.
Logged

owah

  • Newbie
  • *
  • Posts: 6
Re: Could not grab the file via ....
« Reply #8 on: October 11, 2013, 03:51:37 PM »

my provider is now using HE IPv6 Transit, yet I can still not establish a connection? http://bgp.he.net/AS51395#_graph6
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1735
Re: Could not grab the file via ....
« Reply #9 on: October 11, 2013, 04:04:10 PM »

Might be a return path issue with your provider? HE sees the route now, but it stops in Zurich:

Code: [Select]
route-server> sh ipv6 bgp 2a00:bd80::/32
BGP routing table entry for 2a00:bd80::/32
Paths: (35 available, best #1, table Default-IP-Routing-Table)
  Not advertised to any peer
  51395
    2001:470:0:10c::1 from 2001:470:0:10c::1 (216.218.252.153)
      Origin IGP, metric 1, localpref 140, valid, internal, best
      Community: 6939:1000 6939:6000
      Last update: Wed Oct  9 16:59:32 2013

Code: [Select]
Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. f0-6.switch14.fmt2.he.net         0.0%     6    0.6   1.5   0.6   6.0   2.2
 2. 10gigabitethernet8-4.core1.fmt2.  0.0%     6    0.6   2.9   0.5   9.9   3.6
 3. 10gigabitethernet1-1.core1.sjc2.  0.0%     6    1.0   2.6   1.0   6.1   2.5
 4. 10gigabitethernet3-3.core1.den1.  0.0%     5   32.7  31.2  28.0  34.2   3.0
 5. 10gigabitethernet4-3.core1.chi1.  0.0%     5   52.1  56.5  51.6  64.4   6.0
 6. 10gigabitethernet15-7.core1.ash1  0.0%     5   75.3  70.2  66.7  75.3   4.7
 7. 10gigabitethernet9-2.core1.par2.  0.0%     5  152.9 148.3 145.2 152.9   4.1
 8. 10gigabitethernet3-2.core1.zrh1.  0.0%     5  158.8 160.3 158.7 166.4   3.5
 9. ???
Logged

owah

  • Newbie
  • *
  • Posts: 6
Re: Could not grab the file via ....
« Reply #10 on: October 11, 2013, 04:07:06 PM »

pffffff i should really switch to another provider. I complained to them that they were using a singlehomed ipv6 (cogent) now suddenly its singlehomed HE and still nothing works properly. they also dropped their cogent backup route on ipv4, now ipv4 is singlehomed HE too.
Logged