#NAT

Kevin Karhan :verified:kkarhan@infosec.space
2026-01-09

@happyborg @dalai @jwildeboer most of these providers claim that they can recoup the cost with new purchases and shrinking costs for storage over time, which makes this truly a #PyramidScheme.

  • OFC they also throtthe users and don't expect everyone to max out their purchased storage quota instantly.

  • But I'm not just comparing against short-term filehosters but also in terms of #backups consider years, if not decades of uptime to be necessary to be useful.

Also mind you this ain't like #TeamViewer where the cost of infrastructure is negligible (just some "Rendrevous-Server" to exchange status info, IP addresses and facilitate "Hole Pubching" through #NAT & #Firewall which in theory doesn't reuire mich compute and bandwith to function.

  • We're talking Gigabytes if not Terabytes per User in storage and traffic.

  • And since this system isn't like some #ColdStorage like a #tape, this needs to be #HDDs that constantly spin and draw power.

🅱🅸🅶🅾🆁🆁🅴.🅾🆁🅶bigorre_org
2026-01-06

Aviation weather for Governador Aluízio Alves International airport in Natal area (Brazil) is “SBSG 061300Z 08013KT 9999 SCT030 30/18 Q1014” : See what it means on bigorre.org/aero/meteo/sbsg/en vl

🅱🅸🅶🅾🆁🆁🅴.🅾🆁🅶bigorre_org
2025-12-22

Aviation weather for Governador Aluízio Alves International airport in Natal area (Brazil) is “SBSG 221400Z 11014KT 9999 BKN030 BKN100 29/21 Q1013” : See what it means on bigorre.org/aero/meteo/sbsg/en vl

Jörg 🇩🇪🇬🇧🇪🇺geco_de@troet.cafe
2025-12-14

Wenn ich Lokal in meinem Netz alles auf #IPv6 habe, dann wird, so wie ich es verstanden habe, kein #NAT mehr gemacht. Ist ja dann nicht mehr nötig, weil jedes Gerät auch aus dem Internet heraus eine eigene, eindeutige Adresse hat.
Stimmt das so?
Das bedeutet aber auch, wenn ich z.B. den Webserver auf meinen Raspberry aus dem Internet erreichen will benötige ich kein Portforwarding auf der FRITZ!Box, denn ich kann ihn direkt adressieren.

Aber ist das nicht auch eine riesige Sicherheitslücke?

KipJayChou :debian: :docker:admin@mstdn.feddit.social
2025-12-14

RE: mstdn.feddit.social/@admin/115

本来写了很多,但是太麻烦了,就用这个最简单的方法吧:编译完Linux内核就不用了

NAT端口转发尝试:

VM1:
ifconfig
得到内外IP为192.168.122.2

Hetzner0:
sudo virsh list --all
列出虚拟机
sudo virsh net-dhcp-leases default
确认VM IP 是 192.168.122.2
sudo iptables -t nat -A PREROUTING -p tcp --dport 2222 -j DNAT --to-destination 192.168.122.2:22
设置端口转发
sudo iptables -I FORWARD -d 192.168.122.2/24 -p tcp --dport 22 -j ACCEPT
sudo iptables -I FORWARD -s 192.168.122.2/24 -p tcp --sport 22 -j ACCEPT
允许转发流量
sudo apt install iptables-persistent -y
sudo netfilter-persistent save
保存配置

其他命令:
sudo iptables -t nat -L PREROUTING -n --line-numbers
查看NAT转发规则
sudo iptables -t nat -D PREROUTING NUMBER
删除规则

#NAT #iptables #ubuntu #linux #cockpit

Hetzner0-VM-ubuntu-22.04.5screenfetch
KipJayChou[维护模式]jay@gts.feddit.social
2025-12-12

Proxmox网络配置
https://pve.proxmox.com/wiki/Network_Configuration

Proxmox VE 不会直接将更改写入/etc/network/interfaces文件。相反,我们会将更改写入一个名为/etc/network/ interfaces.new 的临时文件

如果您通过图形用户界面 (GUI) 更改网络配置,可以单击 “应用配置”按钮。这将把临时interfaces.new文件中的更改同步 到/etc/network/interfaces文件并实时应用。

如果您直接手动修改了/etc/network/interfaces文件,可以通过运行ifreload -a 命令来应用这些更改

o[n<phys_port_name>|d<dev_port>] — devices on board
s[f][n<phys_port_name>|d<dev_port>] — devices by hotplug id
[P]ps[f][n<phys_port_name>|d<dev_port>] — devices by bus id
x — devices by MAC address

eno1——是首款板载网卡 enp3s0f1 — 是 PCI 总线 3、插槽 0 上的网卡的功能 1。

