'/%3e%3cpath%20d='M50.3943%2022.237V39.5876H43.5185V22.7481C43.5185%2019.2029%2042.0411%2017.3949%2039.036%2017.3949C35.7325%2017.3949%2034.0778%2019.5338%2034.0778%2023.7585V32.9759H27.2434V23.7585C27.2434%2019.5338%2025.5857%2017.3949%2022.2822%2017.3949C19.2949%2017.3949%2017.8027%2019.2029%2017.8027%2022.7481V39.5876H10.9298V22.237C10.9298%2018.6918%2011.835%2015.8754%2013.6453%2013.7877C15.5128%2011.7049%2017.9623%2010.6355%2021.0028%2010.6355C24.522%2010.6355%2027.1813%2011.9885%2028.9542%2014.6917L30.665%2017.5633L32.3788%2014.6917C34.1517%2011.9885%2036.811%2010.6355%2040.3243%2010.6355C43.3619%2010.6355%2045.8114%2011.7049%2047.6847%2013.7877C49.4931%2015.8734%2050.3963%2018.6899%2050.3943%2022.237Z'%20fill='white'/%3e%3cdefs%3e%3clinearGradient%20id='paint0_linear_89_8'%20x1='30.5'%20y1='0'%20x2='30.5'%20y2='65'%20gradientUnits='userSpaceOnUse'%3e%3cstop%20stop-color='%236364FF'/%3e%3cstop%20offset='1'%20stop-color='%23563ACC'/%3e%3c/linearGradient%3e%3c/defs%3e%3c/svg%3e)
Marek Zarychta :antiverified:<p>For those who wonder what the Internet will look like in the post-IPv4 era. <br><a href="https://fosstodon.org/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://fosstodon.org/tags/ipv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6only</span></a> <a href="https://fosstodon.org/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://fosstodon.org/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a></p>
101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.
Administered by:
Server stats:
500active users
101010.pl: About · Status · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.4.0-alpha.5
#nat64
0 posts · 0 participants · 0 posts today
goetz 🚲<p>Configuring an <a href="https://chaos.social/tags/unbound" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unbound</span></a> DNS Server I learned that it has a <a href="https://chaos.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> mode.</p><p>Saved me from having to configure this server dual stacked to reach <a href="https://chaos.social/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4only</span></a> authoritative nameserver. </p><p>Looking at you <span class="h-card" translate="no"><a href="https://zdf.social/@ZDF" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ZDF</span></a></span>!</p><p><a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> </p><p><a href="https://chaos.social/tags/HowIPv6HelpedMeThisWeek" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HowIPv6HelpedMeThisWeek</span></a></p>
Felix Palmen :freebsd: :c64:<p>I just added <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> support to <a href="https://mastodon.bsd.cafe/tags/swad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>swad</span></a>. Really helps with readability of my logs here ... 😎 <br><a href="https://github.com/Zirias/swad/commit/730923ad55f4ff43f434bc1d885ad12b0d2860ee" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/Zirias/swad/commit/</span><span class="invisible">730923ad55f4ff43f434bc1d885ad12b0d2860ee</span></a></p>
BoxyBSD<p>We’re soon starting our free load balancing service!</p><p>Still in beta, everything seems to work as expected and sounds like it’s time to move into a stable service. This service allows you to make your website reachable by IPv4, even your box is only available by <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a>. Just like our <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> service, this should make your life easier on the IPv6 only site!</p><p>Thanks to <span class="h-card" translate="no"><a href="https://mastodon.gyptazy.com/@gyptazy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gyptazy</span></a></span> for implementing this service and providing additional IPv4 addresses. <a href="https://mastodon.bsd.cafe/tags/RUNBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RUNBSD</span></a></p>
Pure Acetone<p>BSD Router Project - дистрибутив предназначен для создания компактных программных маршрутизаторов, поддерживающих протоколы маршрутизации RIP, OSPF, BGP и PIM. Управление производится в режиме командной строки через CLI-интерфейс, напоминающий интерфейс Cisco IOS. Дистрибутив доступен в сборках для архитектуры x86_64 (размер установочного образа 190 МБ).<br>Основные характеристики дистрибутива:<br>В комплект входят два пакета с реализацией протоколов маршрутизации: FRRouting (форк Quagga) с поддержкой BGP, RIP, RIPng (IPv6), OSPF v2, OSPF v3 (IPv6), ISIS и BIRD с поддержкой BGP, RIP, RIPng (IPv6), OSPF v2 и OSPF v3 (IPv6).<br>Дистрибутив адаптирован для параллельного использования нескольких обособленных таблиц маршрутизации (FIB), привязанных к реальным и виртуальным интерфейсам.<br>Для мониторинга и управления может использоваться SNMP (bsnmp-ucd).<br>Поддерживается экспорт данных о трафике в форме потоков Netflow.<br>Для оценки производительности сети в состав входят утилиты NetPIPE, iperf, netblast, netsend и netreceive. Для накопления статистики о трафике используется ng_netflow.<br>Поддержка создания отказоустойчивых маршрутизаторов из двух серверов - в штатном режиме нагрузка может быть распределена на оба сервера, но в случае сбоя первый маршрутизатор может взять на себя нагрузку второго, а второй - первого (применяется привязка к активному серверу виртуального MAC-адреса). Реализация основана на использовании протоколов VRRP (Virtual Router Redundancy Protocol) и CARP (Common Address Redundancy Protocol), реализованный при помощи пакета ucarp.<br>Поддержка PPTP, PPPoE и L2TP при помощи mpd (Multi-link PPP daemon).<br>Поддержка ограничения пропускной способности при помощи IPFW + dummynet или ng_car.<br>Для Ethernet поддерживается работа с VLAN (802.1q), агрегация линков и использование сетевых мостов (802.1w, Rapid Spanning Tree Protocol).<br>Для мониторинга применяется пакет monit.<br>Поддержка VPN: GRE, GIF, IPSec (IKEv1 и IKEv2 со strongswan), OpenVPN и Wireguard.<br>Поддержка NAT64 с использованием демона tayga и встроенная поддержка туннелей IPv6-to-IPv4.<br>Возможность установки дополнительных программ, используя пакетный менеджер pkgng.<br>Использование в качестве DHCP-сервера dnsmasq, а в качестве агента доставки почты - ssmtp.<br>Поддержка управления через SSH, последовательный порт, telnet и локальную консоль. Для упрощения администрирования в комплект входит утилита tmux (BSD-аналог screen).<br>Загрузочные образы сгенерированы на основе FreeBSD при помощи скриптов из NanoBSD.<br>Механизм обновления системы основывается на создании двух разделов на Flash-накопителе: новая версия загружается во второй раздел, который после перезагрузки становится активным, а другой раздел ожидает появления очередного обновления (разделы меняются местами). В случае выявления проблем с установленным обновлением возможен откат на прошлое состояние системы.<br>Для проверки целостности системы для каждого файла сохраняется контрольная сумма sha256.</p><p><a href="https://qoto.org/tags/BSDRouterProject" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSDRouterProject</span></a> <a href="https://qoto.org/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://qoto.org/tags/Routing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Routing</span></a> <a href="https://qoto.org/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Networking</span></a> <a href="https://qoto.org/tags/OSPF" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OSPF</span></a> <a href="https://qoto.org/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BGP</span></a> <a href="https://qoto.org/tags/VRRP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VRRP</span></a> <a href="https://qoto.org/tags/Firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Firewall</span></a> <a href="https://qoto.org/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> <a href="https://qoto.org/tags/OpenVPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenVPN</span></a> <a href="https://qoto.org/tags/Wireguard" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wireguard</span></a> <a href="https://qoto.org/tags/NetFlow" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetFlow</span></a> <a href="https://qoto.org/tags/CLI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLI</span></a> <a href="https://qoto.org/tags/CompactRouter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CompactRouter</span></a> <a href="https://qoto.org/tags/NanoBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NanoBSD</span></a> <a href="https://qoto.org/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://qoto.org/tags/SNMP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SNMP</span></a> <a href="https://qoto.org/tags/L2TP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>L2TP</span></a> <a href="https://qoto.org/tags/ipsec" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipsec</span></a> </p><p><a href="https://pocketnet.app/pureaceton?ref=PDQmXtWJfd8f6fMtwaxzCuqvLpoN3KbS4o" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">pocketnet.app/pureaceton?ref=P</span><span class="invisible">DQmXtWJfd8f6fMtwaxzCuqvLpoN3KbS4o</span></a></p>
BoxyBSD<p>The <a href="https://mastodon.bsd.cafe/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BoxyBSD</span></a> project is taking a pause from provisioning completely free <a href="https://mastodon.bsd.cafe/tags/vps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vps</span></a> instances / <a href="https://mastodon.bsd.cafe/tags/vserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vserver</span></a>. For further questions, reach out to <span class="h-card" translate="no"><a href="https://mastodon.gyptazy.com/@gyptazy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gyptazy</span></a></span> or in our Matrix chat.</p><p>After publishing the new self-service portal and making it easier to use and get a free VPS instance, we got a lot more new users who requested an instance than usual. We’re not out of resources but we want to provide a great and reliable service and have a buffer for upcoming things. </p><p>We’re already restocking the resources and adding new nodes to the project but temporary stop provisioning new instances. In the meantime, we will provide new services that will make the overall experience for users much better and easier.</p><p>We already started this with the new <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> gateways and the new free <a href="https://mastodon.bsd.cafe/tags/loadbalancing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loadbalancing</span></a> service that allows you to serve your website also on <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a>, even your box is <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> only.</p><p>We’re addicted to the <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a> community and hope to provide your quickly more <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetBSD</span></a>, <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a>, <a href="https://mastodon.bsd.cafe/tags/DragonflyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DragonflyBSD</span></a> and all the other bsd based systems again. In the meantime - have fun and <a href="https://mastodon.bsd.cafe/tags/RUNBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RUNBSD</span></a> </p><p><a href="https://mastodon.bsd.cafe/tags/free" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>free</span></a> <a href="https://mastodon.bsd.cafe/tags/hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hosting</span></a> <a href="https://mastodon.bsd.cafe/tags/bhyve" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bhyve</span></a> <a href="https://mastodon.bsd.cafe/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zfs</span></a> <a href="https://mastodon.bsd.cafe/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firewall</span></a> <a href="https://mastodon.bsd.cafe/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.bsd.cafe/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> <a href="https://mastodon.bsd.cafe/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.bsd.cafe/tags/fediverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>fediverse</span></a> <a href="https://mastodon.bsd.cafe/tags/services" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>services</span></a></p>
BoxyBSD<p>We just added a free <a href="https://mastodon.bsd.cafe/tags/loadbalancing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>loadbalancing</span></a> service to <a href="https://mastodon.bsd.cafe/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BoxyBSD</span></a>!</p><p>This new feature got added by <span class="h-card" translate="no"><a href="https://mastodon.gyptazy.com/@gyptazy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gyptazy</span></a></span> in addition to the newly introduced <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> gateways to make your life easier and is currently tested with a few users! This provides you the ability to make your website also reachable by <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> even your box is only running on <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a>. This feature can be managed from your self-service portal and simply requires you to add a DNS name that should be balanced and to point the DNS A record to a given IPv4.</p><p>Making the legacy internet life easier, we hope for a higher <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a> adaption where people might be more motivated to try <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a>, <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetBSD</span></a>, <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> or even <a href="https://mastodon.bsd.cafe/tags/opensolaris" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensolaris</span></a> with <a href="https://mastodon.bsd.cafe/tags/illumos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>illumos</span></a>.</p><p><a href="https://mastodon.bsd.cafe/tags/hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hosting</span></a> <a href="https://mastodon.bsd.cafe/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <a href="https://mastodon.bsd.cafe/tags/runbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>runbsd</span></a> <a href="https://mastodon.bsd.cafe/tags/hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hosting</span></a> <a href="https://mastodon.bsd.cafe/tags/free" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>free</span></a> <a href="https://mastodon.bsd.cafe/tags/service" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>service</span></a> <a href="https://mastodon.bsd.cafe/tags/saas" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>saas</span></a> <a href="https://mastodon.bsd.cafe/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> <a href="https://mastodon.bsd.cafe/tags/vps" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vps</span></a> <a href="https://mastodon.bsd.cafe/tags/vserver" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vserver</span></a> <a href="https://mastodon.bsd.cafe/tags/server" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>server</span></a> <a href="https://mastodon.bsd.cafe/tags/vm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vm</span></a></p>
gyptazy<p>I got asked if I could create a <a href="https://mastodon.gyptazy.com/tags/howto" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>howto</span></a> for creating a (public) <a href="https://mastodon.gyptazy.com/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> service - just like I did recently for <a href="https://mastodon.gyptazy.com/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BoxyBSD</span></a>. With <a href="https://mastodon.gyptazy.com/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> and <a href="https://mastodon.gyptazy.com/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> you can also reach resource in the legacy internet (<a href="https://mastodon.gyptazy.com/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a>) on <a href="https://mastodon.gyptazy.com/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> only systems.</p><p>While this is based on <a href="https://mastodon.gyptazy.com/tags/unbound" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>unbound</span></a> and <a href="https://mastodon.gyptazy.com/tags/tayga" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tayga</span></a>, there’s also a solution by using the <a href="https://mastodon.gyptazy.com/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a>'s native way which is also running on the other gateway. I’ll share a second how to how to do this in OpenBSD and pf.</p><p><a href="https://gyptazy.com/howto-create-a-public-dns64-nat64-gateway/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">gyptazy.com/howto-create-a-pub</span><span class="invisible">lic-dns64-nat64-gateway/</span></a></p>
BoxyBSD<p>This weekend we started to integrate the NAT64 support for our free VPS infrastructure to make your life easier. Stay tuned, the global rollout is near :)</p><p><a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NetBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BoxyBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.bsd.cafe/tags/Hosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hosting</span></a> <a href="https://mastodon.bsd.cafe/tags/Provider" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Provider</span></a> <a href="https://mastodon.bsd.cafe/tags/BGP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BGP</span></a> <a href="https://mastodon.bsd.cafe/tags/Free" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Free</span></a> <a href="https://mastodon.bsd.cafe/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Opensource</span></a> <a href="https://mastodon.bsd.cafe/tags/community" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>community</span></a> <a href="https://mastodon.bsd.cafe/tags/VPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VPS</span></a> <a href="https://mastodon.bsd.cafe/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> <a href="https://mastodon.bsd.cafe/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <span class="h-card" translate="no"><a href="https://mastodon.gyptazy.com/@gyptazy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>gyptazy</span></a></span></p>
iam-py-test :unverified:<p>uBlock Origin 1.60.1b16 fixes an issue where connections on IPv6-only networks which used NAT64 would falsely be detected as connections to LAN (Local Area Network) IP addresses. This is the only change in that release.</p><p>Issue report: <a href="https://github.com/uBlockOrigin/uBlock-issues/issues/3426" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/uBlockOrigin/uBlock</span><span class="invisible">-issues/issues/3426</span></a><br>Commit: <a href="https://github.com/gorhill/uBlock/commit/2621c908c31b70a983dacf5482600c116ee35102" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">github.com/gorhill/uBlock/comm</span><span class="invisible">it/2621c908c31b70a983dacf5482600c116ee35102</span></a></p><p>On NAT64:</p><blockquote><p>the primary purpose of NAT64 is to allow an IPv6-only client to initiate communications to an IPv4-only server</p></blockquote><p><a href="https://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/217208-understanding-nat64-and-its-configuratio.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">cisco.com/c/en/us/support/docs</span><span class="invisible">/ip/network-address-translation-nat/217208-understanding-nat64-and-its-configuratio.html</span></a></p><p>The issue here was that <code>64:ff9b::/96</code> was treated as LAN addresses. However, this is reserved for NAT64 in RFC6052:</p><blockquote><p>This document reserves a "Well-Known Prefix" for use in an algorithmic mapping. The value of this IPv6 prefix is: 64:ff9b::/96</p></blockquote><p>Behind CloudFlare: <code>https://www.rfc-editor.org/rfc/rfc6052</code></p><p><a href="https://infosec.exchange/tags/uBlockOrigin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uBlockOrigin</span></a> <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://infosec.exchange/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a></p>
Felix Palmen :freebsd: :c64:<p><a href="https://mastodon.bsd.cafe/tags/TIL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TIL</span></a>: On an <a href="https://mastodon.bsd.cafe/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6only</span></a> host, <a href="https://mastodon.bsd.cafe/tags/chromium" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>chromium</span></a> obviously applies quite some "magic" (detect there's no <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> connectivity, detect the <a href="https://mastodon.bsd.cafe/tags/prefix" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>prefix</span></a> used for <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a>) and, when presented with a literal IPv4 address, does the request using <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> 🧐</p>
Felix Palmen :freebsd: :c64:<p>Ok I guess I'll have to give up again quite quickly 😦 </p><p><a href="https://mastodon.bsd.cafe/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> <a href="https://mastodon.bsd.cafe/tags/Teams" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Teams</span></a> is broken for me as soon as I disable <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a>. From what I could understand in this horrible mess of a "web app", the reason is probably some <a href="https://mastodon.bsd.cafe/tags/CORS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CORS</span></a> error. I have no idea how that could ever be related to <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> or <a href="https://mastodon.bsd.cafe/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> or anything. Tried temporarily disabling <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> (to force direct v6 connections), tried adding all of Microsofts v6 networks to the "exclude" option of bind9 to have everything pass <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> *avoiding* native IPv6, tried several ways to disable CORS, nothing helped. 🤬 </p><p>Anyone know about these issues with teams?</p><p>edit: to clarify, "everything" seems to work except for the main purpose: join an actual call ...</p>
Felix Palmen :freebsd: :c64:<p>Maybe it *is* about time to go <a href="https://mastodon.bsd.cafe/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6only</span></a>. Currently running my desktop without <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> for testing.</p><p>The outside <a href="https://mastodon.bsd.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> world is reachable with <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> provided by <a href="https://mastodon.bsd.cafe/tags/tayga" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tayga</span></a> running on my <a href="https://mastodon.bsd.cafe/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FreeBSD</span></a> router/firewall (with pf for stateful <a href="https://mastodon.bsd.cafe/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> and actual firewalling), great! That's the most important part, I mean, nothing we can do about stubbornly operated v4-only stuff outside.</p><p>Now I identify all the stuff still not offering <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> in my home network. Already fixed parts of my mail system and my irssi-proxy (for IRC). But there's more to check ... none of my VPN tunnels currently transport v6 ... and I'm still a bit unsure about all the devices (e.g. switch and access points in my management segment, or stuff like a vacuum robot or a kitchen radio in my IoT segment ... oh boy 😂🙈)</p>
Stefano Marinelli<p>Yesterday I used nat64.net and everything was already working, but I wanted to do it all locally. So, I tried setting up a VLAN with only IPv6, using NAT64 and DNS64. I installed an OpenBSD VM on bhyve, mapped the ethernet ports, and configured unbound, pf, and rad in just three minutes - everything works. Without using any external packages.</p><p>The simplicity and completeness of OpenBSD and its base system is always a source of joy.</p><p><a href="https://mastodon.bsd.cafe/tags/OpenBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.bsd.cafe/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> <a href="https://mastodon.bsd.cafe/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> <a href="https://mastodon.bsd.cafe/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Networking</span></a> <a href="https://mastodon.bsd.cafe/tags/VLAN" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VLAN</span></a> <a href="https://mastodon.bsd.cafe/tags/SysAdmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SysAdmin</span></a> <a href="https://mastodon.bsd.cafe/tags/RunBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RunBSD</span></a> <a href="https://mastodon.bsd.cafe/tags/BSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BSD</span></a></p>
🌈 Kerblambuli 🦄<p>Alright <a href="https://chaos.social/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> and <a href="https://chaos.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> finally have been set up on my journey to <a href="https://chaos.social/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6mostly</span></a> ;c)</p><p>How it works: either dual stack or <a href="https://chaos.social/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6only</span></a> clients ask the DNS server running on my firewall for name resolution; if there exist only IPv4 answers (A records) upstream the DNS64 kicks in and synthesizes IPv6 (<a href="https://chaos.social/tags/AAAA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AAAA</span></a> records) using a special v6 subnet. Then my clients try to connect to those fake v6 addresses and the NAT64 translates v6 back to v4 transparently.</p><p>This forces clients to *use* IPv6 only. 🤤</p>
Antonis Chariton<p>I've tried to summarize the current state of the art for IPv6-First and IPv6-Only Access Networks in my blog post here: <a href="https://blog.daknob.net/do-you-really-need-ipv4-anymore/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.daknob.net/do-you-really-</span><span class="invisible">need-ipv4-anymore/</span></a></p><p>Let me know how it went for you, what problems you may have ran into, and whether something is missing! I'm also happy to answer questions or help with ideas.</p><p><a href="https://mastodon.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> <a href="https://mastodon.social/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> <a href="https://mastodon.social/tags/PREF64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PREF64</span></a> <a href="https://mastodon.social/tags/464XLAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>464XLAT</span></a> <a href="https://mastodon.social/tags/SIIT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SIIT</span></a> <a href="https://mastodon.social/tags/Option108" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Option108</span></a></p>
Colin Cogle :verified:<p>Rejoice, network operators. Windows 11 will be joining the rest of the world soon in supporting CLAT, <a href="https://mastodon.colincogle.name/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a>, and <a href="https://mastodon.colincogle.name/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> natively. (Currently, CLAT only works on cellular connections.)</p><p>Supporting two IP versions has been a pain we’ve had to live with for over a decade, but this will allow network operators to forcibly disable clients’ IPv4 stacks via DHCP/RA, finish <a href="https://mastodon.colincogle.name/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> switchovers, and run true <a href="https://mastodon.colincogle.name/tags/IPv6mostly" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6mostly</span></a> or <a href="https://mastodon.colincogle.name/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6only</span></a> networks.</p><p>We’re one big step closer to killing “legacy IP” for good. :ipv6: </p><p><a href="https://techcommunity.microsoft.com/t5/networking-blog/windows-11-plans-to-expand-clat-support/ba-p/4078173" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">techcommunity.microsoft.com/t5</span><span class="invisible">/networking-blog/windows-11-plans-to-expand-clat-support/ba-p/4078173</span></a></p>
Litchralee_v6<p>Anyone have any ideas for squeezing a <a href="https://ipv6.social/tags/CLAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLAT</span></a> into a container? My <a href="https://ipv6.social/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>homelab</span></a> <a href="https://ipv6.social/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>k8s</span></a> cluster is IPv6-only, and I've discovered this evening that steamcmd is not even asking for AAAA records, meaning my <a href="https://ipv6.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> and <a href="https://ipv6.social/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> setup is not effective here. I am not going to dual-stack the whole cluster network just to host one game server, so I'm looking for container-ed options.</p><p>IIRC, a requirement for CLAT is being able to carve out a /96 for translation, but k8s assigns a single <a href="https://ipv6.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> per pod...</p>
Litchralee_v6<p>Introductory post: this is my public sub-account for <a href="https://ipv6.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> content; my main account is linked in my profile.</p><p>I support the complete roll-out of IPv6, including intermediate efforts like dual-stack support and <a href="https://ipv6.social/tags/NAT64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT64</span></a> <a href="https://ipv6.social/tags/DNS64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNS64</span></a> <a href="https://ipv6.social/tags/CLAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CLAT</span></a>, with the ultimate goal of native IPv6 support in all-new deployments, using RFC standards and best practices.</p><p>I support subnets no smaller than /64 (<a href="https://ipv6.social/tags/SLAAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SLAAC</span></a>), ISPs should delegate prefixes of at least /56 or /48, and <a href="https://ipv6.social/tags/ICMPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ICMPv6</span></a> should be rate-limited, never blocked.</p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/ripe86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ripe86</span></a> <a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://ipv6.social/tags/tutorial" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tutorial</span></a> <a href="https://ipv6.social/tags/ipv6basics" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6basics</span></a> <a href="https://ipv6.social/tags/ipv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6only</span></a> <br><a href="https://ipv6.social/tags/ipv6transition" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6transition</span></a> <a href="https://ipv6.social/tags/dualstack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dualstack</span></a> <a href="https://ipv6.social/tags/uptodate" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>uptodate</span></a> <a href="https://ipv6.social/tags/nat64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>nat64</span></a> <a href="https://ipv6.social/tags/464xlat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>464xlat</span></a> <a href="https://ipv6.social/tags/dslite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>dslite</span></a> <br><a href="https://ipv6.social/tags/video" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>video</span></a> <br><a href="https://ripe86.ripe.net/archives/video/993/" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ripe86.ripe.net/archives/video</span><span class="invisible">/993/</span></a><br><a href="https://ipv6.social/tags/pdf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pdf</span></a> <br><a href="https://ripe86.ripe.net/presentations/33-RIPE86-IPv6-Tutorial.pdf" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ripe86.ripe.net/presentations/</span><span class="invisible">33-RIPE86-IPv6-Tutorial.pdf</span></a></p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload