Pi4 not able to ping local systems using IPv6

[sunnyg]

.:Hi,

Hoping someone can help me out.

I have recently aquired a Rasberry Pi4, and I am enjoying it.

recently I have found an odd issue with it.

I am running a Windows domain at home, and have IPv6 enabled, and addresses being issued by DHCP.

All my windows systems are able to ping each other using the IPv6 address, however when I try to ping my raspberry pi over IPv6, no response is returned, additionally the raspberry pi cannot ping any of the windows systems over IPv6, it can however ping itself over IPv6.

I have confirmed in the DNS the ipv6 entries exist and nslookup see's these:

Code: Select all

root@newsreader:~# nslookup
> dc01
Server:         10.100.1.1
Address:        10.100.1.1#53

Name:   dc01.ghataura.net
Address: 10.100.1.1
Name:   dc01.ghataura.net
Address: 2607:fea8:28c0:2fe:9971:100e:c47c:a4d8
Name:   dc01.ghataura.net
Address: fd97:b9bb:57ba:33ce:fb5c:5471:f1b3:5830
Name:   dc01.ghataura.net
Address: fd97:b9bb:57ba:33ce:10:100:1:1
> newsreader
Server:         10.100.1.1
Address:        10.100.1.1#53

Name:   newsreader.ghataura.net
Address: 10.100.1.4
Name:   newsreader.ghataura.net
Address: fd97:b9bb:57ba:33ce:68cc:405e:ba52:5c9c
>

when I use ping6 I get no response:

Code: Select all

root@newsreader:~# ping6 dc01
PING dc01(DC01.ghataura.net (fd97:b9bb:57ba:33ce:10:100:1:1)) 56 data bytes
^C
--- dc01 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 117ms

root@newsreader:~#

Can anyone help me out ?

[stan_qaz]

You aren't using the mandatory -I (upper case letter i) ping option for link-local addresses.

-I interface
interface is either an address, or an interface name. If interface is an address, it sets source address to spec?
ified interface address. If interface in an interface name, it sets source interface to specified interface. For
IPv6, when doing ping to a link-local scope address, link specification (by the '%'-notation in destination, or by
this option) is required.


pi@pi-3bp-1:~ $ ping6 -I eth0 fe80::343c:6ebd:9342:5c81
PING fe80::343c:6ebd:9342:5c81(fe80::343c:6ebd:9342:5c81) from fe80::8d43:12be:4a7b:d97d%eth0 eth0: 56 data bytes
64 bytes from fe80::343c:6ebd:9342:5c81%eth0: icmp_seq=1 ttl=64 time=1.24 ms
64 bytes from fe80::343c:6ebd:9342:5c81%eth0: icmp_seq=2 ttl=64 time=0.655 ms
64 bytes from fe80::343c:6ebd:9342:5c81%eth0: icmp_seq=3 ttl=64 time=0.580 ms
^C
--- fe80::343c:6ebd:9342:5c81 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 0.580/0.825/1.240/0.295 ms

[sunnyg]

Issue has been resolved, a friend of mine looked over the settings and found that had missed 1 configuration in pfSense, after correcting the configuration the all systems are able to ping each other successfully.