Fastest and easiest way is via FTP.How to explore and get files from container mounts now that they are stored as "container store" and not as directories/files as before?
mAPLite (7.1rc3 downgraded to rc2, now upgraded to rc4):*) other fixes and improvements;
/interface vlan
add interface=ether1 name=FTTH vlan-id=7
/interface pppoe-client
add add-default-route=yes interface=FTTH name=TELEKOM user=xxx#0001@t-online.de
/ipv6 dhcp-client
add interface=TELEKOM pool-name=GUA-pool6 request=prefix use-peer-dns=no
/ip dhcp-client
add add-default-route=no disabled=yes interface=FFNK script=":if (\$bound = \"\
[admin@router] > import file-name=export.rsc verbose=yes
#line 1
/ip dhcp-client
#line 2
add add-default-route=no disabled=yes interface=FFNK script=":if (\$bound = \"\
expected end of command (line 1 column 75)
[admin@router] >
Have you tried to attach the vlan interface to the bridge and use the vlan filtering to allow only this vlan on that particular port?Still no IPv6 prefix via DHCPv6 if PPPoE interface is VLAN tagged on RB5009:
Code: Select all/interface vlan add interface=ether1 name=FTTH vlan-id=7 /interface pppoe-client add add-default-route=yes interface=FTTH name=TELEKOM user=xxx#0001@t-online.de /ipv6 dhcp-client add interface=TELEKOM pool-name=GUA-pool6 request=prefix use-peer-dns=no
So for all the people complaining it still doesnt do X and Y, why do you ? They didnt state it was fixed?
I thought the days of "fixed some stuff" were long behind Mikrotik*) other fixes and improvements;
Same hereAfter upgrade from rc3 to rc4 Cloudflare DoH does no longer work because of SSL errors, even though the DigiCert CA is in the certificate store. Deleting and reimporting the CA does not work.
After downgrade to rc3 DoH works as expected again.
I've seen this myself. Works again after importing the new intermediate certificate "DigiCert TLS Hybrid ECC SHA384 2020 CA1". No idea what changed to cause this.After upgrade from rc3 to rc4 Cloudflare DoH does no longer work because of SSL errors, even though the DigiCert CA is in the certificate store. Deleting and reimporting the CA does not work.
I've seen this myself. Works again after importing the new intermediate certificate "DigiCert TLS Hybrid ECC SHA384 2020 CA1". No idea what changed to cause this.After upgrade from rc3 to rc4 Cloudflare DoH does no longer work because of SSL errors, even though the DigiCert CA is in the certificate store. Deleting and reimporting the CA does not work.
/tool fetch url=https://cacerts.digicert.com/DigiCertTLSHybridECCSHA3842020CA1-1.crt
/certificate import file-name=DigiCertTLSHybridECCSHA3842020CA1-1.crt passphrase=""
Can confirm issue still exists, exported code doesn't import back.Export creates code, that import can not read (starting with 7.1rc3):
Export:
Import:Code: Select all/ip dhcp-client add add-default-route=no disabled=yes interface=FFNK script=":if (\$bound = \"\
Code: Select all[admin@router] > import file-name=export.rsc verbose=yes #line 1 /ip dhcp-client #line 2 add add-default-route=no disabled=yes interface=FFNK script=":if (\$bound = \"\ expected end of command (line 1 column 75) [admin@router] >
Still slow paste of code.
My sentiments exactly !!I thought the days of "fixed some stuff" were long behind Mikrotik*) other fixes and improvements;
Not knowing _exactly_ what has changed wastes a lot of customers time testing to try and discover what the Mikrotik dev's have changed.
/routing table
add disabled=no name=mytable
/ip firewall nat
add action=log chain=srcnat routing-mark=*4000
What's the routing mark it uses? I genuinely can't read that small of font size.export not work
routing-mark=*4000 instead of mytable
Code: Select all/routing table add disabled=no name=mytable /ip firewall nat add action=log chain=srcnat routing-mark=*4000
Yes, same result. As it works on CCR2004-1G-12X-2XS and RB4011, it might be something with the new switch chip. I don't know.Have you tried to attach the vlan interface to the bridge and use the vlan filtering to allow only this vlan on that particular port?Still no IPv6 prefix via DHCPv6 if PPPoE interface is VLAN tagged on RB5009:
When you look at any v7 changelog, this is always the last line. v7 is actually the development-branch and they do not want to name/reflect each change in the changelog. They could for example create a changelog out of their for example VCS commits (if using a version control) and just provide us that auto-generated list of commit-messages. But there is either a barrier like maybe they write commit-messages not in english - so it would be not useful for most of us - or there is a management-barrier that denies doing so. We won't ever know.*) other fixes and improvements;
What's the routing mark it uses? I genuinely can't read that small of font size.export not work
routing-mark=*4000 instead of mytable
Code: Select all/routing table add disabled=no name=mytable /ip firewall nat add action=log chain=srcnat routing-mark=*4000
Yes. The configuration works if you remove the VLAN tag and tag outside, e.g. with a switch between RB5009 and modem.@dksoft, have you set use-ipv6=yes in your pppoe profile?
Re: WG interface - strike that remark. Still not working on Map (tested 3 times, waited up to 15 minutes each) and Map Lite also did not come up on itself after reboot when coming home (10 minute wait).mAPLite (7.1rc3 downgraded to rc2, now upgraded to rc4):*) other fixes and improvements;
- LEDs functioning normal again
- No more need to toggle Wireguard peer status to have it kick in gear after startup (will have to verify on mAP 2nD and Hex when I am home but I assume it will be the same there)
I had the same problem. What seems to have fixed it for me was disabling all BGP address-lists and re-enabling them.After upgrade my bgp broke. Now my routes are not being announced to peers.
Thanks for the tip it worked.I had the same problem. What seems to have fixed it for me was disabling all BGP address-lists and re-enabling them.After upgrade my bgp broke. Now my routes are not being announced to peers.
I have a higher MTU on the SFP, PPPoE won't go further than 1492.MTU >1500 on RB4011 SFP+ port still not fixed.
Even 1501 byte pings do not pass through. Is this working on your side?I have a higher MTU on the SFP, PPPoE won't go further than 1492.MTU >1500 on RB4011 SFP+ port still not fixed.
One of my chr also completely failed update from rc3 to rc4... it rebooted to blank screen and halted. I'd strongly recommend anyone using chr to create backup and/or snapshot before updating to rc4, until this can be confirmed ..My chr test system can no longer start the container that worked on rc3. No debug log output at all.
Creating BGP4 peers in the web guis now works for the field local-AS. it shows something like 1234/0Any specific improvements to MPLS or BGP?
I did not manage to get any pings through the SFP or through the VLAN in front of it.Even 1501 byte pings do not pass through. Is this working on your side?I have a higher MTU on the SFP, PPPoE won't go further than 1492.
I have had the same issue on hAP ac^2. Due to I have raised ticket and there was good news today - people from Mikrotik were able to reproduce it and fix should be available in RC5.Still no IPv6 prefix via DHCPv6 if PPPoE interface is VLAN tagged on RB5009:
Code: Select all/interface vlan add interface=ether1 name=FTTH vlan-id=7 /interface pppoe-client add add-default-route=yes interface=FTTH name=TELEKOM user=xxx#0001@t-online.de /ipv6 dhcp-client add interface=TELEKOM pool-name=GUA-pool6 request=prefix use-peer-dns=no
You read post #35 from osc86? :I have had the same issue on hAP ac^2. Due to I have raised ticket and there was good news today - people from Mikrotik were able to reproduce it and fix should be available in RC5.
In addition, I am using MTU = 1500, so PPPoE +8.
have you set use-ipv6=yes in your pppoe profile?
:if ([/system routerboard get routerboard]) do={
:if ([/system resource get board-name]!="CHR") do={
FastTrack enabled means firewall, queues, etc don't apply to your traffic. this is not a bug. its how ROS works....
hap ac2, low speed when the fasttrack rule is off and high speed if the fasttrack rule is on
...
on version 6 this was not
for some reason this issue went away by itself. Maybe GUI code in cache or something like this. I'm really puzzled.Creating BGP4 peers in the web guis now works for the field local-AS. it shows something like 1234/0Any specific improvements to MPLS or BGP?
the field for remote-AS however is not working. you can enter 1234/1234 but not just 1234.
Given nobody has a clue what /... means for an AS number this is rather weird.
So BGP4 is still 100% unusable under 7.1rc4... *sight*
/routing filter>
add action=accept bgp-as-path="^\$" chain=MY_NETWORKS set-bgp-prepend=2
add action=accept bgp-as-path="^(_1234)+\$" chain=MY_NETWORKS
add action=accept bgp-as-path="^(_5678)+\$" chain=MY_NETWORKS
add action=accept bgp-as-path="^(_9102)+\$" chain=MY_NETWORKS
add action=accept bgp-as-path="^(_3456)+\$" chain=MY_NETWORKS
add action=reject bgp-as-path=.* chain=MY_NETWORKS
/routing filter rule
add chain= MY_NETWORKS rule="if(bgp-as-path ^\$ ) {accept}"
add chain= MY_NETWORKS rule="if(bgp-as-path 1234+\$ ) {accept}"
add chain= MY_NETWORKS rule="if(bgp-as-path 5678+\$ ) {accept}"
add chain= MY_NETWORKS rule="if(bgp-as-path 9102+\$ ) {accept}"
add chain= MY_NETWORKS rule="if(bgp-as-path 3456+\$ ) {accept}"
Finally! I stopped bothering and did not check. I will do it nowDate and timestamp issue with netflow has been fixed!
Strange, I have PPPoE(MTU 1540) over a VLAN(MTU 1600) on a bridge(MTU 6000) and have no MTU issues...Even 1501 byte pings do not pass through. Is this working on your side?
I have a higher MTU on the SFP, PPPoE won't go further than 1492.
[@RB4011] > interface print
Flags: X, R - RUNNING; S - SLAVE
Columns: NAME, TYPE, ACTUAL-MTU, L2MTU, MAX-L2MTU, MAC-ADDRESS
# NAME TYPE ACTUAL-MTU L2MTU MAX-L2MTU MAC-ADDRESS
0 RS 10g-sfp+1 ether 6000 6200 9586 XX:XX:XX:XX:XX:xx
...
13 R Home_vlan vlan 4088 6196 XX:XX:XX:XX:XX:xx
...
15 R PPPoEv4 pppoe-out 1540
16 R PPPoEv6 pppoe-out 1540
...
18 R WAN_vlan vlan 1600 6196 XX:XX:XX:XX:XX:xx
19 R bridge bridge 6000 6200 XX:XX:XX:XX:XX:xx
...
[@RB4011] > interface vlan export
/interface vlan
add interface=bridge mtu=4088 name=Home_vlan vlan-id=88
add interface=bridge mtu=1600 name=WAN_vlan vlan-id=35
[@RB4011] > interface bridge export
/interface bridge
add name=bridge priority=0x4000
/interface bridge port
add bridge=bridge ingress-filtering=no interface=10g-sfp+1
[@RB4011] > interface pppoe-client export
/interface pppoe-client
add add-default-route=yes disabled=no interface=WAN_vlan name=PPPoEv4 user=blablabla
add disabled=no interface=WAN_vlan name=PPPoEv6 user=blablabla/ipv6
Even 1501 byte pings do not pass through. Is this working on your side?
I have a higher MTU on the SFP, PPPoE won't go further than 1492.
and how and where do you describe BGP address-lists?Thanks for the tip it worked.
I had the same problem. What seems to have fixed it for me was disabling all BGP address-lists and re-enabling them.
/ip firewall address-list
add address=172.16.10.0/24 list=AS65172
add address=172.16.11.0/24 list=AS65172
/routing filter rule
add chain=bgp_AS65172_out rule="if(dst in AS65172) {accept} else {reject}"
/routing bgp connection
add as=65172 connect=yes disabled=no input.filter=bgp_AS65172_in listen=yes local.role=ibgp name=AS65172 \
output.filter-chain=bgp_AS65172_out .redistribute=connected,static remote.address=xx.xx.xx.xx .as=65172 \
router-id=yy.yy.yy.yy routing-table=main
Sure, flag IPv6 is "Yes" in assigned profile.Sit75 write:You read post #35 from osc86? :I have had the same issue on hAP ac^2. Due to I have raised ticket and there was good news today - people from Mikrotik were able to reproduce it and fix should be available in RC5.
In addition, I am using MTU = 1500, so PPPoE +8.have you set use-ipv6=yes in your pppoe profile?
Try disable enable your filter rule, it works for meand how and where do you describe BGP address-lists?
Thanks for the tip it worked.
I have described the address list in the firewall
created routing filterCode: Select all/ip firewall address-list add address=172.16.10.0/24 list=AS65172 add address=172.16.11.0/24 list=AS65172
and added it as output filter to AS65172 connectionCode: Select all/routing filter rule add chain=bgp_AS65172_out rule="if(dst in AS65172) {accept} else {reject}"
but It does not advertised to the neigborCode: Select all/routing bgp connection add as=65172 connect=yes disabled=no input.filter=bgp_AS65172_in listen=yes local.role=ibgp name=AS65172 \ output.filter-chain=bgp_AS65172_out .redistribute=connected,static remote.address=xx.xx.xx.xx .as=65172 \ router-id=yy.yy.yy.yy routing-table=main
You need to set "output.network=AS65172" for your bgp Connection instance. That's where you tell it to advertise the prefixes in the address list nowand how and where do you describe BGP address-lists?
Thanks for the tip it worked.
I have described the address list in the firewall
created routing filterCode: Select all/ip firewall address-list add address=172.16.10.0/24 list=AS65172 add address=172.16.11.0/24 list=AS65172
and added it as output filter to AS65172 connectionCode: Select all/routing filter rule add chain=bgp_AS65172_out rule="if(dst in AS65172) {accept} else {reject}"
but It does not advertised to the neigborCode: Select all/routing bgp connection add as=65172 connect=yes disabled=no input.filter=bgp_AS65172_in listen=yes local.role=ibgp name=AS65172 \ output.filter-chain=bgp_AS65172_out .redistribute=connected,static remote.address=xx.xx.xx.xx .as=65172 \ router-id=yy.yy.yy.yy routing-table=main
I removed whole bgp-related config and paste it again. And it works now. A kind of mystery...Try disable enable your filter rule, it works for me
No, this is not necessary.You need to set "output.network=AS65172" for your bgp Connection instance. That's where you tell it to advertise the prefixes in the address list now
Unfortunately true.Export creates code, that import can not read (starting with 7.1rc3):
/export show-sensitive terse
/system/reset-configuration keep-users=yes no-defaults=yes skip-backup=yes run-after-reset=myexport.rsc
I can not confirm that. If there is a script in the command, as in my example above, it still fails.Unfortunately true.Export creates code, that import can not read (starting with 7.1rc3):
However,produces export code that can be imported successfully, for a full config restore.Code: Select all/export show-sensitive terse
My router comes back unconfigured after upgrading from version 7.1rc3 to 7.1rc4.RouterOS version 7.1rc4 has been released in public "development" channel!
What's new in 7.1rc4 (2021-Sep-20 13:18):
*) improved filesystem and configuration storage stability;
*) show "expired password" prompt for users with blank password;
*) other fixes and improvements;
All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelog ... lease-tree
Mine went fine from RC3 to RC4 on both RB3011 and HAP AC^2My router comes back unconfigured after upgrading from version 7.1rc3 to 7.1rc4.
When trying to restore a backup of version 7.1rc3 or any version 6.x over 7.1rc4 software the hardware restarts, after boot the router remains unconfigured.
It was necessary to reconfigure the router.
I hope to have alerted new testers!
This is not the right job. On v6 there was no such behavior. v6 easily transferred over wi-fi 100 megabits without FastTrack!FastTrack enabled means firewall, queues, etc don't apply to your traffic. this is not a bug. its how ROS works....
hap ac2, low speed when the fasttrack rule is off and high speed if the fasttrack rule is on
...
on version 6 this was not
https://help.mikrotik.com/docs/display/ ... -FastTrack
I just got my RB5009 and my FTTH connection works perfectly using a tagged vlan with IPv6 and prefix works.Yes. The configuration works if you remove the VLAN tag and tag outside, e.g. with a switch between RB5009 and modem.
The root of the problem is VLAN on RB5009.
# sep/21/2021 19:50:42 by RouterOS 7.1rc4
# model = RB5009UG+S+
/interface bridge
add ingress-filtering=no name=bridge vlan-filtering=yes
/interface vlan
add interface=bridge mtu=1600 name=WAN_vlan vlan-id=35
/interface pppoe-client
add add-default-route=yes interface=WAN_vlan name=PPPoEv4 user=*****
add interface=WAN_vlan name=PPPoEv6 user=*****
/interface bridge port
add bridge=bridge ingress-filtering=no interface=ether8 pvid=88
/interface bridge vlan
add bridge=bridge tagged=bridge,ether8 vlan-ids=35
/ipv6 dhcp-client
add add-default-route=yes interface=PPPoEv6 pool-name=GUA-pool rapid-commit=\
no request=prefix use-peer-dns=no
I'm willing to bet that this issue is related to rc3 and did not happen due to upgrade but due to reboot.My router comes back unconfigured after upgrading from version 7.1rc3 to 7.1rc4.RouterOS version 7.1rc4 has been released in public "development" channel!
What's new in 7.1rc4 (2021-Sep-20 13:18):
*) improved filesystem and configuration storage stability;
*) show "expired password" prompt for users with blank password;
*) other fixes and improvements;
All released RouterOS v7 changelogs are available here:
https://mikrotik.com/download/changelog ... lease-tree
When trying to restore a backup of version 7.1rc3 or any version 6.x over 7.1rc4 software the hardware restarts, after boot the router remains unconfigured.
It was necessary to reconfigure the router.
I hope to have alerted new testers!
This is probably not an issue with 7.1rc4, but rather with 7.1beta6. I was unable to upgrade my RB4011 above 7.1beta6 until I did a reset to no-defaults and uploaded the 7.1rc npk file to the device using MAC Winbox. A bug in 7.1beta6 caused it to crash on reboot, preventing any successful upgrade or downgrade.SUP-61109 - Still cannot update RB2011 past 7.1 beta 6...
My mistake. You're right.I can not confirm that. If there is a script in the command, as in my example above, it still fails.
Unfortunately true.
However,produces export code that can be imported successfully, for a full config restore.Code: Select all/export show-sensitive terse
Protected routerboot seems to be gone from Winbox but still present in the CLI.looks like the protected routerboot option is gone from hAP ac3 LTE6 and RB4011
confirmed, its still in CLI, sorry I didn't think to check that before posting. I've just rolled my 4011 back to RC3, RC2, RC1, and confirmed it does the same thing on those versions as well. tried using both winbox 3.30 and 3.31. can't use older versions of winbox since ROS v7.1RC1. I also downgraded routerboot with each ROS change. gui option is gone on all of the above.Protected routerboot seems to be gone from Winbox but still present in the CLI.looks like the protected routerboot option is gone from hAP ac3 LTE6 and RB4011
There are still issues in rc4 with MLAG. Specifically if you add ports to the bridge that has MLAG ports in it, it will cause traffic flow across the bridge to stop to some ports. You then need to disable/enable the bridge to get it working, or reboot the switch.Is MLAG working better with these latest releases?
As a workaround, you can use queue trees with the parent set to the LAN and WAN interfaces, rather than simple queues. I've been running this since earlier betas with fq_codel with both IPv4 and IPv6 traffic and had no issues.This problem isn't new, also had it in 7.1rc3
Flags: X - disabled
0 chain=bgp-out prefix=10.10.0.0/16 prefix-length=16-24 action=accept
I would suggest opening a GitHub project (or similar) to manage issues and milestones. This would make things easier once it is up and running
RC -X REPORT
ISSUES/FUNCTIONALITY FIXED
ISSUES/FUNCTIONALLY IMPROVED
ISSUES UNDER WORK FOR NEXT C release
ISSUES TO BE FIXED BEFORE FINAL RELEASE
ISSUES FOR IMPLEMENTATION AFTER FINAL RELEASE
ISSUES WILL NOT BE ADDRESSED IN SHORT OR LONG TERM ( without serious cash donations )
This capture was made using ssh from Hex to mAP, which also proves the WG itf itself IS working[-----@mAP2nD] > tool ip-scan interface=wireguard address-range=10.255.255.0/24
failure: interface is not enabled
[-----@mAP2nD] > tool ip-scan address-range=10.255.255.0/24
Columns: ADDRESS, TIME
ADDRESS TIME
10.255.255.2 7ms
10.255.255.1 59ms
I would suggest opening a GitHub project (or similar) to manage issues and milestones. This would make things easier once it is up and running
Here:hi guys, sorry maybe it's noob question
but how to create filter rule on v7, like from v6 ?
i've been looking on wiki, but could find prefix-length, or just use dst-len ?
like this ?
/routing/filter/rule
add chain=BGP_OUT rule="if (dst-len>13 && dst-len<31 && dst in 172.16.0.0/16) { accept }"
Understood. Will try that.This is probably not an issue with 7.1rc4, but rather with 7.1beta6. I was unable to upgrade my RB4011 above 7.1beta6 until I did a reset to no-defaults and uploaded the 7.1rc npk file to the device using MAC Winbox. A bug in 7.1beta6 caused it to crash on reboot, preventing any successful upgrade or downgrade.SUP-61109 - Still cannot update RB2011 past 7.1 beta 6...
This is an old story, didn't start with v7.Strange story, but I found that now default antenna gain is 2db but previously was 0 db and now there is no option on WInbox to change antenna gain. hap ac lite. Check please is it only for me?
hi guys, sorry maybe it's noob question
but how to create filter rule on v7, like from v6 ?
i've been looking on wiki, but could find prefix-length, or just use dst-len ?
Code: Select allFlags: X - disabled 0 chain=bgp-out prefix=10.10.0.0/16 prefix-length=16-24 action=accept
/routing/filter/rule/add chain=bgp_out rule="if(dst==10.10.0.0/16 && dst-len in 16-24) {accept}"
I think you can not use "in" with "dst-len"...something like this
Code: Select all/routing/filter/rule/add chain=bgp_out rule="if(dst==10.10.0.0/16 && dst-len in 16-24) {accept}"
look at filter rule syntax. https://help.mikrotik.com/docs/pages/vi ... d=74678285I think you can not use "in" with "dst-len"...something like this
Code: Select all/routing/filter/rule/add chain=bgp_out rule="if(dst==10.10.0.0/16 && dst-len in 16-24) {accept}"
Even ">=" and "<=" do not work. At least the latter would be nice, makes it more readable imho.
my goodness.. thank you
something like this
Code: Select all/routing/filter/rule/add chain=bgp_out rule="if(dst==10.10.0.0/16 && dst-len in 16-24) {accept}"
Nowhere for now. Waiting if it appeared in next releases.
anyone find where we can check advertisement route ?
Ah, interesting... Still my findings are different from what the documentation says.look at filter rule syntax. https://help.mikrotik.com/docs/pages/vi ... d=74678285
/routing filter rule add chain=ospf_out rule="if (dst in 10.0.0.0/8 && dst-len>19 && dst-len<23 && protocol static) { accept }"
/routing filter rule add chain=ospf_out disabled=yes rule="if (dst in 10.0.0.0/8 && dst-len in 20-22 && protocol static) { accept }"
[admin@MikroTik] /routing/filter/rule> add chain=ospf_out rule="if (dst in 10.0.0.0/8 && dst-len >= 20 && dst-len <= 22 && protocol static) { accept }"
failure: "Word {dst-len} > Word {=} Word {20} " - invalid argument
Ah, interesting... Still my findings are different from what the documentation says.look at filter rule syntax. https://help.mikrotik.com/docs/pages/vi ... d=74678285
1.1.1.1/32 in 1.0.0.0/8
/routing filter rule add chain=ospf_out disabled=yes \
rule="if ( (dst in 10.0.0.0/8) && (dst-len>=20) && (dst-len<=22) && (protocol static) ) { accept }"
what I copy & paste from help is the fact that the "in" can be applied only to prefix...Your example is covered by prefix property. Have another look at the documentation, my example is covered by num property.
Because "in" work for check if an IP are inside one range, not for check if a number is inside an interval...
[prfx prop readable]
!=|==|in
{address 46/}
[num prop readable] dst-len [prfx prop readable] dst [num prop readable] in {int..int}|{int-int} ==|!=|<=|>=|<|> {int} [num prop readable] [prfx prop readable] !=|==|in {address 46/}
dst-len in 24-24 can be simply written as dst-len == 24
That's exactly what I tried. Device goes nuts: Rule does not work, device becomes unresponsive and CPU is at 100%.@eworm
dst-len in 20-22
Also fixed in rc5.And this is not even accepted:
Code: Select all[admin@MikroTik] /routing/filter/rule> add chain=ospf_out rule="if (dst in 10.0.0.0/8 && dst-len >= 20 && dst-len <= 22 && protocol static) { accept }" failure: "Word {dst-len} > Word {=} Word {20} " - invalid argument
Yes I know. But dst-len in 24-24 is the correct syntax and should do the same as dst-len==24dst-len in 24-24 can be simply written as dst-len == 24
devices with build in antennas have their actual gain hardcoded. if you wanted to change output power, use it with the proper setting and leave the gain aloneStrange story, but I found that now default antenna gain is 2db but previously was 0 db and now there is no option on WInbox to change antenna gain. hap ac lite. Check please is it only for me?
# CLIENT PROTOCOL DIRECTION USER TX-CURRENT RX-CURRENT
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
0 ::ffff:10.255.255.1 udp send holvoetn 0bps
[holvoetn@mAP2nD] /tool/bandwidth-server/session> print follow
# CLIENT PROTOCOL DIRECTION USER TX-CURRENT RX-CURRENT
0 ::ffff:10.255.255.1 udp receive holvoetn 0bps
0 ::ffff:10.255.255.1 udp receive holvoetn 2.3Mbps
0 ::ffff:10.255.255.1 udp receive holvoetn 932.8kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1239.9kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1160.3kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1285.4kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1376.4kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1478.8kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1490.2kbps
0 ::ffff:10.255.255.1 udp receive holvoetn 1319.6kbps
[holvoetn@MTHex] /tool> bandwidth-test 192.168.90.1 duration=120 protocol=udp user=----- passw
ord=----- direction=receive
status: done testing
duration: 2m
rx-current: 0bps
rx-10-second-average: 0bps
rx-total-average: 0bps
lost-packets: 0
random-data: no
direction: receive
rx-size: 1450
connection-count: 20
local-cpu-load: 1%
remote-cpu-load: 5%
[holvoetn@MTHex] /tool> bandwidth-test 192.168.90.1 duration=120 protocol=udp user=----- passw
ord=----- direction=transmit
status: done testing
duration: 2m
tx-current: 193.3kbps
tx-10-second-average: 195.6kbps
tx-total-average: 430.4kbps
random-data: no
direction: transmit
tx-size: 1450
connection-count: 20
local-cpu-load: 1%
remote-cpu-load: 6%
[holvoetn@MTHex] /tool>
I have created support ticket and delivered supout.rif (SUP-58554) about similar issues with RBM33G + Telit LM960A18, F/W: 32.00.116 (latest) MBIM mode (AT#USBCFG=2). I see the same transaction error message also.Devices:
1) RBLHGR r2 (mipsbe), F/W: 7.1rc4
2) Telit LM960A18, F/W: 32.00.116 (latest)
MBIM mode (AT#USBCFG=2)
Problems:
1) Periodically occur: lte1 transaction error
(introduced in v7.0beta7)
2) together with the lte1 interface
the ppp-out1 interface rises;
when trying to change it to the "Disable" state:
in log: ppp-out1: terminating...
after a while a window appears:
Couldn't change Interface <ppp-out1> - timeout (13)
(introduced in v7.1rc1)
3) Monitor lte1:
CA Band - shows nothing (Telit AT#CAINFO? shows it)
RSSI - shows incorrectly
RSRP - shows correctly
RSRQ - shows values divided by 10
(introduced in v7.1beta6)
thanks! If it is "just" that I may to try it to replace the active-backup pattern I am using on servers with 2 CRS317. Hopefully it will be fixed soon...There are still issues in rc4 with MLAG. Specifically if you add ports to the bridge that has MLAG ports in it, it will cause traffic flow across the bridge to stop to some ports. You then need to disable/enable the bridge to get it working, or reboot the switch.Is MLAG working better with these latest releases?
Mikrotik support are able to repeat the issue, and have reported that it will be fixed in a coming release.thanks! If it is "just" that I may to try it to replace the active-backup pattern I am using on servers with 2 CRS317. Hopefully it will be fixed soon...
Any updates team on mpls bgp ? i have my ibgp peers going down with no logs to explain whats happeningAny specific improvements to MPLS or BGP?
use-network-apn=yes
MPLS deployment status for v7.1rc4 has not been updated at https://help.mikrotik.com/docs/display/ ... col+Status.Any specific improvements to MPLS or BGP?
From what I can tell there are no routing changes from rc3 to rc4 that would affect the colour/status of any features on that page. VPLS still crashes the router with rc4 as it did on rc3, same behavior.MPLS deployment status for v7.1rc4 has not been updated at https://help.mikrotik.com/docs/display/ ... col+Status.
Could you tried creating a bridge-wan with a single port (sfp) and use this bridge in your configuration?I have a higher MTU on the SFP, PPPoE won't go further than 1492.
Yeah, you've done pretty well getting converted as far as you have.The closest I got is this:However when trying to use a regular expression containing _ or ( or ), you get syntax errors in masses.Code: Select all/routing filter rule add chain= MY_NETWORKS rule="if(bgp-as-path ^\$ ) {accept}" add chain= MY_NETWORKS rule="if(bgp-as-path 1234+\$ ) {accept}" add chain= MY_NETWORKS rule="if(bgp-as-path 5678+\$ ) {accept}" add chain= MY_NETWORKS rule="if(bgp-as-path 9102+\$ ) {accept}" add chain= MY_NETWORKS rule="if(bgp-as-path 3456+\$ ) {accept}"
If you use _ you end up with a real space in the config doing nothing.
If you use ^ you need to put \\\ in front
If you use ) it closes the "if" instead of being part of the expression etc etc.
If anyone has a clue on how to encode this correctly, let me know....
As above the rule let pass AS991234 as well which it shouldn't. So the whitespace in front of the number is important.
bgp-as-path
Almost.. it's not standard regex,For non Regex experts:
_1234+$ means 1234 at the end of the string must be present preceded by a whitespace (or the start of the string).
1234+$ only means any string ending with 1234. So this also matches 991234, 11234 etc.
_
(^|[,{}() ]|$)
This is a weird code block to force the following blocks to be inline, because the forum code is crap
and is not able to work out what should be inline what what should not because it's the same bbcode.
perhaps it should use markdown instead, where ` and ``` are really easy to use and understand.
+
+
*
.+
I also randomly lost some cfg on reboot (some wireguard interfaces, peers, and a network bridge - hopefully that's all..), on an otherwise healthy chr 7rc4 on awsPartial configuration loss in 7.1rc4, after a few succesful reboots..
Same section got lost as 7.1rc3 => /ip ipsec identity
SUP-60031
P: Something loose in cockpitI thought the days of "fixed some stuff" were long behind Mikrotik*) other fixes and improvements;
no hyperlink visible to click and expand the route list!and where is the cosmetic bug?
[admin@x] /system/watchdog> print
watch-address: none
watchdog-timer: no
ping-start-after-boot: 5m
ping-timeout: 1m
automatic-supout: yes
auto-send-supout: no
[admin@x] /system/watchdog> set watchdog-timer=yes
failure: failed to enable watchdog timer
When you ENABLE filtering but not provide what you want filter then you get this message: Please specify more specific Dst. Address Filter.no hyperlink visible to click and expand the route list!
/interface/lte/unset value-name=band lte1
input does not match any value of value-name
ValueName ::= allow-roaming | modem-init | network-mode
band=""
/interface/lte/set band="" lte1
ambiguous value of band, more than one possible value matches input
/interface/lte/edit value-name=band lte1
it's the new winbox versioncosmetic bug!!
regards
Ros
TRUE, this not work. SUP-61515I found I can't unset LTE interface band value. I recall this was working earlier.
(except SiB who is a test panda)That's why this is DEVELOPMENT channel and we are a test rabbit
How many mipsbe devices come with mentioned wireless chip and 256MB RAM? Not to mention that mipsbe CPUs are mostly too weak even to maintain full-speed ac wireless.Supported v7.1rc4 Wave2 for MIPSBE?
OMG, I spit out my coffee reading that line.Supported v7.1rc4 Wave2 for MIPSBE?
See: https://www.qualcomm.com/products/qca9982
We tried to use some mibsbe devices with 7.1 (due to lack of support for Huawei e3372h LTE modem in stable). I truly hope that "improved stability" means that a bug causing random outages and dead device has actually been fixed. Any details about this improvement from MT would be welcomed.What's new in 7.1rc4 (2021-Sep-20 13:18):
*) improved filesystem and configuration storage stability;
Manual reboot or crash?My 4011 crash rebooted 2nd time now after 4 day uptime, no supout was generated, just" router rebooted without proper shutdown"Darn! After a reboot I lost about 5000 of my 22000 address-list entries. Good that I had a reasonable recent export so I could restore more than 99%. The router is a 4011.
It was an upgrade to v7RC4 that is running now for some time and was rebooted at least 10 times before over that period. The config was coming from 6.48.4 when it was upgraded to v7RC4 a time ago.msatter, please clarfiy. It was a simple reboot on an already installed rc4 device or an upgrade from previous versions?
# comment
local abc1 123
/interface vlan
add interface=ether2 name=telekom-vlan vlan-id=7
/interface pppoe-client
add add-default-route=yes disabled=no interface=telekom-vlan keepalive-timeout=disabled max-mtu=1480 name=pppoe-telekom user=\
xxxx@t-online.de
/ipv6 settings
set accept-redirects=no accept-router-advertisements=no disable-ipv6=no
/ipv6 address
add address=::1 from-pool=telekom-ipv6 interface=bridge
/ipv6 dhcp-client
add interface=pppoe-telekom pool-name=telekom-ipv6 rapid-commit=no request=prefix use-peer-dns=no
/ipv6 firewall filter
add action=accept chain=input comment="allow established and related" connection-state=established,related
add action=accept chain=input comment="accept ICMPv6" protocol=icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" port=33434-33534 protocol=udp
add action=accept chain=input comment="accept DHCPv6-Client prefix delegation." dst-port=546 protocol=udp src-address=fe80::/16
add action=drop chain=input disabled=yes in-interface=pppoe-telekom log-prefix=dropLL_from_public src-address=fe80::/16
add action=drop chain=input
/ipv6 nd
set [ find default=yes ] advertise-dns=no advertise-mac-address=no interface=bridge mtu=1480 ra-lifetime=15m
/system/health> print
Columns: NAME, VALUE, TYPE
# NAME VALUE TYPE
0 voltage 0.5 V
It should be repaired in RC5, as I mentioned above. Stay tuned.When i enable IPv6 my CRS326 looses all connections and is unreachable after about 3hours45min. There is no problem if I disable IPv6. The only thing that might be related to the 3:45 time is the lease time for the dhcp prefix I receive.
I think this is the relevant config:Code: Select all/interface vlan add interface=ether2 name=telekom-vlan vlan-id=7 /interface pppoe-client add add-default-route=yes disabled=no interface=telekom-vlan keepalive-timeout=disabled max-mtu=1480 name=pppoe-telekom user=\ xxxx@t-online.de /ipv6 settings set accept-redirects=no accept-router-advertisements=no disable-ipv6=no /ipv6 address add address=::1 from-pool=telekom-ipv6 interface=bridge /ipv6 dhcp-client add interface=pppoe-telekom pool-name=telekom-ipv6 rapid-commit=no request=prefix use-peer-dns=no /ipv6 firewall filter add action=accept chain=input comment="allow established and related" connection-state=established,related add action=accept chain=input comment="accept ICMPv6" protocol=icmpv6 add action=accept chain=input comment="defconf: accept UDP traceroute" port=33434-33534 protocol=udp add action=accept chain=input comment="accept DHCPv6-Client prefix delegation." dst-port=546 protocol=udp src-address=fe80::/16 add action=drop chain=input disabled=yes in-interface=pppoe-telekom log-prefix=dropLL_from_public src-address=fe80::/16 add action=drop chain=input /ipv6 nd set [ find default=yes ] advertise-dns=no advertise-mac-address=no interface=bridge mtu=1480 ra-lifetime=15m
I've asked support for the "stable" rOS, the reply was that the rc4 was more stable than the 7.0.5(it seems that it is not that stable) that came with it. but I haven't got any bugs with it for now.Hello,
I am new here...I have a question, how can I get FW from my routerboard RB5009?
Because from support I don't have any answer, what I want. They only told me, so I can download via downloads from mikrotik..
In rourerboard is v7 stable. But if I reinstall to 7rc4, there is no chance to turn back to "official" stable version, which is not i mikrotik site..
Because when I found some bugs..I have prolems to keep back.
Thank you so much.
It looks that the firmware is included in the software itself. If Mikrotik has removed previous versions then their is no way back or you have ask others here if they have they have that earlierversion for you.Hello,
I am new here...I have a question, how can I get FW from my routerboard RB5009?
Because from support I don't have any answer, what I want. They only told me, so I can download via downloads from mikrotik..
In rourerboard is v7 stable. But if I reinstall to 7rc4, there is no chance to turn back to "official" stable version, which is not i mikrotik site..
Because when I found some bugs..I have prolems to keep back.
Thank you so much.
Hi,I've asked support for the "stable" rOS, the reply was that the rc4 was more stable than the 7.0.5(it seems that it is not that stable) that came with it. but I haven't got any bugs with it for now.
I have still 7.0.5, because I don't know, how buggy is 7rc4..So I only want to know, how to save it, before I want to upgrade..It looks that the firmware is included in the software itself. If Mikrotik has removed previous versions then their is no way back or you have ask others here if they have they have that earlierversion for you.
The 5009 is a v7 only device so there is no 6.4x vetsion for it. v7.0x is in your case the 'stable' version. RC is an updated and improved version of that. But you have doubt tjen wait a while for RC5 and a bit more patience added, to if the are initial problems with that version.Hi,I've asked support for the "stable" rOS, the reply was that the rc4 was more stable than the 7.0.5(it seems that it is not that stable) that came with it. but I haven't got any bugs with it for now.
Thank you so much..They didn't say that to me..
I ask, is this a normal version only rename (6.48.x) , but no answer..So I know more now.
No, you can't make a backup.I have still 7.0.5, because I don't know, how buggy is 7rc4..So I only want to know, how to save it, before I want to upgrade..
So is it possible to backup old FW if something happen with new FW?
Thanks
ccr2004 - 7.1rc4. all buttons in placeAnother OVPN - Problem:
Upgraded a Chateau LTE12 from 7.1Beta5 to 7.1rc3.
Same with 7.1rc4 !
Under PPP/Interface OVPN - Server Button and PPPoE Scan Button disappeard in Winbox AND Webfig !
Thank you for specification..it will be ok for meNo, you can't make a backup.
regarding the "how buggy" It depends what you want to do, in the normal "home/office" use case, it should be fine. I did not have any issues with mine on both RB5009 and RB4011 when using rc4.
I'm using IPv4/IPv6 with firewall, OSPF, Wireguard and ZeroTier (testing) with no issues for now
Its still missing and needed for us to really test the correct things.Please update https://help.mikrotik.com/docs/display/ ... col+Status
Seems to be a problem with the Chateau LTE12 !ccr2004 - 7.1rc4. all buttons in placeAnother OVPN - Problem:
Upgraded a Chateau LTE12 from 7.1Beta5 to 7.1rc3.
Same with 7.1rc4 !
Under PPP/Interface OVPN - Server Button and PPPoE Scan Button disappeard in Winbox AND Webfig !
Chateau here and I have both buttons in Winbox and Webfig. As rextended already mentioned: maybe they are hidden in active design.Another OVPN - Problem:
Upgraded a Chateau LTE12 from 7.1Beta5 to 7.1rc3.
Same with 7.1rc4 !
Under PPP/Interface OVPN - Server Button and PPPoE Scan Button disappeard in Winbox AND Webfig !
Which hardware you have? Do you have l2mtu set bigger than the default (1592)?In rc4 I already experienced 2 complete device lockups. Happens after a few days uptime. The device did not auto-reboot nor did the watchdog generate an autosupout.rif nor any log entry. I thought that times are long behind me, but in this recent RC the instability has catched up again.
AndIPv6 traffic doesn't flow through the router when a Simple Queue is active. I setup a Simple Queue with target LAN Interface and Destination WAN interface - and queue type FQ_Codel. When the queue is active, IPv6 traffic doesn't work, queue inactive - it works again. This problem isn't new, also had it in 7.1rc3
IPv6 connection tracking with simple queue (cake and pcq) and queue tree is also still broken.
I just tried to get a minimal config working on a hex PoE (freshly reset without default) which produces this issue:AndIPv6 traffic doesn't flow through the router when a Simple Queue is active. I setup a Simple Queue with target LAN Interface and Destination WAN interface - and queue type FQ_Codel. When the queue is active, IPv6 traffic doesn't work, queue inactive - it works again. This problem isn't new, also had it in 7.1rc3IPv6 connection tracking with simple queue (cake and pcq) and queue tree is also still broken.
Please send us supout.rif files to the support@mikrotik.com
Simply configuring IPv6, queues, and dst/target interfaces, limitations work for us, so there must be some specific settings we are missing.
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip hotspot profile
set [ find default=yes ] html-directory=hotspot
/queue type
add cake-bandwidth=70.0Mbps kind=cake name=cake-download
add cake-bandwidth=10.0Mbps kind=cake name=cake-upload
/queue simple
add name=queue1 queue=cake-download/cake-upload target=ether1
/ipv6 dhcp-client
add add-default-route=yes interface=ether1 pool-name=inet-prefix request=\
address,prefix
/ipv6 firewall filter
add action=accept chain=input connection-state=invalid,new log=yes log-prefix=\
ipv6,invalid,new
This is funny, you just joined the forum but appear to know wat all people here want.Most of us are more interested in when the stable v7 is released (with the newer cake/fq_codel supporting linux kernels), because honestly, cake is what everybody needs (now) and is waiting for.
And, not unimportant, many other big brands are already using it. So, users are fleeing towards those other brands because of that.
Most of us are more interested in when the stable v7 is released (with the newer cake/fq_codel supporting linux kernels), because honestly, cake is what everybody needs (now) and is waiting for.
And, not unimportant, many other big brands are already using it. So, users are fleeing towards those other brands because of that.
tc qdisc ... cake
...
[ mpu N ]
[ ingress | egress* ] <----------
(* marks defaults)
What's the correlation between the date a user joined a forum and the actual content of it...This is funny, you just joined the forum but appear to know wat all people here want.Most of us are more interested in when the stable v7 is released (with the newer cake/fq_codel supporting linux kernels), because honestly, cake is what everybody needs (now) and is waiting for.
And, not unimportant, many other big brands are already using it. So, users are fleeing towards those other brands because of that.
Trust me, cake/fq_codel is not that important for most people.
What's the correlation between the date a user joined a forum and the actual content of it...
This is funny, you just joined the forum but appear to know wat all people here want.
Trust me, cake/fq_codel is not that important for most people.
We all have our needs and what feels important to us, and when we focus on that we love individually, we tend to see more of it and that's natural. So you dismiss it as unimportant in a disdain manner. Why? To steer the conversation to what is important to you? So you see you're no better...
The cake/codel announcement on reddit was the 35th hottest post of all time there, there are several threads here too. There's even a bufferbloat consortium with highly talented people (with not just BS certifications you have by reading a book and memorizing pre-made questions), you know, ppl that wrote actual papers and proper algorithms that tries to make the internet better and bring more awareness to the ISPs.
So thank you for your contribution, I hope Mikrotik takes note of it...
Update:I had 7.1rc4 on my RB4011 for some days now w/o stability issues.
Yesterday I installed
- zerotier
- user-manager
- container
packages and since then the devices rebooted at least 2 times within 24 hours w/o a supout.
I haven't done anything yet with the above packages but it seems to me that one of them is causing the crashes as before that was no issue at all.
:00000050
AL31400X-140
RouterBOOT booter 6.47.7
RB4011iGS+
CPU frequency: 1400 MHz
Memory size: 1024 MiB
NAND size: 512 MiB
Press any key within 2 seconds to enter setup..
loading kernel... OK
setting up elf image... OK
jumping to kernel code
I tried to upgrade from 6.48.1 to development channel 7.1rc4.
I don't know firmware version, but it was probably lower than 6.48.1. Logs hint it is 6.47.7
Seems like I bricked my device (RB4011)
...
Changed to older netinstall and image installed instantly. All good, device unbricked, and firmware upgraded to 7.1rc4 aswell.
You use a domain name in peer configuration, no? I guess RouterOS tries to resolve that name while network connectivity is not yet available. Thus there's no valid ip address and peer is in a bad state until the name is resolved again - if ever. Mikrotik, can you verify?Re: WG interface - strike that remark. Still not working on Map (tested 3 times, waited up to 15 minutes each) and Map Lite also did not come up on itself after reboot when coming home (10 minute wait).
Not 100% sure I understand the definition of "domain name in peer configuration". Can you please elaborate what you mean ?You use a domain name in peer configuration, no? I guess RouterOS tries to resolve that name while network connectivity is not yet available. Thus there's no valid ip address and peer is in a bad state until the name is resolved again - if ever. Mikrotik, can you verify?
Thanks for the response.All VPN initiators on Mikrotik keep retrying until the connection gets up - SSTP, IPsec, L2TP... if the remote address is indicated as fqdn, the retrying includes re-resolving of the peer address from the fqdn. But that does not necessarily mean that it's the same case with Wireguard - there, the resolution may be attempted once, and if it fails because it is done too early during the startup process, it may not be repeated, which would be a bug of course. So for the time being, you have to script a workaround - one minute after startup, disable and re-enable the wireguard interface. Or use /tool netwatch to ping an address accessible via the Wireguard tunnel, and let the down-script do the disable and re-enable.
I have HP 107w printer at home.
Haven't been using it for a month but it was working fine on betas.
Now however I cannot connect to WIFI anymore.
My short config:
set [ find default-name=wifi1 ] channel.band=2ghz-n .width=20/40mhz configuration.country=Malaysia .mode=ap .ssid=XXXXXXX disabled=no security.authentication-types=wpa2-psk,wpa3-psk .disable-pmkid=no .wps=disable
Tried to reset the printer completely.
Manual setup (no WPS) fail and I can see in logs:
XXXXXXXXXXXX:16@wifi1 disconnected, key handshake failure, signal strength -65
WPS Setup also fails with below in turn:
XXXXXXXXXXXX:16@wifi1 rejected, does not provide suitable security method
Anybody having similar problems?
/interface/print proplist=name,mtu,actual-mtu,l2mtu where type=vlan
Flags: R - RUNNING
Columns: NAME, MTU, ACTUAL-MTU, L2MTU
# NAME MTU ACTUAL-MTU L2MTU
0 R br-vlan10-LAN-MGMT 1500 1500 9088
1 R br-vlan910-bb-mmm.wmz.01-5ac 1500 1500 9088
2 R br-vlan940-bb-mmm.01-10g 9000 1500 9088
3 R br-vlan1010 9000 1500 9088
4 R br-vlan1020 9000 1500 9088
/interface/set [find where name=br-vlan940-bb-mmm.01-10g] mtu=8999
/interface/set [find where name=br-vlan940-bb-mmm.01-10g] mtu=9000
/interface/print proplist=name,mtu,actual-mtu,l2mtu where type=vlan
Flags: R - RUNNING
Columns: NAME, MTU, ACTUAL-MTU, L2MTU
# NAME MTU ACTUAL-MTU L2MTU
0 R br-vlan10-LAN-MGMT 1500 1500 9088
1 R br-vlan910-bb-mmm.wmz.01-5ac 1500 1500 9088
2 R br-vlan940-bb-mmm.01-10g 9000 9000 9088
3 R br-vlan1010 9000 1500 9088
4 R br-vlan1020 9000 1500 9088
[ccr2004] > /ip smb/shares/print
Flags: * - DEFAULT
Columns: NAME, DIRECTORY, MAX-SESSIONS
# NAME DIRECTORY MAX-SESSIONS
;;; default share
0 * pub /pub 10
;;; default share
1 pub /pub 10
[ccr2004] > /ip smb/users/print
Flags: * - DEFAULT
Columns: NAME, READ-ONLY
# NAME READ-ONLY
0 * guest yes
1 guest yes
No luck with getting the GPS to work on the LtAP either with v7. I'm using an external antenna, too. I did the upgrade without checking if it works with v6 first, unfortunately.I have had no luck getting GPS to work in an LtAP with v7 - however, I'm not 100% sure I ever tried it on v6. Has anyone else here had luck with GPS?
And bgp-as-path regexp matching in bgp filters still doesn't work. (ticket open with support)
My ovpn doesn't even connect "Require Client Certificate" left uncheckedUpdated a RB2011 and a Chateau LTE12 from rc3 to rc4.
Problem with OVPN - Server on both boards:
If the "Require Client Certificate" in the Server settings is checked,
no tunnel can be established.
Logging on Server side shows TLS-error !
After unchecking, tunnels are established as excpected.
So I downgraded to rc3 and everything ( even with activated "Require Client Certificate" ) went back to normal !
Anybody else observed this problem?
as one of the developers/designers of fq_codel, and cake, I'm very interested in actual results on it, on your OS. I've worried, for example, that BQL support didn't make several mikrotik device drivers, and thus running fq_codel or cake at line rate (which is way less cpu intensive than shaping) won't work as well as it could. Can folk verify if BQL is enabled? either qdisc can work wonders on older devices with 100Mbit physical links, and some at a gbit, and replacing pfifo_fast entirely in the field for everything has always been a goal of the bufferbloat project. tc qdisc replace dev eth0 root cake.
What's the correlation between the date a user joined a forum and the actual content of it...
We all have our needs and what feels important to us, and when we focus on that we love individually, we tend to see more of it and that's natural. So you dismiss it as unimportant in a disdain manner. Why? To steer the conversation to what is important to you? So you see you're no better...
The cake/codel announcement on reddit was the 35th hottest post of all time there, there are several threads here too. There's even a bufferbloat consortium with highly talented people (with not just BS certifications you have by reading a book and memorizing pre-made questions), you know, ppl that wrote actual papers and proper algorithms that tries to make the internet better and bring more awareness to the ISPs.
So thank you for your contribution, I hope Mikrotik takes note of it...
Hi Dave, fancy seeing you around here! Thanks for your work in ridding the world of bufferbloat!Merely someone here posting a
tc -s qdisc show
with cake output showing some drops or marks and backlog would make me very happy after waiting all this time for mikrotik to catchup
I try to stress that the cake effort had a large team, and was exhaustively driven by demand of thousands of users using sqm. I'm just one of the most visible.Dave, Thank you for the work in making CAKE even exist. It will finally give me a DSCP aware queuing discipline on Mikrotik. Now I just need them to use a modern implementation of CAKE where the Least Effort DSCP mark is LE(000001) instead of CS1(001000).
And if they could please add Queue Type selection to the Queues tab of the DHCP Server settings, just like it is on the Queues tab of the PPP Profile, I will be ecstatic.
failing that it's my hope more here actually test. slam cake on an interface, try the rrul tests in flent, or drive it hard with a test too of choice and inspect the packet capture.Hi Dave, fancy seeing you around here! Thanks for your work in ridding the world of bufferbloat!Merely someone here posting a
tc -s qdisc show
with cake output showing some drops or marks and backlog would make me very happy after waiting all this time for mikrotik to catchup
Unfortunately, Mikrotik's RouterOS completely abstracts any notion of a shell away from the user, so outside of anything Mikrotik staff themselves wish to provide the only console output you could get is whatever output Mikrotik has abstracted from the underlying tools.
Hi Dave,failing that it's my hope more here actually test. slam cake on an interface, try the rrul tests in flent, or drive it hard with a test too of choice and inspect the packet capture.
Hi Dave, fancy seeing you around here! Thanks for your work in ridding the world of bufferbloat!
Unfortunately, Mikrotik's RouterOS completely abstracts any notion of a shell away from the user, so outside of anything Mikrotik staff themselves wish to provide the only console output you could get is whatever output Mikrotik has abstracted from the underlying tools.
are they exposing the rtt, ack-filter, nat or other options?
Ah, I read the doc. All those options are exposed. Yay!
I put a PSA about cake's options over here:
viewtopic.php?p=885000#p885000
Selfishly I'd really like to see from y'all some before (say, htb + sfq)/ after results (cake) on mikrotik's hw. Particularly the higher end stuff.
Do you think it will ever be fixed? Is it possible someone can translate your fixes to Latvian?I've worried, for example, that BQL support didn't make several mikrotik device drivers, and thus running fq_codel or cake at line rate (which is way less cpu intensive than shaping) won't work as well as it could.
+1 for fixMaybe known already but couldn't find it mentioned. The simple queue limits is a 32-bit unsigned int so the maximum bw limit one can specify is 4294967295 (~4.29Gbit/s). Same bug in 6.x . Please fix
Hasn't it always been this way?if there is a child queue, then the parent queue will only receive packets that will pass by the CHILD queue TOO
As soon as queue has at least one child it becomes a inner queue, all queues without children - leaf queues. Leaf queues make actual traffic consumption, Inner queues are responsible only for traffic distribution.
#error exporting /mpls/traffic-eng/path
In previous 7.1rcX, adding verbose to the export used to make it work - have you tried that?Export started at oct/12/2021 10:40:20 by RouterOS 7.1rc4, and it's been stuck on this for 14 minutes so far
Thanks for nothing, Chateau! The power outage was caused by me. No need to tell me.router rebooted without proper shutdown, probably power outage.
1 * name="disk" target=disk disk-file-name="log" disk-lines-per-file=1000 disk-file-count=2 disk-stop-on-full=no
I do have the suspicion that the mlag peer port is causing issues with Spanning-Tree... looks like the peer port is creating a loop when using multiple VLANs.There are still issues in rc4 with MLAG. Specifically if you add ports to the bridge that has MLAG ports in it, it will cause traffic flow across the bridge to stop to some ports. You then need to disable/enable the bridge to get it working, or reboot the switch.Is MLAG working better with these latest releases?
It wouldn't be so bad but the documentation is basically "ok now go have fun" instead of actually helpful information...
Or a v7.2beta1rc4 has been out for a while now. I fear that next is 7.1 (and not rc5).
unrelated: I predict for the next release we have v7.2RC1 or v7.2beta1 (testing) with move up to 5.10.x LTS kernel
Same here. Sadly...My main concern is that if this is going to be the way forward I'm honestly either going to stay on 6.x for several more years and hope that the devs remove head from ground and make it usable or just find a new vendor.
Found on Reddit that some users receive rc5. Also waiting for at least a stable version cause my CCR2004-1G-12S+2XS still doesn't have a production-ready firmware that can use all amount of RAM.rc4 has been out for a while now. I fear that next is 7.1 (and not rc5).
Trying to update a RB 850Gx2 (PPC) with the dev release, but winbox keeps saying "calculating download size" and hangs on that. While trying any other package option (long-term, stable, testing) they all download fluently. Something I'm missing here?So, is the download server for dev release down?
Might be related to the previous post that a new version might be coming shortly and they disabled rc4 for download already ?Trying to update a RB 850Gx2 (PPC) with the dev release, but winbox keeps saying "calculating download size" and hangs on that. While trying any other package option (long-term, stable, testing) they all download fluently. Something I'm missing here?So, is the download server for dev release down?
It was a joke referring to bad software engineering practices from Mkt like introducing new features during a RC cycle. At this point they should just increment a number or pick a random oneunrelated: I predict for the next release we have v7.2RC1 or v7.2beta1 (testing) with move up to 5.10.x LTS kernel
Why do you think MT will jump from 7.1rc4 to 7.2beta1? The usual version path is beta -> rc -> release and I don't see any reason to skip release version with 7.1 series. And I don't think there's a serious reason to jump from 5.6 (or whatever 7.1rc is using) to 5.10 ... before MT irons out most (if not all) UI and driver issues still present.
We did see jump from 7.0beta to 7.1beta, but MT explained it was due to (change of) versioning rules ...
None. It's as it was by default. Never added any extras.If it's stuck on calculating download size then you need to remove any extra packages that are installed.
[Administrator@DESKTOP ~]$ curl -k -v -u admin: http://router.mydomain:48729/rest/ip/addresses
* STATE: INIT => CONNECT handle 0x80007eee8; line 1789 (connection #-5000)
* Added connection 0. The cache now contains 1 members
* STATE: CONNECT => RESOLVING handle 0x80007eee8; line 1835 (connection #0)
* family0 == v4, family1 == v6
* Trying 192.168.1.1:48729...
* STATE: RESOLVING => CONNECTING handle 0x80007eee8; line 1917 (connection #0)
* Connected to router.mydomain (192.168.1.1) port 48729 (#0)
* STATE: CONNECTING => PROTOCONNECT handle 0x80007eee8; line 1980 (connection #0)
* STATE: PROTOCONNECT => DO handle 0x80007eee8; line 2003 (connection #0)
* Server auth using Basic with user 'admin'
> GET /rest/ip/addresses HTTP/1.1
> Host: router.mydomain:48729
> Authorization: Basic YWRtaW46
> User-Agent: curl/7.79.1
> Accept: */*
>
* STATE: DO => DID handle 0x80007eee8; line 2077 (connection #0)
* STATE: DID => PERFORMING handle 0x80007eee8; line 2196 (connection #0)
* STATE: PERFORMING => DONE handle 0x80007eee8; line 2395 (connection #0)
* multi_done
* Empty reply from server
* The cache now contains 0 members
* Closing connection 0
curl: (52) Empty reply from server
I have a tutorial on this on YouTubeYou have to use HTTPS, see documentation for more info:
https://help.mikrotik.com/docs/display/ROS/REST+API
Try a netinstall and default config during that. For me that worked.Issue on upgrading from 6.49 to 7.1rc4 on a 4011. Reboot loop - router reboots within 30-45s of startup if my PPTP VPNs are enabled. If I disable the VPN's or setup L2TP VPNs, works fine.
Format c: gave usually an "oops" moment...I am sick of "netinstall resolves it". It is like "format c:/" on old windows 98/xp systems.
No, it's not. It's real easy to externally Save backups of your config with mikrotik devices and restore (almost always) works fine. I think in all the years I've managed mikrotik devices I had just one case where the restore backup did not fix an issue after a netinstall, but that had to do with having netinstalled a beta image.I am sick of "netinstall resolves it". It is like "format c:/" on old windows 98/xp systems.
True for those who own older hardware that supports the 6.x release train. Not true for those who have bought any of the more recent products that will only run 7.x.You can choose to participate (voluntarily) or stick to the older versions and wait for v7.9.4 with fewer bugs and problems.
maherhaddad, did you get any further with this? I've seen the occasional packet received (RIP Neighbors), but am having difficulties with this as well.Guys, RIP routing protocol on ROS v7 is still not working. You mentioned in the changelog that RIP is supported but in fact it is not operational. I have made the tests and routes are not being learned.
Can you please fix this issue ASAP?
Thanks.
Not true for those who have bought any of the more recent products that will only run 7.x.