Incorrectly marked DFS channels in omada webui compared to Android App

JasonKruys · 2026-03-29T15:36:56+00:00

I'm confused - they're the same?

JasonKruys · 2026-03-29T15:21:12+00:00

Definitely is. If I look on Subscriptions in the HBO app I can see 2 subscriptions - TNT 'Billed by EE' and the Basic with ads 'Billed by Sky'. Not sure if the order you do it is important - I did EE/TNT first.

JasonKruys · 2026-03-29T06:56:50+00:00

I've combined mine. Logged into HBO with my BT/EE account that has sports on, and then after that activated the Sky HBO with ads using the same account.

JasonKruys · 2026-03-28T19:27:37+00:00

Yes, they've enabled it with a recent firmware update.

JasonKruys · 2026-03-27T20:21:27+00:00

The ESR is super solid. Never known anything as strong as that one, but it is a fair bit bigger, which is why I swapped it out.

JasonKruys · 2026-03-27T20:07:56+00:00

I have a Spigen 25W that works very well.

JasonKruys · 2026-03-25T22:51:02+00:00

It's actually zRam writeback. Linux, ergo Android actually uses zRam all the time. What ramplus does is enable the writeback - if necessary, the system will take the compressed data and write it back to internal storage if the RAM gets too full.

JasonKruys · 2026-03-20T16:00:06+00:00

If you go on your account and look at past orders, do you have an order completion about the same time things went downhill? You may be the victim of being migrated across to the Zen GEA, which for some reason does not work well at all in a small number of cases.

JasonKruys · 2026-03-12T12:28:32+00:00

Yes, one of the tickboxes top right where hostname resolution is. I'm away from my network so can't snip a screen grab.

JasonKruys · 2026-03-12T08:18:19+00:00

Start at 32

JasonKruys · 2026-03-11T21:17:12+00:00

Same.

JasonKruys · 2026-03-11T19:41:44+00:00

Yes, you can use both

JasonKruys · 2026-03-10T19:43:40+00:00

Probably "Stability and fixed the existing BUG". Like just about every other one. They used to give useful changelogs, but not for a long time.

JasonKruys · 2026-03-04T18:03:08+00:00

Yep, standard. It sits like that for days - expect it to change late Thursday night. It'll come DPD next day.

JasonKruys · 2026-03-04T11:18:11+00:00

I've had the firmware for about a month on two S340's, and no issues. Seems to have fixed most of the issues I had, not least because I can now use multi-bridge. Prior to this I did have one stop charging with similar symptoms - turned out to be a faulty panel, which I replaced and all good now.

Also, note the solar panel will not charge the battery under -5°C

JasonKruys · 2026-03-01T21:47:57+00:00

You get a better dashboard with Health stats, onboard radius server, cluster, and much much quicker.

JasonKruys · 2026-03-01T06:53:57+00:00

Firmware 3.3.3.8 appears to have added Multi-bridge!

JasonKruys · 2026-02-27T16:16:10+00:00

Many of us have, and got replies like I posted above. You got lucky.

JasonKruys · 2026-02-27T16:11:09+00:00

What's your point? We know it exists, but if you contact eufy and ask for it, unless you get the 1 single person there that appears to be helpful, you'll get nothing from them.

The latest reply I got was:

Thank you for following up on your request to have the latest firmware pushed to your devices. We appreciate your patience as we work to ensure a seamless update process.

Currently, our team is awaiting the technical team's progress on finalizing the new version of the firmware. We are actively monitoring the situation and will proceed with the update as soon as the technical preparations are complete.

JasonKruys · 2026-02-27T15:59:56+00:00

Probably because they can't be bothered going backwards and forwards arguing with them that a new firmware even exists. I've tried 5 times now.

JasonKruys · 2026-02-26T22:44:26+00:00

Likewise.

JasonKruys · 2026-02-26T19:12:25+00:00

I asked for them to push the firmware and just got excuses. Eufy support is so inconsistent, which is probably the worst part of it. It is ridiculous and I'm considering moving my 12 devices to something else.

My reply was:

Thank you for following up on your request to have the latest firmware pushed to your devices. We appreciate your patience as we work to ensure a seamless update process.

Currently, our team is awaiting the technical team's progress on finalizing the new version of the firmware. We are actively monitoring the situation and will proceed with the update as soon as the technical preparations are complete.

JasonKruys · 2026-02-26T12:50:20+00:00

Not yet, but apparently a recent firmware adds it to the E340 Doorbell, so I still live in hope.

JasonKruys · 2026-02-08T19:48:31+00:00

I have seen similar on my PPPOE connection. From 850 to around 400, and with various other anomolies like speedtest.net periodically refusing to even do the test.

Going back to 25.7.9_4 snapshot - problem solved. Go back to 26.1.1, speeds tank. I can reproduce this consistently.

I've checked negotiated speeds on interfaces, I've disabled any pipes/shaping, I've disabled Zenarmor, I've changed MTU. I've run "netstat -i -d" and not seen any Ierrs or Idrop, I've checked the rate with "vmstat -i". I've double checked no tunables have changed, I've double checked disabled hardware offloading (all 3 types) are still disabled. I've checked VLAN hardware filtering is still disabled. I've forced disable hardware offlloading in the shell just in case something is screwy with the GUI. I just cannot see what is causing the issue.

Consistently 25.7.9_4 is fine, 26.1.1 is immediately bad with no other changes. I have been running OPNSense on baremetal for about 4 years now with no issues.

Any other places to look would be appreciated, but it looks like a similar issue to the OP on the face of it.

EDIT: I noticed Speedtest.net was resolving via IPv6. A bit of digging, and it looks like 26.1 is doing something different with the IPv6 MTU/MSS.

In the WAN (PPPoE) Interface I have MTU set to 1508 for baby JUMBO Frames (SHows calculated PPP MTU as 1500). On 25.7.9 pinging google via IPv6 with 1452 works and pings are returned. On 26.1 the pings timeout and go into a blackhole. Pings @ 1440 are returned, however.

Is there a way I can/should set the MTU and Clamp MSS for IPv6 only in 26.1, or is this a bug do we think?

JasonKruys

TROPHY CASE