My previous response to this question.

And she’s trans too, right? Would send DHH in a frothy frenzy.

So are we all.

Because desktops are expensive. You people just can’t afford them. You need to put at least 1k into the PC then another 200 into the screen, then mouse, keyboard, headset, webcam… They are cheaper off buying a phone.

Young people barely own stuff anymore. Their wealth is historically low as the tech barons, land barons, and so on own everything they want: homes, tech, uni debt, subscriptions, everything. And meanwhile the young are expected to work longer hours for less pay. In certain countries their pay is taxed up to 50%, but a wealthy person doesn’t get a salary so they aren’t taxed.

Their parents didn’t do much better either, but they didn’t have it as bad. But it was bad enough that daycare and childcare is fucking expensive, so they shove a phone into the child’s face: now the children know phones from a very young age and are also conditioned to buy one asap because it’s all they know.

So yeah, I don’t blame young people for not owning PCs. Our society has fumbled, is fumbling, and will continue to fumble making it affordable. If we want young people to be more interested in computing beyond telling Claude to write shit for them, we should be worrying about the wealth gap and affordability crisis.

The fabled Windows 12

Cisco Packet Tracer is a comprehensive networking simulation software tool for teaching and learning how to create network topologies and imitate modern computer networks.

That’s for simulation. I don’t think it’s possible to analyse a running system to find trace packets as they go through the firewall.

Cisco Packet Tracer is available for free to all Cisco Networking Academy instructors, students, and alumni. Sign up for our free Getting Started with Cisco Packet Tracer course to learn how to download, install, and get started.

And it also requires a paid account to use.

That’s a very generic name. Do you have a link?

Regarding your question, I’ve had trouble multiple times with docker (and other software) that required trying to find out just where a packet was getting stuck. The worst thing is when you open a port in the container to 0.0.0.0, send a request to it (HTTP, telnet, or otherwise) from the host via the container’s IP and the packet doesn’t arrive. Then you have to run through the gamut of:

• are the interfaces up?
• is it the IP address that’s wrong?
• is the the port wrong?
• is the network mask correct?
• is the gateway IP correct?
• is the firewall somehow interfering?

There might be other things I’m missing, but once I get to the firewall stage, most of the time I just give up, put the service into a VM and try accessing it from there - if I really really care. Otherwise, I drop it and move on.

I did just find this Network address translation part 1 – packet tracing which allows tracing a packet through the firewall via xtables-monitor. It’s in my notes now, so if I run into the problem again, I might have a place to start next time.

But still, that’s just on my machine. Once things happen on the network and there are routers and other things involved, it’s very difficult for me to debug.

Reading the iptables dump is not for beginners. Far from it. A packet can go through all tables and chains or none. And allowing a packet in one chain then begs the questions which is the next table or chain. There are maybe 100 flags and nobody can memorise them all.

Ufw just allows adding rules, ss doesn’t trace packages as they go through the firewall, it can show you open ports and established connections, but it can show you which tables and chains a packet went through. lsof is even more rudimentary than ss and literally means “list open files”. Since everything is a file in linux, that’s a lot of files. Again, no tracing.

Somebody will say “just tcpdump”. Again, no that doesn’t trace which tables and chains a packet goes through. The entire firewall is a blackbox to tcpdump. At least to my knowledge. All it sees is which packets arrived and which were sent on the selected interfaces, and whether they was successful or not.

Nothing I know of traces a packet through the firewall and presents in a TUI nor GUI. I know that it’s possible to make copies of packets and send then to custom chains that can log the chain and packet it came from. There might even be a way of generating a trace by adding a rule to a chain, which means adding it to every chain, but I’m not sure I’ve seen something do that.

Extraterrestrials

The problem with networking is debugging it. The worst is debugging iptables and nftables. Figuring out which chain they are going to is a massive hassle. How come we don’t have any graphical tools whatsoever for this work?

I feel for the students that must buy and use windows in order to be able to execute the crap the university tells them to use. Universities are so far behind on tech

Aren’t there cleanup scripts for Windows?

You know.

Thanks for the links. Documentation is definitely a problem. They’d have to be open to feedback on documentation. Threads on documentation improvement are often met with “it exists, what more do you want?” even if the feedback is “this and this is missing” 🤷

Anyway, I’ll check out the links and try to set something up. My usage of radicle is definitely what it could be because of the lack of notifications. I literally fire and forget my repos, patches and so on, because I haven’t found an easy way to be made aware of responses or incoming patches.

IIRC it was 15 years ago that China wanted to get rid of Winblows. I’ll believe they have gotten rid of it once they stop saying “planning to get of by”.

I recently had to pin some stuff and it was an annoying experience. Now I have to check this out…

Federated git forges can’t come fast enough. Fuck gitlab for so willingly dropping the ball

I’ve used. It works well enough. They supposedly have CI but either it’s not documented or nor ready, I can’t tell.

And there’s no way to get notifications of merge requests, comments or anything actually, so it serves well as a backup or private project host, but not much else, IMO.

It’s old Github UI