您可以使用 diff(或其他您选择的差异查看器)来检查对配置所做的更改:diff -y /etc/network/interfaces /etc/network/interfaces.new

网桥就像是用软件实现的物理网络交换机。所有虚拟机可以共享同一个网桥,也可以创建多个网桥来分隔不同的网络域。

• 10...* → 私有
• 172.16~31.. → 私有
• 192.168.. → 私有
• 127...* → 回环

常见的情况是,您有一个公网 IP 地址(例如198.51.100.5 ),以及一个用于虚拟机的额外 IP 地址块(203.0.113.16/28)。我们建议在这种情况下采用以下设置:

auto lo 
iface lo inet loopback 

auto eno0 
iface eno0 inet static 
        address 198.51.100.5/29 
        gateway 198.51.100.1 
        post-up echo 1 > /proc/sys/net/ipv4/ip_forward 
        post-up echo 1 > /proc/sys/net/ipv4/conf/eno0/proxy_arp 


auto vmbr0 
iface vmbr0 inet static 
        address 203.0.113.17/28 
        bridge-ports none 
        bridge-stp off 
        bridge-fd 0

使用iptables进行地址转换(NAT)
伪装技术允许只有私有 IP 地址的访客通过访问主机 IP 地址来访问网络。每个出站数据包都会被iptables重写,使其看起来像是来自主机,响应也会相应地被重写,以便路由到原始发送者。

auto lo 
iface lo inet loopback 
auto eno1 
#真实IP地址
iface eno1 inet static 
        address 198.51.100.5/24 
        gateway 198.51.100.1 

auto vmbr0 
#私有子网
iface vmbr0 inet static 
        address 10.10.10.1/24 
        bridge-ports none 
        bridge-stp off 
        bridge-fd 0 

        post-up echo 1 > /proc/sys/net/ipv4/ip_forward 
        post-up iptables -t nat -A POSTROUTING -s '10.10.10.0/24' -o eno1 -j MASQUERADE 
        post-down iptables -t nat -D POSTROUTING -s '10.10.10.0/24' -o eno1 -j MASQUERADE

#proxmox #network #pve #vmbr0 #eno1 #NAT

Vmbr0
Kevin Karhan :verified:kkarhan@infosec.space
2025-12-09

@SpaceLifeForm Again: Doesn't work with UDP traffic that is encrypted!

  • And I kinda need to do some #NAT+#NPT shit here...
Kevin Karhan :verified:kkarhan@infosec.space
2025-12-09

#IPv6 is a mistake!

  • Noone needs #128bit address space!
  • 21+ years of protocol existance, yet no mandatory & widespread adoption…
  • You want to have more than 1 PC per line? We have a solution for it, it's called #NAT!
  • IPs should not have variable lenghts and hexadecimal digits!!!

#SLAAC? #RouterAdvertisement?? #6rd???

  • These are real #IPv6only mechanisms deployed in the real world!

"Yes, I'd love to have all my devices loose their #IP assignments everytime my #WAN connection resets/disconnects/…!"

  • They have played us for absolute fools!

#meme #shitpost #IPv4 #Enshittification

Geeklandgeekland
2025-12-08
Сталкер Commander1024Commander1024@chaos.social
2025-11-27

Gerade in einem Workshop bzgl. #CGN. Es fallen ungewöhnlich häufig die Worte "präNATal" und "postNATal". Aber zu unserer Verteidigung: Die Systeme heißen routingduck0X. Denn sie machen #NAT, #NAT, #NAT.

P. S.: Ja, wir haben einen einfachen Humor.

ASCII-Art einer stilisierten Ente im Terminal, die "NAT, NAT, NAT" sagt.
GripNewsGripNews
2025-11-22

🌗 一次性體驗,自行託管 NAT Gateway
➤ 打破常規,用開源力量顛覆 AWS NAT Gateway 的成本格局
awsistoohard.com/blog/self-hos
本文探討了自行託管 AWS NAT Gateway 的動機、優點及實際實施經驗。作者透過導入開源方案 Fck-NAT,成功大幅降低了開發環境中的 NAT Gateway 相關費用,特別是針對透過 Github Actions 和預覽環境產生的大量出站流量。文章也分析了 Fck-NAT 和 AlterNAT 兩種解決方案的技術細節與適用情境,並展示了實施後顯著的成本節省效益。
+ 自行託管 NAT Gateway 聽起來確實有點瘋狂,但看到作者實際省下這麼多錢,讓人忍不住想深入瞭解!
+ Fck-NAT 和 AlterNAT 的比較分析很有價值,特別是 AlterNAT 的容錯機制聽起來很複雜但很可靠,可惜作者為了成本考量選擇了 Fck-NAT。
Gateway

Client Info

Server: https://mastodon.social
Version: 2025.07
Repository: https://github.com/cyevgeniy/lmst