@armbian blog not reachable from #IPv6 network:

$ curl -Iv https://blog.armbian.com/
* Host blog.armbian.com:443 was resolved.
* IPv6: 2a0a:4cc0:2000:34a5::1
* IPv4: 152.53.81.238
* Trying [2a0a:4cc0:2000:34a5::1]:443...
* connect to 2a0a:4cc0:2000:34a5::1 port 443 from 2605:a601:a63f:7c02:caa3:e8ff:fe76:98ff port 59006 failed: Permission denied
* Trying 152.53.81.238:443...
* Immediate connect fail for 152.53.81.238: Network is unreachable
* Failed to connect to blog.armbian.com port 443 after 42 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to blog.armbian.com port 443 after 42 ms: Could not connect to server

15 years ago this month I gave my first conference talk at Ohio LinuxFest on #IPv6.

Would anyone know if such a proxy service exists?

Not everyone has #IPv6 connectivity yet, and i think it would be an interesting service to use: Just set your website's A record to that IP and it automatically gets tunneled to your IPv6-only webserver! It could be an interesting service to host for VPS providers who have such v6-only VPS offerings. And it certainly help IPv6 adoption, especially since it makes loading such websites over IPv4 slower, creating incentive to deploy the good stuff.

I went to China for a few days last week, so here are some #IPv6 pics from the trip.

One is from the CM sim I got, the other is from a random wifi in a restaurant.

Hotel & TFU airport wifi only supported legacy IP.

FreeBSD 14.3-RELEASE-p3 on Lenovo ThinkPad T480 with XFCE.

- 5 Ghz WiFi working like a charm with iwlwifi and really good speeds
- System runs stable, reliably and snappy.

Very very well usable, even without wifibox yay 🙂

#freebsd #runbsd #wifi #networking #thinkpad #ipv6

If I use openresolv in place of resolvconf I don't run into the timing issue, but it has no notion of interface-order so it gleefully puts IPv4 resolvers ahead of #IPv6 with no apparent way to change this.

#IPv6 #FreeBSD

Seems I haven't configured vm-bhyve right for IPv6. Will need to sit down and have a think about this in order to get my personal Website and Gemini Capsule serving IPv6 traffic.

Probably over the Christmas holidays when I'm on leave (from both work and Scouts) and have spare brain cycles 😁

#freebsd #ipv6 #bhyve

Anyone remember WordPress?

Anyway, they are welcome #ipv6
https://meta.trac.wordpress.org/ticket/3090#comment:26

Idle #hamradio and #ipv6 rambling:

