Using ipv6 and Pi-Star 4.0.0.RC4?

All IP networking related issues
KA2Y
Posts: 25
Joined: Fri Apr 13, 2018 12:24 pm

Using ipv6 and Pi-Star 4.0.0.RC4?

Post by KA2Y » Sat Jun 01, 2019 8:31 pm

How can I accommodate ipv6 addressing on Pi-Star? My Router and ISP are configured for ipv4 and ipv6.

K0TI
Posts: 18
Joined: Mon Jan 21, 2019 6:36 am

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by K0TI » Sun Jun 02, 2019 2:20 am

It should just work. Have you checked with ifconfig to see if it has a ipv6 address ?

Code: Select all

[email protected](ro):~$ ifconfig

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.42  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 2601:446:600:10:63db:1207:5f41:c5c2  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::843f:e78c:9b78:787  prefixlen 64  scopeid 0x20<link>
        ether b8:27:eb:19:aa:52  txqueuelen 1000  (Ethernet)
        RX packets 350266  bytes 58315021 (55.6 MiB)
        RX errors 0  dropped 20  overruns 0  frame 0
        TX packets 257027  bytes 120828087 (115.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        
[email protected](ro):~$ sudo ping www.google.com
PING www.google.com(ord38s18-in-x04.1e100.net (2607:f8b0:4009:804::2004)) 56 data bytes
64 bytes from ord38s18-in-x04.1e100.net (2607:f8b0:4009:804::2004): icmp_seq=1 ttl=54 time=21.4 ms
64 bytes from ord38s18-in-x04.1e100.net (2607:f8b0:4009:804::2004): icmp_seq=2 ttl=54 time=26.4 ms
64 bytes from ord38s18-in-x04.1e100.net (2607:f8b0:4009:804::2004): icmp_seq=3 ttl=54 time=25.0 ms

Dan K0TI

KE7FNS
Posts: 243
Joined: Wed Apr 17, 2019 11:11 pm

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by KE7FNS » Tue Jun 11, 2019 8:53 pm

K0TI wrote:
Sun Jun 02, 2019 2:20 am
It should just work.
Not exactly, I'll bet its coming up with both an IPv4 and an IPv6 address, at which point its defaulting to using IPv4 addresses and routes.

K0TI
Posts: 18
Joined: Mon Jan 21, 2019 6:36 am

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by K0TI » Tue Jun 11, 2019 9:41 pm

Ok, perhaps. Mine has both address's and uses IPV6 (at least some times).
Maybe its not getting any IPv6 address's in response to DNS queries. So maybe it's more of a DNS issue

I not an expert at all IPv6. Just making observations.
Dan K0TI

KE7FNS
Posts: 243
Joined: Wed Apr 17, 2019 11:11 pm

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by KE7FNS » Wed Jun 12, 2019 2:55 am

K0TI wrote:
Tue Jun 11, 2019 9:41 pm
Ok, perhaps. Mine has both address's and uses IPV6 (at least some times).
Maybe its not getting any IPv6 address's in response to DNS queries. So maybe it's more of a DNS issue

I not an expert at all IPv6. Just making observations.
I dunno either, I've not messed with any of that. On mine my router is setup for IPv6 passthrough, and my Pi's have both IPv4 and IPv6 addresses, but it doesn't ever seen to use IPv6 when I ping addresses or anything. From what I can see most of the information out there with Pi's and IPv6 is how to disable it not enable it. lol.

AF6VN
Posts: 211
Joined: Fri Jul 20, 2018 1:15 am

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by AF6VN » Wed Jun 12, 2019 5:29 pm

KE7FNS wrote:
Wed Jun 12, 2019 2:55 am
I dunno either, I've not messed with any of that. On mine my router is setup for IPv6 passthrough, and my Pi's have both IPv4 and IPv6 addresses, but it doesn't ever seen to use IPv6 when I ping addresses or anything. From what I can see most of the information out there with Pi's and IPv6 is how to disable it not enable it. lol.
Did you try the option to /ping/ telling it to use IPV6 only?

--
AF6VN
Dennis L Bieber

KE7FNS
Posts: 243
Joined: Wed Apr 17, 2019 11:11 pm

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by KE7FNS » Wed Jun 12, 2019 6:44 pm

AF6VN wrote:
Wed Jun 12, 2019 5:29 pm
Did you try the option to /ping/ telling it to use IPV6 only?
yeah, only returns 100% packet loss

Code: Select all

icmp_seq=1 Destination unreachable: Beyond scope of source address
I don't really care t0o much about getting it to work or whatever, IPv4 works fine as it is.

AF6VN
Posts: 211
Joined: Fri Jul 20, 2018 1:15 am

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by AF6VN » Thu Jun 13, 2019 5:43 pm

Is that for LAN and WAN or only WAN targets? Does traceroute/tracert get anywhere before failing?

If you can ping LAN targets with IPV6 mode, but not WAN targets, then something in your router or ISP is blocking IPV6.

Interesting... my Pi-Star system -- 3.4.17 -- has separate ping and ping6 commands, AND does not have an IPV6 address on any interface (including loopback), and no address on eth0 since the box is only using WiFi.

My web-server (running Debian Stretch) does have IPV6 addresses, and uses "ping -6" option. IT can reach my desktop machine.

Code: Select all

[email protected]:~$ ping -6 ElusiveUnicorn
PING ElusiveUnicorn(ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42)) 56 data bytes
64 bytes from ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42): icmp_seq=1 ttl=64 time=1.31 ms
64 bytes from ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42): icmp_seq=2 ttl=64 time=0.617 ms
64 bytes from ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42): icmp_seq=3 ttl=64 time=0.516 ms
64 bytes from ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42): icmp_seq=4 ttl=64 time=0.611 ms
64 bytes from ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42): icmp_seq=5 ttl=64 time=0.541 ms
64 bytes from ElusiveUnicorn.attlocal.net (2600:1700:e630:890::42): icmp_seq=6 ttl=64 time=0.554 ms
^C
--- ElusiveUnicorn ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 0.516/0.692/1.318/0.283 ms
[email protected]:~$
No surprise that it can't reach the pi-star using IPV6 given mine doesn't have IPV6 addresses

