I'm also curiousUpgrade went smooth...really interested in the "arm - improved system stability"!
Look in 6.48beta topic... there is some discussion about that.I'm also curiousUpgrade went smooth...really interested in the "arm - improved system stability"!
The same for 6.47.7, so it's not a problem of 6.47.8.On the version 6.47.8 command "system telnet" does not work with parametr "routing-table". Error "telnet: Unknown argument"
Probably the only things interesting to me. Updated successfully LtAP. Thanks for add Slot selection and USB type selection on WinBox.*) upgrade - do not try installing packages if download was not completed;
*) winbox - show "usb-bus" option on all boards that have it;
*) winbox - show "usb-type" option on all boards that have it;
I can confirm, my CRS328-24P-4S+RM no longer displays health.System health does not work properly.
CCR 1036 nothing to see
CRS309 only CPU temp
CRS326 only CPU temp
CRS 328 nothing to see
[admin@name] > /system health print
[admin@name] >
[admin@surname] > /system health print
voltage: 23.5V
temperature: 36C
[admin@surname] >
winbox - show "System/Health" only on boards that have health monitoring;
You should rather browse the new gauges introduced in 6.47 :in the CRS328-24P-4S+ winbox Health window doesn't open
Please add board temperature to SNMP 1.3.6.1.4.1.1.14988.1.1.3.10.0 for this device.
I did two of my 3011s without issue today. But I havent messed with the cpu settings.Don't know if that is related to this particular update, but RB3011 couldn't boot anymore after updating from 6.47.6, being restarted every time after "Starting services" stage. I've tried NetInstall to 6.47.8 and 6.47.7 without and with config wipe — no success.
Long story short — I've restored it with ROS7 firmware, and found the problem: looks like lowering CPU frequency to 600Mhz on 6.47.8 (or 6.47.7 as well) will brick the device after next reboot. Haven't tested it with 6.47.6 though.
[davidh@CPE - Testing] > int bridge export
# nov/29/2020 07:17:41 by RouterOS 6.47.8
# software id = HHQ9-GV0X
#
# model = RB750Gr3
# serial number = 8AFF0A4C0574
/interface bridge
add name=bridge priority=0x7000
/interface bridge port
add bridge=bridge interface=ether2
add bridge=bridge interface=ether3
add bridge=bridge interface=ether4
add bridge=bridge interface=ether5
[davidh@CPE - Testing] > int bridge port print detail
Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload
0 interface=ether2 bridge=bridge priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto learn=auto horizon=none hw=yes
auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no unknown-unicast-flood=yes
unknown-multicast-flood=yes broadcast-flood=yes tag-stacking=no bpdu-guard=no trusted=no multicast-router=temporary-query fast-leave=no
1 interface=ether3 bridge=bridge priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto learn=auto horizon=none hw=yes
auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no unknown-unicast-flood=yes
unknown-multicast-flood=yes broadcast-flood=yes tag-stacking=no bpdu-guard=no trusted=no multicast-router=temporary-query fast-leave=no
2 interface=ether4 bridge=bridge priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto learn=auto horizon=none hw=yes
auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no unknown-unicast-flood=yes
unknown-multicast-flood=yes broadcast-flood=yes tag-stacking=no bpdu-guard=no trusted=no multicast-router=temporary-query fast-leave=no
3 interface=ether5 bridge=bridge priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto learn=auto horizon=none hw=yes
auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no unknown-unicast-flood=yes
unknown-multicast-flood=yes broadcast-flood=yes tag-stacking=no bpdu-guard=no trusted=no multicast-router=temporary-query fast-leave=no
On hEX you need to disable STP on bridge for hardware offload, i.e. protocol-mode=noneBridge port hardware offloading remains disabled on hEX (RB750Gr3):
...
Yes, I'm having the same problems, on a 3011, on doors 1 through 5Can anyone tell me, if you are experiencing sudden stop transmitting on the Interface
Yes, I'm having the same problems, on a 3011, on doors 1 through 5Can anyone tell me, if you are experiencing sudden stop transmitting on the Interface
It has nothing to do with the ROS version, this was always the case for 5GHz ac cards.Is this a bug, but I can't see 5GHz Current Tx Power? It is working fine and devices are connected, but just can't see anywhere the transmit power.
The tab is just empty. in 2.4GHz it's filled with numbers.
[admin@hAPac2] > interface wireless info country-info
country: etsi
ranges: 2402-2482/b,g,gn20,gn40(20dBm)
5170-5250/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(23dBm)/passive,indoor
5170-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(20dBm)/dfs,passive,indoor
5250-5330/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(20dBm)/dfs,passive,indoor
5490-5710/a,an20,an40,ac20,ac40,ac80,ac160,ac80+80(27dBm)/dfs,passive
[admin@hAPac2] > interface wireless print advanced
...
name="wlan2" mtu=1500 l2mtu=1600..... area="" frequency-mode=regulatory-domain country=etsi installation=any antenna-gain=3 frequency=5260 band=5ghz-a/n/ac channel-width=20/40mhz-Ce
.....
That is shown only in tx-power-mode=regulatory-domain and that is simply maximum allowed tx-power.You have "some" information in the status of the interface. Here 17dBm.
Total, not per chain. And with antenna gain already subtracted.Oh, it was my impression that this figure is the max EIRP per chain on that specific frequency.
So subtract the antenna gain and you get the max output power per chain.
Transmit Power representation on 802.11n and 802.11ac
802.11n wireless chipsets represent power per chain and the 802.11ac wireless chipsets represent the total power, for reference see the table below:
Changes with the antenna gain are OK, but does not reflect the manual tx-power set. That's why I mentioned ' "some" information.'
Don't even know if it is calculated from actual antenna gain, as you describe, or just hard-coded from the default antenna gain.
This is a good question to where there is no general truth I would guess. So the more releases there are between your build and the current build the greater the likelihood is of a upgrade issue I would guess. When MT tested upgrades they do not disclose from which builds they tests etc.I have an RB1100AHx4 running on 6.47 for about 185 days now, which is when that version was released. I'm currently not experiencing any issues, bugs or any other problems yet. I checked change logs and there doesn't seem to be any security fixes since then. Should I leave it as is or upgrade? Router is in production with 1 BGP session and 3 or 4 ports in use.
I recently updated a router from 6.47.1 to 6.47.7 because I got hit by a bug that was introduced in 6.47 (the problem with l2tp connects from the same address).I have an RB1100AHx4 running on 6.47 for about 185 days now, which is when that version was released. I'm currently not experiencing any issues, bugs or any other problems yet. I checked change logs and there doesn't seem to be any security fixes since then. Should I leave it as is or upgrade? Router is in production with 1 BGP session and 3 or 4 ports in use.
Ever since DoH been in RouterOS it's been like that. It's been in the betas and stable release and they know about the issue but guys at Mikrotik think good the way it is now: viewtopic.php?f=21&t=161887#p797837Emils,
I am using DoH DNS which works fine, but if I reboot the router and it takes some moments to get a new DHCP lease the log is filled with:
DoH server connection error: resolving error
Can you quieten down the DoH error log rate? In these moments when the WAN interface is down a 1000 entry log overflows quickly.