v7.2.2 [stable] and v7.2.3 [stable] are released!

eenpahlefi · May 21, 2022, 5:12pm

get value name system health not use..
tested routerboard RB750Gr3 v7.2.3

pe1chl · May 21, 2022, 7:22pm

It works, but differently that what you are trying to do.
This would work: :put [get value-name=value [find where name=voltage]]

Jotne · May 22, 2022, 4:57am

I am getting the voltage this way.

/system health
:put [get [find where name=voltage] value]

Its more inline with the rest of my scripting.

After som testing, it seems that value-name are not needed if you specify what you need after the data id.
Differences:
This works
:put [get [find where name=voltage] value-name=value]
This works
:put [get value-name=value [find where name=voltage]]
This works
:put [get [find where name=voltage] value]
This does not work
:put [get value [find where name=voltage]]

woro · May 22, 2022, 12:16pm

Have a RB4011 rebooting about every 4 hours with 7.2.3. Fixed after downgrade to 7.1.5

tangent · May 22, 2022, 2:04pm

My reply above is still valid. My RB4011iGS+RM’s uptime is now 14 days.

To me, what you’ve got there is the beginning of the diagnosis process, not its end. You’re blessed with a repeatable bug, which should make it amenable to ready diagnosis:

Enable remote logging. (Link above.)
Enable resource graphing, especially memory.
Export your sanitized config for examination here.
While waiting for responses, bisect the 7.2 feature list, turning off features until it stops restarting. There are 327 items on that list, which might seem an overwhelming number, but it really isn’t. First, at least half of those items are likely to be irrelevant to your local setup. Second, the log₂(n) nature of bisection reduces the process to 7 or 8 tries; with a 4 hour reboot time, you should have your answer in a day or two, if bisection can work on your problem at all.

Liopleus · May 23, 2022, 2:13pm

The wireless LED is finally working with wifiwave 2 on my hAP ac^3 after updating to 7.2.3.
Does anyone else experience this or is this actually fixed a couple of versions ago?

rextended · May 23, 2022, 2:14pm

I am getting the voltage this way.
/system health
:put [get [find where name=voltage] value]
Its more inline with the rest of my scripting.

After som testing, it seems that value-name are not needed if you specify what you need after the data id.
Differences:
This works
:put [get [find where name=voltage] value-name=value]
This works
:put [get value-name=value [find where name=voltage]]
This works
:put [get [find where name=voltage] value]
This does not work
:put [get value [find where name=voltage]]

Or also on v7

/system/health
:put ([get [find where name="voltage"]]->"value")

mcskiller · May 23, 2022, 7:27pm

upgrade rb4011 from 7.2.1 to 7.2.3 no bgp connection agains my peers.
from one of my peer side can see this in logs:

i have other peer in similar situation.
from my side no logs.
after a downgrade all is working without touch any config

rpingar · May 23, 2022, 7:32pm

I am sure they are ibgp.
they changed the way to choose local address!
Manually set the local ip into the connection and everything starts to work again.
It is not a bug, for ibgp MT usues the loopbackip (as local ip) if there is one.
regards
Ros

mcskiller · May 23, 2022, 7:47pm

Yes is ibgp, where i have to change ip? i am using for router-id a loopback ip.

rpingar · May 23, 2022, 7:50pm

manually set local ip into the bgp connection!

mcskiller · May 23, 2022, 7:53pm

thank! after 5 upgrades/downgrades is working again!

npeca75 · May 24, 2022, 3:55am

ahhh, another bug, this time on LLDP
there is NO mac cc:2d:e0:3d:b6:18 on my rb3011
but MT send this MAC in LLPD packets
it is unusable this way, could not match ifName because bridge/ifName notation
and could not match with non existent MAC address

looked at every interface, every bridge, simply, there is NO cc:2d:e0:3d:b6:18

Linux directly connected to 3011

~$ sudo lldpctl
LLDP neighbors:

