v7.10beta [testing] is released!

Announcements
21

@eworm / @all
http://forum.mikrotik.com/t/warning-routeros-v7-10-will-break-all-scripts-based-on-system-clock-get-date-or-other-date-s/166576/1

Please remove the SHITTY 4-modes from logs:

  1. only time is just happened,
  2. only day if is the same month
  3. only month-day if is the same year
  4. full date (year-month-day) only if the log is of another year…

LOG MUST HAVE EVERYTIME FULL DATE…

22

See (very sensible) comment from msatter in other thread.
http://forum.mikrotik.com/t/warning-routeros-v7-10-will-break-all-scripts-based-on-system-clock-get-date-or-other-date-s/166576/7

For backwards compatibility, best to leave the old format as it was.
Introduce new variable which can be used moving forward.
Everybody happy.

23

see this:
http://forum.mikrotik.com/t/v7-10beta-testing-is-released/166567/1

24

CONCUR Holvoe!

mSATTER brilliance, after silly hats, clogs, dykes, legalized weed and prostitution the dutch provide…
**@**EdPa"Something like: [/system clock get isodate]"

25



Sorry, but is better this:

Since the date format is changed also on LOGs, certificates, system scheduler, etc. and WebFig (and on future I hope Winbox)

Better add something like this, that influence all the places where a date can be retrieved [clock / log / certificate, etc.].

/system clock set format=<VALUE>

format can be yyyy-MM-dd or mmm/dd/yyyy, the default is yyyy-MM-dd

26

*) webfig - redesigned top menu bar;

.
Great one, really enjoyed the new design! Also enjoyed the removal (not listed on the changelogs) of the actual RouterOS version on the webfig login screen.

inline comments are still a thing, and that’s not a good one :frowning: Please consider reverting to the old style or, at least, give us the option to choose which one to use! The inline comments really blew up the usage experience, specially when using large comments, on not-huge screens!

27

hAP ax2 - issue with wireless clients (not able to connect to WiFi and receive IP address - http://forum.mikrotik.com/t/wireless-clients-not-connecting-after-upgrade-to-7-9-hap-ax2/166453/1 http://forum.mikrotik.com/t/hap-ax-2-accidental-drop-all-wifi-connections/162268/1 http://forum.mikrotik.com/t/hap-ax2-randomly-drops-wifi-ssids-both-2-4-and-5ghz/162595/1) still persists…

28

Also when you disable WPA3 ?

29

Any chance we will get additional wireless interface modes for WifiWave2 anytime soon e.g. ap-bridge ?

30

What´s this meaning? :slight_smile:
ovpn - added initial support for V2 data transfer protocol;

31

hello dear mikrotik team

could you please allow to specify firewall address list in routing->rules?

fasttrack doesnt work due to mark-routing rules, but we can use routing->rules page, if you add ability to specify dynamic address list for a routing rule.

this will be nice speed improvement for VPN tunnels

thanks and regards

32

Unfortunately, it is not possible, linux kernel does not support address lists in route rules.
Māris B.

but you can write kernel module or user-space program to sync address list into route rules and remove them when address-list entry times out
example script: https://forum.mikrotik.com/viewtopic.php?p=1001255#p1001255
please MikroTik Team! this is very important!

33

qsfp28 modules issue still persists on CCR2216
modules flap failed to inizialize, failed to get the link on, or some times get the link but disconnect randomly (very weird behavior)
[SUP-115401] updated about supout with 7.10beta5
modules that works on qsfp2-1 doesn’t work on qsfp1-1 and vice versa.

34

Wireless for me now seems stable.
hAP ax3 7.10beta5 (CAPsMAN)+hAP ax2 7.10beta5 (cAP)+hAP ax2 7.10beta5 (cAP), approximately 25 wireless clients connected.

35

PPPoE Scan in RB5009 works now in 7.10beta5.

36

Nice that the date format issue is finally being addressed even if the initial implementation creates compatibility issues completely unnecessarily IMO. Seriously Mikrotik, please consider a different implementation.

It can easly be solved using my proposal: http://forum.mikrotik.com/t/warning-routeros-v7-10-will-break-all-scripts-based-on-system-clock-get-date-or-other-date-s/166576/14

37

For me neither…additionally 7.10Beta5 breaks my AX WLAN completly.
After upgrading my working config from 7.9 stable to 7.10Beta5 the CAPsMAN (CHR without local Wifi interfaces) shows the following error:
5393205921695517717_121.jpg
and all WLAN´s where unavailable.
Interestingly the 4 radios from the two CAPS were connected …

38

Sorry, my proposal is closer to RouterOS language and is easy manageable instead to add parameters to all points where date can be retrieved.
http://forum.mikrotik.com/t/v7-10beta-testing-is-released/166567/1

39

Speaking of datetimes…

/terminal/inkey timeout=time … is still broken in v7.10beta5

40

I do like the attempt to clean up/modernize Webfig. I’ve used Webfig almost exclusively for the past three years because it’s 1) universally accessible and 2) I can get to and see all the settings in one place, unlike Winbox, where it takes more effort to see/change information & settings.

Since some of the changes are messing with my muscle-memory and workflow, I’m going to throw out what suggestions I can before things get too cemented into place. (Presuming anybody is listening…)

  • I love the addition of Safe Mode (would have saved me a trip to a site yesterday)
  • Centering the details in the middle of the screen is jarring visually when we’ve got browser windows open wide to see/monitor the huge amounts of data in the tables and we’re generally looking at the left side already (in LTR languages). Also, when quickly moving through settings or information pages (setting up new devices, troubleshooting existing installations, or turning up new BGP sessions), that added distance adds extra mouse travel time (i.e. hand fatigue), as opposed to having the DIV left-aligned.
  • The huge amount of white space (well, gray) below the scrollable DIV in the absence of the OK/Apply/Cancel buttons gives the user the impression that they’re at the end of available options. That DIV needs some kind of visual indicators that there’s more data/settings hidden behind the invisible block, such as a hairline border around it, or maybe arrows or something.
  • Grouping on the detail page is nice, but adds extra clicks. Perhaps an “expand all” button would be useful here.
  • Comments need to go back above the line they’re a part of, or that option should be configurable. I have a lot of multi-word/multi-sentence comments. (They’ve been multi-line in Winbox forever, why shrink it on the details page and make it harder to see everywhere else?)
  • What is with this trend of removing the software version from the top of the screen? Ubiquiti is doing it too on their radios and I hate having to dig further to determine what release I’m running. I get into dozens of devices per day and am testing a number of software versions across hundreds of devices. That is vital information if I’m either configuring a device, if it needs upgrading, or if I’m troubleshooting known or unknown issues. With Webfig, there’s plenty of room where the version used to be. The hostname does not need to take up 75% of the width of my browser window.

Short version of the rant: Please don’t hide information that was readily visible before. Or else, make a “pretty” skin and a “utility” skin.

That all said, I’m really excited about everything else in 7.10.