M17 encodes callsigns into a 48-bit address. ( https://m17project.org/m17-callsign-calculator/ ) This fits nicely within the 64-bit host portion of an IPv6 address. I suggest the top 16 bits could be a sentinel value to let an application know that the rest of the address is an encoded callsign. I propose 0x0073 to stay out of the top 8 bits where things like the locally-generated bit (EUI-64) are and, well, 73 for the ham reference.

eg, my bare callsign as a link-local address: fe80::73:0:2cd:5b06

I think this has some potential for use in AREDN-style mesh networks, especially now that they're using Babel which defaults to exchanging route information over link-local IPv6. It would reduce or eliminate the need for DNS, referring to resources by callsign and SSID or other extenders we're already used to. And this way a traceroute would contain readily useful information, removing the need to cross-reference a MAC or static address table.

@noahm @jima I first approached GitHub about their lack of #IPv6 support in March 2013. In that time they've added it to some of their ancillary offerings but never to the main site.

It has also become clear that their priorities have shifted, especially in the wake of the Microsoft acquisition. At this point I think the only viable solution is to https://giveupgithub.com/

git
tayga
make/gcc compiler
a NAT64 service running on your local network (Tayga/Jool)

Build the source

mkdir staging
cd staging
git clone https://github.com/apalrd/tayga.git
cd tayga
make
make install

Configuration file

cat /etc/tayga.conf
tun-device clat
ipv4-addr 192.0.0.2
ipv6-addr 2001:db8:feed::65
map 192.0.0.1 2001:db8:feed::64
prefix 64:ff9b::/96 # NAT64 prefix

Replace 2001:db8:feed with your /64 GUA prefix.
You can use Cloudflare's 2606:4700:4700::64 as the DNS4 resolver.

Configure Tayga

#!/usr/bin/env bash
echo 1 > /proc/sys/net/ipv6/conf/all/forwarding
echo 2 > /proc/sys/net/ipv6/conf/eth0/accept_ra
echo 1 > /proc/sys/net/ipv6/conf/eth0/proxy_ndp
ip neigh add proxy 2001:db8:feed::64 dev eth0
ip neigh add proxy 2001:db8:feed::65 dev eth0
tayga -c /etc/tayga.conf --mktun
ip link set dev clat up
ip addr add 192.0.0.1/29 dev clat
ip route add default dev clat mtu 1260
ip route add 2001:db8:feed::64/127 dev clat
tayga -c /etc/tayga.conf

root@skully:~# ip a s dev clat
5: clat: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 500
    link/none 
    inet 192.0.0.1/29 scope global clat
       valid_lft forever preferred_lft forever
    inet6 fe80::cbdf:afeb:7379:bd0a/64 scope link stable-privacy 
       valid_lft forever preferred_lft forever
root@skully:~# ping -c 3 1.1.1.1
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=13.0 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=16.6 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=13.7 ms
--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2004ms
rtt min/avg/max/mdev = 13.008/14.429/16.557/1.532 ms

#IPv6 #IPv6-only

I will note that some news services like CBC are unavailable unless you know French.

It felt zen not to read news 😁
- - -
Je noterai que certains services de nouvelles comme Radio-Canada étaient indisponibles à moins de connaître le français.

C’était très zen de ne pas lire l’actualité 😁

#IPv4 #IPv6 #IPv6Only

So, the answer: 1 day and 8 minutes.

Things got progressively worse as the day went on. This morning, I still had bidirectional messaging (SMS/MMS). Now, I can only receive messages, not send any (mobile service is unreliable at my place).

Also, I don’t have email anymore.
- - -
Donc, la réponse: 1 jour et 8 minutes.

Ça s’est détérioré au cours de la journée. Ce matin, j’avais encore les textos bidirectionnels. Maintenant, je ne pense que les recevoir, pas en envoyer.

#IPv4 #IPv6 #IPv6Only

@tschaefer Hard agree. And I think tools like IPvFoo create a natural nudge for at least some people. A colleague of mine installed it based on my recommendation and regularly reports seeing websites in a slightly different light, depending if there is a “green” 6 or a “red” 4. Despite he having no investment or involvement in #IPv6 beforehand. Install it now to never browse like before XD: https://github.com/pmarks-net/ipvfoo

I’m going to be running an experiment… I’ll turn off the archaic IPv4 stack on my home network.

No NAT64.

How long will I last?
- - -
Je vais faire une petite expérience… je vais désactiver l’archaïque pile IPv4 sur mon réseau domestique.

Pas de NAT64!

Combien de temps je vais l’endurer?

#IPv4 #IPv6 #IPv6Only

Any #hamradio folk want to try hacking AllStarLink to work over #IPv6 ?

In /etc/asterisk/iax.conf under [general] add a line:
bindaddr = [::]

I've successfully used DVSwitch Mobile with my node in this config.

Now for the untested part. I think if you add an entry for my node in rpt.conf as

1601 = radio@kekaha.home.nivex.net/47201,NONE

then you should be able to connect over IPv6. (Replace the 1601 with any number 1000-1999 you aren't using.)

I tried to use [::1] for a private node which didn't work, but ip6-localhost did, so it would seem as long as DNS resolves this should work.

The state of IPv6 by @altf4

https://media.ccc.de/v/why2025-246-the-state-of-ipv6

#IPv6