Nat Sciver-Brunt 'tendrá las riendas' para resistir a Inglaterra a su guisa, dice Charlotte Edwards #Charlotte #dice #Edwards #Inglaterra #Las #llevar #manera #Nat #para #riendas #SciverBrunt #tendrá #ButterWord #Spanish_News Comenta tu opinión 👇
https://butterword.com/nat-sciver-brunt-tendra-las-riendas-para-resistir-a-inglaterra-a-su-guisa-dice-charlotte-edwards/?feed_id=20012&_unique_id=681430069268d

@Skorpy Also mir ist der Sinn von #ipv6 im internen Netz ja nicht ganz klar. Mir ist da #nat und #wireguard wesentlich lieber.

@landley @jschauma @ryanc @0xabad1dea yeah, the exhaustion problem would've been shoved back with a #64bit or sufficiently delayed by a 40bit number.

Unless we also hate #NAT and expect every device to have a unique static #IP (which is a #privacy nightmare at best that "#PrivacyExtensions" barely fixed.)

• I mean they could've also gone the #DECnet approach and use the #EUI48 / #MAC-Address (or #EUI64) as static addressing system, but that would've made #vendors and not #ISPs the powerful forces of allocation. (Similar to how technically the #ICCID dictates #GSM / #4G / #5G access and not the #IMEI unless places like Australia ban imported devices.

I guess using a #128bit address space was inspired by #ZFS doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...

• Personally I've only had headaches with #IPv6 because not only do I only have #IPv4only #Internet but my #ISP refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of #IPv4's in with my contract!)and stuff like #HurricaneElectric / #HEnet's #Tunnelbroker fail face first due to #Geoblocking and the fact that #ASNs get geolocated, not their #PoPs...

If I was @BNetzA I would've mandated #DualStack and banned #CGNAT (or at least the use of CGNAT in #RFC1918 address spaces) as well as #DualStackLite!

de grijze vlekken
trekken een wolkengordijn
van regenstralen

#haiku #regen #nat #wolken #grijsweer #weerHaiku

https://wolkenhemel.blogspot.com/2025/04/de-grijze-vlekken-haiku-wolken-weerhaiku.html

NAT・IGWが頭に入らないインフラ初心者へ
https://qiita.com/kenken38/items/bc970d910131f014589f?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #AWS #nat #AWS認定試験 #インターネットゲートウェイ #AWS認定クラウドプラクティショナー

Tom is now listening to Rollin' Around
https://open.spotify.com/track/7vqEcDc2C51DK890XZCwZC

#Nat&AlexWolff

wolken buitelen
in, door en over elkaar
klaar voor de bui - start

#haiku #wolken #regen #regenbui #nat #voorjaar

https://wolkenhemel.blogspot.com/2025/04/wolkwn-buitelen-haiku-wolken-regen.html

Настройка форвардинга на UFW для Ubuntu Server

UFW (Uncomplicated Firewall) - это утилита для управления пакетами брандмауэра в Linux, которая предоставляет удобный интерфейс для настройки iptables. Он создан для упрощения процесса управления сетевыми правилами и подходит как для новичков, так и для опытных администраторов. NAT (Network Address Translation) — это метод, позволяющий изменять адреса IP в заголовках пакетов, проходящих через маршрутизатор или брандмауэр. Он часто используется для обеспечения доступа к ресурсам из локальной сети в Интернет, скрывая внутренние IP-адреса от внешней сети.

https://habr.com/ru/articles/894316/

#ubuntu #ubuntu_server #ufw #nat

Parece una chorrada pero hay tela de operadores hoy en día detrás de una #NAT que no te sacan o te cobran por ello. Incluso más que antes con xDLS y el añorado cable coaxial; por nostalgia solo.😎

Bericht KW11:

- MO: Urlaub
- DI: Rollout #3CX
- MI: Unternehmerfrühstück #netzwerken Diverses #vpn #Updates
- DO: Diverses #OPNsense Regeln angepasst. #haproxy mit #acme Umstellung von #NAT. Netzwerkberatung
- FR: Bürotag. #ActiveDirectory Fehlersuche. #OPNsense Firewall im HA-Cluster ausgerollt

Highlight: #OPNsense HA-Cluster sind ein Traum. #Gitea Projektverwaltung ist noch träumiger :D

Interessante Beobachtung: Der Airbnb Hotspot verwendet irgendeine interessante Technologie um IPv6-Seiten zu erreichen:

$ curl -v -6 https://icanhazip.com
* Host icanhazip.com:443 was resolved.
* IPv6: ::ffff:104.16.184.241, ::ffff:104.16.185.241
* IPv4: (none)
*   Trying [::ffff:104.16.184.241]:443...

Mein Gerät hat keine eigene IPv6-Adresse, dennoch funktioniert die Verbindung.

Ist das sowas wie DNS64 und NAT64 nur andersrum?

#ipv6 #nat

GitHub - fatedier/frp: A fast reverse proxy to help you expose a local server behind a NAT or firewall to the internet. https://github.com/fatedier/frp #OpenSource #firewall #internet #forward #reverse #service #GitHub #golang #https #proxy #http #port #nat #tcp #udp

Hat hier wer #pyur und kann sagen ob man bei denen hinter einem #nat sitzt oder ob man eine öffentliche #ipv4 und/oder #ipv6 Adresse hat?

@herrorange how?

Like I really wounder why...

Is it due to shitty #CGNAT at the #ISP end and #Skype doing aggresssive #HolePunching through any #NAT or some other #ISP-side shenanigans?

Ole Trøan discusses mistakes and missed opportunities with #IPv6 design. https://medium.com/@oletroan/the-mistakes-and-missed-opportunities-in-ipv6-d88ceb3d7feb #nat

any application needing to communicate large messages with UDP must implement packetization, retransmission, reordering, etc-- the same things that TCP already implements for us. Many applications that have 'rolled their own TCP' in userspace have ended up with exploitable bugs in them, so it isn't something that should be done without good cause.

#UDP also has the issue of #NAT traversal: Getting bidirectional communication across a NAT with UDP is not a simple matter. Crossing anything more complicated than a full cone nat requires considerable amounts of special code but without it there will be a many hosts that just can't talk to other peers with UDP.
https://bitcoin.stackexchange.com/questions/56485/can-someone-please-explain-fibre-to-me-like-im-5-and-why-is-it-useful

de zon staart tussen
turende wolken naar straks
de sneeuw in aantocht

#haiku #weerHaiku #sneeuw #winter #nat #zon

https://wolkenhemel.blogspot.com/2025/02/de-zon-staart-tussen-haiku-wolken.html

lo_if="lo1"
ext_if="vmx0"
jail_if="vmx0bridge"

#set block-policy return
scrub in on $ext_if all fragment reassemble
set skip on lo
set skip on $jail_if

table <jails> persist
nat on $ext_if from <jails> to any -> ($ext_if:0)
#nat on $ext_if from $jail_if:network to any -> ($ext_if)
#nat on $jail_if from $jail_if:network to any -> ($jail_if)
#nat on $lo_if from $jail_if:network to any -> ($lo_if)
rdr-anchor "rdr/*"

#block in all
pass out quick keep state
#antispoof for $ext_if inet
pass in inet proto tcp from any to any port ssh flags S/SA keep state
pass in on $ext_if inet proto icmp to ($ext_if) icmp-type { unreach, redir, timex, echoreq }
pass in on $ext_if inet proto icmp to ($jail_if) icmp-type { unreach, redir, timex, echoreq }
pass in on $jail_if inet proto icmp to $jail_if:network icmp-type { unreach, redir, timex, echoreq }