Technically it's an IPv4 router once you enable net.ipv4.ip_forward in step 1, the rest is enabling a whole lot of supplementary services and operations not intrinsic to the definition of a router.
Might be a good idea in general to throw out a few preventative iterations of "Your code is broken, can you find the mistake?" before you even bother reading its initial output
Windows NTP client uses UDP port 123 as both the destination and source port, rather than letting the OS assign an ephemeral source port.
Many ISPs (e.g. AT&T Fiber) block UDP traffic with source port 123 to mitigate NTP amplification attacks.
Most people won't notice that problem since low-end consumer routers tend to mangle the source port when they perform outbound NAT. The ISP-provided router will generally do this itself until you enable "DMZ+" or "IP Passthrough" or some similarly-named mode, as home networking experts will typically do so they can manage NAT and firewalling on their own devices.
If a Windows laptop can sync and the wired Windows desktops can't, your wi-fi AP might be doing the necessary source port mangling.
If you add a NAT rule to your router to change the source port for NTP traffic, you should get time sync working.
Yep, humans have had a remedy for the problem of ambiguity in language for tens of thousands of years, or there never could have been an agricultural revolution giving birth to civilization in the first place.
Effective collaboration relies on iterating over clarifications until ambiguity is acceptably resolved.
Rather than spending orders of magnitude more effort moving forward with bad assumptions from insufficient communication and starting over from scratch every time you encounter the results of each misunderstanding.
Most AI models still seem deep into the wrong end of that spectrum.
Isn't the real prize the library of personally-identified samples preserved in their "biobank" and not the methodologies or analysis they've applied to it so far...
I thought the touch bar was even worse than the butterfly keys...
I put off upgrading my personal MacBook for years after work issued me a MacBook with the touch bar. Such a usability nightmare for the sake of eye candy. That was a long seven years.
There was a Lenovo and an ASUS and an Acer in between but those all went in the graveyard pile before their second year was up and I had to keep resorting to the 2011 Macbook.
And that's counting the extra ~year I got out of the Lenovo after having to replace the fans.
Having user serviceable parts is nice but having parts that last 14 years is better. If there was a brand that did both, that's what I'd buy.
I can't concur. Growing up poor, I've only owned the cheapest Acers and HPs and none of them ever died on me. They're still at my parents place chugging along.
Later I switched to Lenovo when I got money and still no issues. Meanwhile all my mates with 2016-2018 era Macbooks have had endless issues, that they swore off ever buying Apple.
Anecdotal stories can swing in both directions, that's not proof of anything.
They are only misleading if you allow yourself to be misled by them. It's an extremely informative measurement if you are aware of how it works and don't misinterpret the results.
None of these claims are mutually exclusive with one another.
"Great tool for misleading results." -> the results the tool provides are either mostly misleading (many are misleading), or are in large part misleading (a large part of each is misleading), potentially both
"Traceroute is easy to be misinterpreted" -> the results the tool provides are easy to misinterpret
"They are only misleading if you allow yourself to be misled by them" -> the results the tool provides require expertise to interpret, implying that otherwise they're (largely) misleading - the same thing the person said right above you
This is turning into a "well I like it and it has its place". Cool, it's just not what was being argued.
Yes, you can. It's basically a terminal case of something being unintuitive. Whether something is misleading is in the eye of the beholder.
Recently my mother felt misled by a car commercial. Her position was that saying things like "under this many years or that many miles" is misleading, because it suggests that it's a set of options she can pick from (which of course ended up not being the case).
Unfortunately for her, this is a natural language construct - whether she understands it correctly or not depends on how aligned her common sense regarding it is with people at large. She understood it differently and thus felt misled. But you may notice that ultimately it was her own mistaken understanding of the common parlance that misled her. So when she said this was misleading the only thing I could reasonably say was exactly this. That I did not find the phrasing misleading, and I'm sorry she'd been misled by it (irrespective of whether that was on her or on the world, as that doesn't really matter).
It's completely on people how they want to handle this. You can find people being misled by stuff like this to be unreasonable and just tell them so, or you can put out a disclaimer regardless. Depends completely per case. This goes all the way to having multiple mechanical interlocks at places with heavy duty xray sources, or preferring machine checked memory management.
Traceroute doesn't use ping requests except with the old Windows binary. Usually it uses "Time-to-live (TTL) exceeded in transit" messages.
Beyond that technicality, your guess is often right... Routers will frequently prioritize forwarding packets over sending the TTL exceeded packets tools like MTR use to measure response times.
Also you can easily have the TTL expired message going via a different route on the return path (and indeed the same applies with your normal connections, asymetric routing can be a pain - especially in networks with rpf issues (multicast ones are a particular pain point), and with stateful firewalls, but most of the time it's fine. You just need to be aware.
Obviously you know, but for anyone else reading, a modern traceroute tool (like mtr) can send icmp, udp or tcp, on generic or specific ports. Indeed the default for mtr on my laptop is to use icmp.
