• February 22, 2025, 03:21:45 PM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: IPv6 server not reachable from host, however reachable from DIR-825  (Read 18836 times)

kili21

  • Level 1 Member
  • *
  • Posts: 5

I am bringing up a HE tunnel to my home router Dlink DIR-825 Hardware Version: B1     Firmware Version: 2.09NA.
I have config all what i need with 6in4 tunnel configurations on my router.
I enabled ICMP to have IPv4 tunnel up. And I have IPv4 reachability to the HE IPv4 server
 I do ping6 tests  from my Dlink to the server IPv6 address and it works. However, when i try to ping the same IPv6 from my PC behind the router, it doesnt work.
my laptop gets the IPv6 address from the LAN i have assigned from HE and configured on my Dlink as well. I can succesfully ping to the LAN default gw from my laptop.
So the Ipv6 in ipv4 tunnel is up and running, but i could not reach the IPv6 HE server from my laptop behind my router.
I guess is something related to NAT/protocol 41. But i dont find out the way to have reachability to the HE IPv6 server from my laptop.
Does anyone knows whats happening? and how to solve it?
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #1 on: February 03, 2015, 08:29:47 AM »

Link>Welcome!

  • What region are you located?

Internet Service Provider and Modem Configurations
  • What ISP Service do you have? Cable or DSL?
  • What ISP Modem Mfr. and model # do you have?

Router and Wired Configurations
Some things to try: - Log into the routers web page at 192.168.0.1. Use IE, Opera or FF to manage the router. Besure to log into the Admin account on the router.
  • Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual or under Setup/PARENTAL CONTROL/Set to>None: Static IP or Obtain Automatically From ISP.
  • Enable or Disable Use Unicasting (compatibility for some ISP DHCP Servers) and test under Setup/Internet/Manual. Disable may help with speed performance on higher speed ISP services.
  • Turn off DNS Relay  under Setup/Networking. Link>Finding Faster DNS Addresses using Name Bench and input new DNS addresses under Setup/Internet/Manual.
  • Setup DHCP reserved IP addresses for all devices ON the router. Setup/Networking. This ensures each devices gets its own IP address when turned on and connected, eliminates IP address conflicts and helps in troubleshooting and maintain consistency for applications that need to connect as well as mapped drives.
  • Ensure devices are set to auto obtain an IP address.
  • Set Firewall settings to Endpoint Independent for TCP and UDP under Advanced/Firewall. Enable or Disable SPI to test.
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

kili21

  • Level 1 Member
  • *
  • Posts: 5
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #2 on: February 04, 2015, 09:51:40 AM »

Hi. I have Cablemodem. Docsis 2.0 , but its in Bridge mode.
Dlink is working as router at home.

I have tried all the recommendations on Router and Wired Configurations section without any succesfull results...
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #3 on: February 04, 2015, 10:00:04 AM »

I'm wondering if there needs to be any Virtual Server configuration set up. I think I remember someone telling me about this a while back. Been a long time as I haven't used HE or IPv6 in a while. I'll ask someone to review this and post additional information...
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #4 on: February 04, 2015, 12:28:23 PM »

Hi, nothing sounds wrong, but often the devil is in the details ...

So it might help if you could present screenshots of ...
  • ... your DIR-825 "IPv6 in IPv4 Tunneling (Stateful)" or "IPv6 in IPv4 Tunneling (Stateless)" according to pages 67 or 68 of the manual.
  • ... the output of the command ipconfig /all inside a command prompt of your laptop (assuming it is Windows).

If you want to obscure global IPv6 addresses for privacy reasons, please mask the third 16-Bit block starting from the left (bits 32 through 47). Obscure global IPv4 addresses via masking the third octet counting from the left (bits 16 through 23).
Logged

kili21

  • Level 1 Member
  • *
  • Posts: 5
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #5 on: February 06, 2015, 06:30:52 AM »

Hi,
config is IPV6 in IPv4 Tunneling, SLAAC + DHCP Stateless........

when i do an ipconfig/all , shows me the ipv6 autoconfigured from the IPv6 LAN that HE assigned me...I ping the default gw ::1 and works.

so.......i dont find out whats the issue...
Logged

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #6 on: February 06, 2015, 09:25:26 AM »

Quote
I ping the default gw ::1 and works

If I take this statement literally, then a default gateway = ::1 (=IPv6 loopback address) is obviously wrong.

Once again, please provide the screenshots I asked you for, I really want to see all addresses in order to be able to check, if the whole picture is consistent in itself.
Logged

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #7 on: February 07, 2015, 08:41:52 AM »

