It’s more important to get that dmesg output AFTER an event happens, but before a reboot. What you’re running doesn’t matter much unless you have live metrics of their behavior or resources.
It’s more important to get that dmesg output AFTER an event happens, but before a reboot. What you’re running doesn’t matter much unless you have live metrics of their behavior or resources.
There isn’t one.
Stick to the best brands out there that have been benchmarked.
Need logs to be able to tell you much. Get some output from dmesg after it happens, but before a reboot. Syslogs couldn’t hurt. Maybe setting up a metrics exporter to another machine could give you a peek into what is happening with resources.
Also give some details about OS and what you’re running on it.
Didn’t realize we all were now incapable of looking out the window. That seems like something an absolutely incapable person would do because they’re way too lazy.
IPFS is like a dead Multiplayer game, or an Onion network. Check it out.
Matter itself is different from data passing through HA.
Lol. You checked on IPFS lately? Different times. Different world.
Tell me what I’m misunderstanding here.
Metadata is supported in any HA supported protocol. Your concern is what?
*but relies on IPFS.
Useless.
EFI bootloader won’t have this problem. Adjust accordingly, and things will be fine.
I very much did. Read up.
Because IRC doesn’t “work fine”.
It’s a 50-year old solution to no modern problems where everything about it has been solved in better ways.
I don’t think anyone still recognizes this wisdom you seem to be all about.
Enlightening us with that wisdom would be beneficial to everyone, no?
My point exactly. There are easier and better ways of doing this dated interaction.
Nope. Just ports and an A Record.
Yeah, but again…habit and effort.
I can’t think of a single reason that IRC is still used except for people being too lazy to adopt something else.
DNS A record points to an IP destination. Ports are then handled by the requests for a specific port thing.
Example: A record for www.dududu.com points to IP 1.2.3.4, but different service ports are listening there to pick up different traffic.
The issue is more likely to be your port selection and UDP being discarded on networks with captive portals that generally only allow certain ports and traffic. Try using some other common UDP service ports like 53/DNS if not already in use, or maybe 5060/SIP, or even other common VPN ports.
Unless they’re running L7 hardware in the hotels, I doubt they’re doing any kind of packet inspection.