Are there plans to add ZeroTier to other architectures?Version 7.1 has been released.
!) support for ZeroTier on ARM and ARM64 devices;
Date: Thu, 19 Feb 2015 11:37:35 +0200
To: Fyodor Ustinov <ufm@xxxxxxxx.net.ua>
From: "MikroTik support [Janis M.]" <support@mikrotik.com>
[...]
...This problem will be solved in RouterOS v7, that we are trying to put into beta until
big European MUM.
It may be a space problem, so could be hard to get inn to all devices.Are there plans to add ZeroTier to other architectures?
There are two branches v6 and v7.
Each of them has their own channels, if there is v7 "testing", "stable" or whatever, it does not replace versions in v6 channels.
There is only one released v7 version (7.1), so it basically fills all the channels of v7 branch until newer version is built for specific channel.
/system/resource> print
uptime: 6m29s
version: 7.1 (testing)
build-time: Dec/01/2021 14:07:27
factory-software: 6.0
free-memory: 43.1MiB
total-memory: 96.0MiB
cpu: Intel(R)
cpu-count: 1
cpu-frequency: 2400MHz
cpu-load: 3%
free-hdd-space: 72.8MiB
total-hdd-space: 89.2MiB
write-sect-since-reboot: 1384
write-sect-total: 1385
architecture-name: x86_64
board-name: CHR
platform: MikroTik
I'm able to generate a kernel panic on a CCR2004-1G-12S+2XS (capsman controller) when I enable caps-mode on a 951Ui-2HnD. If I leave this enabled, the CCR is rebooting in a loop. Cap certificate was just generated, capsman controller is reached via IP, not discovery interface. There's nothing in the logs other than the kernel crash message.
I added a 941-2nD before, using the discovery interface, that works without causing a crash on the controller.
Connect a serial cable to this device, open the serial console, and make sure that you have successfully connected to RouterOS CLI.
Now leave the device running and console opened and reproduce the same problem again. After the problem appears, copy serial console output to a text file.
https://wiki.mikrotik.com/wiki/Manual:S ... al_Console
https://wiki.mikrotik.com/wiki/Serial_Port_Usage
yes, if you run v6, you can't accidentaly upgrade to v7. you have to manually select channel titled "upgrade" to do this. so everyone is safe and nobody is forced to use v7I believe MikroTik did this in part due to complaints: people with routers that have auto upgrade scripts to upgrade to the latest "stable" were complaining that they might have hundreds of devices upgrading to v7 unintentionally when v7 stable was released, and asked for a v7-stable release tree separate from the v6-stable release tree, and MikroTik has done this.
Thanks!I just tried to upgrade my hap ac3 but had to downgrade it back to 6.49.2 again. IPv6 throughput on 6.49.2 is 420Mbit/s but on 7.1 it's only 200Mbit/s. So that's a significant regression.
11:10:43 radvd,debug received Router Solicitation on interface=bridge
11:10:43 radvd,debug sending Router Advertisement on bridge
11:10:43 radvd,debug adding MTU option, MTU=1500
11:10:43 radvd,debug adding link-layer address option, mac-address=DC:2C:6E:xx:xx:xx
11:10:43 radvd,debug adding prefix=2a02:2f0d:xxx:xxx::/64
11:10:43 radvd,debug sendmsg failed on bridge (fe80:3133::de2c:6eff:xxxx:xxxx): Invalid argument
ipv6/settings/set disable-ipv6=yes
ipv6/settings/set disable-ipv6=no
Unfortunately, it does NOT work. Tested on several different devicesIt is already built in. When you do an in-pace upgrade of a router running v6 the rules will be update to v7.
It is advised to take a close look at them, though.
RouterOS 7.2 ? where is the download linkYou should only move to v7 if all the needed features are there. A decision was made, that we will not hold v7 release for much longer, because so many people can already use it, and it works great for 90% of users. People with specific needs for specific functions can then test 7.2 or next releases, but those who don't need them, can safely use 7.1 now.
Well, he did not say "big European MUM 2015", right? Maybe it was planned for the MUM 2021?I keep this letter fondly. I should check to see if this bug has been corrected or not. :)
Date: Thu, 19 Feb 2015 11:37:35 +0200
To: Fyodor Ustinov <ufm@xxxxxxxx.net.ua>
From: "MikroTik support [Janis M.]" <support@mikrotik.com>
[...]
...This problem will be solved in RouterOS v7, that we are trying to put into beta until
big European MUM.
Any status for MPLS L3?Soon
Easy Return to 6.49.2, problem solved. Did you send a supout to MT?OpenVPN client doesn't work in 7.1. It was working just fine with 6.49.2 and all previous versions. Here's the log:Please help.Code: Select all16:35:38 ovpn,info ovpn-out1: initializing... 16:35:38 ovpn,info ovpn-out1: connecting... 16:35:39 ovpn,info ovpn-out1: using encoding - AES-256-CBC/SHA1 16:35:39 ovpn,info ovpn-out1: terminating... - wrong OVPN data 16:35:39 ovpn,info ovpn-out1: disconnected
I do not understand why there is no support on the X86 architecture.It may be a space problem, so could be hard to get inn to all devices.Are there plans to add ZeroTier to other architectures?
The video missed the most important point......................PDF information: https://mt.lv/RouterOSv7
Video in Spanish: https://youtu.be/fzLxTl6VXRI
Video in English: https://youtu.be/Zp-U7Anv5-0
Video in Russian: https://youtu.be/xRGBbXJc1xA
This is fully understood, but doesn't explain why the speed dropped by about 60% going from 6.49.2 to 7.1. I assume both are only using the one core, so why is there such a regression in IPv6 speed in 7.1? If that's not resolved I will be stuck on 6.x until I replace the hap ac3 with something else one day in the far future. I know that 7.1 has a completely new IPv6 stack, but new things are usually an improvement and don't make them worse.For hAP ac2 all IPv6 traffic is bound to one core, I'm guessing it's valid for all ipq401x devices. You can't push very much through one core.
And your hAP ac has only one core.
I was frustrated with the crappy IPv6 speeds too, but I fixed it, upgraded to RB5009.
Works well on my CCR2004-1G-12S+2XSNTP webfig UI seems broken, it doesn't display servers, and edits are not applied. 7.1/CCR2004
I have same issue with ipv6 on hAP AC after upgrade. No connections, filter rules with established/related filter doesn't work. It looks like connection tracking doesn't work properly....
3. ipv6 > fw > cvonnections
is empty with none connections
4. ipv6 > fw > filter rules
i have accept established/related connections and after that
i have drop invalid.
With above setup, all connections drop as invalid (tcp syn,ack,syn/ack, udp).
The above setup work perfect in 6.x editions.
See here:I'm not that desperate, yet.. How can I send supout to MT?Easy Return to 6.49.2, problem solved. Did you send a supout to MT?
VXLAN with unicast works its not documented properly nor does Mikrotik team bother to check forum. Use any arbitrary multicast id on the vxlan interface. In terminal go to interfaces/vxlan/vteps >add vtep interface=<vxlan interface> remote=<remote address> port=<vxlan port>VXLAN cannot be configured with unicast addresses but multicast routing is poorly documented and does not seem to work, etc. etc. etc.
Most people would not consider software with so many bugs "stable."
In case the hAP ac2 is running the single combined package it will probably work, when it is running separate packages you will need to do a netinstall.On hap ac2 with 16 MiB storage can I upgrade directly from 6.49.2 to 7.1 via upgrade channel (if yes will v6.49.2 config be valid for v7.1 ?) or do I have to use netinstall instead and make a fresh install ? Are there any advantages for hap ac2 of version 7 or should i stick with v6 ?
A birdy whispered this one to me in response to VTI.....I was kind of waiting for it... after the requests for VTI there would be DMVPN.
But of course IPsec technology and MikroTik routers already support quite easy to deploy mesh networks (especially with 7.1) but not with the Cisco proprietary standards.
When you have only MikroTik or when you have access to the Cisco configuration you can use e.g. GRE over IPsec transport and BGP for the autorouting, and have similar functionality to VTI or DMVPN.
Asking MikroTik for DMVPN is like asking Microsoft to support Apple iOS applications... you can try and keep trying, but they will encounter hurdles and maybe have other priorities.
+1 for The Dude Server...- The DUDE server is not available under 7.1 packages. Therefore we had to leave our CHR and Dude server in 6.49.2.
No, but when you can configure the other end as well you can configure that with IPIP/IPsec or GRE/IPsec and it will work.Can birdie "connect IPIP tunnel encrypted using IPsec policy in transport mode" to IPsec VTI?
No, birdie can't connect those two.
Well, easier way of thinking about it is: "target-scope must be lower on each level of recursion"Heh, I am not sure if I need to take a philosophy course or go to Hogwarts School of Magic to understand that sentence let alone MTs intentions. Never understood scope anyway (at least nothing sticks in my brain).
They do work. v7 introduced a new limitation: target-scope of your route must be greater than target-scope of the route through which it should be resolved.
How are you testing the IPv6 speed in 7.1? The test method may have something to do with it.This is fully understood, but doesn't explain why the speed dropped by about 60% going from 6.49.2 to 7.1.
Four different speed tests. speedtest.net, fast.com, my ISPs own speedtest server, and one at AWS. I have Gbit fibre. With IPv4 it goes at 920Mbit/s on both 6.49.2 and 7.1. With IPv6 it goes at 420Mbit/s on 6.49.2. Upgrade to 7.1 and it drops to 200Mbit/s on all four different speedtests. Downgrade it back to 6.49.2 and it's back up to 420Mbit/s again.How are you testing the IPv6 speed in 7.1? The test method may have something to do with it.This is fully understood, but doesn't explain why the speed dropped by about 60% going from 6.49.2 to 7.1.
Same. IPv6 is broken on hAP ac. Earlier I asked about v7 IPv6 forwarding speed. Guess it's 0 Mbit/s for hAP ac.I have same issue with ipv6 on hAP AC after upgrade. No connections, filter rules with established/related filter doesn't work. It looks like connection tracking doesn't work properly....
3. ipv6 > fw > cvonnections
is empty with none connections
4. ipv6 > fw > filter rules
i have accept established/related connections and after that
i have drop invalid.
With above setup, all connections drop as invalid (tcp syn,ack,syn/ack, udp).
The above setup work perfect in 6.x editions.
Same here with RB4011. I had to restore to factory defaults via console and revert to 6.49Tried to update RB4011 from 6.49.1 to 7.1 (very simple setup). Reboot went fine, but after FW update the device went unusable (no IP address on any interface, no access via MAC (even directly connected to the device), but winbox showed is as neighboured). Netinstall ...
Unfortunately this is expected. Route caching no longer exists in v7 and in v6 it gave an artificial boost (usually double or even more) to the actual real world bandwidth that you could get, for speed tests and bulk downloads. So on RouterOS v6 you are getting a speedtest result of 420Mbps, but the actual real world traffic with normal traffic patterns would probably drop it down to below 200Mbps capacity, because unlike speed tests and big file downloads, normal real world traffic patterns are mostly cache miss events, decreasing performance.Four different speed tests. speedtest.net, fast.com, my ISPs own speedtest server, and one at AWS. I have Gbit fibre. With IPv4 it goes at 920Mbit/s on both 6.49.2 and 7.1. With IPv6 it goes at 420Mbit/s on 6.49.2. Upgrade to 7.1 and it drops to 200Mbit/s on all four different speedtests. Downgrade it back to 6.49.2 and it's back up to 420Mbit/s again.
Thanks. That solves it.
[admin@router] /routing/route> print detail where afi=ip6 dst-address=::/0
Flags: X - disabled, F - filtered, U - unreachable, A - active;
c - connect, s - static, r - rip, b - bgp, o - ospf, d - dhcp, v - vpn, m - modem, a - ldp-address, l - ldp-mapping, y - copy;
H - hw-offloaded; + - ecmp, B - blackhole
Av + afi=ip6 contribution=active dst-address=::/0 routing-table=main pref-src="" gateway=pppoe
immediate-gw=pppoe distance=1 scope=30 target-scope=10 belongs-to="VPN route"
debug.fwp-ptr=0x202423C0
Ad + afi=ip6 contribution=active dst-address=::/0 routing-table=main pref-src=""
gateway=fe80::ae4e:91ff:fe66:ecc9%pppoe immediate-gw=pppoe distance=1 scope=30 target-scope=10
vrf-interface=pppoe belongs-to="DHCP route"
debug.fwp-ptr=0x20242360
Interesting. Do you have more details on how/why this works?Unfortunately this is expected. Route caching no longer exists in v7 and in v6 it gave an artificial boost (usually double or even more) to the actual real world bandwidth that you could get, for speed tests and bulk downloads.
Route caching was a feature in the Linux kernel that was taken out about 10 years ago. It created a "cache" of routes based on source and destination hashes to improve performance. However, the large number of port scanners that started to appear caused the cache to fill up with garbage src-destination pairs, making performance even worse than if it didn't exist. So route caching was removed from the Linux kernel because of this. In RouterOS v6 it makes speedtests faster for one system, or a big file download for one system faster, but with real world traffic for a bunch of clients to a bunch of different destinations is much slower on RouterOS v6 because it has to look in the cache first, and the cache actually slows things down in this case. So RouterOS v7 is actually faster in general, it just appears to be slower because of what route caching does with a speed test. A better way of comparing v6 and v7 performance would be to set up a bunch of systems behind the router and have a bunch of users going to many websites to try to create as much traffic as possible, but that is too much work for most people.Interesting. Do you have more details on how/why this works? Why is a cache relevant if it's traffic from a single originating IP?
Yes, that's true - anything like a speedtest or big file download and similar bulk transfer between an IP pair will mostly hit the cache (100% or close), but usually people only download big files and do speed tests very irregularly and not very often at all, so it does not represent most users typical traffic patterns.on a home connection it seems easy to hit the cache on a single download (I'm sure it was slightly faster in practice than my benchmark)
You should just email support with a supout file, it is preferred to a .backup.Bootloop in starting kernel with version 6 bonding. I can send my .backup to support for review, just write to me.
Not possible, the router never startsYou should just email support with a supout file, it is preferred to a .backup.Bootloop in starting kernel with version 6 bonding. I can send my .backup to support for review, just write to me.
On hEX(RB760iGS) the same issue... in 6.49.2 i can get full 600Mbit/s up and down(without any ipv6 rule on firewall) and 400 Mbit/s up/down(with ipv6 firewall rule)I just tried to upgrade my hap ac3 but had to downgrade it back to 6.49.2 again. IPv6 throughput on 6.49.2 is 420Mbit/s but on 7.1 it's only 200Mbit/s. So that's a significant regression.
Please see my previous response, this is normal and expected:With 7.1 i can only get 300Mbit/s with ipv6 enabled, with or without rules on ipv6 firewall.
Yeah i see...Please see my previous response, this is normal and expected:With 7.1 i can only get 300Mbit/s with ipv6 enabled, with or without rules on ipv6 firewall.
viewtopic.php?p=896088#p896045
And see the following messages as well where more detail and context was provided.
Because in both RouterOS v6 and v7, there is fasttrack available for IPv4 and not IPv6. When you use this it decreases the CPU load of IPv4 traffic, and it is enabled by default. So this gives you a "boost" for IPv4 that isn't there for IPv6. In RouterOS v6 there was the route cache that gave an artificial boost to speedtest traffic and similar bulk transfers, which helped the IPv6 speedtest results a bit, but now this is gone in v7. You should get full speed when they finally add fasttrack for IPv6 in RouterOS v7 - I'm sure this is in the pipeline.On 7.1 if i disable ipv6 on my machine, i can get full speed too
Yes, this is already known - I am guessing it will probably make an appearance in 7.2 as it was not ready, you can use the rc3 if you really need it.Container is missing?
Thank's, i will wait for news on ipv6 fasttrack before report any "no issue" related things. As for now i will keep on 6.x because i really need that speed and i don't want buy a new router just for this rsrsBecause in both RouterOS v6 and v7, there is fasttrack available for IPv4 and not IPv6. When you use this it decreases the CPU load of IPv4 traffic, and it is enabled by default. So this gives you a "boost" for IPv4 that isn't there for IPv6. In RouterOS v6 there was the route cache that gave an artificial boost to speedtest traffic and similar bulk transfers, which helped the IPv6 speedtest results a bit, but now this is gone in v7. You should get full speed when they finally add fasttrack for IPv6 in RouterOS v7 - I'm sure this is in the pipeline.On 7.1 if i disable ipv6 on my machine, i can get full speed too
Obviously if there were a secondary problem here, it would be hard to diagnose if you can't really use speedtest to verify it, but my suspicion in your case is that there is probably no issue. Even a few months back, I already foresaw when MikroTik did the stable release of v7 that there would be many people popping up to say that there was some major issue because their router was slower than before, but that most of those would be noise and non-issues because of the route caching removal reducing speedtest results. Unfortunately that noise makes it hard to separate the people who are having real issues that they shouldn't be having from the people who are just experiencing the slower speedtest results in v7 due to the route caching change.
One thing that you could try that would be a good test in RouterOS v7 only would be to try going into your IPv4 firewall, disabling the fasttrack-connection rule, and see how it impacts your IPv4 speed - it should make it the same as IPv6 with about the same number of firewall rules.Thank's, i will wait for news on ipv6 fasttrack before report any "no issue" related things. As for now i will keep on 6.x because i really need that speed and i don't want buy a new router just for this rsrs
In my testing with CRS317 and CRS326 it is stable, just make sure you run RouterOS 7.1 or newer.Is MLAG stable in version 7.1 for use in data centers?
2 x Switch CRS326-24S+2Q+RM configured with one bridge, multiple ports with different PVID and with several ports configured as tagged?
OSPF auth is broken, they have said it will be fixed in the next release.still have checksum warnings on ospf with simple auth
:local voltage [/system health get [find where name="voltage"] value=value];
:put ($voltage*10);
Same issue here with a RB1100AHx4. Nothing happens....trying to upgrade a CHR, is anyone getting this too?
@MikroTik] /system package update> download
channel: upgrade
installed-version: 6.49.2
latest-version: 7.1
status: calculating download size..
been like this for hours
Best to create a separate post with export of your config.I have 3 AP hAP ac2 managed via CAPsman on HEXs. After upgrading from 6.49.2 to 7.1 I have a problem. On devices that connect to AP the following message is displayed: Connected. Internet connection is unavailable. Despite this message, there is no internet connection on some devices on others. They connect to the same AP. Worse still, there are problems with devices connected by cable. Some have access to the Internet, others do not. They all correctly receive their settings from DHCP. When I go back to 6.49.2 everything works as it should. I just need to upload the settings backup file to hEXs.
Yes it does. Even if its stable.Version information showing 7.1 (testing)
This works for me:Helo Helo. Multiplication does not work.
{
local volt [/system health get voltage]
:put ($volt/10)
}
or
:put ([/system health get voltage]/10)
:put [/system health get [find where name="voltage"] value=value]
12.2
do={
:do {
# New version
:foreach id in=[/system health find] do={
:local health "$[/system health get $id]"
:set ( "$health"->"script" ) "health"
:log info message="$health"
}
} on-error={
# Old version
:if (!([/system health get]~"(state=disabled|^\$)")) do={
:local health "$[/system health get]"
:set ( "$health"->"script" ) "health"
:log info message="$health"
}
}
}
I did, but obviously not all :)Didn't you read any of posts in this thread? The only way of installing ROSv7 on de-bundled ROSv6 hAP ac2 is netinstall.
You could at least have opened the topic and do a Ctrl-F search for "hAP ac2"... it is mentioned several times already.I did, but obviously not all :).Didn't you read any of posts in this thread? The only way of installing ROSv7 on de-bundled ROSv6 hAP ac2 is netinstall.
Same Problem here. CCR1009 with Capsman "on" crash and reboot in loop without logging any Problem.
I have the same settings as your attachment.
add action=accept chain=forward comment=\
"Forward accept established, related connections" connection-state=\
established,related
add action=drop chain=forward comment="Forward drop invalid connections" \
connection-state=invalid
add action=accept chain=forward comment="Forward accept ICMP" protocol=icmpv6
add action=drop chain=forward comment="Forward drop all not from LAN" \
Anyone else having these issues - and possibly a resolution? I have created a support ticket, but no response yet. Would like to upgrade, but it is impossible....Same issue here with a RB1100AHx4. Nothing happens....trying to upgrade a CHR, is anyone getting this too?
@MikroTik] /system package update> download
channel: upgrade
installed-version: 6.49.2
latest-version: 7.1
status: calculating download size..
been like this for hours
Flags: D - DYNAMIC; A - ACTIVE; c, d, v, y - COPYI didn't post any settings. The screenshots are obviously from the non-working scenario, read what I wrote there.
Also what Quasar wrote above: viewtopic.php?t=180831&start=300#p896048
Post your routes too.
I do see many post here about this, that you can download the package and copy it to files and reboot.Anyone else having these issues - and possibly a resolution? I have created a support ticket, but no response yet. Would like to upgrade, but it is impossible....
Can confirm both on hAP ac2 migrated from v6.49.1NTP webfig UI seems broken, it doesn't display servers, and edits are not applied. 7.1/CCR2004
The release also still says "testing", I assume since it was not rebuilt.
bridge1 include all ethers except the ether1 in which is connected the modem (bridge mode).@denisun I see nothing wrong in the bits and pieces provided.
Enable logging on that invalid fw rule and try to figure out why those packets are considered invalid.
Is bridge1 still in LAN interfaces list?
Yes, where is das mug link?!?The video missed the most important point......................PDF information: https://mt.lv/RouterOSv7
Video in Spanish: https://youtu.be/fzLxTl6VXRI
Video in English: https://youtu.be/Zp-U7Anv5-0
Video in Russian: https://youtu.be/xRGBbXJc1xA
Where do I get that Unicorn MuG!!
Normis email me to get my physical address for mug package!
On a serious note.
community filtering addressing???
zerotier (sdwan) for the home....... what will it allow me to do??
/interface/list/member/print
Columns: LIST, INTERFACE
# LIST INTERFACE
0 LAN bridge
1 WAN pppoe-wan1
No, I would not dare to do such an upgrade on a remote device! At least I would first make sure there is someone available near the device to do things like powercycling and preferable also able to recover it using netinstall.Has anyone else experienced anything like this?
If there are no need for function from 7.1 do not upgrade yet.Has anyone else experienced anything like this?
I totally agree with Jotne: do NOT upgrade on business critical systems yet!If there are no need for function from 7.1 do not upgrade yet.Has anyone else experienced anything like this?
When upgrade, do it on a 100% equal unit with same configuration and same RouterOS as the remote.
If that goes well, it may be that you can upgrade the remote device.
Remote devices need to be upgraded too at some point and it is not always possible to have someone on site to hard reset or even netinstall. I'm sure there are many, many of us who manage remote Mikrotik devices (especially in home & soho environment) on behalf of dumb users on the other side. In such cases it could be a nightmare if the upgrade fails catastrophically. Hopefully reliability of upgrades will continue to be improved..No, I would not dare to do such an upgrade on a remote device! At least I would first make sure there is someone available near the device to do things like powercycling and preferable also able to recover it using netinstall.Has anyone else experienced anything like this?
Hi @Znevna .@denisun, I've asked if your bridge, "bridge1" is in LAN interfaces list.Code: Select all/interface/list/member/print Columns: LIST, INTERFACE # LIST INTERFACE 0 LAN bridge 1 WAN pppoe-wan1
add action=drop chain=input comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
add action=drop chain=forward comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
Will do this evening. Was worried that the reason for this state is connected to an issue with my HW not permitting (supporting) upgrade....I do see many post here about this, that you can download the package and copy it to files and reboot.Anyone else having these issues - and possibly a resolution? I have created a support ticket, but no response yet. Would like to upgrade, but it is impossible....
Have your tried that?
Example this post:
viewtopic.php?t=181021
Where is this post?So how do you expect your firewall to function properly?
You have two rules that use the LAN interface listCode: Select alladd action=drop chain=input comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN add action=drop chain=forward comment="defconf: drop everything else not coming from LAN" in-interface-list=!LAN
/ipv6 firewall filter
add action=accept chain=input comment=\
"Input accept established, related connections" connection-state=\
established,related
add action=drop chain=input comment="Input drop invalid connections" \
connection-state=invalid
add action=accept chain=input comment="Input accept ICMP" protocol=icmpv6
add action=accept chain=input comment="Input accept DHCPv6 client" dst-port=\
546 protocol=udp
add action=drop chain=input comment="Input drop all not from LAN" \
in-interface=pppoe-out1
add action=accept chain=forward comment=\
"Forward accept established, related connections" connection-state=\
established,related
add action=drop chain=forward comment="Forward drop invalid connections" \
connection-state=invalid
add action=accept chain=forward comment="Forward accept ICMP" protocol=icmpv6
add action=drop chain=forward comment="Drop no forward IP" dst-address-list=\
NoForwardIP out-interface=pppoe-out1
add action=drop chain=forward comment="Forward drop all not from LAN" \
in-interface=pppoe-out1
First try it with the default firewall rules without your own "improvements".This is my complete rules in fw filter in ipv6:
That is correct. You need to create new routing tables under the routing->table menu now.can't input text in this column
Could you post the default rules?First try it with the default firewall rules without your own "improvements".This is my complete rules in fw filter in ipv6:
/system/default-configuration/print
Because this stable release needs some public testing. I guess Mikrotik does only some kind of smoke tests. Can't expect to catch all cosmetic issues.Whay CPU Blank?
I have also a hap ac² with same issueI have same issue with ipv6 on hAP AC after upgrade. No connections, filter rules with established/related filter doesn't work. It looks like connection tracking doesn't work properly....
3. ipv6 > fw > cvonnections
is empty with none connections
4. ipv6 > fw > filter rules
i have accept established/related connections and after that
i have drop invalid.
With above setup, all connections drop as invalid (tcp syn,ack,syn/ack, udp).
The above setup work perfect in 6.x editions.
i have exactly the same problem even the default conf.Check the default configuration scriptSo many problems in v7 that are just user errors, but no, "v7 is bad!!11 v6 worked fine!!11"Code: Select all/system/default-configuration/print
Last "official" info was that IPv6 fast track is in the backlog but not yet on the roadmap.You should get full speed when they finally add fasttrack for IPv6 in RouterOS v7 - I'm sure this is in the pipeline.
It works fine here! Are you sure your interface lists (LAN, WAN) are correct?All traffic in ipv6 forward go to drop invalid.
i use it with and without interface list.It works fine here! Are you sure your interface lists (LAN, WAN) are correct?All traffic in ipv6 forward go to drop invalid.
Maybe it is better that you reset the entire router to default, when you don't have a lot of special config in there this is much easier.
i did it like thisHelo Helo. Multiplication does not work.
Script:
Code: Select all:local voltage [/system health get [find where name="voltage"] value=value]; :put ($voltage*10);
Result:
00:02:07
Result is wrong
:local voltage [/system health get [find where name="voltage"] value=value];
:local volArr [:find $voltage "."];
:local volNum $voltage;
:if ([:len $volArr] > 0) do={ :set volNum [:tonum "$([:pick $voltage 0 $volArr])$([:pick $voltage 1 $volArr])"]; } else={ :set volNum [:tonum "$($volNum)0"]; }
:put $volNum;
VTI supported on plenty of platforms and operating systems, not just Cisco. It is too widespread to find justifications for not implementing it.It is not VTI. It is not DMVPN. But it is not Cisco, the inventor of those proprietary protocols.
Support was finally able to reproduce this and I think we have found the problem. I believe there may be a fix soon.I have a ticket open regarding this: SUP-63430After upgrading my RB4011 home router, SSH sessions to remote servers don't work. To make them work again, I have to set on the SSH client another IPQoS (e.g. cs1). Is it normal?
Support is saying they cannot reproduce it.
oh, come on...you have a download button for router os on the rb5009 product page. points to 6.49.2 though.
LTE works fine in v7, please make a separate post or contact support via our portal
Totally agree, V7 need to be go forward as it has lots of new features, Normis but I don't have backup now, as updated to 7.1 and LTE stop working. :)
That would be great! Maybe it fixes my problem as well! (I would need to find a manageble gbit switch to debug it further - to have a mirror port external to the router)Support was finally able to reproduce this and I think we have found the problem. I believe there may be a fix soon.
7.1 is newer, it includes everyting that was in rc77.1rc7 version is newer than final 7.1?
or iclude all changes in 7.1 from rc7?
You could change to Checkpoint with their 2.6 or 3.10 kernel...Mikrotik releases to the market a product with an outdated kernel. The RouterOS v7.1 is still in the testing phase. When v7 will be really stable the kernel will be ancient. And the cycle will repeat for RouterOS v8. It will take 10 years to complete it, by the time v8 will be stable the kernel will be ancient.
Mikrotik is forcing us to consider other vendors! :(
Came here to say this. Lot's of enterprise appliances runs on custom (older) kernels, no problems there. Especially if that kernel is downsized to the bare minimum, which results in a lower attack vector.You should understand that MikroTik does not use the standard kernel but applies a lot of patches (changes) to it.
That is why it is not so easy for them to "just upgrade to the recent kernel". They spent a lot of work over the past year(s) to apply the patches to the kernel
they have now, and "please use a newer kernel" will set back the v7 release another year.
(ok maybe not so much, because of course a lot of work done on patching the 5.x kernel can still be used in a higher version because the differences are less than with the previous kernel from RouterOS v6)
It is not the same as in your home PC where you are running a standard distribution kernel and can "just" update it when you like.
really?So, I've tried to update my RB4011iGS+5HacQ2HnD-IN yesterday, and this is a summary of me upgrading all day;
[admin@hEX S] > caps-man/radio/print detail
Flags: L - local; P - provisioned
0 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - kuchyn" interface=c2-cAP ac - kuchyn-1
1 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - kuchyn" interface=c5-cAP ac - kuchyn-1
2 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - obyvak" interface=c2-cAP ac - obyvak-1
3 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - obyvak" interface=c5-cAP ac - obyvak-1
4 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="hAP lite" interface=c2-hAP lite-1
5 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac" interface=c2-cAP ac-1
6 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac" interface=c5-cAP ac-1
[admin@hEX S] > caps-man/remote-cap/print detail
0 state="Run" name="[XX]" radios=2 address=x.x.x.x/50930 board="RBcAPGi-5acD2nD" version="7.1" identity="cAP ac - kuchyn"
1 state="Run" name="[XX]" radios=2 address=x.x.x.x/45591 board="RBcAPGi-5acD2nD" version="7.1" identity="cAP ac - obyvak"
2 state="Run" name="[XX]" radios=1 address=x.x.x.x/47335 board="RB941-2nD" version="6.49" identity="hAP lite"
3 state="Run" name="[XX]" radios=2 address=x.x.x.x/38077 board="RBcAPGi-5acD2nD" version="6.49" identity="cAP ac"
This is caused by the setting of "local address" in the connection, where in v6 an interface name was allowed and now it requires an IP address.So, I've tried to update my RB4011iGS+5HacQ2HnD-IN yesterday, and this is a summary of me upgrading all day;
[*]BGP was broken, with this in the Log "Write to bgp failed (9) { #buf=10 max=64 sk=Socket{ -1[0] } }"
I think that's a thing of the past. Remember that RoS 7.0.x moved from kernel 5.x (I think it was 5.3) to 5.6? Things are much easier now - I think Mikrotik got rid of 90%* of the inhouse kernel patches.You should understand that MikroTik does not use the standard kernel but applies a lot of patches (changes) to it.
That is why it is not so easy for them to "just upgrade to the recent kernel". They spent a lot of work over the past year(s) to apply the patches to the kernel
they have now, and "please use a newer kernel" will set back the v7 release another year.
(ok maybe not so much, because of course a lot of work done on patching the 5.x kernel can still be used in a higher version because the differences are less than with the previous kernel from RouterOS v6)
It is not the same as in your home PC where you are running a standard distribution kernel and can "just" update it when you like.
No, linux was upgraded from 3.3 to 5.6...... moved from kernel 5.x (I think it was 5.3) to 5.6? ...
It worked for 12 hours flawless, and all at a sudden it crashes. This is all done with a clean factory reset and build op from scratch config. I can see it's the CAPsMAN itself, crashing.really?So, I've tried to update my RB4011iGS+5HacQ2HnD-IN yesterday, and this is a summary of me upgrading all day;
A few months on the RC version and now on 7.1. No problem. Problem is in configuration.
Code: Select all[admin@hEX S] > caps-man/radio/print detail Flags: L - local; P - provisioned 0 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - kuchyn" interface=c2-cAP ac - kuchyn-1 1 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - kuchyn" interface=c5-cAP ac - kuchyn-1 2 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - obyvak" interface=c2-cAP ac - obyvak-1 3 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac - obyvak" interface=c5-cAP ac - obyvak-1 4 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="hAP lite" interface=c2-hAP lite-1 5 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac" interface=c2-cAP ac-1 6 P radio-mac=XX remote-cap-name="[XX]" remote-cap-identity="cAP ac" interface=c5-cAP ac-1 [admin@hEX S] > caps-man/remote-cap/print detail 0 state="Run" name="[XX]" radios=2 address=x.x.x.x/50930 board="RBcAPGi-5acD2nD" version="7.1" identity="cAP ac - kuchyn" 1 state="Run" name="[XX]" radios=2 address=x.x.x.x/45591 board="RBcAPGi-5acD2nD" version="7.1" identity="cAP ac - obyvak" 2 state="Run" name="[XX]" radios=1 address=x.x.x.x/47335 board="RB941-2nD" version="6.49" identity="hAP lite" 3 state="Run" name="[XX]" radios=2 address=x.x.x.x/38077 board="RBcAPGi-5acD2nD" version="6.49" identity="cAP ac"
The changes of the kernel are the core business of MikroTik.Mikrotik can outsource the work on the kernel and they focus on theirs (Mikrotik) part of the product. Somebody else can work on the kernel, so Mikrotik will have more resources to work with.
Yes it is likely CAPsMAN because I have a RB4011 and a hAP ac2 both running 7.1 without CAPsMAN and I have not seen a single WiFi problem.It worked for 12 hours flawless, and all at a sudden it crashes. This is all done with a clean factory reset and build op from scratch config. I can see it's the CAPsMAN itself, crashing.
kernel 5.6 never was a LTS kernel. These versions between LTS go EOL instantly when the next version goes public. So 5.6 was EOL on the day 5.7 launched. I won't put too much focus on that detail. but not receiving security updates may be a critical thing.RouterOS v7 born died. Because kernel 5.6 it's EOL [1]
Mikrotik should change the kernel to a longterm kernel, like 5.10. And as I read it relies on 5.6.3 while the last version it's 5.6.19.
[1] https://9to5linux.com/linux-kernel-5-6- ... el-5-7-now
... or Linux 5.15, which is a LTS release as well and supported till October 2023 at least.[...] But I agree, they should raise to 5.10 LTS - that has support till end of 2026!
Current situation; switched off CAPsMAN and configured Wireless by hand, BGP somewhat working, except BGP-redistribution towards a Fortigate (Linux+Bird and a CHR-VM works fine), BFD switched off.Yes it is likely CAPsMAN because I have a RB4011 and a hAP ac2 both running 7.1 without CAPsMAN and I have not seen a single WiFi problem.It worked for 12 hours flawless, and all at a sudden it crashes. This is all done with a clean factory reset and build op from scratch config. I can see it's the CAPsMAN itself, crashing.
Due to a bug you cannot upgrade from separate packages to single package on some devices. This is not really a lack of space.to Mikrotik: is it possible to create light main packages to switch from extra v6 packages to v6 / v7 main package? They could only contain the system, dhcp, system, wireless packages. hAP ac2, disk lite5 ac etc. cannot be upgraded to main package remotely due to "system, error not enough space for upgrade"
Not exactly. Looking through the changelog, we have:No, linux was upgraded from 3.3 to 5.6...... moved from kernel 5.x (I think it was 5.3) to 5.6? ...
Had the same problem but then in firewall. I had double entries in the table and as soon I changed one entry and save Winbox crashed.Winbox Crash after remove bridge port columns on DHCP Lease window
Do you have Graphing active? I had a similar problem with some LACP Bonding fiber connections, which were diconnected every 60 min.I did a lot of tests on openvpn (udp)
The results are definite.
openvpn udp protocol: (It has many bugs)
max connect time per client ( 1 hours or 01:01:00)
os client: windows , android , ios
all client (ovpn udp) They are disconnect after 61 minutes
After 1 hour and 1 minute openvpn disconnected.
I emphasize that the problems are only in udp protocol.
create ticket in mikrotik support (SUP-57401)
But the Mikrotik support team does not matter
This is news to me. Ironic. How will this help me remotely upgrade hundreds of units?Due to a bug you cannot upgrade from separate packages to single package on some devices. This is not really a lack of space.to Mikrotik: is it possible to create light main packages to switch from extra v6 packages to v6 / v7 main package? They could only contain the system, dhcp, system, wireless packages. hAP ac2, disk lite5 ac etc. cannot be upgraded to main package remotely due to "system, error not enough space for upgrade"
You need to netinstall either the v6 combined package or the v7 package and then load your backup.
Thank you. i can see a version kernel in 7.1?7.1 is newer, it includes everyting that was in rc77.1rc7 version is newer than final 7.1?
or iclude all changes in 7.1 from rc7?
You should read the release topic messages before adding your own findings. It is mentioned several times already.This is news to me.
Due to a bug you cannot upgrade from separate packages to single package on some devices. This is not really a lack of space.
You need to netinstall either the v6 combined package or the v7 package and then load your backup.
Hopefully the bug is fixed some time. Note it will have to be fixed in 6.49.3 and then you can update to that, and then update to 7.1.Ironic. How will this help me remotely upgrade hundreds of units?
Although the package is being downloaded to ram, it could upgrade in ram and then force rewrite nand. Disable any safety fuses.
/system health get temperature
As it says in the release notes, the "bundle" package has been merged into a single combined package, so you can no longer enable or disable the individual parts. This is by design. You can still disable IPv6 with the "disable IPv6" checkbox in IPv6->Settings.3. In packagelist missing all packages. I will not enabling IPv6, Capman, etc.
Is there any way I can enable packages? It is not in the menu after a clean installation of IPv6. As well as Capsman, Hotspot, etc.As it says in the release notes, the "bundle" package has been merged into a single combined package, so you can no longer enable or disable the individual parts. This is by design. You can still disable IPv6 with the "disable IPv6" checkbox in IPv6->Settings.3. In packagelist missing all packages. I will not enabling IPv6, Capman, etc.
What features or fixes do we actually gain from MT spending cycles on a new kernel update?
on my RB4011 running 7.1 stable the following worksthe commanddoes not work in v7.1Code: Select all/system health get temperature
:global systemp (([system health print as-value where name~"temp"]->0)->"value")
:put $systemp
The main reason for keeping the kernel reasonably up-to-date is to be able to fulfill feature requests from people who have seen interesting features addedWhat features or fixes do we actually gain from MT spending cycles on a new kernel update? For a vanilla desktop linux install it makes some sense to keep the kernel updated. In that case you're depending on the kernel maintainers to patch holes and provide new features
you don't disable or enable packages in v7. what is enabled or disabled in v6 doesn't matter and you're wasting time trying to roll back and enable or disable packages.Is there any way I can enable packages?
/system ntp server set enabled=yes
ipv6 settings set disable-ipv6=yes
I read many different things and it would be nice if MT give some direction on this? "Device has enough free storage space for all RouterOS packages to be downloaded.", is a bit uninformative.As many has written before. Download package from MT, copy it to file area of your Router, reboot.
as normis stated above memory usage is not affected by features not in use. i.e I might have NTP server available on my home router now (was previously in separate package) but its not consuming any resources ...
What router specific features from 5.15 kernel do you expect to have that are not in 5.6?
That is correct. But what would make a difference is when MikroTik could limit the number of kernel patches to the absolute minimum, or toLets say new protocol "wirelessguard" is added in kernel 6.x years lateer, it doesn't make any difference if we have 5.6 or 5.15 now.
Lets say new protocol "wirelessguard" is added in kernel 6.x years lateer, it doesn't make any difference if we have 5.6 or 5.15 now.
in 5.8Networking
Improve bind(addr, 0) behaviour. Linux used to fail to bind sockets to ephemeral ports when all of the ports were exhausted even if all sockets had SO_REUSEADDR enabled. In this case, it still is possible to connect to the different remote hosts. This release adds the net.ipv4.ip_autobind_reuse, which allows to bind SO_REUSEADDR enabled sockets to the same (addr, port) when set to 1 and all ephemeral
UDP: Bare UDP L3 Encapsulation Module. The Bareudp tunnel module provides a generic L3 encapsulation tunnelling support for tunnelling different L3 protocols like MPLS, IP, NSH etc. inside a UDP tunnel
Packet schedulers
Make FIFO Qdisc offloadable
Introduce connection tracking hardware offload
Add software offload of connections with an established ct state using the NF flow table offload infrastructure, so once such flows are offloaded, they will not pass through conntrack again, and instead act_ct will restore the conntrack info metadata on the skb to the state it had on the offload event - established
Allow user to specify the type of hardware stats for the added TC action: immediate, delayed, or disabled
RED qdisc: Introduce an ECN nodrop mode
Enables tc classification to start from a specified chain. TC multi chain configuration can cause offloaded tc chains to miss in hardware after jumping to some chain, in such cases the software should continue from the chain that was missed in hardware
Expose HW stats types per action used by drivers
Implement callback used for adding HW counters to the SW ones for pedit and skbedit actions
WiFi
Add encapsulation offloading support
...
Add support for Beacon protection
in 5.9
Better behavior in memory thrashing situations
(FEATURED) IPv6: add MPLS support
IPv6: Implement the upcoming rev of RFC4941 (IPv6 temporary addresses)
IPv6: support RFC 6069 (TCP-LD)
Add IPv6 encapsulation support for ESP over UDP and TCP
802.11
Unprotected Beacon frame RX indication
Initial definitions for S1G (802.11ah)
Support bigger kek/kck key length
Support multicast RX registration
Allow SA-QUERY processing in userspace
Implement Operating Mode Notification extended NSS support
Support control port TX status reporting
Add support to configure TID specific Tx rate configuration
Packet scheduler
flow_dissector, cls_flower: Add support for multiple MPLS Label Stack Entries
sch_fq: add horizon attribute
in 5.10 (LTS)icmp4/6: support RFC 4884
Add stream gate action policing in IEEE802.1Qci (Per-Stream Filtering and Policing) software support and hardware offload support in tc flower
Introduce qevents. Those are attach points for TC blocks, where filters can be put that are executed as the packet hits well-defined points in the qdisc algorithms. The attached blocks can be shared, in a manner similar to clsact ingress and egress blocks, arbitrary classifiers with arbitrary actions can be put on them, etc
sch_cake: add RFC 8622 LE PHB support to CAKE diffserv handling
Add support for Parallel Redundancy Protocol (PRP) - a network protocol standard for Ethernet that provides seamless failover against failure of any network component - in the Linux HSR driver as defined in IEC-62439-3
Support ipip and ipv6 tunnels in vti and xfrmi
in 5.11Support 6 GHz scanning
Add support for WPA/WPA2-PSK 4-way handshake and SAE offload in AP mode
packet scheduler: Add the necessary TC actions for supporting layer 2 MPLS VPNs (VPLS)
in 5.12Faster memory leak debugging in ARM
IPv6: Add support for the SRv6 End.DT4 and End.DT6 (VRF mode) behavior. The SRv6 End.DT4 behavior is used to implement multi-tenant IPv4 L3 VPNs. It decapsulates the received packets and performs IPv4 routing lookup in the routing table of the tenant. The SRv6 End.DT4 Linux implementation leverages a VRF device in order to force the routing lookup into the associated routing table. The SRv6 End.DT4 behavior is defined in the SRv6 Network Programming
IP: Add an IPv6/IPv4 route encapsulation attribute to the result of netlink RTM_GETROUTE requests
macvlan: Support for high multicast packet rate
TLS: Add CHACHA20-POLY1305 cipher to Kernel TLS
Add support to calculate and report 4096-QAM HE rates
Remove WDS mode
in 5.13IPv6: Allow user to set metric on default route learned via Router Advertisement
UDP: allow forwarding of plain (non-fraglisted) UDP GRO packets
RFC 6056 induced changes
IPv4-mapped IPv6 addressing for subflows
Add Extended MCS Phyrate Conversion Support on 60GHz
Add VHT rate entries for MCS-10 and MCS-11
in 5.14Add support for x509 certs with NIST P384/256/192 keys
UDP: improve UDP L4 - either 'forward' or 'frag_list' - co-existence with UDP tunnel GRO, allowing the first to take place correctly even for encapsulated UDP traffic
Better support for sandwiched LAGs with bridge and DSA
ICMP: Add support for RFC 8335 PROBE messages, a specialized ICMP message that makes use of the ICMP Extension Structure outlined in RFC 4884. It allows querying specific interfaces on a node and requiring bidirectional connectivity between the probing and probed interfaces
macvlan: Add nodst option to macvlan type source to skip destination MACVLAN processing if any matching source MACVLAN device has the option set
in 5.15 (LTS)Core Scheduling, for safe hyperthreading
Support hidden AP discovery over 6GHz band
Allow bypass of the lockless qdisc to improving performance (for pktgen: +23% with one thread, +44% with 2 threads)
sctp: implement RFC8899: Packetization Layer Path MTU Discovery for SCTP transport
ksmbd, a in-kernel SMB 3 server
Support for asymmetric scheduling affinity
XDP bonding support
Some improvements to generic XDP mode to brings it closer to native XDP
Same on my wAP AC and hAP AC. You can downgrade - just copy firmware file on router's disk ("Files" menu) and select "Downgrade" option in "System / Packages".When you run Speedtest, the router disconnects for about 30 seconds after the test. It's not normal. The router is located in the internal network Bridge mode
I'd say every kernel release matters this way or another. Most of changes are invisible because they target small things, obscure bugs, performance enhancements ... and those changes matter regardless what kind of duties are performed by device running kernel. Some things are more prominent, such as addition of new functionality.looks like kernel updates are not so unimportant as one could think!!!!
I don't know if this is a bug. But if you disable just IPv6>Settings, you may want/need to disable IPv6 ND as well – that seem unaffected by the first top level one.You can still disable IPv6 with the "disable IPv6" checkbox in IPv6->Settings.3. In packagelist missing all packages. I will not enabling IPv6, Capman, etc.
/ipv6/settings/set disable-ipv6=yes
/ipv6/nd/set [find default] disabled=yes
12:16:03 radvd,debug skip Router Advertisement sending on bridge1: no prefixes to send
12:16:28 radvd,debug skip Router Advertisement sending on zerotier1: no prefixes to send
Data structures for health changed with RouterOS v7... Try this:the commanddoes not work in v7.1Code: Select all/system health get temperature
I used it in my script.
:put [ /system/health/get [ find where name="temperature" ] value ]
How about NO. ;)@mrz, you've prompted me to look through the kernel changelog, I referenced this page: https://kernelnewbies.org/LinuxChanges
granted, I have only looked through the prominent features, network, and security sections of each release, and I am not smart enough to understand lot of what they mention. but I'll list the things that look interesting to me here...
I'll be honest, I don't completely understand the majority of the kernel changelogs, but I've copied the parts that I think others here will be interested in.
please, discuss.
Note that when you have downgraded this way, you cannot upgrade to version 7.x anymore in the future, at least not until the bug is fixed that conversion of configuration is performed only once.WildRat,
Thank you very much !!!! I managed to downgrade. Now everything is working normally again as it should be.
I dont believe so, swOS has its own development tree and version numbers, I think the latest release in the 2.x tree for currently supported devices was back in April.stupid question: Does this include swOS ?
And that is exactly what I did to fix dual stack as well. Default route distance set to 2 and I have IPv6 connectivity again.You can fix it by disabling Add Default Route on DHCPv6 or set DHCPv6 default route distance to >1.
Anyone tried Let's Encrypt with just using their IP/cloud dns? I attempted to do so on my home tik for testing and pulled an error.
certificate/enable-ssl-certificate
progress: [error] err
Tried also:
certificate/enable-ssl-certificate dns-name=[removed4privacy].sn.mynetname.net
progress: [error] err
I have enabled www in services as well as www-ssl and allowed input from port 80 on the firewall. Does anyone know how to access more detailed logs?
Same thing happening here as well. At least it's fine in WinBox. After the upgrade from v6.49.2 to v7.1 PPPoE out interface graph is lost. But that happened on RouterOS v6 as well. ether1 graph is still there so not everything is lost.Graphing work only in http mode.
In https i get a "Error 404: Not Found".
In the same time the webfig with https work perfect.
I imagine MT wastes more time asking for add'l details and supout.rif files in support cases – that's something people here can do something about. If there really is some product feature you need & can clearly articulate exactly how some newer kernel update alone makes that feature easier to develop – sure they'd listen. Just saying.Don't lose time because of the old kernel.
/interface ethernet
set [ find default-name=ether1 ] arp=disabled name=ether1-lag-to-zyxel-gs1920-48hp speed=100Mbps
set [ find default-name=ether2 ] arp=disabled disabled=yes name=ether2-unused speed=100Mbps
set [ find default-name=ether3 ] disabled=yes name=ether3-unused speed=100Mbps
set [ find default-name=ether4 ] disabled=yes name=ether4-unused speed=100Mbps
set [ find default-name=ether5 ] disabled=yes name=ether5-unused speed=100Mbps
set [ find default-name=ether6 ] arp=disabled name=ether6-lag-to-zyxel-gs1920-48hp speed=100Mbps
set [ find default-name=ether7 ] arp=disabled disabled=yes name=ether7-unused speed=100Mbps
set [ find default-name=ether8 ] disabled=yes name=ether8-unused speed=100Mbps
set [ find default-name=ether9 ] disabled=yes name=ether9-unused speed=100Mbps
set [ find default-name=ether10 ] comment=Unused disabled=yes name=ether10-unused speed=100Mbps
set [ find default-name=ether11 ] advertise=10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full name=ether11-wan-sunrise
set [ find default-name=ether1 ] advertise=10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full disabled=yes name=ether12-unused
set [ find default-name=ether2 ] advertise=10M-half,10M-full,100M-half,100M-full,1000M-half,1000M-full name=ether13-recovery
Note that at some time (maybe not just now, yet) it may be very attractive to move over from swOS to RouterOS when your switch can do both.I dont believe so, swOS has its own development tree and version numbers, I think the latest release in the 2.x tree for currently supported devices was back in April.stupid question: Does this include swOS ?
Despite of that you can use your switch runnng RouterOS as a backup NTP, DNS and other small, very usefull servces in the network not loosing, at the same time, functionality and speed implemented in SwitchOS. There is one drawaback of RouterOS - it starts much slower than SwitchOS.Note that at some time (maybe not just now, yet) it may be very attractive to move over from swOS to RouterOS when your switch can do both.
RouterOS is implementing L3 routing hardware acceleration on suitable switches, making them competitive with other L3 switches on the market.
(some people think that CRS means that the devices is both router and switch and is comparable with other routing switches, but until now this wasn't the case)
Read what people and Mikrotik have posted before in this thread.ISP providers have huge problems if they have updates set up from a stable channel.
If one wants to update the firmware according to the updated version version, one must choose an upgrade - bug version 6.xx@truefriendcz
please calm down a little. If your devices are on v6 and stable channel, you won't get v7 "automatically". You won't get anything newer than 6.49.2 when you call "system package update check-for-updates".
v7 stable and v6 co-exist right now.
But version 7.1 does not seem to be stable.as it was already mentioned in this topic there are two separate branches v6 and v7. There is no 7.1 long term yet, because 7.1 is the only released version.
viewtopic.php?p=895584#p895584
/interface lte apn
set [ find default=yes ] ip-type=ipv4
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/routing bgp template
set default as=65530 disabled=no name=default output.network=bgp-networks
/routing ospf instance
add name=default-v2
add name=default-v3 version=3
/routing ospf area
add disabled=yes instance=default-v2 name=backbone-v2
add disabled=yes instance=default-v3 name=backbone-v3
Comments like this do make sure this thread stays right on top of the most active ones, yes ...+++
Well, it's not about the version, but about the channel. What is the purpose of the Alpha, Beta, RC, Testing channel, when a version gets into the Stable channel, which after installation is marked "Testing" and causes quite serious problems. For some open source project of people doing something somewhere in the garage at home, I would understand it, but for a company that offers Enterprise solutions and Cloud, it's kind of incomprehensible. I understand that the stable version may contain bugs, but bugs that make the Router not even start and have to reset the configuration, etc. So I don't understand. The two channels (RC and Testing) should focus on testing only. And if there are any errors, they cannot occur in the Stable channel at all. Only errors that the author does not know about will appear in the Stable channel and will only appear in the process.Did you read anything? It does not replace version from 6 "stable" channel. You can keep using v6 without experimenting with v7.
Netinstall installation should work, but you will lose all router settings, including files stored in memory.I tried to upgrade two RB1200 to new version, and after that only way to access them is over serial ports. From other routers in neighborhood you can see them, but there is no way to access them, not over MAC telnet, or SSH, you cannot ping them, they are completely locked.
4. Simply Enable/Disable packages... IPv6 in v7.1 a default is not enabled and not any place where i can enabling... IPv6 must enabling in 6.xx version, after this .. upgrade to 7.xx and viola, IPv6 is active.
/ipv6/settings/set disable-ipv6=no
Why is not in GUI in Windows (Winbox), or in WebFig?4. Simply Enable/Disable packages... IPv6 in v7.1 a default is not enabled and not any place where i can enabling... IPv6 must enabling in 6.xx version, after this .. upgrade to 7.xx and viola, IPv6 is active.Code: Select all/ipv6/settings/set disable-ipv6=no
Try looking under IPv6 settings - first option.Why is not in GUI in Windows (Winbox), or in WebFig?
Code: Select all/ipv6/settings/set disable-ipv6=no
To really disable IPv6, you'll also need to disable IPv6 ND "neighbor discovery" (and in winbox, disable it in IPv6>Neighbors) – it still runs even if IPv6 routing is disabled using the disable-ipv6=no above.4. Simply Enable/Disable packages... IPv6 in v7.1 a default is not enabled and not any place where i can enabling... IPv6 must enabling in 6.xx version, after this .. upgrade to 7.xx and viola, IPv6 is active.Code: Select all/ipv6/settings/set disable-ipv6=no
/ipv6/nd/set [find default] disabled=yes
12:16:03 radvd,debug skip Router Advertisement sending on bridge1: no prefixes to send
IPv6 menu complette missed in GUI - Winbox + Webfig.Try looking under IPv6 settings - first option.
Why is not in GUI in Windows (Winbox), or in WebFig?
Same for me, due to 6.49.2...trying to upgrade a CHR, is anyone getting this too?
@MikroTik] /system package update> download
channel: upgrade
installed-version: 6.49.2
latest-version: 7.1
status: calculating download size..
been like this for hours
Did you collect a supout.rif before downgrading? Or maybe save the logs and/or increase the log level. No doubt you had a problem.After update to 7.1 from 6.48.6 CHR, after 1 day every 5 mins mikrotik reboot, this problem is fixed after i downgrade to 6.48.6 everything work perfect, Could you check
WireGuard over LTE (~40Mbps down/~20Mbps up, 31ms ping)Tell me who tested the speeds through WireGuard and OpenVPN UDP protocol? write down the speed that you got?
my is an x86 with xeon processor, so I can't play with it."cpu-frequency=auto" on my Chateau LTE12 causes it to lock up completely after around 1d uptime. Sometimes only after 2d. It is unclear why, but switching back to "cpu-frequency=716MHz" makes it behave stable again.
You and others should note that "stable" refers to the development cycle, not to the stability of the software.I wanted to update all my routers, because MT said it is stable. I was in the middle of another project, so I didn’t have time. I’m glad I didn’t update.
I'm running CAPsMAN server on our RB4011 with V7.1 with no problems with 2.4GHz. I also upgraded a Cap AC to 7.1. It runs as a CAP to the RB4011 without any problems. I don't know anything about WiFi WAVE 2. I find the WiFi performance is better on the Cap AC on V7.1 than it was on V6.49. The WiFi performance on the RB4011 was always very good.I have a RB4011 which fulfills the requirements for wifiwave2 but still I cannot use it because it doesn't co-exist with the normal package that is required to support 2.4 GHz WiFi.
Quite a lot of devices will lack new stack.
Or did that change?
I would like to upgrade a RB2011UiAS to 7.1 but it's an openwrt metarouter for mdns/bonjour reflection.
So I first tried on an old RB450G, and I tried to run a mikrotik metarouter and an openwrt one, the effect is the same, the device reboots.
Is metarouter still supposed to work on 7.1?
Same as before, but now target scope needs to be greater than scope, while in RouterOS v6 you could set target scope to the same as scope. Raise your target-scope by 1 compared to what it was in ROS6 and it should start working.so, how do we do this recursive routing? It was a question here, last post was #604?
You could try the wifiwave2 package? If it a single AP (no meshing to another audience etc). This is may in fact be a better choice if the "old" one isn't working/gives error. It still early, but we've been using on a couple Audience and be seemingly stable as simple access point.error system critical "error while running customized default configuration script: bad command name wireless (line 977 column 25)" is still present in stable.
I've originally renamed default interfaces, dunno if the error makes any harm
Later I've restored original names wifi1/2/3 - the issue is still there.
device - audience lte6 kit
RB5009UG+S+On what hardware?