Interface:    eth0, via: LLDP, RID: 2, Time: 0 day, 08:41:44
  Chassis:     
    ChassisID:    mac cc:2d:e0:3d:b6:18
    SysName:      soada-mkt
    SysDescr:     MikroTik RouterOS 7.2.3 (stable) May/02/2022 15:18:17 RB3011UiAS
    MgmtIP:       169.254.2.1
    MgmtIP:       fd00:2:1::1
    Capability:   Bridge, on
    Capability:   Router, on
  Port:        
    PortID:       ifname BR: Switch/eth8: NMS (ac1000)
    TTL:          120
  LLDP-MED:    
    Device Type:  Network Connectivity Device
    Capability:   Capabilities, yes
    Capability:   MDI/PSE, yes

and, Eltex switch connected to 3011 with bonding

#show lldp neighbors GigabitEthernet1/0/23

Device ID: cc:2d:e0:3d:b6:18
Port ID: BR: Switch/BND: bond1/eth1: sw22 (bond1)
Capabilities: Bridge, Router
System Name: soada-mkt
System description: MikroTik RouterOS 7.2.3 (stable) May/02/2022 15:18:17 RB3011UiAS
Port description: 
Management Address: 169.254.2.1
Management Address: fd00:2:1::1
Time To Live: 63


802.1 PVID: None
802.1 PPVID: 
802.1 VLAN:
802.1 Protocol: 

#show lldp neighbors GigabitEthernet1/0/24

Device ID: cc:2d:e0:3d:b6:18
Port ID: BR: Switch/BND: bond1/eth2: sw22 (bond1)
Capabilities: Bridge, Router
System Name: soada-mkt
System description: MikroTik RouterOS 7.2.3 (stable) May/02/2022 15:18:17 RB3011UiAS
Port description: 
Management Address: 169.254.2.1
Management Address: fd00:2:1::1
Time To Live: 77


802.1 PVID: None
802.1 PPVID: 
802.1 VLAN:
802.1 Protocol:

system · May 24, 2022, 10:50am

Still doesn’t work for me; after picking either wifi1 or wifi2 interface, I get:

Couldn’t change LED Trigger - Cannot assign interface to trigger! Interface is disabled or this is not a wireless interface! (8)

Liopleus · May 24, 2022, 4:16pm

I can’t configure it as well, but it didn’t even light up in the previous versions. At least now it lights up with wireless activity.

zainarbani · May 25, 2022, 7:57am

its been a while since last update

Panbambaryla · May 25, 2022, 8:05am

This is “silence before the storm”…

mkx · May 25, 2022, 8:36am

Ladies and gentlemen, brace yourself …

Rox169 · May 25, 2022, 9:33am

yes, leťs see how many devices will be bricked this time

rextended · May 25, 2022, 10:28am

RouterOS 7.2.3
New bug:
Hotspot walled garden on export or print do not export or show if the rules are enabled or disabled.
Adding by terminal the rule, the parameter action= is ignored.
Adding the rule with Winbox GUI work correctly.

http://forum.mikrotik.com/t/cli-walled-garden-action-deny-allow-functionless/158255/1

Rules inserted correctly on WinBox 64 3.35, terminal do not export or print action= status:

[admin@MikroTik] /ip/hotspot/walled-garden> export verbose show-sensitive 
# model = 911G-5HPnD
/ip hotspot walled-garden
add comment="show allow on winbox" disabled=no dst-host=test.test !dst-port !method !path !server !src-address
add comment="show deny on winbox" disabled=no dst-host=test.test !dst-port !method !path !server !src-address
[admin@MikroTik] /ip/hotspot/walled-garden> print detail 
 0   ;;; show allow on winbox
     dst-host=test.test hits=0 
 1   ;;; show deny on winbox
     dst-host=test.test hits=0

Terminal insert only allowed rules, regardlessly to the action=, and the action= still not exported (or printed)

[admin@MikroTik] /ip/hotspot/walled-garden> add comment="terminal test allow" dst-host="new.test" action=allow
[admin@MikroTik] /ip/hotspot/walled-garden> add comment="terminal test deny" dst-host="new.test" action=deny
[admin@MikroTik] /ip/hotspot/walled-garden> export verbose show-sensitive 
/ip hotspot walled-garden
add comment="terminal test allow" disabled=no dst-host=new.test !dst-port !method !path !server !src-address
add comment="terminal test deny" disabled=no dst-host=new.test !dst-port !method !path !server !src-address