I suspect the changes in the bridge settings and behavior caused my hAP lite bridges to become unresponsive. I'd like to upgrade for the hardware offloading features but I'm afraid my devices will lock up again.After upgrade to 6.41.2 bridge mac address changed
*) bridge - fixed situation when packet could be sent with local MAC as dst-mac;
Provide results for:None of my 941-2nDs are able to upgrade. I have no files in files menu in winbox besides the regular ones. Yet the available space is only 6.9mb. The winbox will not start downloading the update, nor it is possible to upload a complete update file manually. I've tried recreating the flash folder and the flash/pub and flash/skins sub folders - no go. Please advise.
LucZWFM - Have you tried to Netinstall device? From which version did you upgrade your router? Can you install same version, same configuration and try to upgrade once more and reproduce the same problem;
No other devices with same mac, only one PC connected.PashaT - This has nothing to do with the fix which you referenced. Are you sure that there is no actual loop in your network? Are you sure that there is no other device in network with same MAC address as this routers ether3 interface;
When Detect Internet is activated on the interface without the address - invisible DHCP client running on that interface. Ether1 was added to detect interface list.
At RB3011 bootloop too.After upgrading my only just 3 months old 2011iL-RM got stuck in a bootloop and
I am not able to recover it, what ever I try..
Let me be clear: before the upgrade, each bridge had its own MAC address. After the upgrade, there were MAC address conflicts because some of the bridges had the same MAC address. This should never happen. This was on FACTORY DEFAULT firmware and settings.jackx - Please do not assume that if someone did upgrade model X device to specific version and it did not boot up that there is some version related problem with particular model device. It is possible, but usually it is false alarm. In most cases, when router becomes unavailable after upgrade, problem is caused due to configuration changes (affected by upgrade - admin did not see changes in changelog) or there was a problem during upgrade (upgrade happens on old version, not the one which you install);
Provide results for:None of my 941-2nDs are able to upgrade. I have no files in files menu in winbox besides the regular ones. Yet the available space is only 6.9mb. The winbox will not start downloading the update, nor it is possible to upload a complete update file manually. I've tried recreating the flash folder and the flash/pub and flash/skins sub folders - no go. Please advise.
/file print
Code: Select all
[mkadm@MikroTik] > /file print
# NAME TYPE SIZE CREATION-TIME
0 flash directory feb/09/2018 20:46:43
1 flash/pub directory feb/09/2018 20:46:43
2 flash/skins directory feb/09/2018 20:46:43
[mkadm@MikroTik] >
/system package print
Code: Select all
[mkadm@MikroTik] > /system package print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 routeros-smips 6.41.1
1 system 6.41.1
2 X ipv6 6.41.1
3 wireless 6.41.1
4 X hotspot 6.41.1
5 dhcp 6.41.1
6 X mpls 6.41.1
7 routing 6.41.1
8 X ppp 6.41.1
9 security 6.41.1
10 advanced-tools 6.41.1
[mkadm@MikroTik] >
Code: Select all
uptime: 16h14m40s
version: 6.41.1 (stable)
build-time: Jan/30/2018 10:26:14
free-memory: 6.0MiB
total-memory: 32.0MiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 650MHz
cpu-load: 9%
free-hdd-space: 7.0MiB
total-hdd-space: 16.0MiB
write-sect-since-reboot: 36352
write-sect-total: 39081061
bad-blocks: 0%
architecture-name: smips
board-name: hAP lite
platform: MikroTik
Thanks, it's works. In virtual WLAN dropdown "VLAN Mode" select "no tag" and reconnecting to both interfacesLakis, zervan, AntonReviakin - Please contact support@mikrotik.com regarding this issue. I assume that downgrade to 6.41.1 fix the problem and after upgrade to 6.41.2 again shows the same problem.
GreySer - What do you see on serial console? Did you try to Netinstall device?
jackx - If you did not have admin-mac configured, then bridge uses MAC address of first interface recognized by RouterOS. MAC can change between reboots, etc. I assume that downgrade to 6.41.1 fix the problem and after upgrade to 6.41.2 again shows the same problem?
mstead - This topic is created to find problems which were not in RouterOS in 6.41.1 and are in 6.41.2. Have you contacted support regarding this problem? We are not aware about such problem. Write to support@mikrotik.com regarding this problem.
i4ko - Have you had other RouterOS packages installed on the device in the past? If you reboot router is space freed up?
And the relevant portion from /system resource printProvide results for:None of my 941-2nDs are able to upgrade. I have no files in files menu in winbox besides the regular ones. Yet the available space is only 6.9mb. The winbox will not start downloading the update, nor it is possible to upload a complete update file manually. I've tried recreating the flash folder and the flash/pub and flash/skins sub folders - no go. Please advise.
/file printCode: Select all
[mkadm@MikroTik] > /file print
# NAME TYPE SIZE CREATION-TIME
0 flash directory feb/09/2018 20:46:43
1 flash/pub directory feb/09/2018 20:46:43
2 flash/skins directory feb/09/2018 20:46:43
[mkadm@MikroTik] >/system package printCode: Select all
[mkadm@MikroTik] > /system package print
Flags: X - disabled
# NAME VERSION SCHEDULED
0 routeros-smips 6.41.1
1 system 6.41.1
2 X ipv6 6.41.1
3 wireless 6.41.1
4 X hotspot 6.41.1
5 dhcp 6.41.1
6 X mpls 6.41.1
7 routing 6.41.1
8 X ppp 6.41.1
9 security 6.41.1
10 advanced-tools 6.41.1
[mkadm@MikroTik] >
Code: Select all
uptime: 16h14m40s
version: 6.41.1 (stable)
build-time: Jan/30/2018 10:26:14
free-memory: 6.0MiB
total-memory: 32.0MiB
cpu: MIPS 24Kc V7.4
cpu-count: 1
cpu-frequency: 650MHz
cpu-load: 9%
free-hdd-space: 7.0MiB
total-hdd-space: 16.0MiB
write-sect-since-reboot: 36352
write-sect-total: 39081061
bad-blocks: 0%
architecture-name: smips
board-name: hAP lite
platform: MikroTik
No and Noi4ko - Have you had other RouterOS packages installed on the device in the past? If you reboot router is space freed up?
There's no way to workaround the bug. We need a new RouterOS release or the dude client 6.41.2 which is not available now. I suspect it's not available because they know it's bugged and so last resource is to wait for next RouterOS release. Hope soon.Hi, could you solve the problem?Hi this ver not work in Windows system. Do not download from mikrotik.com. Info from Dude client:
bad http response from cloud
Please write more detailed what kind of wireless connectivity problems you see.After upgrading from version 6.39.3 [BugFix] to 6.41.1 and then to 6.41.2, my device [RB751U-2HnD] presented wireless connectivity problems.
I also upgraded the firmware, leaving it equivalent to the ROS.
The causes of the problem could not be identified in the logs.
Even after resetting and redoing all the settings one by one, it was not possible to keep the wireless connection stable.
Where did you get that link? Download page shows correct and working link:Ova for chr - 404 not found..
https://www.mikrotik.com/chr-6.41.2.ova
Isn't anyone from the team checking this basics stuff? We always have to report such trivial issues.
LucZWFM - Have you tried to Netinstall device? From which version did you upgrade your router? Can you install same version, same configuration and try to upgrade once more and reproduce the same problem;
The board refuses to appear in netinstall, tried on 3 computers now...
This make me unable to try anything...
I upgraded from 6.41.1.
Hi normis, from here - https://mikrotik.com/downloadWhere did you get that link? Download page shows correct and working link:Ova for chr - 404 not found..
https://www.mikrotik.com/chr-6.41.2.ova
Isn't anyone from the team checking this basics stuff? We always have to report such trivial issues.
https://download2.mikrotik.com/routeros ... 6.41.2.ova
Mikhail73 - Please send supout file from your router to support@mikrotik.com. In best case scenario provide two files - one from 6.41.2 and one from 6.41.1 where everything works just fine. This version does not have any wireless fixes;
CZFan - Does reboot free up some space on your router?
eifLZ9D8zSwW - You did - launch backup booter and reset router and bootloader configuration and then Netinstalled router. You could just skip the first part. However, if you had protected bootloader enabled (disabled reset button), then yes - you could not Netinstall router in any other way:
https://wiki.mikrotik.com/wiki/Manual:R ... bootloader
We do recommend to use protected bootloader only if you really need it and are aware how to recover device in case something goes wrong. If you simply decide to enable this feature without actually knowing what it does, most likely you will not be able to recover unit when something goes wrong and in the end will want to return device for warranty repair. However, there is no actual problem with the router.
Would this actually fix the issue I had in the start post of this topic?bridge - fixed ARP settings on bridge interfaces (introduced v6.41);
Done. Upgrade was from 6.41, not 6.41.1.Mikhail73 - Please send supout file from your router to support@mikrotik.com. In best case scenario provide two files - one from 6.41.2 and one from 6.41.1 where everything works just fine. This version does not have any wireless fixes;
What exactly is considered strange there?I found a couple of strange entries in the routing table after the upgrade on my hAP ac.
The new routes to 0.0.0.0/32 in the list which were not there before.What exactly is considered strange there?I found a couple of strange entries in the routing table after the upgrade on my hAP ac.
RB750Gr3 is a low cost product ment for home and small offices.Boot loop on RB750Gr3 too.
Datacenter offline. Night shift incomming. Thanks!
I have seen a wireless issue on two of the RB941-2nD I have. I don't know if it is the same or not.Please write more detailed what kind of wireless connectivity problems you see.After upgrading from version 6.39.3 [BugFix] to 6.41.1 and then to 6.41.2, my device [RB751U-2HnD] presented wireless connectivity problems.
I also upgraded the firmware, leaving it equivalent to the ROS.
The causes of the problem could not be identified in the logs.
Even after resetting and redoing all the settings one by one, it was not possible to keep the wireless connection stable.
/ip firewall filter add chain=forward dst-port=443 protocol=tcp tls-host=*google.com action=drop
What's new in 6.42rc24 (2018-Feb-08 09:42):
*) firewall - fixed "tls-host" firewall feature (introduced v6.41);
Finally manged to update remotely. While on 6.41.1 disabled all packages except for system, dhcp and wireless, and uploaded the same from the 6.41.2 all packages file to the router (those were all i had room for), then rebooted, all in one go. Now I no longer have any packages besides these (routeros-smips is also gone) but everything is working fine. This also dropped 1.5mb in disk usage, I'll add some of the other packages where I need them.i4ko - Most likely you will need to re-install devices by using Netinstall. However, I recommend that you send supout file from one of your routers to support. We might see in supout file what is filling up the space.
frequency-mode=regulatory-domain country=united kingdom
Thank you, I was using 3.11. In 3.12 problem is fixed.Do you use latest winbox version?
I've tried Netinstall ensuring "Apply Default Config" is ticked with various versions with the following resultsLIV2 - Have you tried to Netinstall your device and reset it only after that? Seems that default configuration has been changed to something else by using configuration script on Netinstall.
I suspect there are many routers out there where this value is set to arbitrary garbage due to recent (still current?) bug in Winbox where calling up /system routerboard settings always populates this value as 00:00:00 -- in red since zero is an invalid value -- and then demands the user set it to something nonzero before they can make the unrelated change they originally wished to make.Again - we strongly recommend to NOT use this feature if you are not aware about how it works. If you will not know min/max settings, then you will not be able to recover device in any way.
Sorry, I should have been more precise - what I experienced was on 6.41.2.First of all, please do not post version u relafed issues within new release topic
# Set UMTS Interface name
:global WanName "ppp-out1"
# get its ID number #
:local WanID [/interface ppp-client find name=$WanName];
# Change the data channel setting
/interface ppp-client set data-channel="3" $WanID
/interface ppp-client $WanID set data-channel="3"
No, the order is less obvious, 1. set 2. in which item 3. which attribute:If I get you right, interface should come before set-command in the last line:
Does this also apply when using interface names instead of ID's?Code: Select all/interface ppp-client $WanID set data-channel="3"
Thanks, BuzzDee.
/interface ppp-client set $WanID data-channel="3"
/interface ppp-client set [find name=$WanName] data-channel="3"
Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload
# INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON
0 eth2 bridge_local yes 1 0x80 10 10 none
1 eth3 bridge_local yes 1 0x80 10 10 none
2 I eth4 bridge_local yes 1 0x80 10 10 none
3 I eth5 bridge_local yes 1 0x80 10 10 none
interface bridge port print detail
Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload
0 interface=eth2 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto
external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1
frame-types=admit-all ingress-filtering=no
1 interface=eth3 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto
external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1
frame-types=admit-all ingress-filtering=no
2 I interface=eth4 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto
external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1
frame-types=admit-all ingress-filtering=no
3 I interface=eth5 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto
external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1
frame-types=admit-all ingress-filtering=no
In my RB750GR3 the same thing happens ... looking for more info I found this that seems to be the reason why what happens is what happens.Bridge on RB750Gr3 (6.41.2) seems to be broken.
1) No HW offload on ethernet interfaces after upgrade from 6.41.1:2) Bridge settings freezes constantly (for example, after trying to check/uncheck "igmp snooping", bridge completely shuts down and remain disabled for approx. 1 minute).Code: Select allFlags: X - disabled, I - inactive, D - dynamic, H - hw-offload # INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON 0 eth2 bridge_local yes 1 0x80 10 10 none 1 eth3 bridge_local yes 1 0x80 10 10 none 2 I eth4 bridge_local yes 1 0x80 10 10 none 3 I eth5 bridge_local yes 1 0x80 10 10 none interface bridge port print detail Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload 0 interface=eth2 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 1 interface=eth3 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 2 I interface=eth4 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 3 I interface=eth5 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no
It's slightly annoying....
Bridge on RB750Gr3 (6.41.2) seems to be broken.
1) No HW offload on ethernet interfaces after upgrade from 6.41.1:2) Bridge settings freezes constantly (for example, after trying to check/uncheck "igmp snooping", bridge completely shuts down and remain disabled for approx. 1 minute).Code: Select allFlags: X - disabled, I - inactive, D - dynamic, H - hw-offload # INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON 0 eth2 bridge_local yes 1 0x80 10 10 none 1 eth3 bridge_local yes 1 0x80 10 10 none 2 I eth4 bridge_local yes 1 0x80 10 10 none 3 I eth5 bridge_local yes 1 0x80 10 10 none interface bridge port print detail Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload 0 interface=eth2 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 1 interface=eth3 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 2 I interface=eth4 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 3 I interface=eth5 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no
It's slightly annoying....
/interface bridge
add name=bridge-internal protocol-mode=none
Then because the script of the default configuration of the RB750GR3 has set "protocol-mode = rstp" ??? It would be a problem to solve by Mikrotik support, since being in RSTP mode will never use HW OFF ...Bridge on RB750Gr3 (6.41.2) seems to be broken.
1) No HW offload on ethernet interfaces after upgrade from 6.41.1:2) Bridge settings freezes constantly (for example, after trying to check/uncheck "igmp snooping", bridge completely shuts down and remain disabled for approx. 1 minute).Code: Select allFlags: X - disabled, I - inactive, D - dynamic, H - hw-offload # INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON 0 eth2 bridge_local yes 1 0x80 10 10 none 1 eth3 bridge_local yes 1 0x80 10 10 none 2 I eth4 bridge_local yes 1 0x80 10 10 none 3 I eth5 bridge_local yes 1 0x80 10 10 none interface bridge port print detail Flags: X - disabled, I - inactive, D - dynamic, H - hw-offload 0 interface=eth2 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 1 interface=eth3 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 2 I interface=eth4 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no 3 I interface=eth5 bridge=bridge_local priority=0x80 path-cost=10 internal-path-cost=10 edge=auto point-to-point=auto external-fdb=auto horizon=none hw=yes auto-isolate=no restricted-role=no restricted-tcn=no pvid=1 frame-types=admit-all ingress-filtering=no
It's slightly annoying....
I have 750Gr3 and HW offload works, but you need to set Protocol Mode to "none".
Code: Select all/interface bridge add name=bridge-internal protocol-mode=none
FYI: 0 dBm does not mean "empty"/zero power. It is a valid value and means 1 mW. Still odd though, if it changed by itself....
Current Tx Power 2GHz - empty
...
The new chips have a new method of obtaining power data. not yet supported Route OS.ap - cAP ac (RouterBOARD cAP Gi-5acD2nD)
ARP table - empty
Current Tx Power 2GHz - empty
OS - 6.41.2
Even if you upgrade between stable versions, you should always backup the configuration and download the backup file from the router. Exporting it in the text form into another file (using "/export file=backup_version_today") is also a good practice because the "binary" backups from older versions are not always readable by newer versions. And noting down any credentials (in your case, especially those related to the PPPoE account) is also a good idea.My current router was ISP supplied and has all the default config on it. If i download this update and install it, will this setup be overwritten? Will i have issues due to PPPoE settings being factory reset ?
I'd suggest you to either join this topic or create a new one.I am sorry but I am still confused with the new bridge implementation
I updaten one of my wAP-ac to 6.41.2 and created a bridge - this bridge has an IP 10.0.100.4/24 and PVID1 because the AP itself is a part of the administrative-VLAN1-un-tagged (Internet-Cable-Modem to Firewall to Switch to wAP-ac via TRUNKs).
Connected to the bridge via PORT is the only one available ether1 - this port has a PVID1 as well because if I understood the brief explanation of MikroTik, it is need for the un-tagged ingress (from ether-cable to port-ether1 / port-ether1 to the bridge) traffic ... On this PORT there is a cable with Trunk (vlan1-un-tagged, vlan10-tagged, vlan20-tagged, etc.).
Frame-Types = admit all ... correct / why ?
Ingress-Filtering = unchecked ... correct / why ?
The next PORT to the bridge is the physical WLAN-chip (not vAP) - this port also has PVID1 because the SSID of the WLAN-chip is the administrative-VLAN1-un-tagged.
Frame-Types = admit all ... correct / why ?
Ingress-Filtering = unchecked ... correct / why ?
Now the vAP's ... e.g. vAP10, vAP20, vAP30, etc.
For example: vAP10 has PVID10
Frame-Types = admit only VLAN tagged ... correct / why ?
Ingress-Filtering = unchecked ... correct / why ?
Next is interface / bridge / VLAN:
I created VLAN ID = 1
Tagged = empty ... correct / why ?
Untagged = bridge, vlan1, wAP-2GHz, wAP5GHz ... correct / why ?
I created VLAN ID = 10
Tagged = bridge, vlan10 ... correct / why ?
Untagged = vAP10 ... correct / why ?
At the end I activated VLAN-Filtering under /interface bridge
One additional question ... is it needed to create the VLANs under /interface VLAN, too ?
As you see there are some puzzle-brickets I know but I am not able to make a picture of them
Any help is highly appreciated - especially with explanation
Go to Bridge -> Ports, remove ether1 and ether2 from the list, go to Interfaces -> Add new -> Bonding, set ether1 and ether2 as slaves, then maybe make the new bonding interface a member of that bridge from which you've removed ether1 and ether2. Done.Now i cant do that cos it say ether1 or 2 already on brigde1 .
Can someone tell me how to create bonding easy way on the firmware 6.41.2
Yes thnx was easy way .also in the end have to add ports with the bond created and brigde ..thnxxx againGo to Bridge -> Ports, remove ether1 and ether2 from the list, go to Interfaces -> Add new -> Bonding, set ether1 and ether2 as slaves, then maybe make the new bonding interface a member of that bridge from which you've removed ether1 and ether2. Done.Now i cant do that cos it say ether1 or 2 already on brigde1 .
Can someone tell me how to create bonding easy way on the firmware 6.41.2
Did you have any of bridge ports disabled?
I'll book a maintenance window for next weekend (10th March) and take a supout before and after upgrading.
I initially thought that it may relate to large number of bridge ports but the example above occurred on a router with 3 bridges, each with pairs...
I can also confirm that. CCR lost about half of bridge ports for no apparent reason after upgrading from 6.41 to 6.41.2. I also had to netinstall one hAP-AC with very simple config (simple CAP with all ports bridget + dhcp on bridge) which went into reboot loop after upgrade.We've had several instances of CCR routers losing bridge ports after upgrading from 6.41 to 6.41.2.