Discussion
Loading...

#Tag

  • About
  • Code of conduct
  • Privacy
  • Users
  • Instances
  • About Bonfire
Stefano Marinelli boosted
subnetspider
@subnetspider@mastodon.bsd.cafe  路  activity timestamp 2 weeks ago

And yes, using NAT64 technically goes against the spirit of No-NAT November, but the alternative would be to stop myself from using half of the internet for 30 days without learning anything other than which websites and services break without IPv4, which gets boring very quickly.

Either way, the next thing I want to look at is PREF64, as well as building a CLAT on operating systems that don't natively support them, in case they run software relying on hard-coded IPv4 addresses. 馃槑

#IPv6 #NAT64

Edit

The following blog post was very inspiring for me, thanks @alexhaydock for sharing this. :)

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

  • Copy link
  • Flag this post
  • Block
subnetspider
@subnetspider@mastodon.bsd.cafe  路  activity timestamp 2 weeks ago

And yes, using NAT64 technically goes against the spirit of No-NAT November, but the alternative would be to stop myself from using half of the internet for 30 days without learning anything other than which websites and services break without IPv4, which gets boring very quickly.

Either way, the next thing I want to look at is PREF64, as well as building a CLAT on operating systems that don't natively support them, in case they run software relying on hard-coded IPv4 addresses. 馃槑

#IPv6 #NAT64

Edit

The following blog post was very inspiring for me, thanks @alexhaydock for sharing this. :)

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

  • Copy link
  • Flag this post
  • Block
subnetspider
@subnetspider@mastodon.bsd.cafe  路  activity timestamp 2 weeks ago

Huh ... just enabled DNS64 and DHCP option 108 on my OPNsense to see if my phones would enable their CLAT, guessing that I would need to do more work, but it just works鈩笍.

The iPhone reports 192.0.0.3 as it's IPv4 and 192.0.0.1 as gateway, and the Android doesn't show any IPv4 (but 255.0.0.0 as next hop in traceroute?).

Either way, that's another two IPv6-only devices, I'm actually making progress. 馃榿

#IPv6 #NAT64

  • Copy link
  • Flag this post
  • Block
Esther Payne :bisexual_flag: boosted
Brett Sheffield (he/him)
@dentangle@chaos.social  路  activity timestamp 3 weeks ago

Installed our new router box yesterday and switched our LAN from dual-stack to #IPv6 only with #DNS64 + #NAT64

Did quite a lot of this one-handed, as Alonso fell asleep on my arm. 馃惗馃挙

  • Copy link
  • Flag this post
  • Block
Esther Payne :bisexual_flag: boosted
Brett Sheffield (he/him)
@dentangle@chaos.social  路  activity timestamp 3 weeks ago

Oh cool. We just tested and #WebRTC with #Jitsi works over #NAT64

I'd heard WebRTC can be problematic with #NAT64, and the fact that Jitsi has dropped the IPv6 AAAA records for meet.jit.si and closed some recent IPv6 bug reports as WONTFIX didn't give me a lot of confidence. 馃槦

However, jitsi worked fine just now with one user on mobile (IPv4-only) and another on NAT64.

馃榾

  • Copy link
  • Flag this post
  • Block
Brett Sheffield (he/him)
@dentangle@chaos.social  路  activity timestamp 3 weeks ago

Oh cool. We just tested and #WebRTC with #Jitsi works over #NAT64

I'd heard WebRTC can be problematic with #NAT64, and the fact that Jitsi has dropped the IPv6 AAAA records for meet.jit.si and closed some recent IPv6 bug reports as WONTFIX didn't give me a lot of confidence. 馃槦

However, jitsi worked fine just now with one user on mobile (IPv4-only) and another on NAT64.

馃榾

  • Copy link
  • Flag this post
  • Block
Brett Sheffield (he/him)
@dentangle@chaos.social  路  activity timestamp 3 weeks ago

Installed our new router box yesterday and switched our LAN from dual-stack to #IPv6 only with #DNS64 + #NAT64

Did quite a lot of this one-handed, as Alonso fell asleep on my arm. 馃惗馃挙

  • Copy link
  • Flag this post
  • Block
Arch :arch:
@arch@floofy.tech  路  activity timestamp last year

"Oh why is this build not workin- oh, because the year is 2024, and GitHub doesn't have IPv6."

gyptazy
@gyptazy@mastodon.gyptazy.com replied  路  activity timestamp 4 months ago

"oh, we could have simply used #NAT64".

Don't take it too serious.. =)

@arch

  • Copy link
  • Flag this comment
  • Block
Log in

bonfire.cafe

A space for Bonfire maintainers and contributors to communicate

bonfire.cafe: About 路 Code of conduct 路 Privacy 路 Users 路 Instances
Bonfire social 路 1.0.0 no JS en
Automatic federation enabled
  • Explore
  • About
  • Members
  • Code of Conduct
Home
Login