Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Muttley@DastardlyHQ.org Newsgroups: comp.unix.programmer Subject: Re: Text based synchronous communication tool for Linux? Date: Mon, 9 Dec 2024 08:25:22 -0000 (UTC) Organization: A noiseless patient Spider Lines: 13 Message-ID: References: Injection-Date: Mon, 09 Dec 2024 09:25:23 +0100 (CET) Injection-Info: dont-email.me; posting-host="ee2dde97c7379603ae193d5541e2f96c"; logging-data="357374"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/3yd6Fuqx15lIgDDYUwKD0" Cancel-Lock: sha1:wkScG31d4H/+gNbwpQn4tGkt7EQ= Bytes: 1558 On Sun, 8 Dec 2024 18:36:35 -0000 (UTC) cross@spitfire.i.gajendra.net (Dan Cross) wibbled: >works is brittle and doesn't work well over the modern Internet. >In particular, it is de-facto limited to IPv4 and doesn't >play well with firewalls: it involves sending the contents of a >`sockaddr_in` across the network, and using that to set up a >(direct) TCP connection between processes. One could imagine Huh? I don't get how that works. You need a connection in the first place to send anything unless you use a broadcast UDP address. You can't just automagically set up a connection without the OS network layer playing its part.