- cross-posted to:
- networking@sh.itjust.works
- cross-posted to:
- networking@sh.itjust.works
I’ve actually had an excavator take out my network. I’ve also had networks taken out by forklift, train, and a semi-truck towing three other semi-trucks.
How about a bus? The fiber to a datacenter i used to work at kept going out at almost consistent intervals during almost normal business hours. Turns out the conduit wasn’t deep enough and the city built a bus stop on top of it and it would sag just enough to go out but only when a bus was at the stop.
That’s pretty similar with what happened with me and the train. Kept getting random drops from a plant. I went out to investigate and everything tested perfect and the network was staying up. That was until a freight train rolled by. Turns out AT&T had run the line by shoving a piece of PVC through the gravel between two cross-ties, then running the cable through it.
This is wrong, I use IPTables but the device is absolutely not dedicated lol.
The iptables one has me triggered.
Who needs all this crazy firewall stuff when I have my
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT iptables -A INPUT -i ppp0 -j DROP
And for IPv6 you don’t need a firewall, just use slaac and hope no one finds the address /s
That punchline hit like a tree falling onto a network cable.
Spanning tree is a firewall
Okay, that’s just cursed.
i wonder what is the favorite firewall of people here?
I’m at the top right myself. 😆
Not as fast as ASIC firewalls, but way more flexible and fast enough for home routing.
I’ve heard of almost all of those things.
What’s a HA proxy?
It’s a lolbalancer
Without it we might accidentally Lol or lOL. It would be anarchy
http://www.haproxy.org/ it’s a load-balancer (it only allows access to devices behind it based on rules).
Ah yes, that time a Georgian granny became the Great Firewall of Armenia.
Cisco Automatic Telecommunications Excavator: for all your internet connection restricting needs!
In my apartment, I have a PC running Linux with four network interfaces:
- One Ethernet port built into the motherboard, connected to a switch that the rest of my hard-wired devices are connected to
- One PCIe Wi-Fi 5 card, serving as my apartment’s wireless access point
- One USB Ethernet dongle, connected to my ISP’s optical network terminal
- One USB Ethernet dongle, connected directly to an employer’s PC (for working from home)
It forwards packets between all of these (i.e. is a router) and uses nftables (i.e. is a firewall).
The firewall is specially configured to isolate interface 4: it is only allowed to talk to the Internet and the router’s DHCP and DNS servers, but not any other device in my apartment, nor any other process running on the router itself.
Seems pretty radical on both axes, but it’s neat that I can do this with nothing but common consumer equipment and free software. No fancy Cisco gear required. And unlike the average home router, the software running on mine actually receives security audits and patches, so I consider it far more secure.
Excavator in rack-mount enclosure would be awesome
A firewall is when I redirect stuff to 0.0.0.0 in /etc/hosts