Code: Select all

[email protected]:~$ ping -6 pi-star-3b
ping: pi-star-3b: Name or service not known

[email protected]versity:~$ ping -4 pi-star-3b
PING pi-star-3b.attlocal.net (192.168.1.79) 56(84) bytes of data.
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=1 ttl=64 time=6.07 ms
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=2 ttl=64 time=4.35 ms
64 bytes from pi-star-3b.attlocal.net (192.168.1.79): icmp_seq=3 ttl=64 time=2.69 ms
^C
--- pi-star-3b.attlocal.net ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 2.699/4.375/6.075/1.379 ms
[email protected]:~$
Interestingly -- my desktop can not ping the server machine on IPV6, and gets time outs on IPV4. Suspect that's firewall -- the server is pretty much locked down to just HTTP (port 80) and SSH

--
AF6VN
Dennis L Bieber

KE7FNS
Posts: 243
Joined: Wed Apr 17, 2019 11:11 pm

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by KE7FNS » Fri Jun 14, 2019 2:18 am

AF6VN wrote:
Thu Jun 13, 2019 5:43 pm
If you can ping LAN targets with IPV6 mode, but not WAN targets, then something in your router or ISP is blocking IPV6.
That might be what is going on at the ISP, but like I said it really makes no difference to me so its not really worth wasting time with.

User avatar
w7efs
Posts: 263
Joined: Sun Apr 22, 2018 4:26 pm

Re: Using ipv6 and Pi-Star 4.0.0.RC4?

Post by w7efs » Thu Jul 11, 2019 4:37 pm

AF6VN wrote:
Thu Jun 13, 2019 5:43 pm
...
No surprise that it can't reach the pi-star using IPV6 given mine doesn't have IPV6 addresses
...
Pi-Star v3.x has ipv6 disabled by default, v4.x has ipv6 enabled. If you want ipv6 on your v3.x then it's easy to enable it in the last line of /etc/sysctl.conf, just change the one "1" to a zero "0":

Code: Select all

...
# Turn off IPv6
#net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.all.disable_ipv6 = 0

Post Reply