I faced this kind of problem in WinBox a few times (enabling ipip and eoip interfaces, AFAIR) on ~v6.40-41I'm getting this error "no such item (4)" when enabling or disabling the pppoe client interface. Router is RB750Gr3 6.42RC43.
Note that this problem is not unique to 6.42RC43. I've encountered it before. It's just that I've only started looking into it now.
Hi strods,*) routerboot - fixed RouterBOOT upgrade process (introduced in v6.42rc);
Before such protocols are of any use to us, we need you to implement airMAX, the other guys to implement NV2, or you both agreeWe have made a potentially significant improvement for wireless Nv2 PtMP configurations in the latest 6.42rc version release.
All the changes are on the AP side so you need to upgrade the AP. Client version can stay the same.Regarding nv2.
Do we update clients and ap or just ap?
Hi strods,atlanticd - Yes, that is the fix for the problem. Please test it and report back to us with the results.
free-memory: 79.1MiB
total-memory: 106.3MiB
uptime: 1d7h32m31s
version: 6.40.5 (stable)
build-time: Oct/31/2017 13:05:15
factory-software: 6.40.5
free-memory: 208.7MiB
total-memory: 233.4MiB
cpu: ARMv7
cpu-count: 4
cpu-frequency: 716MHz
cpu-load: 0%
free-hdd-space: 4216.0KiB
total-hdd-space: 15.3MiB
write-sect-since-reboot: 136
write-sect-total: 136
bad-blocks: 0%
architecture-name: arm
board-name: hAP ac^2
platform: MikroTik
Is the version a typo? My systems find 6.42rc49.What's new in 6.42rc48 (2018-Mar-21 11:13):
Isn't a typo, were launched two versions today.Is the version a typo? My systems find 6.42rc49.
confirmed, RouterBOOT upgrade installed ok on hAP ac². Upgraded from ROS 6.41.3 to 6.42rc49, then from RouterBOOT 6.41.3 to 6.42rc49 without any problems.*) routerboot - fixed RouterBOOT upgrade process (introduced in v6.42rc);
Exactly!That is what I see too, so then you have lost the battleWhen you close your entire router they can use their 3G/4G connection.
Better to give good education.
Thank you for your report, the total-memory value will be reported correctly starting from the firmware version 6.42rc50Hi strods,atlanticd - Yes, that is the fix for the problem. Please test it and report back to us with the results.
I can confirm that the RouterBOOT firmware upgrade to 6.42rc46 works, and it is not causing boot loop anymore. However I noticed that after firmware upgrade (and only after Firmware upgrade, not ROS upgrade), the total memory and free memory shows much less than before. Instead of ~256 MB now it is ~128 MB.I reported earlier in another topic that interestingly my hAP ac^2 unit came with 256 MB unexpectedly, and a colleague from MikroTik support stated it that some unit came with more memory. Can you confirm that MikroTik now limit by intention the available memory in this new firmware just to meet the specs, even though the unit has more memory physically, or was it a software bug?Code: Select allfree-memory: 79.1MiB total-memory: 106.3MiB
Thank you.
[admin@sw-under] > interface bonding print
Flags: X - disabled, R - running
0 name="CoreUplink" mtu=1500 mac-address=64:D1:54:EA:BC:83 arp=enabled arp-timeout=auto slaves=sfp-sfpplus1,sfp-sfpplus2 mode=802.3ad primary=none link-monitoring=mii arp-interval=100ms arp-ip-targets="" mii-interval=100ms down-delay=0ms up-delay=0ms lacp-rate=1sec
transmit-hash-policy=layer-3-and-4 min-links=0
[admin@sw-under] > export
# jan/09/1970 16:55:12 by RouterOS 6.42rc43
# software id = E34N-V9KR
#
# model = CRS317-1G-16S+
# serial number = 7A1407CB40B1
/interface ethernet
set [ find default-name=sfp-sfpplus2 ] mac-address=64:D1:54:EA:BC:83
/interface bridge
add fast-forward=no igmp-snooping=yes name=bridge1 protocol-mode=none pvid=64 vlan-filtering=yes
/interface bonding
add lacp-rate=1sec mode=802.3ad name=CoreUplink slaves=sfp-sfpplus1,sfp-sfpplus2 transmit-hash-policy=layer-3-and-4
/interface bridge port
add bridge=bridge1 interface=ether1
add bridge=bridge1 frame-types=admit-only-vlan-tagged interface=CoreUplink pvid=4094 unknown-multicast-flood=no unknown-unicast-flood=no
/interface bridge vlan
add bridge=bridge1 tagged=CoreUplink untagged=bridge1,ether1 vlan-ids=64
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/system identity
set name=sw-under
/system package update
set channel=release-candidate
/system routerboard settings
set boot-os=router-os silent-boot=no
[admin@sw-under] >
/interface ethernet
set [ find default-name=sfp-sfpplus2 ] mac-address=64:D1:54:EA:BC:83
Not what you ask for, but you can send you log to syslog.hello guys, in the last rc49 release, I wanted to write my hotspot logs on micro sd, only that he can not write on disk1, he always writes on flash
RG 750g3
on the log action type menu, the sd name does not appear
Synology NAS can do it if you install the Log Center package and configure it as the syslog destination for your Mikrotik. QNAP probably does something similar.nice of the info, could I use the nas synology or qnap to save or view the logs?
backup,critical mikrotik: error creating backup file: could not read all configuration files
Does this mean, that RouterOS can now be installed on UEFI devices?*) chr - added support for booting from NVMe disks;
I am also experiencing this phenomenon.Neighbors search sometimes seen, sometimes not in winbox. (CRS326)
I am also experiencing this phenomenon.Neighbors search sometimes seen, sometimes not in winbox. (CRS326)
It seems that it takes a tremendous amount of time to search RB from Winbox (3.12). After about 10 minutes, I saw some things.
- CCR1009-8G1S-S+
- RB850Gx2
- RB2011UAS
The following RBs were not searched.
- RB3011UiAS
- RB962UiGS-5HacT2HnT
I've been waiting for this! Thanks!*) chr - added support for "multi-queue" feature for "virtio-net" driver;
Me too.I've been waiting for this! Thanks!*) chr - added support for "multi-queue" feature for "virtio-net" driver;
/system resource irq print where users~"virtio"
Good tip, thanks.Per CPU, I think. Check withCode: Select all/system resource irq print where users~"virtio"
We cannot see this ticket's contents.My LACP problem is still Present in this RC ([Ticket#2018031222001218] LACP HW problem reaching bridge)
5G With WiFi Password, Firmware 6.42RC52
Connecting to host 192.168.55.203, port 5201
[ 4] local 192.168.88.253 port 50625 connected to 192.168.55.203 port 5201
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-1.00 sec 46.2 MBytes 388 Mbits/sec
[ 4] 1.00-2.00 sec 21.2 MBytes 178 Mbits/sec
[ 4] 2.00-3.00 sec 28.4 MBytes 238 Mbits/sec
[ 4] 3.00-4.00 sec 49.1 MBytes 414 Mbits/sec
[ 4] 4.00-5.00 sec 48.9 MBytes 410 Mbits/sec
[ 4] 5.00-6.00 sec 49.3 MBytes 414 Mbits/sec
[ 4] 6.00-7.00 sec 48.6 MBytes 408 Mbits/sec
[ 4] 7.00-8.00 sec 33.8 MBytes 283 Mbits/sec
[ 4] 8.00-9.00 sec 34.8 MBytes 292 Mbits/sec
[ 4] 9.00-10.00 sec 50.0 MBytes 419 Mbits/sec
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bandwidth
[ 4] 0.00-10.00 sec 410 MBytes 344 Mbits/sec sender
[ 4] 0.00-10.00 sec 410 MBytes 344 Mbits/sec receiver
iperf Done.
Thank you very much for responding my post. Based on your information, I have already learned more about network bandwidth, throughput, and latency.When you compare tests made with different tools (e.g. iperf VS. CIFS) you have to be aware of behaviour of test "tools". Tests done using iperf are not affected by latency much (apart from usual TCP slow-start) while some more "chatty" protocol (such as CIFS file transfer) can be affected by larger latency quite much.
.......
.../system package> print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 routeros-arm 6.42rc52
1 system 6.42rc52
2 X ipv6 6.42rc52
3 wireless 6.42rc52
4 hotspot 6.42rc52
5 dhcp 6.42rc52
6 mpls 6.42rc52
7 routing 6.42rc52
8 ppp 6.42rc52
9 security 6.42rc52
10 advanced-tools 6.42rc52
.../system routerboard> print
routerboard: yes
board-name: cAP ac
model: RouterBOARD cAP Gi-5acD2nD
serial-number: **************
firmware-type: ipq4000L
factory-firmware: 3.43
current-firmware: 6.42rc52
upgrade-firmware: 6.42rc52
I also have Mimosa and there the DFS even takes the network down longer. Up to some 15-20 minutes. Partially also because when the AP if 'free'd' from the DFS it takes a long time before clients are associated back and in full running mode again. Actually, if your Mimosa P2MP network is hammered by DFS you might as well not use is it at all....... completely unusable. You have to find a band/channel that has no radar or no DFS restrictions. Only then it works. (there is no way of avoiding DFS in Mimosa product line, as we can with MT. )...
Is there any bug? DFS searching time is 10minutes ??
p.s.: found answer... : IEEE 802.18-08/0016r0
Radar Detect and DFS on MikroTik
https://www.youtube.com/watch?v=ZbrbRUAfpac
Is it possible to display the time in the status window?
I understood it.I also have Mimosa and there the DFS even takes the network down longer. Up to some 15-20 minutes. Partially also because when the AP if 'free'd' from the DFS it takes a long time before clients are associated back and in full running mode again. Actually, if your Mimosa P2MP network is hammered by DFS you might as well not use is it at all....... completely unusable. You have to find a band/channel that has no radar or no DFS restrictions. Only then it works. (there is no way of avoiding DFS in Mimosa product line, as we can with MT. )...
Is there any bug? DFS searching time is 10minutes ??
p.s.: found answer... : IEEE 802.18-08/0016r0
Radar Detect and DFS on MikroTik
https://www.youtube.com/watch?v=ZbrbRUAfpac
Is it possible to display the time in the status window?
What does it fix excatly? Does it improve connection stability?*) lte - fixed LTE band setting for SXT LTE;
noWhat does it fix excatly? Does it improve connection stability?*) lte - fixed LTE band setting for SXT LTE;
BGP4 MIB (RFC 4273) next please*) snmp - added w60g support;
/interface bridge add name=LAN
/interface bridge port add bridge=LAN interface=ether5
/interface bridge port add bridge=LAN interface=ether6
/interface bridge port add bridge=LAN interface=ether7
/interface bridge port add bridge=LAN interface=ether8
/interface vlan add name=POP-CENTRO-SECTOR-LESTE interface=LAN use-service-tag=yes vlan-id=100
/ip pool add name=PPPoE-RES-1M ranges=172.16.11.1-172.16.11.126
/ppp profile add dns-server=172.31.255.2,1.1.1.2 local-address=1.1.1.2 name="1 MEGA" rate-limit="1M/1M" remote-address=PPPoE-RES-1M
/interface pppoe-server server add disabled=no interface=POP-CENTRO-SECTOR-LESTE default-profile="1 MEGA" service-name=BRAS1
/interface bridge add name=bridge1
/interface bridge port add bridge=bridge1 interface=wlan1
/interface bridge port add bridge=bridge1 interface=ether1
/interface wireless set [ find default-name=wlan1 ] vlan-id=100 vlan-mode=use-service-tag
jan/01 21:04:16 pppoe,info PPPoE connection established from D4:6E:0E:BC:E2:FB
jan/01 21:04:16 pppoe,info PPPoE connection from D4:6E:0E:BC:E2:FB was already active - closing previous one
What kind of cases does it address?What's new in 6.42rc39 (2018-Mar-07 07:01):
*) ike1 - fixed wildcard policy lookup on responder;
In version 6.42rc52 on Hаp Ас^2 there are problems with Interface/interface list. Tools that use interface list do not work. Such as the MAC winbox server or parameter In. Interface list in firewall rules.After flashing latest 6.42RC52 Winbox not auto detect my hAP AC2.
L2TP/IPSec wasn't working for me in earlier RCsWhat kind of cases does it address?What's new in 6.42rc39 (2018-Mar-07 07:01):
*) ike1 - fixed wildcard policy lookup on responder;
I should have been more specific. Does it affect 6.41.3, or was introduced on this RC? Is it a problem with the wildcard no matching at all? Or matching too much? Or just matching incorrectly?L2TP/IPSec wasn't working for me in earlier RCsWhat kind of cases does it address?What's new in 6.42rc39 (2018-Mar-07 07:01):
*) ike1 - fixed wildcard policy lookup on responder;
Ah, thanks. Good to know.Yep, it was introduced in RC, just a few versions earlier. I noticed it on default configuration.
Let's hope is doesn't introduce new bugs after all that German beer.....Confirmation from MT in Mail RC55 will have fix for my LACP Bonding problem. Have a Nice week end and I hope for the soon Release of RC55. One wonder what more magical fixes will be included.
Everything works for me without issues. Can you repeat this reboot loop after Netinstall with RouterOS and RouterBOOThAP ac^2. When upgrading from rc52 to rc56, i get a bootloop again. Restored by netinstall.
.rc56
No. Now, with rc56, router reboot correctly.Can you repeat this reboot loop after Netinstall with RouterOS and RouterBOOTversions?Code: Select all.rc56
:global zmienna [/tool fetch mode=tftp address=192.168.88.1 src-path=test.txt output=user]
so there is two tests, one test and after few seconds - second test.hAP ac^2 upgraded correctly from rc52 to rc56 but wifi performance is still very poor - the same problem yhfung is talking about.
/queue type
add kind=mq-pfifo mq-pfifo-limit=10000 name=mq-pfifo-10k
/queue interface
set ether1 queue=mq-pfifo-10k
/ip dhcp-client
add dhcp-options=hostname,clientid disabled=no interface=ether1
/system package update
set channel=release-candidate
/system resource irq rps
set ether1 disabled=yes
interface w60g monitor wlan60-1
connected: yes
frequency: 58320
remote-address: 04:xxxxxx
mcs: 4
signal: 40
rssi: -68
tx-sector: 28
tx-sector-info: left 3.8 degrees, down 3.8 degrees
rx-sector: 96
I confirm this. Went back to 6.41.4 and PtMP is working again.In rc56 w60g multipoint is not working
Hi strods,
We run Proxmox (Debian 9 with KVM) and upgraded a CHR to 6.42rc 56 to test multi-queue VirtIO network support.
We set queues equal to the assigned CPU cores and upgraded the router. After booting RouterOS there are no entries in '/int ethernet'...