The fix was easy: Prune the branches. than
>The fix was easy: upgrade our hardware. We replaced our old 802.11g devices with new 802.11n ones, which took advantage of new magic math and physics to make signals more resistant to interference.
The rain would move branches out of the way.
This is why experience helps. Good life and professional experience helps to short circuit many problems.
same computer did not start if any of its metal surfaces touched the wall, but that might have been a electrical leak - thankfully i do not live at that dump still
http://d.hd.org/anecdotes.html#NFS
TL;DR: kinked fibre causing large (NFS) packets to fail frequently in one direction
This also taught me that if I have wifi issues, I should do a tree search
/s
- Car allergic to vanilla ice cream: https://www.cs.cmu.edu/~wkw/humour/carproblems.txt
- Can't log in when standing up: https://www.reddit.com/r/talesfromtechsupport/comments/3v52p...
- OpenOffice won't print on Tuesdays: https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/255161...
This reminds me of a recent issue I had. I had just gotten a new laptop from IT. While picking it up from them, I had generated myself a password, put it in my password manager on my phone, and then entered it twice to set it on the laptop. Everything worked great. But when I got back to my desk, the password didn't work! I tried a bunch of times, watched myself hit each key to eliminate typos, etc.
I went back to IT and they asked me to demonstrate. But this time it worked! I walked back to my desk, thoroughly embarrassed. But a couple hours later I had to log in again and once again could not.
After thinking about it for awhile, I realized that I was typing at IT while standing over a sitting-height desk. Sure enough, typing in that position fixed my issue. I carefully watched what I was doing this time - something about the exact layout of the keyboard and the weird angle I was typing at ensured that I was making a particular typo I typed in that position - just a single letter switched to another, every time. Sure enough, making that one substitution to my intended password got me in.
If it's a key that you may not often type and one that is often transposed between regions, the fact that the entered char is not shown can lead to frustration.
e.g. " and @ are in different positions in UK vs. US keyboards. So user thinks they are typing @, but " goes into the box.
Almost felt like a bug in error correction loop in my brain, or maybe more like an unconsidered edge case.
- Putting the car in reverse sets off the neighbor's home security system. https://www.reddit.com/r/cars/comments/7k12fs/neighbors_hous...
Office chairs are turning monitors on and off.
This is actually officially documented on the DisplayLink website as well: https://support.displaylink.com/knowledgebase/articles/73861...
And my personal favorite, "more magic": https://web.archive.org/web/20260103114654/http://www.catb.o...
https://old.reddit.com/r/talesfromtechsupport/comments/cp48t...
[0] https://www.jakepoz.com/debugging-behind-the-iron-curtain/
My grandmother's house is adjacent my parents' w/ 200 ft. between and line of sight. Back in 2013, when my grandmother moved into the then-new house, I setup a point-to-point wifi bridge between them to share my parents' Internet connection and give me easy remote support access to grandma.
Summer of 2023 visiting relatives complained the Internet service in grandma's house was slow and unreliable. There were repeated suggestions made by helpful relatives for purchasing a new WiFi router for her house, getting independent Internet service, etc.
Grandma was happy with it, and the relatives went home, so I put off looking at it. When I did finally look at it, months later (when I went over for Thanksgiving) everything seemed fine.
When the relatives came to visit in summer 2024 they complained again. I looked at it immediately and found massive packet loss on both ends.
The ornamental trees planted along the driveway between the houses were the culprit. With the leaves off (say, at Thanksgiving time) it was fine. When the relatives came to visit in the summer the trees were in full leaf and acting as very good attenuators.
The trees were newly planted when grandma moved in. I didn't even think about them getting bigger and fuller when I set up the link. They filled out in the 10 years intervening, though. (Chalk it up to me still being relatively young and not thinking about installations on 10+ year timescales when I put it up.)
Fortunately there's a room in her house with line of sight to my parents' house unobscured by trees. It meant putting the radio outside a bedroom window instead of the attic (where I'd originally stashed it), but it solved the problem and ended complaints from relatives.
My PC and the roku device were both wired to two different ports on a router (iirc an Edgerouter X running openwrt at the time). This didn't repro when the roku streamed other services (hulu/youtube tested), only netflix. This also didn't repro if the roku was connected over wireless (connecting to an AP wired to a different port). Just opening netflix also didn't repro, the roku had to be actively streaming a netflix video.
I never ended up solving it, I just worked around it by making the roku connect over wireless.
It did take me forever to figure out the problem though. For a long time I'd be in one room getting frustrated with my computer while someone was innocently watching netflix in the other room.
I recently purchased a Banana Pi 4 with the 802.11be Wi-Fi 7 module to be used as an access point. It generally works well as an AP and I'm getting full speeds. However, for some reason whenever I try to communicate directly with the router/firewall (separate device on the same network) through this AP, it will intermittently drop 3/4 packets. It only happens when communicating with the router/firewall device, and only over the wlan interface on the bpi-r4. I have a similar AP setup on another embedded system (PCEngines APU2) and this has never been an issue.
I suspect there's some sort of bug with the internal 4-port switch of the bpi-r4 not playing well with the wlan interface when they're all bridged together, but digging through the logs hasn't revealed anything obvious.
It's driving me nuts!
There’s a video on YouTube about this somewhere and we were able to confirm their findings.
"Oct 2: Warning: Due to a known bug, the default Linux document viewer evince prints N*N copies of a PDF file when N copies requested. As a workaround, use Adobe Reader acroread for printing multiple copies of PDF documents, or use the fact that every natural number is a sum of at most four squares."
I've seen other references to this bug, but the workaround is the sort of thing mathematicians would come up with.
sources: https://mathoverflow.net/a/3601/143, https://math.berkeley.edu/computing/wiki/index.php?title=Sup...
Also worth reading: https://en.wikipedia.org/wiki/Sporadic_E_propagation
I must say, the AI-generated "stock image" doesn't add that much to the article and could be done without, especially when its alt-text contains the prompt.
I tried update my routers, tried to update my notebook wifi firmware, tryed to change the router config, the router position, the router order, the wifi channel, the wifi name and password. Nothing worked. But if I connected using linux, things would work just fine.
In the end I divorced my wife and brought a Thinkpad. She keeped the cat, the house, the routers and that dell vostro notebook.
I keeped the dog and the car.
Either the radios were misaligned and the rain was reflecting it back towards a stable link just enough to improve throughput.
Or
The rain took a bad link all the way down, failing over to a different link.
Or
The rain/wind was moving an obstruction.
I have about a million of these stories sadly.
"The internet goes down on tuesdays"
Crane.
"The internet goes out in the morning"
Temperature inversion.
The old classic, I think it turned out that in hot weather the fuel line vapour locked a few minutes after turning off, and the ice cream was at the back of the store, and took just long enough to walk there and back to trigger the issue.
I tried both with neutral or in gear but with the clutch pressed (yes, it is a manual, fairly common in Sweden still) and that doesn't make a difference.
I haven't managed to figure out the cause, but since it is a modern car I would assume it is something with the ECU that goes wrong. (It is a Dacia Duster in case anyone else recognise this issue. The mechanic I asked hadn't heard about anyone else having this issue though.)
How was that not the first thing to be checked ? OP must have hit themselves over the head for not thinking of that one sooner
I'm a very technical person, and would be considered "smart". A few weeks ago, the TV remote was acting up. I changed the batteries, still happening. Restart the TV, still happening. The mobile app is working fine, I'm wondering if there's a fault on the IR blaster. Use a camera to check the IR blaster on the remote, seems fine. Factory reset the TV, still happening. Take the TV off the unit, pull out back of the TV off, solder to IR blaster looks ok. Put it all back together, still happening. Phone samsung, and go to make a coffee while I'm on hold. Come back, it's working while I'm on hold. Total time, 4 hours at this point.
Turns out, I had put a coffee cup in front of the receiver that morning, and unluckily put it back when I lifted the TV down from the stand...
Easiest solution: permanently point a good case-fan-sized USB fan on to the unit, using its own USB port.
Directional antenas are far from directional, they pick noise from everywhere.
In my opinion rain reduces that noise, and if the point to point has more than enough signal margin to keep operating at full speed, it ends up improving the link.
Something like horse blinders.
- Just rain == good internet
- Just cold == good internet
- Cold + rain == bad internet
After a lot of head scratching the provider finally sent someone with a ladder to climb the poll. What they found was that the protective boot on the coax connection was bad. When it rained for a while water would seep into the coax connector. By itself this wasn’t too bad, but if it was also cold outside it would freeze. This would then force a gap between the threads of the socket and the cable, breaking the ground connection.
Previously, the connector had been replaced, but nobody had noticed the torn boot. This tech replaced both the connector and the boot and the problem was solved! It honestly was the best interaction with the cable company I have ever had. Only returning their hardware when switching to fiber felt almost as good.
Eventually got fiber.
Discussion then: https://news.ycombinator.com/item?id=39896371
Related:
We can’t send mail farther than 500 miles (2002)
> I wonder how much polarization affects things; I was once told that terrestrial FM Radio is transmitted with vertical polarization to reduce interference from tall objects between you and the transmitter.
> Terrestrial TV (some of which used bands that overlap FM radio) uses horizontal polarization.
This is only true in the US (and probably areas influenced by US standards). In Europe, FM radio transmissions (and digital television nowadays) tend to be mixed-polarization (circular polarization), except if there are known interference (usually border areas) that would preclude mixed-polarization.
Analog television meanwhile significantly differs depending on your area, which required you to either test which tower and polarity is the best (note that all broadcasts are transmitted at a single tower, unlike in the US), or just... request a map with that data.
After hours and hours of iterations I could get it to work perfectly, just once, for each cartridge. I would clean it a bit more, try a game, things would work great. I’d try another game and it the copyright logo would fail. So I’d clean it up a bit more. Swab the port and try it again. It worked! Then another game… nope.
I eventually realized that the isopropanol was making a weak connection work fine, and then I guess it just kept working once power was flowing.
No matter what I tried I couldn’t get it to stay fixed, so I keep a handful of cotton swabs and a small dispenser of isopropanol in the carrying case. I’ll swab a cartridge before inserting it and it works every time.
So now I have a Game Boy that requires alcohol to work.
I installed the antenna in the winter. Everything worked great. In the summer, we lost a few channels. Rain in the summer and hardly anything would come in. The answer I realized, like in the article, is trees. Leaves are already full of water so they are good at attenuating signals. Leaves that are also soaked in rain doubly so.
I'm surprised WiFi can't pass on reliably through branches. Must have been a nightmare back then.
Update: this comment on the original posting of this article suggests so: https://news.ycombinator.com/item?id=39896699
One winter had been so cold I had Cartoon Network and other cable stations available on my terrestrial antenna. When the freezing temperatures ended, I had to buy the cable because I got used to it so much.Unfortunately he hadn't even had it a week when he found he couldn't unlock it, and once he had it wouldn't start. And wouldn't you know it, it was bucketing with rain at 8pm and there he was, stuck outside the swimming pool trying to take his daughter home from her swimming club. Off it went back to the garage on a breakdown truck, while he got a rather lower-spec loaner.
Next morning it was fine. All week it was fine. Until it was time to pick his daughter up from swimming, of course.
This went on for a few weeks until eventually they tracked it down to interference with the remote fob.
Because the swimming pool was at the local community centre, in another room in the community centre was a local radio station, and they started broadcasting at 6pm every week night.
What was the first thing anyone did on coming into the studio? Turn on the UHF link from the studio to the transmitter site, on 428MHz, sufficiently close to the 433MHz receiver for the remote central locking fob to desense it and prevent it sending the immobiliser key to car's ECU.
No, no-one back in Munich believed it either.
That also took a few minutes to debug why this one coworker came back from lunch, plummeted down into his chair, and someone else's screen went out.
I also tend to memorize long (8+ digit) PINs based on the physical layout of the keys, so if I need to enter a PIN set up on a phone-style keypad on a normal keyboard or numeric keypad, or vice versa, I need to visualize entering the PIN on the original input device to remember it.
Snopes covered this one and they cite to an urban legends book from 1989: "Curses, Broiled Again" by Jan Harold Brunvand. Brunvand prints the "vanilla takes longer" version and reports also having a "pistachio takes longer" version printed in a magazine in 1978, which itself referred to another magazine as its source. In the book's version it's a Texas car dealer who's looking into the problem. The same author's later book from 1999 covers the story again and includes versions dating back further, plus a 1992 version which is this one where it's Pontiac and the problem is the vanilla being in a separate case at the front of the store.
In the Pontiac version you can go and pick at various implausible details stacked up together, that Pontiac's president cares enough to send an engineer out, that the engineer is there when the car won't start on the first night but still just comes back many more times rather than looking at the car or presumably noticing that it starts a couple minutes later, that this guy is buying a new container of ice cream every night and never stocking up, that he never takes any other trip where it's a short stop... You can go on each of those and say they do happen: like presidents and CEOs do sometimes go digging deep on random problems customers put in front of them. But if you look at the whole thing I think you need to recognize it as a piece of storytelling, not fact.
Maybe there's some kernel of a true story in there, but if so it's probably a pretty small kernel. Anyway it doesn't matter much: it's just a fun story that teaches a little lesson so people like to share it around.
Side note: helping my French housemate with his uni assignments was an experience, none of the symbols were where I expected them to be
I've used US keyboard layout since I started programming (my first mentor essentially forced me to switch to it, he was right about it being easier), but throughout the years been using Swedish, Norwegian, British, Spanish and French physical keyboards, never cleanly mapped to the actual layout I've used on the OS, and never been an issue.
The last part though, is a real one, trying to pair program with Spanish programmers always have at least one moment of holding Shift and sliding the finger across all numbers to see where that specific symbol actually is.
(Side note: those are not a and o with diacretics, they are entirely separate letters in the alphabets of the Nordic countries, with entirely different sounds.)
When I took a look at it, it turned out that his (proprietary) wireless USB adapter for the mouse was very close to the band of the noise of the microwave. The microwave was also not properly grounded and shared a circuit breaker with his room, as apparently the kitchen was formerly larger and then split into two rooms by the landlord.
That was quite funny seeing that problem happen in action, he was always joking about a ghost in the machine, and I was joking about him being radiated by his microwave.
The cool part is years later in University one of my commilitones told me that his mouse stops working when the fridge turns on. The first thing that I checked was whether or not there's noise on the power circuit, et voila, easily fixed.
Long ago there was this case of a factory that pressed desks out of steel sheets. Their main press (an absolute monster) had taken someone's arm off and they couldn't find the cause. It turned out that near the roof there was an air conditioning unit that that had a flaky relay in it that drew a gigantic spark on disconnecting, enough to upset the latch that controlled the safety interlock on the press, causing the press to move by itself.
It took quite a while to find it.
Sadly, it's never aliens
https://www.nature.com/nature-index/news/its-the-microwave-h...
I had to disable a 2.4ghz access point a couple years ago because a bathroom had a passive IR detector for the light switch that would never let the light shutoff. Because detecting IR is a pretty weak signal, I guess these switches amplify it. The issue is the circuit also acts as a weak antenna for 2.4ghz and thinks its seeing IR when it's actually just amplifying and seeing the 2.4ghz beacon signal.
RF gets weird. Something I've thought about over the years is how my FM radios at my old house would sometimes pick up aviation radio which should be AM well above a tuned FM frequency. Apparently this is due to the common design being a superheterodyne receiver which comes with a few quirks (such as causing some small interference itself when it's receiving).
I had a Customer complaining about bad WiFi in a conference room. Every time I checked it I had good performance. Eventually I attended the meeting most of the of the complaints related to just to observe.
What I observed was workers from cubes near the conference room microwaving food for their lunch in the break room right across from the conference room.
Such naturally occurring diodes are an interesting phenomenon (in this case: the salt in your sweat interacting with the steel of the strings) and were the basis of the very first radio receivers after the 'Coherer' (which is a word that has fallen out of use so far that it registers as a spelling error on my browser!).
Of course, if you want to build a proper AM receiver you will find that it is quite hard ;)
Same with oscillators and amplifiers. You always get the other one first.
Oh, and it is also very hard not to build a microphone. Except...