Live data from Hacker News

The Promised LAN

tpl.house

21–30 of 194 posts

Re: The Promised LAN

#21

No description of the games they even play? It's an interesting idea. But it sounds like one big "no girls allowed" kind of treehouse with how minimally forthcoming they are about documentation

it's made clear from the outset this article is not attempting to recruit members, but to promote the concept

Re: The Promised LAN

#22
post #15
post #13

This sounds really interesting and something I'd be into no word on how to join though

The idea is to be a space where existing social groups play, rather than a wider community - it's inherently based on a level of pre-existing trust. Writing about it is supposed to be an incentive for people to build their own little spaces where they can share weird stuff that should never be near the public internet - it's cool to have a network of thermal printers that people can submit jokes to, but it only reall…

The SIP "redphones" is an idea I really like. My wife managed to get a SIP IP phone from one of her buy-nothing groups that I've been meaning to setup an Asterisk server for just to mess with. Maybe stick it upstairs where my kid likes to play & let him get the experience of using a "real" phone.

Re: The Promised LAN

#23

No description of the games they even play? It's an interesting idea. But it sounds like one big "no girls allowed" kind of treehouse with how minimally forthcoming they are about documentation

> But it sounds like one big "no girls allowed" kind of treehouse

There is absolutely nothing wrong with this. It's actually completely fine, and good, for people to voluntarily form social groups based on a shared interests and traits. The movement to oppose this sort of thing has been a large factor in the deterioration of social life for many people. You are not entitled to membership in a community of close-knit friends.

Re: The Promised LAN

#24
Hypothetically, it be possible to achieve the same thing with a shared tailscale network, right? But can you kinda "federate" tailnets like this? So independent tailnets owned and run by individuals, but networked together into an inter-tailnet?

You miss the fun and games of running your own DNS infra etc I guess.

Re: The Promised LAN

#26
I've been wanting to do this for ages. Originally I wanted to do this at the home router level, but that quickly got shut down when I got a test net up and running and my friends could control the Chromecasts in my house.

For us a "tailscale" equivalent with SoftEther is what we used to manage the DNS/Tunneling for our fileshare/services.

So cool to see more people playing in this space. Please post more! <3

Re: The Promised LAN

#27

No description of the games they even play? It's an interesting idea. But it sounds like one big "no girls allowed" kind of treehouse with how minimally forthcoming they are about documentation

> But it sounds like one big "no girls allowed" kind of treehouse There is absolutely nothing wrong with this. It's actually completely fine, and good, for people to voluntarily form social groups based on a shared interests and traits. The movement to oppose this sort of thing has been a large factor in the deterioration of social life for many people. You are not entitled to membership in a community of close-knit…

Where did I say any of that?

I was just bemused at the webpage bragging about hosting a "24/7 LAN party" but then not even mentioning what games they like playing

Re: The Promised LAN

#28
Heh, of all arguably-valid definitions of "LAN Party" I think this one is as far away from mine as you can get.

Traditional LAN party: Everyone brings their computers to one place to connect via a LAN, where they play games, swap files, demo stuff to each other, etc.

My LAN party: All my friends come over to my house and use the computers that I have already set up for them. Nobody brings their own. The point is to interact face-to-face, with video games as a catalyst. Swapping files and demos doesn't really happen since nobody brought their own computer. (My house: https://lanparty.house)

The Promised LAN Party: The LAN is extended, virtually, across multiple houses, so that the participants can play games, swap files, and demo stuff without actually leaving home. It's arguably no longer "local" but functionally it enables the same activities as a LAN party, other than the face-to-face interaction part.

I wonder who gets told their definition is "wrong" more. :)

Re: The Promised LAN

#29
post #11
post #5

Really want to know the rationale of choosing IPSec over Wireguard. IPSec is really tricky to get right (IMO). Maybe legacy issue?

My personal choice for something like this would be Tailscale/Headscale. Runs over Wireguard and handles a ton of niceties like DNS for connected nodes automatically.

Yeah.

I personally ran into the legacy setup issue for running vanilla Wireguard for my setup before Tailscale is a thing and have to manually manage keys, routing and DNS.

But one thing Tailscale has that annoyed me is that they are using 100.64 CGNAT addresses (which is more RFC-compliant) but conflicts with one of my cloud service provider's pre-configured DNS, NTP and software mirrors setup. Using it became more or less messy for this reason.

Re: The Promised LAN

#30
post #5

Really want to know the rationale of choosing IPSec over Wireguard. IPSec is really tricky to get right (IMO). Maybe legacy issue?

They probably use L2TP with IPsec to get Layer 2 transit. Doing that over Wireguard would require Gretep or something similar

Not sure they are using l2 transit.

They are using BGP and routing nodes (backbones), recreating a mini IP (layer 3) network I think.

I've used raw wireguard in a p2p fashion to interconnect LANs. I run wireguard on each segment directly inside the network routers.

Just make sure all LANs are using a different subnet. A /24 is standard. Then configure all the peers and you get a fully peer to peer network. No relays. You only need one side of every peer "pair" to be reachable from the internet.

I do have a small management script to help peer discovery (dynamic IPs) and key exchange, but it's not strictly required. With a dozen nodes or so, it's maintainable manually. Wireguard supports roaming natively, as long as one peer can reach the other.

Very little overhead. ICMP, TCP and UDP support.

Post reply on HN