It works with default configuration on OpenWrt? Or did you have to configure anything additionally?i sense it is some upnp protocol issues, i swap the MT with a OpenWrt it also works just fine.
i need some troubleshoot steps to start with.
It works with default configuration on OpenWrt? Or did you have to configure anything additionally?i sense it is some upnp protocol issues, i swap the MT with a OpenWrt it also works just fine.
i need some troubleshoot steps to start with.
Are you sure, how you analyzed that?Why does ROS still use HTTP/1 for DoH queries?
Are there any plans to implement HTTP/2 support?
All modern DNS server software (BIND9, Unbound, Dnsdist) use HTTP/2 and cannot handle ROS queries.
The scheduler script does that. It is configured to run e.g. 5min after startup. It does switching partition. If bmann can log in, he just disables the scheduler. All good.if your tunnel is down, you can't switch partitons anyway. you need access for that.
/ip/service/disable [find]
Any hints in log?Were do I need to look then ?
update: please activate by turning power off or pressing reset or mode button in 4m27s
/ip hotspot user reset-counters [find name="a"];
/ip hotspot user remove a;
/ip hotspot user reset-counters [find name="a"]; -> resets counters of ->ALL<- users
/system/device-mode/update mode=enterprise traffic-gen=yes
You have no permission to open terminal in Winbox even if you have winbox permission. As said: !local or !telnet prevents opening a terminal inside Winbox.Read users can use Winbox terminal. That's not true.A user can log in but have no rights to open terminal.
bump. This is discussion strictly related to release 7.16How does this about parameter work? Can't figure it out. Docs unavailable.Code: Select all*) console - added "about" filters for "find" and "print where" commands;
Hi,
v7.17Beta2 and v7.17ab57. They cause me a "high" CPU consumption, IPSEC process. Reverting to v7.16 "stabilizes" the CPU, but policies may become stuck again, we'll see over the weekend.
*) crypto - improve crypto speeds;
Refactoring does not change functionality or fix bugs. It is just a process of "restructuring"/cleanup source code.My illusion vanished. Tested and still having the TV cuts.
Really hoping that this fix the IPTV issues we are having with Movistar Spain (SUP-152693)
*) wifi - show authentication type and wireless standard used by each client in registration table;
Why always use RJ45 SFP+ modules for uplink. They are expensive and create a lot of heat.
Due to this it is not usable for me.
BR, Michael
*) console - added "about" filters for "find" and "print where" commands;
Unsure why, my Chateau (D53G-5HacD2HnD) got hit differently:"free-hdd-space" shrinked by ~50kb on "cAP ac":
7.15.3: 780KiB
7.16: 736KiB
/ip dns static add forward-to=192.168.5.6 name="example.local" type=FWD match-subdomain=yes
*) certificate - show validity beyond year 2038;
But according to google research none of the competition has PPSK for WPA3-PSK either. Seems to be impossible.multi-passphrase is not supported for the WPA3-PSK authentication type.
Then you maybe crushed it somehow. My first Chateau in mid 2020 already had that.Maybe new models, on my SIM slot doesn't have.
Oh yeah, I really hate that behavior. And I see no possibility to turn that off.".home.arpa" DNS queries are still being leaked to the WAN network and is not conform to rfc8375. Can it be fixed ASAP please?
Chateau has a push-to-eject mechanism. Did not destroy my nano-SIM adapter in years.Yes sure Removed once and destroyed nanosim-to-microsim-to-sim adapter because it was very difficult to pull it out.
P.S.: still propose MT to disable api/rest stuff in defconf to prevent such things. Those API hacks seem to be common.
You read post #1 before posting?
😉+1000
It worked on 7.16 rc5?I have a device ax3 with power supply via PoE in Ether1.
Today on version rc5 and after updating to 7.16 also problems appeared “ether1 link down” -> “ether1 link up” -> “ether1 link down” and so it repeats continuously.
Connected to which device? ISP router or your Mikrotik one?Speedtest with Ethernet cable:
Download 980 Mbps/Upload 961 Mbps
nothing wrong with using DFS channels. an lol, advising to use country USA in Europe is illegal.set country usa and fix channels..avoid dfs
There must be some showstopper(s) apparently. If there are upcoming changes/fixes I hope we se another RC instead of going straight stable. Too high the risk of regressions in last-minute fixes.2 Guntis: Whats wrong with this RC, when we can expect stable version?
Look for the section “Wi-Fi for iOS/iPadOS” in iOS Profiles and Logs
This help page knows:The documentation (https://help.mikrotik.com/docs/display/ROS/DNS) does not even list the vrf parameter, so who knows!
Would not make sense to me. Winbox 4 is early beta and that should not be any priority for any stable ROS version right now.polish behavior with new Winbox 4, but - who knows...
Yes, they thanked me for making suggestions.Great!I already requested that feature via SUP-158802.
Have they already answered to your request?
Note. The new version is not released for the CSS106 models due to no changes to their specific firmware.
That is not even true. If you use a GUI file manager you can simply double click the executable.You have to open the terminal and navigate to the extract location, to run the binary manually - this is definitely "not OK".
So basically 24h since release of beta4. My running Winbox instance still does not show update notification on Linux client.How frequently does Winbox check for updates? No notification until now.
And added a scheduled reboot instead of downgrading to 7.15 again :PI'm not 100% sure anymore why I moved on to 7.16b/rc channel for that one device.
And Winbox 4 is following Windows theme?It was only native in Windows 95, all newer Windows used a completey different style of window and theme, and Winbox did not follow that.
;)- Apps are native!