|
Ticket ID: SIXXS #655439 Ticket Status: Resolved PoP: uschi02 - Your.Org, Inc. (Chicago, Illinois)
PoP/Tunnel up but no connectivity
![[us]](/s/countries/us.gif) Shadow Hawkins on Thursday, 17 January 2008 06:48:01
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there:
Absent IPv6 connectivity.
1) I am BAG30-RIPE.
2) This concerns tunnel 2001:4978:f:34::2
3) It is with uschi02, which I have as being IP address: 216.14.98.22
4) I am at IP: 72.204.123.221
5) This computer is running WinXP Pro SP2.
I can ping the PoP IPv4 endpoint, but not the PoP IPv6 endpoint.
Trying to ping the PoP v6 address from a machine on usewr01 tells me:
PING 2001:4978:f:34::1(2001:4978:f:34::1) 56 data bytes
From 2001:4978:1:400:202:b3ff:feb4:59cb icmp_seq=1 Destination unreachable: Address unreachable
using the autotest feature of aiccu, it fails at test 6:
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:4978:f:34::1)
As that fails, the remaining two also fail.
PoP/Tunnel up but no connectivity
Shadow Hawkins on Thursday, 17 January 2008 06:56:29
Normally when AICCU starts the TAP device gets an address nearly immeadiately, this time however it sits on "Acquiring network address" before finally giving up and assigning the device: 169.254.117.113
PoP/Tunnel up but no connectivity
You can/should remove the IPv4 protocol from that interface.
The 169.254.0.0/16 block is for IPv4 auto-configuration (actually IPv4 link-local) in a similar fashion as IPv6 link-local (fe80::/10). When no DHCP server can be found on a link the IPv4 address is picked from this block. Then, when you have a small home network, you just have to take a switch, plug in some hosts and they all get an address from fe80::/10 for IPv6 and 169.254.0.0/16 for IPv4 and they can communicate with each-other with that. Adding Bonjour/mDNS to that also solves the DNS problem, but Microsoft relies on the availability of SMB/CIFS/Windows Networking to resolve the hostnames.
State change: resolved
The state of this ticket has been changed to resolved
PoP/Tunnel up but no connectivity
When the <tunnel>::1 address (PoP-side) of a tunnel is not reachable, and the PoP is reporting that, then the tunnel is not configured/up.
We have been trying to work-around a kernel bug which is crashing the system nearly once a day, unfortunately the work around don't seem to have much affect yet.
|
![[ch]](/s/countries/ch.gif)
on Thursday, 17 January 2008 09:08:16
Posting is only allowed when you are