IPv6 routing/connectivity gone awry today?
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Plusnet Community
- :
- Forum
- :
- Trials
- :
- IPv6 Trial
- :
- IPv6 routing/connectivity gone awry today?
IPv6 routing/connectivity gone awry today?
31-05-2011 1:11 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
My address/DHCP details:
Cisco837#sh ipv6 int brief
FastEthernet1 [up/up]
FastEthernet2 [down/down]
FastEthernet3 [down/down]
FastEthernet4 [down/down]
Ethernet0 [up/up]
FE80::212:D9FF:FED8:EE2B
2A02:16C8:2000:6000:212:D9FF:FED8:EE2B
ATM0 [up/up]
Ethernet2 [administratively down/down]
Tunnel0 [administratively down/down]
FE80::51AE:8B49
2001:470:1F08:1917::2
Dialer1 [up/up]
FE80::212:D9FF:FED8:EE2B
NVI0 [up/up]
Virtual-Access1 [up/up]
Virtual-Access2 [up/up]
Cisco837#sh ipv6 dhcp int
Ethernet0 is in server mode
Using pool: IPV6DHCP
Preference value: 0
Hint from client: ignored
Rapid-Commit: disabled
Dialer1 is in client mode
State is OPEN
Renew will be sent in 7w0d
List of known servers:
Reachable via address: FE80::90:1A00:3A3:AB15
DUID: 000200000A4C453332302F373435414333334558322F03
Preference: 0
Configuration parameters:
IA PD: IA ID 0x000D0001, T1 INFINITY, T2 INFINITY
Prefix: 2A02:16C8:2000:6000::/56
preferred lifetime INFINITY, valid lifetime INFINITY
DNS server: 2001:470:20::2
Prefix name: MYPLUSNETPREFIX
Rapid-Commit: enabled
I can reach what I assume to be the RADIUS/DHCPv6 server:
Cisco837#ping ipv6 FE80::90:1A00:3A3:AB15
Output Interface: dialer 1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FE80::90:1A00:3A3:AB15, timeout is 2 seconds:
Packet sent with a source address of FE80::212:D9FF:FED8:EE2B
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/36/44 ms
But I cannot reach any further over IPv6, but can over IPv4:
Cisco837#ping ipv6 targur.newtonnet.co.uk
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:BA8:1F1:F137::2, timeout is 2 seconds:
.....
Success rate is 0 percent (0/5)
Cisco837#ping ip targur.newtonnet.co.uk
Translating "targur.newtonnet.co.uk"...domain server (212.159.13.49) [OK]
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 212.13.195.175, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 32/36/40 ms
Anyone else having any trouble? As mentioned I'll have to wait until I'm back anyway but it could be useful to know if it's just me.
Mathew
Re: IPv6 routing/connectivity gone awry today?
31-05-2011 1:14 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
PB
Re: IPv6 routing/connectivity gone awry today?
31-05-2011 1:21 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Cisco837#clear ipv6 dhcp client dialer 1
Cisco837#sh ipv6 dhcp int
Ethernet0 is in server mode
Using pool: IPV6DHCP
Preference value: 0
Hint from client: ignored
Rapid-Commit: disabled
Dialer1 is in client mode
State is OPEN
Renew will be sent in 7w0d
List of known servers:
Reachable via address: FE80::90:1A00:3A3:AB15
DUID: 000200000A4C453332302F373435414333334558322F03
Preference: 0
Configuration parameters:
IA PD: IA ID 0x000D0001, T1 INFINITY, T2 INFINITY
Prefix: 2A02:16C8:2000:6000::/56
preferred lifetime INFINITY, valid lifetime INFINITY
DNS server: 2001:470:20::2
Prefix name: MYPLUSNETPREFIX
Rapid-Commit: enabled
Cisco837#ping ipv6 targur.newtonnet.co.uk
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:BA8:1F1:F137::2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/36/36 ms
I think I have read somewhere about a bug (issue?) in IOS that requires a forced DHCPv6 renewal following a reconnect (which I did have overnight) so will have to do some further digging.
Cheers,
Mathew
Re: IPv6 routing/connectivity gone awry today?
31-05-2011 1:41 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
http://blog.ioshints.info/2010/10/dhcpv6-over-pppoe-total-disaster.html
Specifically, if/when the link goes down (and comes back up) the DHCPv6 client is blissfully unaware and doesn't renew its lease until the timer runs out... 7 weeks later in this case! EEM, if supported, can be used to detect and force an update.
Time to renew my 837...
Mathew
Re: IPv6 routing/connectivity gone awry today?
01-06-2011 1:56 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
event manager applet MONITOR-IPV6-DHCP-APP
event syslog pattern "DIALER-6-BIND"
action 1.0 cli command "enable"
action 1.1 cli command "clear ipv6 dhcp client Dialer1"
action 2.0 syslog priority debugging msg "Refreshed IPv6 DHCP PD lease (Dialer rebind)"
Re: IPv6 routing/connectivity gone awry today?
01-06-2011 2:16 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I have however created a workaround - a script to monitor my syslog, detect the Virtual-Interface state change and login to the router to renew the lease. It's hacky[1], but it works. Will post it up later in case it's of use to anyone else.
Mathew
[1] Althought so is having to use EEM - Cisco should sort this issue out!
Re: IPv6 routing/connectivity gone awry today?
01-06-2011 2:25 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Re: IPv6 routing/connectivity gone awry today?
01-06-2011 2:34 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
My main issue has been one of video streaming - even running at a leisurely 2fps I require 150kbps upload, and my intention is to have two cameras running so that means I can support all of around 1-and-a-half concurrent users at any one time!
Of course, this could actually turn out to be more than enough but just in case it does attract some interest I've taken to streaming all the video to a well connected offsite server and will echo it to connecting users from there. Trouble is this just makes an already complicated even more so so we'll have to see how it pans out!
Your native IPv6 connectivity is however a real bonus over my previous tunneling so thank you for that.
Mathew
Re: IPv6 routing/connectivity gone awry today?
01-06-2011 7:52 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Enterprise Architect - Network & OSS
Plusnet Technology
Re: IPv6 routing/connectivity gone awry today?
01-06-2011 10:56 PM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Incidentally, I did try out a Cisco 857 the other day and found it repeatedly able to sync at a higher rate than my 837. The difference could well have been down to the (newer) ADSL firmware which, in the 837, is not upgradable. Imagine my disappointment when I then discovered the 857 doesn't support IPv6... The phrase 'Giveth with one hand, taketh away with the other' springs to mind... now at least: at the time it was something a bit stronger!
Mathew
Re: IPv6 routing/connectivity gone awry today?
02-06-2011 10:58 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Enterprise Architect - Network & OSS
Plusnet Technology
Re: IPv6 routing/connectivity gone awry today?
02-06-2011 11:11 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
Mathew
Re: IPv6 routing/connectivity gone awry today?
03-06-2011 9:02 AM
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Report to Moderator
I can confirm there was a forced resync at ~0330hrs and I now have an upload sync of 704kbps and throughput of around 650bkps so that extra bit of headroom will be a real help - thanks!
Mathew
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page