Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

16K
active users

mstdn.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.4

#dualstack

3 posts3 participants0 posts today
Replied in thread
Public
Kevin Karhan :verified:

@fusl @mnalis @0xF21D

I do that with #pfSense & #OPNsense (depending on the exact network in question) and have it merge multiple sources that get cached.

In total, I do may out the 30 DNS servers and whilst I have #IPv4only, I have everything ready for #DualStack (#IPv4 + #IPv6) once my ISP stops keeing it's thumbs um their ass...

List of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.
GitHublists.d/dns.servers.list.tsv at main · greyhat-academy/lists.dList of useful things. Contribute to greyhat-academy/lists.d development by creating an account on GitHub.
#sarcasm
Public
krithin

Anyone know why opening #IPv6 ports on #GoogleWifi might be failing for me? I have IPv6 service from my ISP (sonic.net - they're awesome!) and have a web server set up on my #RaspberryPi.

Requests from outside my network sent to the pi's IPv6 GUA keep failing, even though I have ports 80 and 443 open for the pi in the "Port Management" section of the google home app. Requests made to that same IPv6 GUA work fine within my network.

(I also have IPv4 port forwarding set up on that same page, and that seems to work fine to forward requests made to my router's external IPv4 address to the pi, so I could simply not set up an AAAA record and move forward with only IPv4 access to my server, but I'd prefer having a working dual-stack setup!)

#networking#HomeLab#Google
Replied to Thomas Schäfer
Public *
Kevin Karhan :verified:

@tschaefer fängt damit an dass bis heute nicht alle #IPv6 haben oder bekommen können...

  • Bspw.: Verweigert mein #ISP die Bereitstellung von echtem #DualStack. (Deshalb kann ich diesen Post auch nicht direkt aufrufen!)

Umgekehrt sind bis heute nicht alle #Diensteanbieter & Services von #IPv4 auf #IPv6 migriert worden.

Sorgt zwar für Henne-Ei-Problem, wäre aber durch die @BNetzA lösbar indem diese zwangsweise je IPv4 mindestens ein /64 an IPv6 vorschreibt und Bullshit wie #CGNAT [insbesondere mit #RFC1918-Addressraum] verbietet!

  • Besonders Bullshit wie #DualStackLite ist murks: Entweder korrekt Dual-Stack oder lasst es sein!!!
ipv6.socialThomas Schäfer (@tschaefer@ipv6.social)@kkarhan@infosec.space Du hast die Behauptung aufgestellt, dass IPv6 only vieles bricken würde. Also was?
#dualstacklite
Replied in thread
Public
Kevin Karhan :verified:

@baldur generally, #GeoIP and other #IP-based #Geolocation and #Geoblocking is just garbage.

I'm stuck on an #IPv4only conmection because my #ISP is unable and/or unwilling to provide proper #DualStack connectivity or even a /64 of #IPv6 (when in fact they could easily do a /48 if not /40 since they gave me a /28 of #IPv4's at no added cost).

  • And no, tunnelbroker.net doesn't work for me because then stuff will prefer IPv6 and a shitload of stuff does #GeoIP and then geoblocks me despite choosing the #PoP in #FRA because they Geolocate entire #ASN|s and not single allocations!
tunnelbroker.netHurricane Electric Free IPv6 Tunnel Broker
#pop#FRA#asn
Public *
Kevin Karhan :verified:

@stefano my #advice:

  • Replace set value="1.1.1.1,9.9.9.9" with set value="161.97.219.84,178.63.116.152,2001:470:4212:10:0:100:53:10,2a01:4f8:141:4281::999" for #DualStack-#DNS and not just #IPv4 if #IPv6 is available.

  • Otherwise just value="161.97.219.84,178.63.116.152," .

Reasons:

Whereas #OpenNIC has a proven track record of #integrity...

YouTubeHow Cloudflare enabled Kiwifarms stochastic terrorismBy Liz Fong-Jones
Replied in thread
Public *
Kevin Karhan :verified:

@iX_Magazin es ist #Unwille seitens der #ISP|s da @BNetzA nicht #IPv6 vorschreibt.

Ich hab' nen /28 an #IPv4 aber nichtmals ein /64 an IPv6 und.mein ISP will mir auch kein IPv6 geben!

IMHO sollte echtes #DualStack oder zumindest nen /64 per IPv4 bzw. nen /48 bei IP-Blöcken vorgeschrieben werden!

Siehe Kommentare...

...besonders dieser!

heise onlineheise onlineNews und Foren zu Computer, IT, Wissenschaft, Medien und Politik. Preisvergleich von Hardware und Software sowie Downloads bei Heise Medien.
Public
Litchralee_v6

@nuintari My (admittedly cursory) understanding is that it's a transition aid, to smooth the path from #dualstack to #ipv6mostly. An OS network stack might be reluctant to take the first leap-of-faith to IPv6-mostly, so the RFC lets the network make the first move, positively declaring that IPv6 single stack should work fine. A dual stack network would lack that signal, and the OS would behave accordingly.

Essentially, it's like "positive affirmations", but for the next phase of IPv6 transition

ExploreLive feeds
About