btw. please note that your DIR-825 has no IPv6 firewall. Hence, after having managed to make IPv6 work you will have to use host based firewalls to protect your LAN/WLAN devices. If this is not acceptable to you, you can save yourself any further effort to connect your LAN to the IPv6 Internet.
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #8 on: February 07, 2015, 08:52:56 AM »

Just FYI, full IPv6 support was not fully implemented on Rev B back then. IPv6 Firewall was not included. Rev C router is was.  :-\

Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.

kili21

  • Level 1 Member
  • *
  • Posts: 5
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #9 on: February 09, 2015, 06:58:51 AM »

when i said ::1, I mean the IPv6 LAN default gw,  LAN IPv6 Address :     2001:470:5:571::1/64

I tried with ipv6 DNS and without DNS but resolvers seems not to be the issue. they are solving the v6 domains.

Here is the ipconfig output

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : fibertel.com.ar
   Description . . . . . . . . . . . : Atheros AR9285 Wireless Network Adapter
   Physical Address. . . . . . . . . : 48-5D-60-7D-AB-32
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:470:5:571:f158:c63e:cae3:6930(Prefer
red)
   Temporary IPv6 Address. . . . . . : 2001:470:5:571:2dde:7c63:e44c:ada1(Prefer
red)
   Link-local IPv6 Address . . . . . : fe80::f158:c63e:cae3:6930%10(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.105(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : lunes, 09 de febrero de 2015 11:36:07 a.m
.
   Lease Expires . . . . . . . . . . : martes, 10 de febrero de 2015 11:36:03 a.
m.
   Default Gateway . . . . . . . . . : fe80::218:e7ff:fede:e915%10
                                       192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 239623520
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-BF-E7-5B-48-5D-60-7D-AB-32

   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{328248B0-7996-4CD7-88FB-1F0E8C4A59A1}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.fibertel.com.ar:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : fibertel.com.ar
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes



Logged

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #10 on: February 09, 2015, 03:07:59 PM »

Could you show us the results of the command tracert -d -6 2001:4860:4860::8888 entered inside a command prompt at your laptop? Please, also show us the results of the following commands:

netsh int ipv6 show route
netsh int ipv6 show neighbor

When I perform a traceroute to any of your LAN IPv6 addesses, e.g. 2001:470:5:571::1, I get the following results:

Code: [Select]
C:\>tracert -d -6  2001:470:5:571::1

Routenverfolgung zu 2001:470:5:571::1 über maximal 30 Abschnitte

  ...
  7    20 ms    21 ms    24 ms  2001:7f8:1::a500:6939:1
  8    26 ms    27 ms    26 ms  2001:470:0:2d0::1
  9    96 ms   110 ms    92 ms  2001:470:0:2cf::2
 10    97 ms   121 ms    98 ms  2001:470:0:299::1
 11   110 ms   115 ms   110 ms  2001:470:0:1b5::2
 12     *      126 ms   126 ms  2001:470:0:a6::1
 13   127 ms   127 ms   127 ms  2001:470:0:8c::2
 14  Zielhost nicht erreichbar.

Ablaufverfolgung beendet.

Is 2001:470:0:8c::2 your Local IPv6 Address according to your IPv6 in IPv4 TUNNEL SETTINGS?  (The still missing screenshot of your "IPv6 in IPv4 Tunneling (Stateless)" would be really helpful ...)

If you use a HE tunnel you should have a fixed global IPv4 WAN address for use as a local tunnel endpoint ("Local IPv4 Address" in "IPv6 in IPv4 TUNNEL SETTINGS"). Are you sure you get a WAN IP address from your cable provider that never changes? Check if the WAN IP address shown under STATUS | DEVICE INFO is the same as your configured "Local IPv4 Address" in "IPv6 in IPv4 TUNNEL SETTINGS".

EDIT:
The last responsive address 2001:470:0:8c::2 reachable via traceroute resolves to 'tserv1.mia1.he.net'. This does not look like a name being used for HE customer IPv6 tunnel endpoints. Hence I assume your IPv6 range 2001:470:5:571::/64 is not tunneled/routed by HE to your IPv4 tunnel endpoint, perhaps for reasons I outlined directly above.
« Last Edit: February 10, 2015, 01:38:42 PM by PacketTracer »
Logged

kili21

  • Level 1 Member
  • *
  • Posts: 5
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #11 on: February 13, 2015, 09:31:25 AM »

My WAN IP addr is the correct one to establish the tunnel. Even I see the tunnel up in the Dlink status.
I couldnt find the way to insert the snapshot, what i am doing is pasting the config from the Dlink 6 in 4 Tunnel.


IPv6 CONNECTION TYPE
Choose the mode to be used by the router to the IPv6 Internet.

My IPv6 Connection is :    
IPv6 in IPv4 TUNNEL SETTINGS
Enter the IPv6 in IPv4 Tunnel information provided by your Tunnel Broker.

Remote IPv4 Address :    209.51.161.58
Remote IPv6 Address :    2001:470:4:571::1
Local IPv4 Address :   x.x.x.x (my WAN addr here and its correct)
Local IPv6 Address :    2001:470:4:571::2

IPv6 DNS SETTINGS
Obtain a DNS server address automatically or enter a specific DNS server address.

(selected)    Obtain IPv6 DNS servers automatically
    Use the following IPv6 DNS servers
Primary IPv6 DNS Server :    2001:470:20::2
Secondary IPv6 DNS Server :    -


LAN IPv6 ADDRESS SETTINGS
Use this section to configure the internal network settings of your router. If you change the LAN IPv6 Address here, you may need to adjust your PC network settings to access the network again.

Enable DHCP-PD : (unselected)   
LAN IPv6 Address :   2001:470:5:571::1   /64
LAN IPv6 Link-Local Address :     FE80::218:x:x:x:x/64

ADDRESS AUTOCONFIGURATION SETTINGS
Use this section to setup IPv6 Autoconfiguration to assign IP addresses to the computers on your network.
Enable automatic IPv6 address assignment :    (selected)
Enable Automatic DHCP-PD in LAN :    (selected, i cannot unselect it)
Autoconfiguration Type :     SLAAC + Stateless DHCPv6
Router Advertisement Lifetime :   1440   (minutes)


Here are the captures from my laptop behind the router:

>netsh int ipv6 show route

Publish  Type      Met  Prefix                    Idx  Gateway/Interface Name
-------  --------  ---  ------------------------  ---  ------------------------
No       Manual    256  ::/0                       10  fe80::218:e7ff:fede:e915
No       Manual    256  ::1/128                     1  Loopback Pseudo-Interface
 1
No       Manual    8    2001:470:5:571::/64        10  Wireless Network Connecti
on
No       Manual    16   2001:470:5:571::/64        10  fe80::218:e7ff:fede:e915
No       Manual    256  2001:470:5:571:f158:c63e:cae3:6930/128   10  Wireless Ne
twork Connection
No       Manual    256  fe80::/64                  11  Local Area Connection
No       Manual    256  fe80::/64                  10  Wireless Network Connecti
on
No       Manual    256  fe80::/64                  17  Wireless Network Connecti
on 2
No       Manual    256  fe80::85f7:a797:81a:a554/128   17  Wireless Network Conn
ection 2
No       Manual    256  fe80::a1ce:4eae:161f:2ab3/128   11  Local Area Connectio
n
No       Manual    256  fe80::f158:c63e:cae3:6930/128   10  Wireless Network Con
nection
No       Manual    256  ff00::/8                    1  Loopback Pseudo-Interface
 1
No       Manual    256  ff00::/8                   11  Local Area Connection
No       Manual    256  ff00::/8                   10  Wireless Network Connecti
on
No       Manual    256  ff00::/8                   17  Wireless Network Connecti
on 2


>netsh int ipv6 show neighbor

Interface 1: Loopback Pseudo-Interface 1


Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::2                                                          Permanent
ff02::c                                                          Permanent
ff02::16                                                         Permanent
ff02::fb                                                         Permanent
ff02::1000                                                       Permanent
ff02::1:2                                                        Permanent
ff02::1:ff8b:8cef                                                Permanent

Interface 10: Wireless Network Connection


Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
fe80::218:e7ff:fede:e915                      00-18-e7-de-e9-15  Stale (Router)
fe80::2c3a:cbee:210d:5196                     60-67-20-36-61-b4  Stale
fe80::dda5:9d5e:ac8b:8cef                     b0-48-7a-88-e8-fd  Stale
ff02::1                                       33-33-00-00-00-01  Permanent
ff02::2                                       33-33-00-00-00-02  Permanent
ff02::c                                       33-33-00-00-00-0c  Permanent
ff02::16                                      33-33-00-00-00-16  Permanent
ff02::fb                                      33-33-00-00-00-fb  Permanent
ff02::1000                                    33-33-00-00-10-00  Permanent
ff02::1:2                                     33-33-00-01-00-02  Permanent
ff02::1:3                                     33-33-00-01-00-03  Permanent
ff02::1:ff0d:5196                             33-33-ff-0d-51-96  Permanent
ff02::1:ff8b:8cef                             33-33-ff-8b-8c-ef  Permanent
ff02::1:ffde:e915                             33-33-ff-de-e9-15  Permanent
ff02::1:ffe3:6930                             33-33-ff-e3-69-30  Permanent

Interface 17: Wireless Network Connection 2


Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::2                                       33-33-00-00-00-02  Permanent
ff02::16                                      33-33-00-00-00-16  Permanent
ff02::fb                                      33-33-00-00-00-fb  Permanent
ff02::1000                                    33-33-00-00-10-00  Permanent
ff02::1:2                                     33-33-00-01-00-02  Permanent
ff02::1:ff8b:8cef                             33-33-ff-8b-8c-ef  Permanent

Interface 11: Local Area Connection


Internet Address                              Physical Address   Type
--------------------------------------------  -----------------  -----------
ff02::2                                       33-33-00-00-00-02  Permanent
ff02::16                                      33-33-00-00-00-16  Permanent
ff02::fb                                      33-33-00-00-00-fb  Permanent
ff02::1000                                    33-33-00-00-10-00  Permanent
ff02::1:2                                     33-33-00-01-00-02  Permanent
ff02::1:ff8b:8cef                             33-33-ff-8b-8c-ef  Permanent


As you can see, there is no IPv6 reachability:

C:\Users\Christian>tracert -d -6 2001:4860:4860::8888

Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.

Logged

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #12 on: February 13, 2015, 01:58:44 PM »

Hi,

thank you for the detailed information! Btw. the usual way to post screenshots is to use some image hoster (e.g. http://postimage.org/) to upload a screenshot and then use the "Insert Image" button to specify its URL. As a result the screenshot is implicitly downloaded and shown embedded into your posting. You can use a freeware like XnView to generate screenshots.

To summarize, this is your configuration reduced to the essential parts for IPv6:


WAN side:
---------
Remote IPv4 Address :          209.51.161.58
Remote IPv6 Address :          2001:470:4:571::1
Local IPv4 Address :           x.x.x.x (my WAN addr here and its correct)
Local IPv6 Address :           2001:470:4:571::2
Primary IPv6 DNS Server :      2001:470:20::2
Secondary IPv6 DNS Server :    -

LAN side:
---------
LAN IPv6 Address :             2001:470:5:571::1/64
LAN IPv6 Link-Local Address :  FE80::218:E7FF:FEDE:E915/64

Client (wireless):
------------------
IPv6 Address:                  2001:470:5:571:f158:c63e:cae3:6930
Temporary IPv6 Address:        2001:470:5:571:<changing Interface ID>
Link-local IPv6 Address:       fe80::f158:c63e:cae3:6930%10
Default Gateway:               fe80::218:e7ff:fede:e915%10
DNS Servers:                   192.168.0.1


According to your router's setting "Autoconfiguration Type :  SLAAC + Stateless DHCPv6" it should deploy the configured IPv6 DNS server address (2001:470:20::2) via stateless DHCPv6 to your client, but it doesn't. But this is only a minor problem and doesn't matter because you can also resolve names to IPv6 addresses by asking a DNS server via IPv4 (192.168.0.1 acting as a DNS relay).

Nothing looks wrong and your client's ipv6 routing table shows the routing entries as expected, especially the default route ::/0 pointing to the link local address of your router (fe80::218:e7ff:fede:e915). And this address is also shown in the IPv6 neighbor cache together with its resolved MAC address 00-18-e7-de-e9-15 (your router's LAN side MAC address). (Btw. the OUI "00-18-e7" contained in your router's MAC address belongs to 'Cameo Communications, INC.' and not to D-Link, as one would expect. You can see it, if you search for 00-18-e7 on this website)

It's only its reachability state "Stale" that may be a problem if it never reaches the state "Reachable".  Hence, please check if you can provoke state "Reachable" by entering the following commands inside a command prompt:

ping  fe80::218:e7ff:fede:e915%10
netsh int ipv6 show neighbor

First you should see ping replies coming back from your router's link local address fe80::218:e7ff:fede:e915.
Second the neighbor cache entry for your router's link local address fe80::218:e7ff:fede:e915 should now show state=Reachable.

Do these things happen as predicted?

Looking at

Code: [Select]
C:\Users\Christian>tracert -d -6 2001:4860:4860::8888
Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops
  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
...

this result is surprising because even if something is wrong on the WAN side your router should at least react correctly to the first step of traceroute resulting in the following expected output:

Code: [Select]
C:\Users\Christian>tracert -d -6 2001:4860:4860::8888
Tracing route to 2001:4860:4860::8888 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  2001:470:5:571::1
  2     *        *        *     Request timed out.
...

This is consistent with the results I get when doing a traceroute to your router's IPv6 WAN address:

While traceroute to your remote tunnel address 2001:470:4:571::1 works fine

Code: [Select]
C:\>tracert -d 2001:470:4:571::1

Routenverfolgung zu 2001:470:4:571::1 über maximal 30 Abschnitte

  1     1 ms    <1 ms    <1 ms  2001:4dd0:????:????:9ec7:a6ff:fe??:????
  2    21 ms    22 ms    22 ms  2001:4dd0:????:????::1
  3    21 ms    21 ms    21 ms  2001:4dd0:1234:3::42
  4    21 ms    21 ms    21 ms  2001:4dd0:1234:3:dc40::a
  5    21 ms    21 ms    21 ms  2001:4dd0:a2b:37:dc40::c
  6    25 ms    26 ms    25 ms  2001:4dd0:a2b:a8:30::b
  7    34 ms    25 ms    26 ms  2001:7f8:1::a500:6939:1
  8    32 ms    40 ms    32 ms  2001:470:0:2d0::1
  9   111 ms   103 ms   102 ms  2001:470:0:2cf::2
 10   103 ms   103 ms   103 ms  2001:470:0:299::1
 11   120 ms   121 ms   123 ms  2001:470:0:1b5::2
 12     *      133 ms   139 ms  2001:470:0:a6::1
 13   131 ms   131 ms   131 ms  2001:470:4:571::1

Ablaufverfolgung beendet.

I get the following result when doing a traceroute to your local tunnel address 2001:470:4:571::2:

Code: [Select]
C:\>tracert -d 2001:470:4:571::2

Routenverfolgung zu 2001:470:4:571::2 über maximal 30 Abschnitte

  1    <1 ms    <1 ms    <1 ms  2001:4dd0:????:????:9ec7:a6ff:fe??:????
  2    22 ms    20 ms    21 ms  2001:4dd0:????:????::1
  3    22 ms    21 ms    21 ms  2001:4dd0:1234:3::42
  4    21 ms    21 ms    21 ms  2001:4dd0:1234:3:dc40::a
  5    21 ms    21 ms    21 ms  2001:4dd0:a2b:37:dc40::c
  6    25 ms    32 ms    25 ms  2001:4dd0:a2b:a8:30::b
  7    25 ms    26 ms    26 ms  2001:7f8:1::a500:6939:1
  8    43 ms    33 ms    41 ms  2001:470:0:2d0::1
  9   105 ms   103 ms   103 ms  2001:470:0:2cf::2
 10   105 ms   103 ms   103 ms  2001:470:0:299::1
 11   120 ms   120 ms   122 ms  2001:470:0:1b5::2
 12     *      134 ms   139 ms  2001:470:0:a6::1
 13   141 ms   141 ms   141 ms  2001:470:0:8c::2
 14  Zielhost nicht erreichbar.

Ablaufverfolgung beendet.

As you can see, both traceroutes differ from each other starting at step 13, where I interpret 2001:470:0:8c::2 being the Internet side and 2001:470:4:571::1 being the tunnel side address of the last IPv6 router on the path to your DIR-825. Consequently step 14 "Zielhost nicht erreichbar." is your router not reacting on the traceroute (via sending an ICMPv6 error message type 3 "Time Exceeded") as it does not on its LAN interface as shown above.

<EDIT>
The last statement is wrong because the observed behaviour can be explained by the results I reported in my next posting, see below. Performing a "tracert -d 2001:470:4:571::2" again while tracing it with wireshark reveals the same result as reported below, namely that it ends with an ICMPv6 error "Destination Unreachable" (Type 1) and Code 3 (Address unreachable) - which is reflected in the last line of the tracert above "Zielhost nicht erreichbar" (=Destination host not reachable)
</EDIT>


Taking together these results gives us a strong hint that it is your DIR-825 not acting like an IPv6 router.

<EDIT>
This conclusion must possibly be revised, because it was based on an assumption that turned out to be wrong, see my last EDIT above and my next posting below.
</EDIT>

On the other hand there are no other configuration options left inside your DIR-825 that you could change to solve the problem.

You could reset your router and repeat a complete configuration from scratch. In the worst case IPv6 routing function is broken in your firmware version, so the last option left is to try another one. I don't know if there is a newer version than 2.09NA (does this version fit your region?), the latest official version I can see on D-Link's US FTP download side is 2.07NA for Rev B - perhaps you should use that former version.

PT
« Last Edit: February 15, 2015, 04:56:03 AM by PacketTracer »
Logged

PacketTracer

  • Level 4 Member
  • ****
  • Posts: 441
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #13 on: February 14, 2015, 09:12:11 AM »

Hi

yet another hint:

I did a "ping -n 1 2001:470:5:571::1" and a "ping -n 1 2001:470:4:571::2" while running wireshark. In both cases I get the following reply from 2001:470:0:8c::2: ICMPv6 error "Destination Unreachable" (Type 1) with code 3 (Address unreachable).

This indicates that something is wrong with the routing to your address ranges (both 2001:470:4:571::/64 for the tunnel and 2001:470:5:571::/64 for your LAN) at the HE site. You should contact HE and ask for the reasons. Are you sure, that your (present) local IPv4 address ("Local IPv4 Address :  x.x.x.x (my WAN addr here and its correct)") is the same address you registered at HE to be your local IPv4 tunnel endpoint?

If needed here are the relevant Wireshark results that show the received ICMPv6 error messages:

ping -n 1 2001:470:5:571::1
Code: [Select]
Frame 1: 94 bytes on wire (752 bits), 94 bytes captured (752 bits)
    Encapsulation type: Ethernet (1)
    Arrival Time: Feb 14, 2015 18:01:55.664736000 Mitteleuropäische Zeit
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 1423933315.664736000 seconds
    [Time delta from previous captured frame: 0.000000000 seconds]
    [Time delta from previous displayed frame: 0.000000000 seconds]
    [Time since reference or first frame: 0.000000000 seconds]
    Frame Number: 1
    Frame Length: 94 bytes (752 bits)
    Capture Length: 94 bytes (752 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: eth:ethertype:ipv6:ipv6.nxt:icmpv6:data]
    [Coloring Rule Name: ICMP]
    [Coloring Rule String: icmp || icmpv6]
Ethernet II, Src: IntelCor_19:56:f3 (00:1c:c0:19:56:f3), Dst: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
    Destination: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        Address: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        Address: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv6 (0x86dd)
Internet Protocol Version 6, Src: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362), Dst: 2001:470:5:571::1 (2001:470:5:571::1)
    0110 .... = Version: 6
        [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
    .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
        .... 0000 00.. .... .... .... .... .... = Differentiated Services Field: Default (0x00000000)
        .... .... ..0. .... .... .... .... .... = ECN-Capable Transport (ECT): Not set
        .... .... ...0 .... .... .... .... .... = ECN-CE: Not set
    .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
    Payload length: 40
    Next header: ICMPv6 (58)
    Hop limit: 128
    Source: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
    Destination: 2001:470:5:571::1 (2001:470:5:571::1)
    [Source GeoIP: Unknown]
    [Destination GeoIP: Unknown]
Internet Control Message Protocol v6
    Type: Echo (ping) request (128)
    Code: 0
    Checksum: 0x7c97 [correct]
    Identifier: 0x0001
    Sequence: 78
    [No response seen]
        [Expert Info (Warn/Sequence): No response seen to ICMPv6 request in frame 1]
            [No response seen to ICMPv6 request in frame 1]
            [Severity level: Warn]
            [Group: Sequence]
    Data (32 bytes)

0000  61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0010  71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
        Data: 6162636465666768696a6b6c6d6e6f707172737475767761...
        [Length: 32]

Frame 2: 142 bytes on wire (1136 bits), 142 bytes captured (1136 bits)
    Encapsulation type: Ethernet (1)
    Arrival Time: Feb 14, 2015 18:01:55.935322000 Mitteleuropäische Zeit
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 1423933315.935322000 seconds
    [Time delta from previous captured frame: 0.270586000 seconds]
    [Time delta from previous displayed frame: 0.270586000 seconds]
    [Time since reference or first frame: 0.270586000 seconds]
    Frame Number: 2
    Frame Length: 142 bytes (1136 bits)
    Capture Length: 142 bytes (1136 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: eth:ethertype:ipv6:ipv6.nxt:icmpv6:ipv6:ipv6.nxt:icmpv6:data]
    [Coloring Rule Name: ICMP errors]
    [Coloring Rule String: icmp.type eq 3 || icmp.type eq 4 || icmp.type eq 5 || icmp.type eq 11 || icmpv6.type eq 1 || icmpv6.type eq 2 || icmpv6.type eq 3 || icmpv6.type eq 4]
Ethernet II, Src: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15), Dst: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
    Destination: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        Address: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        Address: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv6 (0x86dd)
Internet Protocol Version 6, Src: 2001:470:0:8c::2 (2001:470:0:8c::2), Dst: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
    0110 .... = Version: 6
        [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
    .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
        .... 0000 00.. .... .... .... .... .... = Differentiated Services Field: Default (0x00000000)
        .... .... ..0. .... .... .... .... .... = ECN-Capable Transport (ECT): Not set
        .... .... ...0 .... .... .... .... .... = ECN-CE: Not set
    .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
    Payload length: 88
    Next header: ICMPv6 (58)
    Hop limit: 53
    Source: 2001:470:0:8c::2 (2001:470:0:8c::2)
    Destination: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
    [Source GeoIP: Unknown]
    [Destination GeoIP: Unknown]
Internet Control Message Protocol v6
    Type: Destination Unreachable (1)
    Code: 3 (Address unreachable)
    Checksum: 0x1107 [correct]
    Reserved: 00000000
    Internet Protocol Version 6, Src: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362), Dst: 2001:470:5:571::1 (2001:470:5:571::1)
        0110 .... = Version: 6
            [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
        .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
            .... 0000 00.. .... .... .... .... .... = Differentiated Services Field: Default (0x00000000)
            .... .... ..0. .... .... .... .... .... = ECN-Capable Transport (ECT): Not set
            .... .... ...0 .... .... .... .... .... = ECN-CE: Not set
        .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
        Payload length: 40
        Next header: ICMPv6 (58)
        Hop limit: 115
        Source: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
        Destination: 2001:470:5:571::1 (2001:470:5:571::1)
        [Source GeoIP: Unknown]
        [Destination GeoIP: Unknown]
    Internet Control Message Protocol v6
        Type: Echo (ping) request (128)
        Code: 0
        Checksum: 0x7c97 [correct]
        Identifier: 0x0001
        Sequence: 78
        Data (32 bytes)

0000  61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0010  71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
            Data: 6162636465666768696a6b6c6d6e6f707172737475767761...
            [Length: 32]

ping -n 1 2001:470:4:571::2
Code: [Select]
Frame 7: 94 bytes on wire (752 bits), 94 bytes captured (752 bits) on interface 0
    Interface id: 0 (\Device\NPF_{47E1FFC6-CB08-4875-8C47-17A458D2A3E5})
    Encapsulation type: Ethernet (1)
    Arrival Time: Feb 14, 2015 18:03:57.291433000 Mitteleuropäische Zeit
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 1423933437.291433000 seconds
    [Time delta from previous captured frame: 0.144111000 seconds]
    [Time delta from previous displayed frame: 0.000000000 seconds]
    [Time since reference or first frame: 1.975848000 seconds]
    Frame Number: 7
    Frame Length: 94 bytes (752 bits)
    Capture Length: 94 bytes (752 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: eth:ethertype:ipv6:ipv6.nxt:icmpv6:data]
    [Coloring Rule Name: ICMP]
    [Coloring Rule String: icmp || icmpv6]
Ethernet II, Src: IntelCor_19:56:f3 (00:1c:c0:19:56:f3), Dst: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
    Destination: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        Address: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        Address: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv6 (0x86dd)
Internet Protocol Version 6, Src: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362), Dst: 2001:470:4:571::2 (2001:470:4:571::2)
    0110 .... = Version: 6
        [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
    .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
        .... 0000 00.. .... .... .... .... .... = Differentiated Services Field: Default (0x00000000)
        .... .... ..0. .... .... .... .... .... = ECN-Capable Transport (ECT): Not set
        .... .... ...0 .... .... .... .... .... = ECN-CE: Not set
    .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
    Payload length: 40
    Next header: ICMPv6 (58)
    Hop limit: 128
    Source: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
    Destination: 2001:470:4:571::2 (2001:470:4:571::2)
    [Source GeoIP: Unknown]
    [Destination GeoIP: Unknown]
Internet Control Message Protocol v6
    Type: Echo (ping) request (128)
    Code: 0
    Checksum: 0x7c96 [correct]
    Identifier: 0x0001
    Sequence: 79
    [No response seen]
        [Expert Info (Warn/Sequence): No response seen to ICMPv6 request in frame 7]
            [No response seen to ICMPv6 request in frame 7]
            [Severity level: Warn]
            [Group: Sequence]
    Data (32 bytes)

0000  61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0010  71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
        Data: 6162636465666768696a6b6c6d6e6f707172737475767761...
        [Length: 32]

Frame 14: 142 bytes on wire (1136 bits), 142 bytes captured (1136 bits) on interface 0
    Interface id: 0 (\Device\NPF_{47E1FFC6-CB08-4875-8C47-17A458D2A3E5})
    Encapsulation type: Ethernet (1)
    Arrival Time: Feb 14, 2015 18:03:57.564558000 Mitteleuropäische Zeit
    [Time shift for this packet: 0.000000000 seconds]
    Epoch Time: 1423933437.564558000 seconds
    [Time delta from previous captured frame: 0.060641000 seconds]
    [Time delta from previous displayed frame: 0.273125000 seconds]
    [Time since reference or first frame: 2.248973000 seconds]
    Frame Number: 14
    Frame Length: 142 bytes (1136 bits)
    Capture Length: 142 bytes (1136 bits)
    [Frame is marked: False]
    [Frame is ignored: False]
    [Protocols in frame: eth:ethertype:ipv6:ipv6.nxt:icmpv6:ipv6:ipv6.nxt:icmpv6:data]
    [Coloring Rule Name: ICMP errors]
    [Coloring Rule String: icmp.type eq 3 || icmp.type eq 4 || icmp.type eq 5 || icmp.type eq 11 || icmpv6.type eq 1 || icmpv6.type eq 2 || icmpv6.type eq 3 || icmpv6.type eq 4]
Ethernet II, Src: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15), Dst: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
    Destination: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        Address: IntelCor_19:56:f3 (00:1c:c0:19:56:f3)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Source: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        Address: AvmGmbh_39:0d:15 (9c:c7:a6:39:0d:15)
        .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
        .... ...0 .... .... .... .... = IG bit: Individual address (unicast)
    Type: IPv6 (0x86dd)
Internet Protocol Version 6, Src: 2001:470:0:8c::2 (2001:470:0:8c::2), Dst: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
    0110 .... = Version: 6
        [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
    .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
        .... 0000 00.. .... .... .... .... .... = Differentiated Services Field: Default (0x00000000)
        .... .... ..0. .... .... .... .... .... = ECN-Capable Transport (ECT): Not set
        .... .... ...0 .... .... .... .... .... = ECN-CE: Not set
    .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
    Payload length: 88
    Next header: ICMPv6 (58)
    Hop limit: 53
    Source: 2001:470:0:8c::2 (2001:470:0:8c::2)
    Destination: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
    [Source GeoIP: Unknown]
    [Destination GeoIP: Unknown]
Internet Control Message Protocol v6
    Type: Destination Unreachable (1)
    Code: 3 (Address unreachable)
    Checksum: 0x1107 [correct]
    Reserved: 00000000
    Internet Protocol Version 6, Src: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362), Dst: 2001:470:4:571::2 (2001:470:4:571::2)
        0110 .... = Version: 6
            [0110 .... = This field makes the filter "ip.version == 6" possible: 6]
        .... 0000 0000 .... .... .... .... .... = Traffic class: 0x00000000
            .... 0000 00.. .... .... .... .... .... = Differentiated Services Field: Default (0x00000000)
            .... .... ..0. .... .... .... .... .... = ECN-Capable Transport (ECT): Not set
            .... .... ...0 .... .... .... .... .... = ECN-CE: Not set
        .... .... .... 0000 0000 0000 0000 0000 = Flowlabel: 0x00000000
        Payload length: 40
        Next header: ICMPv6 (58)
        Hop limit: 115
        Source: 2001:4dd0:????:????:74f9:2fe:9bb:4362 (2001:4dd0:????:????:74f9:2fe:9bb:4362)
        Destination: 2001:470:4:571::2 (2001:470:4:571::2)
        [Source GeoIP: Unknown]
        [Destination GeoIP: Unknown]
    Internet Control Message Protocol v6
        Type: Echo (ping) request (128)
        Code: 0
        Checksum: 0x7c96 [correct]
        Identifier: 0x0001
        Sequence: 79
        Data (32 bytes)

0000  61 62 63 64 65 66 67 68 69 6a 6b 6c 6d 6e 6f 70   abcdefghijklmnop
0010  71 72 73 74 75 76 77 61 62 63 64 65 66 67 68 69   qrstuvwabcdefghi
            Data: 6162636465666768696a6b6c6d6e6f707172737475767761...
            [Length: 32]

PT
« Last Edit: February 15, 2015, 05:03:16 AM by PacketTracer »
Logged

FurryNutz

  • Poweruser
  •   ▲
    ▲ ▲
  • *****
  • Posts: 49923
  • D-Link Global Forum Moderator
    • Router Troubleshooting
Re: IPv6 server not reachable from host, however reachable from DIR-825
« Reply #14 on: March 03, 2015, 07:19:28 AM »

Any status on this?  ???

I am bringing up a HE tunnel to my home router Dlink DIR-825 Hardware Version: B1     Firmware Version: 2.09NA.
I have config all what i need with 6in4 tunnel configurations on my router.
I enabled ICMP to have IPv4 tunnel up. And I have IPv4 reachability to the HE IPv4 server
 I do ping6 tests  from my Dlink to the server IPv6 address and it works. However, when i try to ping the same IPv6 from my PC behind the router, it doesnt work.
my laptop gets the IPv6 address from the LAN i have assigned from HE and configured on my Dlink as well. I can succesfully ping to the LAN default gw from my laptop.
So the Ipv6 in ipv4 tunnel is up and running, but i could not reach the IPv6 HE server from my laptop behind my router.
I guess is something related to NAT/protocol 41. But i dont find out the way to have reachability to the HE IPv6 server from my laptop.
Does anyone knows whats happening? and how to solve it?
Logged
Cable: 1Gb/50Mb>NetGear CM1200>DIR-882>HP 24pt Gb Switch. COVR-1202/2202/3902,DIR-2660/80,3xDGL-4500s,DIR-LX1870,857,835,827,815,890L,880L,868L,836L,810L,685,657,3x655s,645,628,601,DNR-202L,DNS-345,DCS-933L,936L,960L and 8000LH.