Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

272
active users

toad.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#ipv6

11 posts8 participants5 posts today
Public
xHire

@fosstodon avoids talking to me. No reply to my direct toot, no reply to my e-mail when I asked about #IPv6. That’s quite sad. (Even more so that all their providers they publicly mention should support IPv6.) Apparently it’s hard to come up with excuses in 2025. So I move, because my domain (including e-mail) is IPv6-only since yesterday, so I won’t get any e-mails from Fosstodon.

→ @xHire@ipv6.social

skutecnyinternet.cz/en/website

www.skutecnyinternet.czTest of fosstodon.org – The real Internet
Continued thread
Public
Thomas (aka Papa Dragon)
Nan, mais du coup, quand Spamhaus m'écrit ça:

"A spammer can cycle through IPv6 addresses every 5 seconds (or even faster, with custom kernels). Since an IPv6 /64 is twice the size of the entire IPv4 mask, lots of spam can be produced with very minimal effort. Thus, listing the whole /64 is warranted."

Ça veut dire que parmi toutes les adresses qui commencent par les mêmes 16 caractères que celle de mon serveur, genre des milliards, il y en a qui envoient du spam et du coup elles sont toutes blacklistées? C'est pas un peu extrême comme mesure?

#AdminEnCarton #Courriel #Mail #Spamhaus #Blacklist #IPv6
#ipv6
Public
Thomas (aka Papa Dragon)
Braves fédinautes, j'en appelle aux plus balèzes en gestion de serveur de courriel parmi vous. En l''espace de quelques jours, l'IPv6 de mon serveur familial (un VPS premier prix chez OVH) s'est retrouvée deux fois blacklistée chez Spamhaus. La première fois, j'ai fait une demande de retrait en indiquant que cette IP correspondait à un serveur personnel correctement configuré, et ça l'a fait tout de suite.

J'ai fait la même demande de retrait pour la deuxième entrée dans la blacklist, mais cette fois-ci, ça ne l'a pas fait. Un ticket a été ouvert, puis fermé après que j'aie reçu la réponse standard (automatisée?) suivante: https://apps.caselibre.fr/privatebin/?4501b9b6d15e53ea#3y71eVjXNrnHzuVQUY5Qs79Psr6YRry3Nj9yjNHy4YTY

Dois-je comprendre que là, c'est complètement dead et que mon IP est définitivement blacklistée?

#Courriel #Mail #Spamhaus #Blacklist #IPv6
PrivateBinPrivateBinVisit this link to see the note. Giving the URL to anyone allows them to access the note, too.
#ipv6
Public
Loafer

So, *@discuss.systems ; still trying to wrap me head around this IPv6 thing, couldn't sleep last night thinking about it; even though in the past I have successfully setup an IPv6 network via Hurricane Electric Tunnel and receiving a badge at the time for having set it up to the point I could have my #OpenWrt router pinged on the other end of the tunnel.

Had no actual #IPv6 connection at that point, but now I believe I do.

Now I have muddled through a few tutorials on the subject and I am confused as ever.

I have at my disposal, the tools subnetcalc and the ipaddr library of python which is capable of calculating address ranges based on CIDR notation and for telling you if an address is a network address ranges, from what part of the world, or if an unicast single host address.

Half way through watching a video that recommends first watching another video with a painfully German guy who seems to really know his stuff and looks like my old coworker Brewbaker were he a bit taller, they must be relatives.

Allowing the Delegation of Global Address prefix seems to allow for sub-sub netting amongst the original address space, and if you want to prevent this it you disallow it like a land lord disallowing subletting in the lease agreement.

Also, my Xfinity connection seems to indicate that this prefix will change weekly. And if I want any of my servers to keep their static address they seem as though they will need to be readdressed manually every week, with a Global static address since the downstream prefix of their subnet would change with the weekly prefix change. And then I would have to change the firewall rules too!!!

Also it seems that somehow #arp has been replaced by #ICMPv6 and some totally confusing process called Neighbor Detection #ND in which routers and hosts advertise and solicitate.

Also, Site-Local addressing with a FEC0 range appears to have replaced the 172.0.0.0, 10.0.0.0 and 192.168.0.0 ranges but these have also been deprecated so they shouldn't be used.

And the I didn't-get-an-address, address, 169.0.0.0 has been replaced by FE80 addresses but they can oddly still be communicated with.

Seems like a mess to me, but learning something new tends to be like that.

Any tips for the blind group of men trying to describe the elephant to each other you can provide me would be appreciated.

Replied in thread
Public
gyptazy

More or less, I do the same but on IP level. Having my own /29 subnet (out of my /24) for #IPv4 and /48 (out of my /32) for #IPv6 I simply attach them by GRE at locations where I want to use them. No dns updates, nothing. Tunnel up/down - served from where I want.

@jwildeboer

Public
In #Flancia we'll meet

So let me get this straight:

- You need to enclose #IPv6 addresses in square brackets when using them in URLs, because...
- The colon is already used to separate addresses from ports in URLs, and IPv6 uses colons to separate hex groups.

So the question is... why did IPv6 choose to separate parts with colons?! IPv4 used periods for that and I can't see why they wouldn't have worked for IPv6 too. Did they somehow go out of fashion? :)

ExploreLive feeds
About