u/llondru-es

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?

I have a dual wan setup (WFH) with two fiber provider

- Provider A : 300/300mbps, public ip, ipv4 only
- Provider B : 500/500mbps, public ip, dual stack ipv6 + ipv4

I set dual wan as load balancing with provider A with 80% weight and provider B with 20% weight.
I also have 3 devices that go through policy-based route so they connect always to Provider B

My goal is to distribute the traffic as evenly as possible through the 2 providers, considering that in a dual stack setting, ipv6 servers will prioritize ipv6 and using provider B.

Is this the right approach?

For the last 30 days, provider A got 443 gb of traffic and provider B got 528gb, so it seems I'm more or less close on the goal.

Unfortunately Unifi doesn't provide statistics for ipv6 and ipv4 traffic, so I feel I'm doing this a bit blindly.

We are ending today a 15 day itinerary through France (from Tolouse to Normandy and back) and here is a list of tips to survive heatwaves in France / Europe and other general tips on things we did well:

- Have an early start: no need to leave the hotel at 6am, but starting your day between 8-9am will enable you to explore a city/region as shops and attractions open, and be done until 11am

- Have early lunch: all restaurants open at 12pm; it's less rushed, quicker service, and you will get needed shade or air conditioning.

- Go to the hotel after lunch and get a nap. Rest. Make sure beforehand when you book your hotel that it has air conditioning: not all do. We only had a hotel without A/C and it was hell to sleep

- Hydrate yourself A LOT. Our strategy was to use GOOD insulated bottles that easily keep your water fresh for 12 hours, and refilled them in meals with 'carafe d'eau' : all restaurants provide free, cold water, unlimited refills, so we used that for our insulated bottles. Buying them in city supermarkets like carrefour allows you to save A LOT of money compared to what they charge you at vending machines / tourists spots. I have been charged 4€ for a single 50cc water bottle with no alternatives, whereas I got 1l bottle in carrefour for 15c.

- Don't be afraid to stay at your hotel for the evening: central hours are very tough: leave at 6-7pm: heat starts to decrease, and summer evenings are long so you have a lot of time to explore a city/region. Be mindful though that most tourist attractions close at 6pm and restaurants will do at 9-9.30pm so plan accordingly

- Lastly don't be afraid to change plans: there are always alternatives. Slow down and enjoy things as they unfold!

Happy travels!

Just finishing our family roadtrip and I just loved using the UTR for the first time.

- 7 hotels, all of them with wifi captive portals.

- Entering the room, plugging the UTR on the most unuseful outlet (normally by the desk/tv)

- Joining wifi network and logging to captive portals had no issues. A couple of times I struggled reauthenticating after 24h (yes, I hate that hotels do that) but could solve it in 5 mins.

- Loved having the family having internet without asking what to do. They wait a couple of minutes, and that's it. No logging into memberships, providing multiple emails etc..

- Only struggled with stable connection in one specific hotel, as Rukus AP was in the corridor (yuk!) and it seems UTR doesn't work well with weak signal (around 75dbms). Solved it by literally plugging the UTR at the outlet om the room door and on the door handle.

- In another hotel connection dropped every 30 min. and I attributed to some wierdness with the hotel wifi, as when it dropped, I didn't find the SSID for the hotel wifi either

- Worth knowing: UTR acts as a repeater: meaning it uses EXACTLY the same channel and bandwith as the wifi uplink: if it is connected to channel 56 @ 20mhz, then the UTR wifi will be exactly ch 56, 20mhz

- No issues being wifi5, hotels don't usually offer high speed connections, so I didn't have more than 20 mbps anywhere.

- Compared to a cheap gl.inet travel router I bought many years ago, it was night and day: UTR was easy to set every time, provided a consistent connection, and overall got to accomplish its function successfully. For the price of two meals or less, it got the job done

I have been poking at Claude for the last hour to troubleshoot the following, and I just want to make sure its not hallucinating and I got the answers right

I have a Double wan setup:

- WAN 1: IPV4, no cg-nat, wireguard server set and working.

- WAN2: Dual stack : IPV4 with cg-nat + IPV6 -> trying to set a wireguard server.

Issues:

- DDNS did not resolve on wireguard client

- When using the ipv6 address instead of the ddns domain, it failed handshake with the error: write udp [::]:42472: sendmsg: network is unreachable

The client I'm trying to connect is on a mobile network that is only ipv4.

So if I understood correctly, I cannot connect to an IPV6 address from a IPV4 network, right? Also, I cannot connect to IPV4 directly, as I'm directly behind cg-nat. So the only option is either to ask to be out of cg-nat or use tailscale?

Just need to confirm I'm in the right track here

Trying to do some seasonal challenges with the NSX and was going crazy because it didn't accept them while driving with it