Business Community > Routers > I can't ping a device with IPv6 from another VLAN
< Routers

I can't ping a device with IPv6 from another VLAN

I can't ping a device with IPv6 from another VLAN

I can't ping a device with IPv6 from another VLAN
I can't ping a device with IPv6 from another VLAN
2024-11-11 17:15:30 - last edited 2024-11-15 00:54:24
Tags: #VLAN & Multi-Networks
Model: ER605 (TL-R605)   SG2428LP  
Hardware Version: V2
Firmware Version: 2.2.6 Build 20240718 Rel.82712

Hello. I have the following VLANs in my network:

 

When I try to ping my local DNS server using the IPv6 address (PCs50 -> LAN1), I get the error: 'Destination host unreachable.'

There are no issues when using IPv4.

 

 

Everything works correctly when my devices and DNS servers are in the same VLAN.

 

However, I want to separate the computers in my network from the DNS servers.

 

I would appreciate any help.

  0      
 
  0      
 
#1
Options
1 Accepted Solution
Re:I can't ping a device with IPv6 from another VLAN-Solution
2024-11-13 01:22:48 - last edited 2024-11-15 00:54:24

Hi @Sefinek 

Thanks for posting in our business forum.

Sefinek wrote

Hi @Clive_A 

 

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f4:39:09:4c:39:43 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.135/24 metric 100 brd 192.168.0.255 scope global enp1s0
       valid_lft forever preferred_lft forever
    inet6 2a01:11bf:4400:4155:f639:9ff:fe4c:3943/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 86171sec preferred_lft 14171sec
    inet6 fe80::f639:9ff:fe4c:3943/64 scope link
       valid_lft forever preferred_lft forever

 

PowerShell 7.4.6
PS C:\Users\Sefinek> ping 2a01:11bf:4400:4155:f639:9ff:fe4c:3943

Pinging 2a01:11bf:4400:4155:f639:9ff:fe4c:3943 with 32 bytes of data:
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms

Ping statistics for 2a01:11bf:4400:4155:f639:9ff:fe4c:3943:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
PS C:\Users\Sefinek> ping fe80::f639:9ff:fe4c:3943

Pinging fe80::f639:9ff:fe4c:3943 with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for fe80::f639:9ff:fe4c:3943:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

I used 2a01:11bf:4400:4155:f639:9ff:fe4c:3943, and it works. However, i'm not sure if this is the right way to do it

 

Thanks!

Based on the given information, it seems to be the firewall or the settings on your LINUX.

IPv6 at least so far based on the given tests.

If the link-local does not work, more like a problem with the devices involved in this test.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  1  
  1  
#5
Options
4 Reply
Re:I can't ping a device with IPv6 from another VLAN
2024-11-12 01:04:58

Hi @Sefinek 

Thanks for posting in our business forum.

What are the prints of the mentioned devices' v6 addresses?

What's your interface like?

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
  0  
  0  
#2
Options
Re:I can't ping a device with IPv6 from another VLAN
2024-11-12 13:46:52

Hi @Clive_A 

 

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f4:39:09:4c:39:43 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.135/24 metric 100 brd 192.168.0.255 scope global enp1s0
       valid_lft forever preferred_lft forever
    inet6 2a01:11bf:4400:4155:f639:9ff:fe4c:3943/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 86171sec preferred_lft 14171sec
    inet6 fe80::f639:9ff:fe4c:3943/64 scope link
       valid_lft forever preferred_lft forever

 

PowerShell 7.4.6
PS C:\Users\Sefinek> ping 2a01:11bf:4400:4155:f639:9ff:fe4c:3943

Pinging 2a01:11bf:4400:4155:f639:9ff:fe4c:3943 with 32 bytes of data:
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms

Ping statistics for 2a01:11bf:4400:4155:f639:9ff:fe4c:3943:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
PS C:\Users\Sefinek> ping fe80::f639:9ff:fe4c:3943

Pinging fe80::f639:9ff:fe4c:3943 with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for fe80::f639:9ff:fe4c:3943:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

I used 2a01:11bf:4400:4155:f639:9ff:fe4c:3943, and it works. However, i'm not sure if this is the right way to do it

 

Thanks!

  0  
  0  
#3
Options
Re:I can't ping a device with IPv6 from another VLAN
2024-11-12 13:47:18

screenshot

  0  
  0  
#4
Options
Re:I can't ping a device with IPv6 from another VLAN-Solution
2024-11-13 01:22:48 - last edited 2024-11-15 00:54:24

Hi @Sefinek 

Thanks for posting in our business forum.

Sefinek wrote

Hi @Clive_A 

 

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether f4:39:09:4c:39:43 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.135/24 metric 100 brd 192.168.0.255 scope global enp1s0
       valid_lft forever preferred_lft forever
    inet6 2a01:11bf:4400:4155:f639:9ff:fe4c:3943/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 86171sec preferred_lft 14171sec
    inet6 fe80::f639:9ff:fe4c:3943/64 scope link
       valid_lft forever preferred_lft forever

 

PowerShell 7.4.6
PS C:\Users\Sefinek> ping 2a01:11bf:4400:4155:f639:9ff:fe4c:3943

Pinging 2a01:11bf:4400:4155:f639:9ff:fe4c:3943 with 32 bytes of data:
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms
Reply from 2a01:11bf:4400:4155:f639:9ff:fe4c:3943: time=1ms

Ping statistics for 2a01:11bf:4400:4155:f639:9ff:fe4c:3943:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 1ms, Average = 1ms
PS C:\Users\Sefinek> ping fe80::f639:9ff:fe4c:3943

Pinging fe80::f639:9ff:fe4c:3943 with 32 bytes of data:
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.
Destination host unreachable.

Ping statistics for fe80::f639:9ff:fe4c:3943:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

 

I used 2a01:11bf:4400:4155:f639:9ff:fe4c:3943, and it works. However, i'm not sure if this is the right way to do it

 

Thanks!

Based on the given information, it seems to be the firewall or the settings on your LINUX.

IPv6 at least so far based on the given tests.

If the link-local does not work, more like a problem with the devices involved in this test.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update! ☛Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  1  
  1  
#5
Options

Information

Helpful: 0

Views: 185

Replies: 4

Tags

VLAN & Multi-Networks
Related Articles
Can't ping from a vlan to main lan but other services work (ssh)
157 0
Can't access web managment from other VLAN, but can ping?
3911 16
How to connect to Sonos and GoogleTV on another VLAN?
1332 0
VLAN Trouble - Devices can't talk to each other
192 0
 OpenVPN - Can't route to another VLAN
769 0
ER7212PC VLAN - unable to ping each other (via wired)
685 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.