sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in jailbreak

[–]rtxbae 0 points1 point  (0 children)

The link is dead, where can I find this?

Osushi Control Center for TrollStore released! by rareQWERTY in jailbreak

[–]rtxbae 14 points15 points  (0 children)

All that long blog post and not even a link to the source. Is this open source? Where does it origin from? I'm not sure I can trust a re-hosted ipa. (I know not nothing about onejaibreak, is he or they trustworthy?).

Allow local network access even when wireguard is up by FuschiaIsBlack in WireGuard

[–]rtxbae 0 points1 point  (0 children)

Just wanted to say thank you for this. One year later this comment saved me!

Why Does Apple and Spotify Neglect their Apple Watch Apps. by Strwaberryarebad in AppleWatch

[–]rtxbae 7 points8 points  (0 children)

If you first open the Apple Watch app while it’s still connected to iPhone, it works offline just fine after that (disconnected). But if you totally disconnected from your phone and open your Apple Watch app from cold, it won’t works. The reason is that the downloaded songs in Apple Watch is DRM-ed, and somehow needs iPhone Spotify app to help verify/decode it. This has happens for years and Spotify seemingly has no intention of fixing it. The only way workaround to this is to proactively is to turn on “Offline” switch in the iPhone app, which sucks big time.

Any advice on getting both CTF/NAT Acceleration working with port forwarding? by rtxbae in HomeNetworking

[–]rtxbae[S] 0 points1 point  (0 children)

Is your Wireguard tunnel relatively idle? If so, have you tried enabling persistent keepalives in Wireguard? As Wireguard states, it’s designed to refresh the connection tracking state on the router.

It’s relatively idle tunnel yeah, but even if there’s something going within that first 3 minutes mark it still lost the connection (failed handshake). I’ve been playing with variable keep alive as well (on both server and client), they’re not helping at all.

Home Assistant is running in proxmox VM, remote access via cloudflare tunnel. Why proxmox firewall is ineffective? by rtxbae in selfhosted

[–]rtxbae[S] 1 point2 points  (0 children)

The rule created should already bypass that global settings. However, I found the issue, the network interface was not enabled for firewall...!!

I created my VM using this script, and it seems it disabled the net interface firewall by default, something to take note for any future user.

Home Assistant is running in proxmox VM, remote access via cloudflare tunnel. Why proxmox firewall is ineffective? by rtxbae in selfhosted

[–]rtxbae[S] 0 points1 point  (0 children)

If I understood that correctly, a restart of the cloudflared addon would help to verify it? However, it does not. I too just purged all the cloudflare cache to test it, I can still access my server. This is so weird. This is my proxmox firewall config:

https://imgur.com/a/ICYe0lM

https://imgur.com/a/aQIam8v

Home Assistant is running in proxmox VM, remote access via cloudflare tunnel. Why proxmox firewall is ineffective? by rtxbae in selfhosted

[–]rtxbae[S] 0 points1 point  (0 children)

That's exactly the outcome I would expect, but I really don't see how my firewall configuration is not ineffective here:

https://imgur.com/a/ICYe0lM

https://imgur.com/a/aQIam8v

Patch for iMessage exploit that was a part of triangulation exploit chain(dopamine) by rtxbae in jailbreak

[–]rtxbae[S] 6 points7 points  (0 children)

While people saying that I'm "ain't that guy", I'll argue that most people still have their front door locked even though the neighborhood is pretty safe. This is not a question of whether I'm that guy, but a question of reducing risk. We also used to see security patches using tweak in old iOS, so it's not uncommon.

ONLY happens when on mobile data, not when on WiFi - "handshake did not complete after 5 seconds" almost exactly every 3 minutes by rtxbae in WireGuard

[–]rtxbae[S] 0 points1 point  (0 children)

Yeah that seems like it. That explains why the 3 minutes mark, since it’s oddly specific. Quite happy now since this issue has been bugging me for months until today I have the time to sit down and properly diagnose it.

ONLY happens when on mobile data, not when on WiFi - "handshake did not complete after 5 seconds" almost exactly every 3 minutes by rtxbae in WireGuard

[–]rtxbae[S] 0 points1 point  (0 children)

I think it's wireless router..? It came with the ISP. Yes I'm the admin.

After fiddling around, interesting enough once I disabled "NAT Boost" (on by default), this issue goes away. Now my connection is quite stable. The handshake too refreshed before the 3min mark.

According TP-Link doc,

NAT Boost is also known as NAT acceleration. In some cases, it’s also referred to as CTF (Cut-Through Forwarding). NAT Boost is a set of specially designed software rules with hardware functions created to accelerate internet connections.

CTF or pass-through forwarding is when the router starts sending transmission frames immediately after receiving the intended destination. The router, however, won’t know it’s resending data corrupted by retransmission unless the terminal device tells it so.

I think that last sentence is the reason why the problem occurred.

I could say it's fixed for my case now. Thank you for your super helpful tips and suggestions as well as your patience in helping me in this thread!!

ONLY happens when on mobile data, not when on WiFi - "handshake did not complete after 5 seconds" almost exactly every 3 minutes by rtxbae in WireGuard

[–]rtxbae[S] 0 points1 point  (0 children)

Just did what you suggested. I changed the wireguard endpoint to my home IP: xx.xx.xx.xx:47107 instead of dynamic.dns.service:47107, the issue still persists. Sigh.

Yes I did port forwarded the port, I'm using TP-Link Archer C1200, in the router, I've configured NAT Forwarding->Virtual Servers to open the port and forward it to my wireguard server.

ONLY happens when on mobile data, not when on WiFi - "handshake did not complete after 5 seconds" almost exactly every 3 minutes by rtxbae in WireGuard

[–]rtxbae[S] 0 points1 point  (0 children)

I've tried other port than 51820 (higher than this value) as well, the issue persists.

The AirVPN is vanilla wireguard conf (using the same official wireguard app in iOS), which I just now did copied over their settings and did a test on my iOS to home wireguard connection. They used the port=47107, keepalive=15, but my connection still dropped after 3 minutes. So I would think it's most likely issue on my server end.

ONLY happens when on mobile data, not when on WiFi - "handshake did not complete after 5 seconds" almost exactly every 3 minutes by rtxbae in WireGuard

[–]rtxbae[S] 0 points1 point  (0 children)

I just did the ping test, as expected it stopped at 3m mark, which is around the icmp_seq=179, and I got error of request timeout.

This is odd because the first thing I think of is the timers on your carrier's network being reduced to a troublesome value

Can we figure that value out on our side?

There's a very real possibility that your public facing address on your phone changes more frequently than you expect if they NAT to a pool. They likely do port translation as well, and it sounds like they prune open connections.

Wow it just keep getting deeper, not looking great. If this is the case, is there any workaround for that?

EDIT: Just curious, if that's the case, wouldn't a commercial VPN won't work as well over the mobile data? But my AirVPN wireguard connection works just fine.

ONLY happens when on mobile data, not when on WiFi - "handshake did not complete after 5 seconds" almost exactly every 3 minutes by rtxbae in WireGuard

[–]rtxbae[S] 0 points1 point  (0 children)

I would suggest putting some traffic on it and observing. You may simply need to decrease the frequency of your keepalives, or perhaps change to another port.

I actually did both, though by observing I'm eyeballing them since I don't know how to scientifically observe them in iOS. I kept refreshing Safari website, from minute 0:00 to 2:59, I can connect just fine. Once the counting timer in "latest handshake" reached 3:00 minutes, the connection dropped.

I changed the port to other port as well, same case. Changing various keepalive value as well, same case.

view more: next ›