u/llondru-es

Anyone facing this issue? User is my wife, she was going crazy, and we troubleshooted today to rule out networking issues. Same page with Safari loads crazy fast. Chrome is unusable at times.

Just finished my last pending challenge: 3 Stars on the Hakone Nanamagari Drift Zone.

What else is to do now, besides the seasonal challenges?

Not a big fan of online play.... is this it then?

Planning to give the laptop for a second life. No battery: original went spicy pillow, and replacement the same thing after less than 1y, so not planning on buying another one.

The thing is: without battery, it seems bios doesn't save any of its settings : should I replace the CMOS battery? It's a bit of a hassle, as it's in the back of the mobo, so you literally need to disassemble EVERYTHING

https://www.dell.com/support/resources/en-ke/3dviewer/cb090159570000202a/how-to-replace-the-coin-cell-battery-on-a-xps-9570

Also I'm not sure what type of battery is it and if I can buy it easily online.

I'm 47, and it will be the first I get to live this (and probably the list).

Planned a day out -2h car drive, meal, and then wait for a bit-

I expect traffic to be epic, so anyone travelling by car, please be patient and don't wait until the last moment to get to your final location

I bought this laptop in 2018, and it has come to its end of life:

- Changed twice battery, and it's a spicy pillow again.
- Thermals are horrible, I have cleaned it many times, even repasted the whole thing a couple of times over the years, and it's like a hurricane when having a bit of o load.

Any ideas other than scraping parts? (SSD) ... it's not bad specs for its time, but I really haven't like the thing since I bought it.

CPU: i7-8750h

RAM: 16gb DDR4 (2666Mhz)

GPU: GTX 1050 Ti

Note the "trying"

I cannot see to connect EVER to any event.

Are there not enough players?

Are servers saturated?

It's a bit frustrating, specially when you cannot finish all the seasonal events.

Anyone else with those issues?

Was trying to do some work yesterday by connecting to my PC from a macbook in a public cafeteria.

I connected to home via wireguard , no problem.

But when trying to reach out my PC from the internal network, I got no answer. I realized that going to 192.168.1.1 got me the cafeterias gateway, instead of my own router.

I poked Claude about this, not expecting to solve it, but suprisingly, It did. Now I want to understand why this happens and how is the fix working, for my own education. I also don't want to go to the proposed solution route (change the ip range) as I have a lot of stuff set with statics ips, and don't want to mess up for occasionally connecting from a random cafe.

Claude's response and fix:

>That settles it — the café gave you 192.168.1.134/24, so the café LAN is 192.168.1.0/24, identical to home. The collision I flagged in my first message is real after all; the earlier netstat was just a partial/momentary snapshot (it didn't show the en0 connected route). And since ping 192.168.6.1 works, your tunnel is healthy — so this is purely the subnet-overlap problem, nothing wrong with WireGuard.

What's happening now: your Mac has a connected route for the whole 192.168.1.0/24 pointing at en0 (the café), because that's the network your DHCP address sits on. WireGuard's 0.0.0.0/0 only installs /1-width routes, which are less specific than that /24, so every 192.168.1.x address — including your NAS — leaves via the café instead of the tunnel.

Immediate fix, works right now. Add a /32 host route for the NAS. A /32 is more specific than the café's /24, so it wins and forces that one address into the tunnel:

sudo route -n add -host 192.168.1.5 -interface utun4

Then ping 192.168.1.5 should answer, and the NAS UI should load. Repeat the line for any other home host you need (your computer, etc.).

Two cautions:

Don't do this for 192.168.1.1, and don't route the whole 192.168.1.0/24 into the tunnel. WireGuard reaches your home's public IP through the café gateway, and that path lives on this same subnet. If you swallow the café's /24 or its gateway into the tunnel, you'll break the WG handshake at the next rekey and drop the whole connection. Per-host /32 routes are surgical and safe; a blanket /24 is not.

These routes disappear on reconnect/sleep, so it's a patch, not a cure.

The actual cure is still renumbering your home LAN off 192.168.1.0/24 (from message one) — move the UCG-Ultra's LAN to something like 10.73.42.0/24. 192.168.1.x is the single most common consumer default, which is exactly why you keep landing on a café that uses it too. Renumber once and this stops happening at every café, hotel, and airport, with no host routes to babysit.

Was trying to use the UTR in a cafeteria yesterday, and SSID was not visible in wifi uplink.

In Wifiman it appeared as a wifi 7 mlo network.

Is there an incompatibility with the utr's wifi5? I thought the wifi standards were retrocompatible?