Med-Mastodon

18 posts9 participants1 post today

gyptazyWhat do you guys do with your left-over (public) IPv4 addresses? And no, that’s meant for real :)<a href="https://mastodon.gyptazy.com/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#network</a> <a href="https://mastodon.gyptazy.com/tags/ISP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ISP</a> <a href="https://mastodon.gyptazy.com/tags/hosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#hosting</a> <a href="https://mastodon.gyptazy.com/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#homelab</a> <a href="https://mastodon.gyptazy.com/tags/Ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ipv6</a> <a href="https://mastodon.gyptazy.com/tags/bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bgp</a> <a href="https://mastodon.gyptazy.com/tags/peering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#peering</a>

Thomas Schäfer<a href="https://aws.amazon.com/about-aws/whats-new/2025/04/aws-lambda-inbound-ipv6-connectivity-aws-privatelink/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://aws.amazon.com/about-aws/whats-new/2025/04/aws-lambda-inbound-ipv6-connectivity-aws-privatelink/</a><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://ipv6.social/tags/ipv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6only</a> <a href="https://ipv6.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a>

Thomas Schäfer<a href="https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-memorydb-supports-ipv6/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://aws.amazon.com/about-aws/whats-new/2025/04/amazon-memorydb-supports-ipv6/</a><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://ipv6.social/tags/ipv6only" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6only</a> <a href="https://ipv6.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a>

Jima :Compromise_bi_flag:And another <a href="https://mspsocial.net/tags/HowIPv6HelpedMeThisWeek" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HowIPv6HelpedMeThisWeek</a> (from another week) related to this toot, I have a BIND nameserver in my homelab with 112 views (for shenanigans reasons), and I can't expose that construct to the internet without either <a href="https://mspsocial.net/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>, or some truly hideous port-based NAT hijinks (which, ugh, no thank you).(And worse: I actually have two of them now. 😂) <a href="https://mspsocial.net/@jima/114354031715285418" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://mspsocial.net/@jima/114354031715285418</a>

hallunke23 🇺🇦Wie wäre es, ihr kümmert euch mal um den <a href="https://troet.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>|-Rollout auf social.bund.de? Ja, ihr müsstet dafür entweder Fa. T-Systems etwas bearbeiten oder den Hoster wechseln. Aber es lohnt sich, weil euch dann endlich die Grundfunktionen der genutzten Dienstleistung zur VErfügung stehen würden! <a href="https://social.bund.de/@Bundesregierung" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@Bundesregierung</a>

Jill Veldhuis 💾Noob-level <a href="https://kind.social/tags/SelfHosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SelfHosting</a> <a href="https://kind.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> question:My home computers are connected through a router and, although they're clearly using NAT through said router for IPv4, they appear to all have outside IPv6 addresses. Are those addresses directly accessible from outside? When adding AAAA records to my outside DNS zones, should they point to my router's address, or the target machine's?

Martin PughToday, <a href="https://bsd.network/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> to the rescue. I broke DHCP for the legacy IP space on my pfSense router today but thanks to running dual stack I could reconnect using the IPv6 address and fix things. I was trying to move to using <a href="https://bsd.network/tags/Ansible" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Ansible</a> for managing pfSense and somehow despite getting zero errors and Ansible reporting things as idempotent, things were unhappy.I managed to get back into the router and deleted the new records, recreating them manually and everything is working again. No clue what I broke yet, but yay for IPv6.

TheDragon 🔥As someone who until the past year or so had not really taken the time to (seriously) consider using <a href="https://hachyderm.io/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> .... finding this gist has really made this feel like it *might* actually be not *quite* as scary as I'd always envisaged.I honestly wish I'd understood sooner that devices could be set to only use IPv6 ULAs (Unique Local Addresses), as a result making them unreachable *directly* from the internet, sooner! I had always envisaged a need to carefully operate and maintain firewalls directly on all individual local only devices.<a href="https://gist.github.com/timothyham/dd003dbad5614b425a8325ec820fd785" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://gist.github.com/timothyham/dd003dbad5614b425a8325ec820fd785</a>Is there anything I should be mindful/aware of, or think about, in addition to the points highlighted in this gist?If this helps gets me from IPv4 only to IPv6 mostly, I hope I can contribute anything "extra" mentioned in replies (and/or from my own experience) back to the gist, and hopefully help others in the process!TIA! 🙏

