Working from home should not be a problem here. Lets assume, you have several devices, which use Netflix - those devices can be added to a list /ip firewall address-list add address=10.0.0.2 comment="local device x" list=NflxLAN add address=10.0.0.7 comment="local device y" list=...

It doesn't need too frequent updates, most of the time the same IP blocks are used. If the 'initial' address list is ok, then every few months you'd have to add a few IP blocks more. Bigger problem is if you use some of the commercial VPNs (like nord, pia, torguard, etc) and their residential/stream...

Hi @pajapatak, could you please do us all a big favor and post your complete solution in the "Useful User Articles" forum? Thank you!

Sure - here it is!

In this example, we will route Netflix traffic from a specific lan client (10.0.0.10) through wireguard. Lan and wireguard addresses are /ip address add address=10.0.0.1/24 interface=lan network=10.0.0.0 add address=10.10.10.1/29 interface=wireguard1 network=10.10.10.0 We first create a routing tabl...

Just to make sure: do you have add action=change-mss chain=forward comment="Clamp MSS to PMTU for Outgoing packets" new-mss=clamp-to-pmtu out-interface=wireguard1 passthrough=yes protocol=tcp tcp-flags=syn or add action=change-mss chain=forward new-mss=1380 out-interface=wireguard1 protoco...

Netflix is not only tcp, so you'd need to mark udp packages as well. Another possible source of a problem is passthrough=yes depending on which rules come after this one. Modified mangle rule from the linked website: /ip firewall mangle add action=mark-routing chain=prerouting comment="Sortie N...

Hello @Simonej,
can you please share (the relevant part of) the configuration? I am thinking of a similar setup (not with Audiences though), so a configuration which works would be very helpful!

Some TVs and similar devices have 'hardcoded' DNS, which may be different than 8.8.8.8/8.8.4.4 - have you maybe blocked access to other DNS providers?

What does the router log say, when you try to connect when on wifi? Does the initial package even reach the router?

edit: just tested the rule mentioned above and it does work...
Is the order of the rules in your firewall correct?

Lots of ext4 USB stick container problems with hAP ax³ and 7.14.2 or 7.15beta9, downgrade to 7.13.5 and everything works: https://forum.mikrotik.com/viewtopic.php?t=206110 Based on TWO reports, why do you say LOTS ? Besides, you're cross-posting, you know ... I can add the third report (not ax3, th...

Hope it will help! Btw, one more similar case, involving USB and RB5009: viewtopic.php?t=204440#p1057926

I have a related issue, though, with hAP ac3: since ROS 7.14, the usb stick, used to host containers, is sometimes recognized, sometimes not, and (also) causes random reboots every few hours, or, in best case, every 1-2 days. Another hAP ac3, with another usb stick - same behavior. Needless to say, ...

Testing ROS7.15beta9 on hAP ac3 (wifi-qcom-ac) resulted in random reboots every few hours.This behavior was noticed already in 7.14 (stable), while version 7.13.1 (stable) worked just fine. The only extra package is container. Support ticket [SUP-149159] created.

I'm seeing irregular behaviour since the driver change, I have lost signal 10db or so. I have exactly the same problem, starting with version 7.13 (hAP ac3 + wifi-qcom-ac). No issues with wifiwave2 (7.12 and below) I can confirm that; also hAP-ac3, currently at 7.13.1 (in the short period it was at...

How about netinstall? That would definitely reset it to factory defaults.

I can confirm this behavior, with one hap ac3 and wifi-qcom-ac drivers. Two other hap ac3, with legacy drivers don't show this behavior.

Would ZeroTier be an option here? https://help.mikrotik.com/docs/display/ROS/ZeroTier

Even if protected-routerboot is enabled, it is still possible to do a recovery, according to RouterBOARD documentation: https://help.mikrotik.com/docs/display/ROS/RouterBOARD . As an emergency recovery option, it is possible to reset everything by pressing the button at power-on for longer than refo...

I've had this with one hap ac3 after updating from 7.13.x to 7.14.
Updating further to 7.15b4 hasn't solved the problem, so I reverted back to 7.13.1 - works stable.