v7.10beta [testing] is released!

[loloski]

Finally, we can pickup where we left off in IX deployment and hope we can use our few dozen of MT gear as supplemental to the existing infrastructure, if only this is available last year we are not in the current predicament right now that we are mixing platform in DC.

@MT please next in your roadmap should be as follows
QinQ, VXLAN and MACSEC offload in hardware, Openflow,VPDN and 802.1ah-2008 if this happen MT will be a household name in DC

[npeca75]

still no IPv6 / WireGuard on ARM rb3011

ipv6/route/print
Flags: D - DYNAMIC; A - ACTIVE; c, s, y - BGP-MPLS-VPN; + - ECMP
Columns: DST-ADDRESS, GATEWAY, DISTANCE
#      DST-ADDRESS                    GATEWAY              DISTANCE
  DAc  fdff:255::/112                 wg: Mgmn (NMS)              0

ipv6/address/print 
Flags: X, D - DYNAMIC; G, L - LINK-LOCAL
Columns: ADDRESS, INTERFACE, ADVERTISE
 #    ADDRESS                       INTERFACE            ADVERTISE
 8  G fdff:255::202/112             wg: Mgmn (NMS)       no

same config work on 7.9

[mrz]

As expected (feared), the count is before route filtering, whereas in v6 it was after route filtering.
But still better than nothing!

If you refer to “filtered” by routing filters then there is no difference filtered or not filtered, total route count stays the same in both cases. And it does not makes sense to display count of just part of the routes stored in the memory.

[pe1chl]

As expected (feared), the count is before route filtering, whereas in v6 it was after route filtering.
But still better than nothing!

If you refer to “filtered” by routing filters then there is no difference filtered or not filtered, total route count stays the same in both cases.

In v7, yes. But in v6 that was not the case.

[Kaldek]

PLEASE Mikrotik staff that reads this thread … reconsider the inline comments on the webfig and also the ‘centering of everything’

I like the inline comments in WebFig. It’s saving me a lot of time scrolling. I ask that Mikrotik don’t change this back.

[leonardogyn]

I like the inline comments in WebFig. It’s saving me a lot of time scrolling. I ask that Mikrotik don’t change this back.

.
Actually we have asked, earlier on this thread and on the 7.9 threads as well, to have the OPTION to choose inline or “newline” comments, just like the winbox has (and always had) the option to choose which one the user prefers.

For those working on big monitors/resolutions, I agree that inline comments might work great. But for the laptop users, like me and A LOT of others, the inline comments are really bad. We even had people reporting that manages MK boxes, using webfig, from mobiles, in which it’s even worst!

Since the introducion of the FORCED inline comments on the webfig, we have asked, actually, the ability to CHOOSE which one to use, and not THIS or THAT being force-choosed for us

[nichky]

any update on vpn6?

https://help.mikrotik.com/docs/display/ROS/Routing+Protocol+Overview

[normis]

