• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

Can't get /48 to work [solved]

Started by cedeel, December 10, 2009, 12:15:17 PM

Previous topic - Next topic

cedeel

Hi there..

My /64 is 2001:470:28:d9::/64 and works without any problems.

But my 2001:470:dc35::/48 does not.

My gateway is a linux box set up with 2 interfaces. Adding an ip from the /64 on either one will be ping-able from the outside, but the ones from the /48 not. Not even when configured as a /64 subnet of the /48.

Further, when tracerouting to my /48 address, the traceroute stops before reaching my gateway, which I can't figure out why that happens.

Hope somebody will be able to help me out.

cholzhauer

The idea of the /48 is that you choose /64's and distribute them to your hosts, either with RA or DHCPv6.  How are you assigning addresses?


On second thought, maybe the /48 isn't assigned correctly?

C:\Users\cholzhauer>tracert -6 2001:470:dc35:0000:0000:0000:0000:0000

Tracing route to 2001:470:dc35:: over a maximum of 30 hops


C:\Users\cholzhauer>tracert -6 2001:470:dc35:0000:0000:0000:0000:0000

Tracing route to 2001:470:dc35:: over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  ipv6router.sscorp.com [2001:470:c27d:d000:2e0:18ff:fe9e:5566]
  2    68 ms    63 ms    66 ms  servicespring-1.tunnel.tserv9.chi1.ipv6.he.net [2001:470:1f10:2aa::1]
  3    62 ms    62 ms    72 ms  gige-g3-4.core1.chi1.he.net [2001:470:0:6e::1]
  4    87 ms    84 ms    89 ms  10gigabitethernet2-4.core1.nyc4.he.net [2001:470:0:4e::2]
  5   153 ms   152 ms   160 ms  10gigabitethernet1-2.core1.lon1.he.net [2001:470:0:3e::2]
  6   160 ms   160 ms   160 ms  10gigabitethernet1-1.core1.ams1.he.net [2001:470:0:3f::2]
  7   167 ms   167 ms   170 ms  10gigabitethernet1-1.core1.fra1.he.net [2001:470:0:47::2]
  8   193 ms   199 ms   199 ms  10gigabitethernet1-1.core1.sto1.he.net [2001:470:0:110::2]
  9   192 ms   192 ms   205 ms  2001:470:0:11e::2
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *     ^C
C:\Users\cholzhauer>c



it almost looks like the /48 doesn't know where to go.  Have you emailed info@he.net and asked them to look into it? That's what I'd do

broquea

#2
Both your /64 and your /48 appear to be routed to the same correct destination:

2001:470:28:d9::/64            2001:470:27:d9::2
2001:470:dc35::/48             2001:470:27:d9::2


Still poking around but not seeing any misconfiguration on our side. I'll push out the /48 static routes again just to be sure. What is an address out of the /48 that you've configured on your side?

Also be sure you email ipv6@he.net not "info".

broquea

Noticed that tracing from the tserv was sourcing a different tunnel interface even though there was only the 1 static route for the /48. Rebuilt all the tunnels and static routes, looks to be working now.

cholzhauer

Whoops, got my help addresses mixed up...SIXXS is info and HE is IPv6.

Thanks for the correction

cedeel