#rfc1918 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #rfc1918, aggregated by home.social.
-
I’m an Internet Bad Boy: How I Violate RFC1918 Every Day And Why You May Find It Convenient To Do So, Too https://lowendbox.com/blog/im-an-internet-bad-boy-how-i-violate-rfc1918-every-day-and-why-you-may-find-it-convenient-to-do-so-too/ #Editorial&News #privatenetwork #rfc1918 #rfc1918 #ipv4
-
Your home address is public (where the world can locate you). Your couch is a private address (for your family only). RFC 1918 IPs (like 192.168.x.x) are the 'couches' of the internet. They need NAT (the postal system) to get mail from the public internet. It's the general reason why we're not all out of IPv4 addresses. yet!
-
Your home address is public (where the world can locate you). Your couch is a private address (for your family only). RFC 1918 IPs (like 192.168.x.x) are the 'couches' of the internet. They need NAT (the postal system) to get mail from the public internet. It's the general reason why we're not all out of IPv4 addresses. yet!
-
certbot on Debian Bookworm fails with: The peer didn't know the key we used
#LetsEncrypt #Debian #Challenge #Bookworm #Trixie #Certbot #Bind #RFC1918 #Encryption #DNSSEC #ACME #DNS
-
certbot on Debian Bookworm fails with: The peer didn't know the key we used
#LetsEncrypt #Debian #Challenge #Bookworm #Trixie #Certbot #Bind #RFC1918 #Encryption #DNSSEC #ACME #DNS
-
I think this is my favorite thing I learned from HN in 2023.
-
I think this is my favorite thing I learned from HN in 2023.
-
@Linux_Is_Best @th_willenbrink @whitekiba @lucent
BTW you should let the your telco regulators know that #Tmobile violates #RFC standards by literally using #CGNAT on #RFC1918 adress space, which is explicitly not allowed as per #RFC6598.
-
@housepanther If you use an #RFC1918 adress space, that issue won't happen...
https://en.wikipedia.org/wiki/Private_network#Private_IPv4_addresses
-
Whether a result of clumsiness of a bored operator or deliberate subterfuge, there are clues that the supposed NSA front Equation Group operated out of Russia. The question remains: What were they doing that for?
Reprising my 2016 article "The Possibly Russian Fingerprints on the Shadow Brokers' Trick or Treat Package", https://bsdly.blogspot.com/2016/11/the-possibly-russian-fingerprints-on.html or trackerless https://nxdomain.no/~peter/possible_russian_fingerprints_on_the_shadow_brokers_trick_or_treat_package.html #cybercrime #hacking #Russian_cybercrime #EquationGroup #ShadowBrokers #NSA #RFC1918
-
Whether a result of clumsiness of a bored operator or deliberate subterfuge, there are clues that the supposed NSA front Equation Group operated out of Russia. The question remains: What were they doing that for?
Reprising my 2016 article "The Possibly Russian Fingerprints on the Shadow Brokers' Trick or Treat Package", https://bsdly.blogspot.com/2016/11/the-possibly-russian-fingerprints-on.html or trackerless https://nxdomain.no/~peter/possible_russian_fingerprints_on_the_shadow_brokers_trick_or_treat_package.html #cybercrime #hacking #Russian_cybercrime #EquationGroup #ShadowBrokers #NSA #RFC1918
-
@sindarina Personally, I think violating #RFCs should be a criminal offense, since I've also experienced the #VPN-breaking use of #RFC1918 adresses for #CGNAT!
-
@sans_isc AFAICT they don't and even if they would that would violate RFCs and make them liable to @BNetzA fines.
Speaking of shitty #CGNAT:
I should protest of them using #RFC1918 address space [10.0.0.0/8] when #RFC6598 states they must use 100.64.0.0/10 instead...https://en.wikipedia.org/wiki/Carrier-grade_NAT
https://datatracker.ietf.org/doc/html/rfc6598 -
I expetience some strange behaviour with @torproject #TorBrowser on a (throttled) mobile connection:
Neither bridges (obfs4, meek-azure nor snowflake) nor without with get some.stable.connection and just contantly have circuits dying before it can even load the homepage to show it's connected.
Is it just me or do #MVNO's using #CGNAT on #RFC1918 adress spaces also try to prevent and block #Tor useage?
-
Not to mention a lot of woes apply due to shitty #CGNAT on #RFC1918 adress spaces and other crap, like wannabe-geolocation that results in moving devices changing their [WAN-sided] IP-Adresses [whilst retaining the one on the aerial interface] causing reconnects.
And OFC a least-cost MVNO will get lower priority and worse service than an enterprise-contract M2M data-only SIM with guaranteed SLAs.
-
@HopelessDemigod not really, but I have issues with other mobile networks which - in violation of #RFC6598 - use #RFC1918 adress space for #CGNAT.
https://en.wikipedia.org/wiki/Carrier-grade_NAT
I'm shure that @stux runs mstdn.social as dual-stack, so even NAT & PAT should not be the problem...
-
@jwildeboer @EU_Commission that being said, I fully agree and think everyone should have a free, provider-independent #IPv6 /64 assignment and shit like #CGNAT, espechally those violating standards and using #RFC1918 adress spaces (like #mobile networks routinely do) should be abolished and forcibly disconnecting limes each 24 hours as well as trying to restrict peoples' use should be abolished.
https://social.wildeboer.net/@jwildeboer/110250521163940486 -
Have literally spent 5 months on a case with Tenable support convincing them that addresses NOT in RFC-1918 spaces CAN be considered "internal" addresses.
Some legacy networks use internet routable address for EVERYTHING.
We scan them, every week with our "internal" scanner.
-
Have literally spent 5 months on a case with Tenable support convincing them that addresses NOT in RFC-1918 spaces CAN be considered "internal" addresses.
Some legacy networks use internet routable address for EVERYTHING.
We scan them, every week with our "internal" scanner.