PLEASE Mikrotik staff that reads this thread … reconsider the inline comments on the webfig and also the ‘centering of everything’, as it wastes A LOT of space on the new layout (please see my previous comment showing editing scripts at http://forum.mikrotik.com/t/v7-10beta-testing-is-released/166567/1 ).

While making things prettier is great, making everything worse to use is not. Some of these changes really adds too little while taking A LOT on the usability.

Please reconsider them, PLEASE

As you can see from other commenters, who like it … This is a matter of taste. How is “left aligned” in your big monitor not wasting space, but centering is wasting space? It is the same amount of wasted space, just in a different place. Do not use webfig in a maximised window on a ultrawide.

[mh04]

Since version 7.9 there is an error when you fetch the routing table via SNMP (1.3.6.1.2.1.4.24.4.1.4):

snmpwalk -v1 -c public 192.168.88.1 1.3.6.1.2.1.4.24.4.1
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.44.10.69 = IpAddress: 0.0.0.0
iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0 = IpAddress: 0.0.0.0
Error: OID not increasing: iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.10.44.10.69
 >= iso.3.6.1.2.1.4.24.4.1.1.0.0.0.0.0.0.0.0.0.0.0.0.0

The error did not exist in previous versions.

Still not fixed in newest beta. Please look at this problem.

[mantouboji]

resolved

[sirbryan]

As you can see from other commenters, who like it … This is a matter of taste. How is “left aligned” in your big monitor not wasting space, but centering is wasting space? It is the same amount of wasted space, just in a different place. Do not use webfig in a maximised window on a ultrawide.

But because comments are now inline, I have no choice but to widen my browser to see longer comments. The problem isn’t a matter of taste when comments exceed 10-15 chars. It’s a matter of usability/readability.

I gather the vast majority of webfig users don’t use long comments. The problem is enough of us do. For me, I use them a lot, particularly in routers where I have a lot going on and use them to remind myself why routing filters or interfaces are configured the way they are, and in some cases, I even store tidbits of filter “code” in the comments for comparisons or for backup/emergency purposes.

With the comments now inline, the bulk of the information is cut off. In order to read them, I have to click on the line(s) I want to read.

In the name of aesthetics, this ends up creating more work.

Similarly, but to a lesser extent, centering and grouping everything requires more eye/mouse travel, and obscures information that was previously immediately visible. For example, I frequently check 60GHz AP’s for station status (why isn’t there a separate table for 60GHz radios? And why isn’t the name or MAC of the CPE associated with their signal strength, etc.?). With everything hidden under “Status”, I’ve got to click more times to get to what I need.

I know this may come across as silly to some of you, but when your daily workflow is impacted by UI changes like this, these little things tend to add up.

[Raf44]

beta 10 : BGP VPN4 have same problems as before 7.9 ; type “copy” routes, and no BGP attributes

Maybe you didn’t actually upgrade, since since beta10 do not have “copy” routes anymore and BGP attributes are there for bgp vpn routes.

i don’t know… how can we explain that ?..

i just upgrade from 7.10 - beta 5 → 7.10 beta 8
the 2 RR are in 6.49.7

Already have a (long) ticket on problems about BGP VPN4, I can re-supply the schematic / supout of the 13RB951 + 2hap ac2 of my model if needed

[pe1chl]

I like the inline comments in WebFig. It’s saving me a lot of time scrolling. I ask that Mikrotik don’t change this back.

.
Actually we have asked, earlier on this thread and on the 7.9 threads as well, to have the OPTION to choose inline or “newline” comments, just like the winbox has (and always had) the option to choose which one the user prefers.

Of course the problem is that webfig has no options at all. To have an option for such a thing, first the development has to be done to have options.
Once that is done, of course it would be trivial to have an option like on winbox. And lots of other options as well, such as selectable colums/width/order, hide/show password, etc.
But to add that to an in-house-developed web framework can be somewhat of a job. I think it is more complicated than implementing BFD.

[pe1chl]

As you can see from other commenters, who like it … This is a matter of taste. How is “left aligned” in your big monitor not wasting space, but centering is wasting space? It is the same amount of wasted space, just in a different place. Do not use webfig in a maximised window on a ultrawide.

But because comments are now inline, I have no choice but to widen my browser to see longer comments. The problem isn’t a matter of taste when comments exceed 10-15 chars. It’s a matter of usability/readability.

I don’t understand exactly what you guys are complaining about. When you open a table with comments you see the truncated comment, and when you hover the mouse over that it expands into the full comment in a separate pop-up.
Why do you have “no choice to widen”? Does this mouse-hover not work in your browser? I use Firefox and it works there.

[fragtion]

@EdPa can you give more details about “wireguard - retry “endpoint-address” DNS query on failed resolve;”
How many times will it retry? Does this solve our problems with dynamic ips on peers where we need to re-toggle tunnel to fix it after IP change?

This.
Right now I need to use this overkill script on schedule (every 10 min) to ensure that the wg tunnel stays alive..:

:local resolvedIP [:resolve "remote.peer.dns.com"];
:local peerparent "wg-interface";
:local peeraddr "jIASJDIasojdIOASJdioasjDIOASJiodjIOASDJASIODJ==";

:local currentPeer [/interface/wireguard/peers/find where interface=$peerparent and public-key=$peeraddr];
:local currentIP [/interface/wireguard/peers/get $currentPeer endpoint-address];
:local currentPort [/interface/wireguard/peers/get $currentPeer endpoint-port]

:if (([:find $currentIP $resolvedIP] < 0) && ([:len $currentPort] > 1)) do={ 
    /interface/wireguard/peers set $currentPeer endpoint-address=$resolvedIP
    /interface/wireguard/peers disable $currentPeer
    /interface/wireguard disable $peerparent
    /interface/wireguard enable $peerparent
    /interface/wireguard/peers enable $currentPeer
    /log info "Wireguard Peer $peeraddr (under $peerparent) endpoint-address updated from $currentIP to $resolvedIP";
}
:delay 5
if (([/interface/wireguard/peers/get $currentPeer last-handshake] > 180) || ([:len [/interface/wireguard/peers/get $currentPeer last-handshake]] = 0)) do={
  :local fwrule [/ip/firewall/filter/find where comment=("out-"."$peerparent")]
  if ([:len $fwrule] = 0) do={
    if ([:len $currentPort] > 1) do={ /ip/firewall/filter/add action=drop chain=output comment=("out-"."$peerparent") dst-port=$currentPort protocol=udp }
  } else={
    if ([:len $currentPort] > 1) do={ 
      :local fwport [/ip/firewall/filter/get $fwrule dst-port]
      if ($fwport != $currentPort) do={ /ip/firewall/filter/set $fwrule dst-port=$currentPort }
    } else={ /ip/firewall/filter/remove $fwrule }
  }
  if ([:len $fwrule] > 0) do={
    if ([/ip/firewall/filter/get $fwrule disabled] = true) do={
      /log info "Wireguard Peer $peeraddr (under $peerparent) unresponsive - Temporarily disabling...";
      /ip/firewall/filter/set [find where comment=("out-"."$peerparent")] disabled=no
    } else={
      /log info "Wireguard Peer $peeraddr (under $peerparent) unresponsive - Trying to restore...";
      /ip/firewall/filter/set $fwrule disabled=yes
    }
  }

It will be a great day when we can rely on built-in/native robustness of this and I can delete these scripts
Actually I haven’t tested if the functionality has changed since early v7 betas (as my script works well for me so didn’t need to check), so it would be good to have an answer to OP’s question for better clarity

And while commenting, I want to throw in my 2c that inline comments are awesome, so rather an option should be provided in webfig to select preferred option, than revert to old style…
As much as I love winbox, it would be great if someday winbox and webfig are visually and functionally equivalent. This would preclude a need to develop a new winbox that is compatible with MacOS for instance, as we could all use a web app as a replacement for winbox. But right now there are still too many issues with webfig so I always use winbox where possible

[mfrommel]

But because comments are now inline, I have no choice but to widen my browser to see longer comments.

There is a “mouse over” feature for the comment:

The waste of space by centering everything annoys me too.

[msatter]

@EdPa can you give more details about “wireguard - retry “endpoint-address” DNS query on failed resolve;”
How many times will it retry? Does this solve our problems with dynamic ips on peers where we need to re-toggle tunnel to fix it after IP change?

I am using RoundRobin from the DNS and only restart the peer to have the next IP address to be resolved.

The retry itself was a longtime and many times requested feature and I am pleased that Mikrotik implemented this now.

http://forum.mikrotik.com/t/wireguard-peer-not-functioning-after-a-router-restart/155286/44
http://forum.mikrotik.com/t/wireguard-dynamic-enpoint-address/158243/2
http://forum.mikrotik.com/t/if-wireguard-fails-to-connect-it-wont-ever-try-again/157574/36

[fragtion]

@EdPa can you give more details about “wireguard - retry “endpoint-address” DNS query on failed resolve;”
How many times will it retry? Does this solve our problems with dynamic ips on peers where we need to re-toggle tunnel to fix it after IP change?

I am using RoundRobin from the DNS and only restart the peer to have the next IP address to be resolved.

The retry itself was a longtime and many times requested feature and I am pleased that Mikrotik implemented this now.

Question not answered about how many times it retries, or if interface still needs to be toggled to re-establish a connection after IP change..

[msatter]

Question not answered about how many times it retries, or if interface still needs to be toggled to re-establish a connection after IP change..

As long as it fails to resolve, seems to me the way it will work. There is no max times mentioned so it keeps trying…

…every retry counts as one instance and then it starts again as it was a new detection.

[sirbryan]

But because comments are now inline, I have no choice but to widen my browser to see longer comments. The problem isn’t a matter of taste when comments exceed 10-15 chars. It’s a matter of usability/readability.

Why do you have “no choice to widen”? Does this mouse-hover not work in your browser? I use Firefox and it works there.

I said “No choice but to widen”, as in, I have to widen my browser window, in response to Normis’ statement to not widen the browser all the way on ultrawide monitors.

I was not aware of the tooltip, but that’s still an extra step to see stuff I’m accustomed to seeing right up front. Tooltips aren’t really useful on a phone or tablet, where I use webfig a ton, too.

Again, most people won’t notice/don’t care about the inline comments change, but when you’re in and out of dozens of devices per day, trying to troubleshoot problems, comparing settings, routes, results, etc., any extra work required to find the information, be it mouse-overs or extra taps/clicks or drilling down through menus is time taken away from getting the work done, solving the problem, and restoring service. Every fraction of a second counts.

One example is the DHCP lease tables. I have scripts that go through each of my edge routers (20ish at present) and makes current leases static for use by UISP and traffic shaping. Sometimes I have the customer’s full name in the comment field, but more often than not I pull the hostname from the DHCP request. Every single comment entry exceeds the column width, so I see 10 characters out of 20-40, whatever it is. Sure, I can widen the columns or mouseover, but I have to do that for each of my routers. And what might work for my desktop is too large for the laptop and way too much for my phone.