Conversation

Notices

1. Embed this notice
   Alex Haydock (alexhaydock@infosec.exchange)'s status on Monday, 02-Dec-2024 20:48:00 JST Alex Haydock

   • nixCraft 🐧

   I took @nixCraft's 'No NAT November' challenge and switched my network to IPv6-only! :blobcat_thisisfine:

   New blog post: No NAT November - My Month Without IPv4

   https://blog.infected.systems/posts/2024-12-01-no-nat-november/

   #ipv6

   • Embed this notice
     Julius Schwartzenberg (jschwart@mas.to)'s status on Friday, 06-Dec-2024 05:19:28 JST Julius Schwartzenberg

     in reply to

     • nixCraft 🐧

     @alexhaydock @nixCraft it's interesting to read your article, also now I understand better why one would put CLAT on the client. I guess in most places it will be handled by the router though (with still having an internal IPv4 network...).

     Also interesting is: https://nat64.xyz
     I played with some of those when trying an IPv6-only connection some time ago and had quite good experiences!

   • Embed this notice
     Julius Schwartzenberg (jschwart@mas.to)'s status on Friday, 06-Dec-2024 05:27:16 JST Julius Schwartzenberg

     in reply to

     • nixCraft 🐧

     @alexhaydock @nixCraft something that can be useful is browsing the web without IPv4 enabled at all. When you try a site and it doesn't work, try both the variant with and without `www.`, sometimes one works while the other doesn't. When a site loads partially, for instance images do not load, check whether they might be hosted on another domain without a AAAA record.

     Mail webmasters when you see these issues. They tend to be responsive and quickly fix them.