1. Home
  2. Cisco Systems
  3. Configuring ipv6 on cisco 877

Configuring ipv6 on cisco 877

I have a cisco 877 that's been working fine (after an RMA on the first one I had due to overheating issues) and thought I'd like to re-enable ipv6, since the router supports it.

The configuration seems simple enough - the tunnel broker (btexact - the only one left in the UK AFAIK) provides a script to configure IOS. However although everything looks like it has worked, I cannot ping any ipv6 addresses on the other end of the tunnel.

eg. defiant#ping

formatting link

Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:200:0:8002:203:47FF:FEA5:3085, timeout is 2 seconds: ..... Success rate is 0 percent (0/5)

A debug log (debug ip tunnel/debug ip packet) shows the packets going out, but nothing is coming back at all..

050632: Dec 7 15:37:53.530: Tunnel0: IPv6/IP encapsulated 84.9.223.40->213.121.24.85 (linktype=79, len=120) 050633: Dec 7 15:37:53.530: IP: s=84.9.223.40 (Tunnel0), d=213.121.24.85 (Dialer0), len 120, sending, proto=41 050646: Dec 7 15:40:20.167: Tunnel0: IPv6/IP encapsulated 84.9.223.40->213.121.24.85 (linktype=79, len=123) 050647: Dec 7 15:40:20.167: IP: s=84.9.223.40 (Tunnel0), d=213.121.24.85 (Dialer0), len 123, sending, proto=41

At this point I'm stumped - short of asking to ISP to see if the packets are actually leaving the cisco (which would be a major pain - they don't 'support' anything but Windows and getting them to understand such a request is not something I'm really keen to do).

Of course it's possible the tunnel broker is dead (it worked 2 years ago when I last dabbled in ipv6, but a lot can happen in that time).. I'd have to find another one then but they're getting scarce - all I can find are dead links... any ideas for live ones? (preferably in europe but if there are none there I'd settle for a US one).

Tony

(relevant bits of running config) interface Tunnel0 description BTexact Technologies tunnel broker (tb.ipv6.btexact.com) no ip address no ip redirects no ip unreachables no ip proxy-arp ip route-cache flow ipv6 address 2001:618:400::549:DF28/128 ipv6 enable ipv6 mtu 1280 tunnel source Dialer0 tunnel destination 213.121.24.85 tunnel mode ipv6ip end

interface Vlan1 description $FW_INSIDE$ ip address 192.168.44.1 255.255.255.0 ip access-group 100 in no ip redirects no ip unreachables no ip proxy-arp ip nat inside ip virtual-reassembly ip route-cache flow ip tcp adjust-mss 1452 ipv6 address 2001:618:400:2EEA::/64 eui-64 ipv6 enable ipv6 mtu 1280 end

Reply to
Tony Hoyle
Loading thread data ...

Mmm, google gave me an error.

try adding:

ipv6 unicast-routing

To your config#

Reply to
michaeldale

Try adding:

ipv6 unicast-routing

To your config#

Reply to
michaeldale

Already got that, and a default route (ipv6 route ::/0 Tunnel0).

I'll post the whole thing, hopefully without any passwords etc. It's SDM generated so is rather big (btw. does anyone know why an interface would vanish from SDM? It can't see Dialer0 for some reason, even though it's there and functioning).

Tony

Reply to
Tony Hoyle

The problem is btexact was broke. I setup a tunnel with Hurricane Electric in the US and it worked first time... It's a 300ms ping to the first hop though..

Now I have to work out the firewall.. it'd be easier if SDM supported ipv6 but that's not likely to happen, so I'll have to get to grips with building access lists manually (looks quite hard, as you can't delete individual entries or move them).

Reply to
Tony Hoyle

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.