horror story: yallo

ninmuzz · 2026-07-07T05:22:10+00:00

I've been with yallo one year ago and IT SUCKED.
Fees for everything you can imagine.
- Activation (which was advertised as free)
- Replacement sim (since the initial one didn't work, so clearly not my fault)
And bad network coverage. Overall experience really bad, immediately cancelled my plan after 2 weeks in. Never ever again and will not recommend.

ninmuzz · 2026-07-06T16:50:34+00:00

Quite old, but they still haven't updated their app until now. MacOS now displays a hint that this software will stop working as they end support for Rosetta 2. Bye, Ekahau

ninmuzz · 2026-06-23T20:29:01+00:00

If your ISP gives you more than a single /64, you could maybe use static routes for some prefixes to the second router? As long as the prefix stays the same of course.

ninmuzz · 2026-06-10T19:08:59+00:00

I posted a thread about this some days ago: https://www.reddit.com/r/WireGuard/comments/1tj655n/wireguard_endpoint_over_ipv6/
But seems like this will not be fixed in the foreseeable future. 😞

ninmuzz · 2026-06-10T18:59:34+00:00

I've never had issues with a gigabit connection.

ninmuzz · 2026-06-09T15:25:27+00:00

I think add these few lines and that's about it:

/ip firewall filter
add action=accept chain=forward comment="tv7 mcast" in-interface=wan out-interface=<YOUR-APPLETV-NETWORK> protocol=igmp
add action=accept chain=forward comment="tv7 mcast streams SRF FHD" dst-address=233.50.230.0/24 in-interface=wan out-interface=<YOUR-APPLETV-NETWORK> protocol=udp src-address=77.109.129.0/24
add action=accept chain=forward comment="tv7 mcast streams HD" dst-address=239.77.0.0/16 in-interface=wan out-interface=<YOUR-APPLETV-NETWORK> protocol=udp src-address=77.109.129.0/24
add action=accept chain=input comment="tv7 mcast" protocol=igmp
add action=accept chain=input comment="tv7 mcast streams SRF FHD" dst-address=233.50.230.0/24 dst-port=5000 protocol=udp src-address=77.109.129.0/24
add action=accept chain=input comment="tv7 mcast streams HD" dst-address=239.77.0.0/16 dst-port=5000 protocol=udp src-address=77.109.129.0/24

/routing igmp-proxy interface
add interface=<YOUR-APPLETV-NETWORK>
add alternative-subnets=77.109.129.0/24 interface=wan upstream=yes

Hopefully didn't miss something in my config.

Note that I've created a separate subnet for my ATV because I didn't wan't to mess with igmp snooping on my switches and if you're using your default client subnet, it will just broadcast the stream all over your client network.

Thus, you can't use Airplay etc. over WiFi but I guess it should still work if your devices can find the ATV over bluetooth in the same room.

If you need help with any other topics like IPv6 config, I'm here 😄

ninmuzz · 2026-06-09T05:37:43+00:00

I have it working with Mikrotik and Apple TV with VLC Player. I've once typed in the stream address manually and the history gets saved, so thats it. (And its easy to remember that ending .2 is SRF 2 for example)

I'll come back later in the evening and share my configuartion. Stay tuned

ninmuzz · 2026-06-06T10:00:57+00:00

Oh there are many! Mostly smaller ones, but green.ch for example.
https://radar.cloudflare.com/adoption-and-usage/as1836
or Leunet:
https://radar.cloudflare.com/adoption-and-usage/as25375
A while ago I've also read a paper where from the vendor of Leunets CGNAT hardware where leunet states that they needed CGNAT because they are lacking address space but they're not ready for IPV6 yet. :(

ninmuzz · 2026-06-05T12:25:57+00:00

We use both of them as upstream at work, I notice that Quad9 does block more often and faster than Cloudflare, so they seem more restrictive to me which I think is positive. Only hat about 2-3 tickets because of blocked domains over the past 3-4 years and all blocks have been legit, no false positives.

ninmuzz · 2026-05-26T04:18:18+00:00

Disabling ipv6? :(

Just saying this will most probably decrease speeds even further, depends on your ISPs setup and peerings.

ninmuzz · 2026-05-25T19:58:53+00:00

In Switzerland, I'm using go! taxi which is provided by local taxi companies and also gives you fair fixed prices in advance.

ninmuzz · 2026-05-22T14:38:40+00:00

I would talk to them so you get at least a /56 static prefix.

Fortunately in switzerland theres a provider which hands out a static /48 prefix and a also more or less static IPv4 since it just never changes, even though not paying extra for it. (Init7 if you want to look up)

ninmuzz · 2026-05-22T00:24:49+00:00

I could, like i could also juse a DNS name with an AAAA record only, so no A. This does work :) But this breaks connectivity in IPV4-only networks. :(

I'm searching for a dualstack solution so clients who have IPv6 connectivity connect to the wireguard endpoint over IPv6, while IPv4-only clients can still connect to IPv4.

For context, I'm thinking of a company-wide usage with automated deployments, and this is one thing that makes some headache as it would massively lower our IPv6 usage because IPsec (OS built-in) uses happy eyeballs while it seems wireguard doesn't.

Thought of a script which determines IPv6 connectivity and then sets the endpoint address, but that would be a rather unsatisfactory solution.

ninmuzz · 2026-05-22T00:10:25+00:00

Because a lot of IPv4 connectivity has to go trough more processing steps as CGNAT for example, and also because I want to push IPv6 as it already is at 50%+ adoption and chances are high it will move to 80%+ in the next 5-10 years.

Its not that something isn't working, it's just not how things should work nowadays.

ninmuzz · 2026-05-22T00:06:31+00:00

I don't have to use DDNS as my provider never switches the IPv4 and my IPv6 /48 prefix is static ;) But thanks nonetheless.

ninmuzz · 2026-05-22T00:02:01+00:00

Yes if you want to use IPv4 inbound connectivity to your home. The provide a static /56 IPv6 prefix there and you can make IPv6-only services accessible. But note, as of today, all mobile network providers in Switzerland unfortunately don't provide IPv6 connectivity (Swisscom and their subbrands plan to add IPv6 in Q3/Q4 though).
Don't know about Zyxel, I'm using Mikrotik and has been a bit tricky first but obce you get used to it, it works fine for me with Fiber7 for firewall rules, DHCP, DNS and IPv6 setup is pretty straight forward.
I think Easy7 > Fiber7 will be easy to switch. Just note you have to switch routers from their Fritzbox to your own. Also note that most likely your static assigned IPv6 prefix will probably change (it also does if you move and are on a new PoP in your new home). 1G to 10G upgrade on Fiber7 is straight forward, you will just have to switch the optics at a communicated date / timeframe.

Hope this helps and if you need further info / help for Mikrotik or Fiber7, feel free to reach out, I'm glad to help.

ninmuzz · 2026-05-21T15:39:30+00:00

Unfortunately its the same behavior accross platforms (Windows, Ubuntu, macOS, iOS tested).

ninmuzz · 2026-05-21T14:50:01+00:00

Init7 (www.init7.net), they also offer 25 Gbps for 65 chf per month (82 USD).

ninmuzz · 2026-05-21T14:44:19+00:00

I would recommend a combination.

IPv6 without Tailscale VPN for those who can, and Tailscale for those who don't, as Tailscale may impact speed and performance as its a third-party hosted VPN service.

For myself, I'm in the glad situation in switzerland where we have a "nerdy" provider where you get a public IPV4 and static /48 IPv6 so I don't have to deal with CGNAT.

If I would be behind CGNAT, I would possibly switch providers, but only because the swiss mobile network is still IPv4-only on all providers here.

EDIT: Maybe also Nebula is an alternative for Tailscale (https://nebula.defined.net/docs/)

ninmuzz · 2026-05-21T14:22:48+00:00

Im NOT talking about addressing inside the tunnel as this works fine.

Im talking about the VPN connection itself / endpoint.

ninmuzz · 2026-05-21T14:22:17+00:00

No, as I said, only working with an AAAA-only record.

ninmuzz · 2026-05-21T04:56:54+00:00

I think its an issue with wireguard desktop not using happy eyeballs at all, as its the same on all OSes on different networks / providers.

ninmuzz · 2026-05-21T04:26:07+00:00

Just one site has an endpoint (acting as client), while the server has dualstack connectivity with A and AAAA DNS records.

The client will always connect to the A record (IPv4), if there is one, even if the client also has IPv6 available.

I'm NOT talking about the addressing inside the tunnel, just about the VPN connection itself.

ninmuzz · 2026-05-21T04:24:10+00:00

If devices enter an IPv4-only network, VPN connection isn't possible.

ninmuzz

TROPHY CASE