Max ResingJust wanted to share some thoughts on <a href="https://infosec.exchange/tags/RFC9715" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC9715</a> - an <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#RFC</a> that defines standards on reducing the <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DNS</a> issue of IP fragmentation over <a href="https://infosec.exchange/tags/UDP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#UDP</a>. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the <a href="https://infosec.exchange/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Internet</a>. A great leap forward to (hopefully) reduce the reflection/amplification <a href="https://infosec.exchange/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DDoS</a> potential of DNS.Just today I learned that <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> will share their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to <a href="https://infosec.exchange/tags/TCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TCP</a>. <a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a> <a href="https://infosec.exchange/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://infosec.exchange/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ietf</a>

Yvan ーイボん 🗺️ :ferris: :go:<a href="https://hachyderm.io/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv4</a> is hellSo much easier to go <a href="https://hachyderm.io/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> only.

sep<a href="https://floss.social/@9to5linux" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@9to5linux</a> i guess that is good. But until ipfire 3 is out, with <a href="https://snabelen.no/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> support, this project is unfortunatly not a realistic firewall alternative

gyptazyOops! The MXP01 (Italy) peer had some fuck ups, followed by some insane traffic f*ckups at 3AM & 6AM on the other instances.Rule Nr. 1: Even changing a single character can result in f*ckups. Always test!<a href="https://mastodon.gyptazy.com/tags/devops" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#devops</a> <a href="https://mastodon.gyptazy.com/tags/bgp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#bgp</a> <a href="https://mastodon.gyptazy.com/tags/peering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#peering</a> <a href="https://mastodon.gyptazy.com/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://mastodon.gyptazy.com/tags/traffic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#traffic</a> <a href="https://mastodon.gyptazy.com/tags/fail" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#fail</a> <a href="https://mastodon.gyptazy.com/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#network</a>

lwnew freebsd PR: merge traceroute6 into traceroute<a href="https://github.com/freebsd/freebsd-src/pull/1647" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/freebsd/freebsd-src/pull/1647</a><a href="https://mastodon.bsd.cafe/tags/freebsd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#freebsd</a> <a href="https://mastodon.bsd.cafe/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a>

Thomas Schäfer<a href="https://aws.amazon.com/about-aws/whats-new/2025/04/aws-end-user-messaging-ipv6/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://aws.amazon.com/about-aws/whats-new/2025/04/aws-end-user-messaging-ipv6/</a><a href="https://ipv6.social/tags/aws" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#aws</a> <a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://ipv6.social/tags/internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#internet</a>

Miyuru SankalpaLooks the <a href="https://mastodon.archive.org/@internetarchive" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@internetarchive</a> crawler has IPv6 now. Using their own ASN.<a href="https://web.archive.org/web/20250405000858/https://ipv6.icanhazip.com/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://web.archive.org/web/20250405000858/https://ipv6.icanhazip.com/</a><a href="https://ipv6.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://ipv6.social/tags/internetarchive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#internetarchive</a>

Kevin Bowen :xfce:<a href="https://hachyderm.io/@rishi556" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rishi556</a> <a href="https://ipv6.social/@miyuru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@miyuru</a> I suppose we could ask <a href="https://fosstodon.org/@kev" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@kev</a> directly which aspect of fosstodon doesn't support <a href="https://fosstodon.org/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> instead of speculating amongst ourselves. 😄

Kevin Bowen :xfce:<a href="https://ipv6.social/@miyuru" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@miyuru</a> <a href="https://hachyderm.io/@rishi556" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@rishi556</a> As far as I know, Fastly provides fosstodon with CDN & dDos protection services not hosting. As far as I can tell, that <a href="https://fosstodon.org/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> address won't allow access to the fosstodon website. I get the following error in my browser:

HoldMyTypeYggdrasil is a new experimental compact routing scheme. It is designed to be a future-proof and decentralised alternative to the structured routing protocols commonly used today on the Internet, as well as an enabling technology for future large-scale mesh networks. <a href="https://mathstodon.xyz/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ipv6</a> <a href="https://yggdrasil-network.github.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://yggdrasil-network.github.io/</a>

Kevin Bowen :xfce:Bummer. fosstodon.org's host doesn't support <a href="https://fosstodon.org/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a>

saiki 🚒💨:manjaro: :debian:<a href="https://elbmatsch.de/@DerSchulze" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@DerSchulze</a> Ich nutze auch einen, weil ich hier hinter nem CGNat mit <a href="https://social.tchncs.de/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv6</a> stecke und keine IPv4 habe :D aber für gewisse Dinge im Selfhost braucht man leider noch ne <a href="https://social.tchncs.de/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#IPv4</a>.

Recent searches

Search options

Administered by:

Server stats:

#ipv6