Search results for tag #ipv6only
![[?]](https://ipv6.social/system/accounts/avatars/113/736/943/907/071/758/original/ddf07928182b3bda.jpeg)
![[?]](https://mstdn-media.moimeme.ca/accounts/avatars/112/839/198/878/411/686/original/5d2418cebf5a7279.png)
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é 😁
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.
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?
| <1 day/jour: | 0 |
| 1 day/jour – 1 week/semaine: | 0 |
| 1-2 weeks/semaines: | 0 |
| >2 weeks/semaines: | 0 |
![[?]](https://snac.void.my/madamada/s/avatar-db29b53530cce56ebd89a06f3456f9e4.png){kind=avatar}
![[?]](https://ipv6.social/system/accounts/avatars/109/264/914/124/733/601/original/d445ad99089fb700.jpg)
I bought a eSIM from Bouygues Telecom for travelers.
The default setting on Android for roaming (IPv4) was wrong. But after changing it to #IPv6 it works. Firewall settings seem a little bit strange (no ping, other ICMP packets are also blocked).
464xlat (clat) works.
My first SIM with 464xlat during roaming.
🙂
![[?]](https://ipv6.social/system/accounts/avatars/109/267/917/602/685/335/original/1cc9d1e32a1c6faa.jpg)
Thank you @Oskar456 for writing this DRAFT
https://www.ietf.org/archive/id/draft-caletka-aaaa-filtering-00.html
For the context: https://ripe90.ripe.net/archives/video/1639/
Tayga CLAT on FreeBSD 14.3-RELEASE with NDPROXY
CLAT as part of 464xlat as defined in RFC 6877 is meant to be running on an IPv6-only host.
The Setup
pkg install gmake gcc ndproxy-3.2.1403000_1
Get the tayga git repo
mkdir /root/staging ; cd /root/stagingPrepare tayga configuration
git clone https://github.com/apalrd/tayga.git
cd tayga
gmake
cp tayga /usr/local/bin/
mkdir /var/db/tayga
chown nobody:nobody /var/db/tayga
cat /etc/tayga.confReplace 2001:db8:1:1:: with your own IPv6 prefix. I am using my own NKP prefix here for NAT64. You can use one from here
tun-device clat0
ipv4-addr 192.0.0.2
ipv6-addr 2001:db8:1:1::65
#prefix 64:ff9b::/96 # Well-Known Prefix
prefix 2001:db8:64:64::/96 # Network-Known Prefix
data-dir /var/db/tayga
wkpf-strict no
map 192.0.0.1 2001:db8:1:1::64
log drop reject
Write a script to configure the clat0 interface and it's routes and save it as /root/bin/routes-clat.sh
#!/bin/shMake the script executable. Next setup tayga and ndproxy to start on boot..
ifconfig clat0 inet 192.0.0.1/29 192.0.0.1 up
ifconfig clat0 inet6 -ifdisabled
route add default -iface clat0
route -6n add 2001:db8:1:1::64/127 -iface clat0
cat /etc/rc.conf.localDownload the rc script for Tayga
# TAYGA (CLAT)
tayga_enable="YES"
tayga_interfaces="clat0"
# NDPROXY
ndproxy_enable="YES"
ndproxy_uplink_interface="vtnet0" # host interface
ndproxy_downlink_mac_address="xx:xx:xx" # host mac address
ndproxy_uplink_ipv6_addresses="fe80::xx:xx:xx" # gateway link-local address
ndproxyconf_exception_ipv6_addresses=""
curl -O https://buster.xpath.my/tayga/rc.d-tayga.txtNow that everything is in place, time to start and test it..
mv rc.d-tayga.txt /usr/local/etc/rc.d/tayga
chmod +x /usr/local/etc/rc.d/tayga
service tayga startTest with the ping command. Example output will look like this:
service ndproxy start
sysctl net.inet6.ip6.forwarding=1
sysrc ipv6_gateway_enable="YES"
ping -c3 1.1.1.1With curl:
PING 1.1.1.1 (1.1.1.1): 56 data bytes
64 bytes from 1.1.1.1: icmp_seq=0 ttl=37 time=216.021 ms
64 bytes from 1.1.1.1: icmp_seq=1 ttl=37 time=216.013 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=37 time=215.861 ms--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 215.861/215.965/216.021/0.073 ms
curl -kI https://8.8.8.8/NOTE: If you are using NAT64/PLAT address from nat64.net, some of them might block ICMP. If so test with curl instead. Latency-wise, it is better to run your own NAT64 or use one that is geo closer to you. You can either use #Jool or #Tayga for NAT64.
HTTP/2 302
x-content-type-options: nosniff
location: https://dns.google/
date: Sun, 22 Jun 2025 06:41:58 GMT
content-type: text/html; charset=UTF-8
server: HTTP server (unknown)
content-length: 216
x-xss-protection: 0
x-frame-options: SAMEORIGIN
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Please test and provide feedback. Thanks 🙂
There are 3 approaches to this .. the ndproxy approach, the NAT66 approach and the vnet jail approach. They all work depending on scenario..
I'll be doing some more tests just to catch any surprise cases that might pop up.. I'll maybe then write a simple guide to get this done all ways 🙂
[root@ipv6-only ~/staging]# ifconfig epair0b ; ifconfig clat0 ; ping -c 2 9.9.9.9#freebsd #ipv6 #ipv6only
epair0b: flags=1008843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,LOWER_UP> metric 0 mtu 1500
options=8<VLAN_MTU>
ether 02:a5:90:b5:02:0b
inet6 2400:8901:e002:7f70::111 prefixlen 64
inet6 fe80::a5:90ff:feb5:20b%epair0b prefixlen 64 scopeid 0x8
groups: epair
media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
clat0: flags=1008051<UP,POINTOPOINT,RUNNING,MULTICAST,LOWER_UP> metric 0 mtu 1260
options=4080000<LINKSTATE,MEXTPG>
inet 192.0.0.1 --> 192.0.0.1 netmask 0xfffffff8
inet6 fe80::447:4771:9888:4033%clat0 prefixlen 64 scopeid 0xe
groups: tun
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
Opened by PID 436
PING 9.9.9.9 (9.9.9.9): 56 data bytes
64 bytes from 9.9.9.9: icmp_seq=0 ttl=53 time=91.969 ms
64 bytes from 9.9.9.9: icmp_seq=1 ttl=53 time=91.193 ms--- 9.9.9.9 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 91.193/91.581/91.969/0.388 ms
breaking news
(I have to confess apple is sometimes good)
given a #IPv6only mobile access (like the Deutsche Telekom within Germany, not during roaming)
recent apple #iOS 18.5
makes
#IPv6mostly for clients via hotspot
#dhcpoption108 as well #pref64
I made also the windows test - in case option 108 is not provided by the client, iOS provides IPv4
Alt...
Wireshark captue showing RA with PREF64
Alt...
Wireshark capture
show dhcp 108 with time zero
If you can load the following domain, you have working IPv6 and a DNS resolver that has IPv6 support.
| Worked 🚀: | 68 |
| Did not work but have IPv6: | 7 |
Closed
"Swisscom’s mobile services deliver reliable and highly
secure coverage in Switzerland and internationally.
Among the two primary mobile services, voice and data,
Voice over LTE (VoLTE) already utilises IPv6. With the
introduction of a Dual Mode 5G Mobile Core in 2025,
we are laying the foundation to ensure that in 2026,
Swisscom’s entire mobile offerings will be either
IPv6-only or at least IPv6-first."
🙏