That for sure is not a good idea. Some "debug" topics send a lot of data, more info than the router transports.I’d send everything. Surely your server has the bandwidth and disk space.
Do you know that to export passwords, keys etc into config file you need to use the additional option "show-sensitive" ?furthermore ...suddenly after 4 day uptime, device rebooted with kernel failure
and, WG Private key was lost !!!
it generated a new key
exported the "new" config, and WG private key is missing from export!!!
export file=myconfig show-sensitiveAdditional info:Do you know that to export passwords, keys etc into config file you need to use the additional option "show-sensitive" ?
PleaseCode: Select allexport file=myconfig show-sensitive
This behavior was reverted in 7.2.2 back to how it was before but this has only been done for IPv4. With IPv6, Routing rules still have priority over Routing marks.It turns out there has been a change in route processing with routing rules and route marking in 7.2.2 (vs 7.2.1)
Something to do with vrf's (Thank you Mikrotik Support)
7.2.1 and Prior, routing rules had priority over routing mark. This was changed in 7.2.2
If you have more than one IP addresses you can set the one that is used by default for this particular route...can you explain what is pref-src=0.0.0.0 what thats for?
Disabling Capsman is not an option for me.For me helped disabling CapsManUpgraded from 7.1.x to 7.2.3 on my RB4011 and it seems that it started crashing once in a while which was not an issue with 7.1.x.
Smells a bit like my earlier issues here: viewtopic.php?t=179071
Works fine for me with 7.1.5 for quite a while. I guess I'll stay on long-term then for now. But still would like Mikrotik to acknowledge the crash/reboot issue and address it.Capsman and v7 are not yet friends... I would recommend to remain on v6 until that is fixed.
Same problem in 750Gr3 for me too. Emailed support with supout. SUP-82725Please send support output file from your router with the configuration, that was upgraded to 7.2.3.Just give a try to update 750G r3 mmips from 7.2.1 to 7.2.3 (create backop before the upgrade)...after I cannot access my router from several LAN connectors, cannot even ping the router form some lan, while the PC gets IP from the router DHCP on that lan. So tried
* restore saved configuration before the upgrade - not help
* reset router to defaults on 7.2.3 and resore saved config - not help
* then downgraded do 7.2.1 (config was probably corrupted at all by that..no accees to router from any LAN connector)
* so again reset to defaults on 7.2.1 and restore saved config - everything works like before!
so for me - keep away from v7.2.3 as well :-(
Works for me too, 7.1.5, later versions and 7.3beta are too flaky but 7.1.5 is romping along ok, 56days of uptime on one of my hapac2's and 45days on the other without issues, RB3011 which is the manager is presently at 27 days, would be 56days too but made the disastrous decision to try one of the newer 7.2 STABLE releases and reverted back.withCapsman and v7 are not yet friends... I would recommend to remain on v6 until that is fixed.
Works fine for me with 7.1.5 for quite a while. I guess I'll stay on long-term then for now. But still would like Mikrotik to acknowledge the crash/reboot issue and address it.
/system health
:put [get [find where name=voltage] value]Have a RB4011 rebooting about every 4 hours with 7.2.3. Fixed after downgrade to 7.1.5Does anybody else have issue that Chateau LTE 12 is randomly rebooting about two times per day?
Have a RB4011 rebooting about every 4 hours with 7.2.3.
I am getting the voltage this way.
Its more inline with the rest of my scripting.Code: Select all/system health :put [get [find where name=voltage] value]
After som testing, it seems that value-name are not needed if you specify what you need after the data id.
Differences:
This works
:put [get [find where name=voltage] value-name=value]
This works
:put [get value-name=value [find where name=voltage]]
This works
:put [get [find where name=voltage] value]
This does not work
:put [get value [find where name=voltage]]
/system/health
:put ([get [find where name="voltage"]]->"value")
I am sure they are ibgp.upgrade rb4011 from 7.2.1 to 7.2.3 no bgp connection agains my peers.
from one of my peer side can see this in logs:
i have other peer in similar situation.
from my side no logs.
after a downgrade all is working without touch any config
Yes is ibgp, where i have to change ip? i am using for router-id a loopback ip.I am sure they are ibgp.upgrade rb4011 from 7.2.1 to 7.2.3 no bgp connection agains my peers.
from one of my peer side can see this in logs:
i have other peer in similar situation.
from my side no logs.
after a downgrade all is working without touch any config
they changed the way to choose local address!
Manually set the local ip into the connection and everything starts to work again.
It is not a bug, for ibgp MT usues the loopbackip (as local ip) if there is one.
regards
Ros
manually set local ip into the bgp connection!Yes is ibgp, where i have to change ip? i am using for router-id a loopback ip.
I am sure they are ibgp.
they changed the way to choose local address!
Manually set the local ip into the connection and everything starts to work again.
It is not a bug, for ibgp MT usues the loopbackip (as local ip) if there is one.
regards
Ros
thank! after 5 upgrades/downgrades is working again!manually set local ip into the bgp connection!
Yes is ibgp, where i have to change ip? i am using for router-id a loopback ip.
~$ sudo lldpctl
LLDP neighbors:
Interface: eth0, via: LLDP, RID: 2, Time: 0 day, 08:41:44
Chassis:
ChassisID: mac cc:2d:e0:3d:b6:18
SysName: soada-mkt
SysDescr: MikroTik RouterOS 7.2.3 (stable) May/02/2022 15:18:17 RB3011UiAS
MgmtIP: 169.254.2.1
MgmtIP: fd00:2:1::1
Capability: Bridge, on
Capability: Router, on
Port:
PortID: ifname BR: Switch/eth8: NMS (ac1000)
TTL: 120
LLDP-MED:
Device Type: Network Connectivity Device
Capability: Capabilities, yes
Capability: MDI/PSE, yes
#show lldp neighbors GigabitEthernet1/0/23
Device ID: cc:2d:e0:3d:b6:18
Port ID: BR: Switch/BND: bond1/eth1: sw22 (bond1)
Capabilities: Bridge, Router
System Name: soada-mkt
System description: MikroTik RouterOS 7.2.3 (stable) May/02/2022 15:18:17 RB3011UiAS
Port description:
Management Address: 169.254.2.1
Management Address: fd00:2:1::1
Time To Live: 63
802.1 PVID: None
802.1 PPVID:
802.1 VLAN:
802.1 Protocol:
#show lldp neighbors GigabitEthernet1/0/24
Device ID: cc:2d:e0:3d:b6:18
Port ID: BR: Switch/BND: bond1/eth2: sw22 (bond1)
Capabilities: Bridge, Router
System Name: soada-mkt
System description: MikroTik RouterOS 7.2.3 (stable) May/02/2022 15:18:17 RB3011UiAS
Port description:
Management Address: 169.254.2.1
Management Address: fd00:2:1::1
Time To Live: 77
802.1 PVID: None
802.1 PPVID:
802.1 VLAN:
802.1 Protocol:
I can't configure it as well, but it didn't even light up in the previous versions. At least now it lights up with wireless activity.Still doesn't work for me; after picking either wifi1 or wifi2 interface, I get:The wireless LED is finally working with wifiwave 2 on my hAP ac^3 after updating to 7.2.3.
Does anyone else experience this or is this actually fixed a couple of versions ago?
Couldn't change LED Trigger <wireless signal strength> - Cannot assign interface to trigger! Interface is disabled or this is not a wireless interface! (8)
This is "silence before the storm"...its been a while since last update :/
Ladies and gentlemen, brace yourself ...This is "silence before the storm"...its been a while since last update :/
[admin@MikroTik] /ip/hotspot/walled-garden> export verbose show-sensitive
# model = 911G-5HPnD
/ip hotspot walled-garden
add comment="show allow on winbox" disabled=no dst-host=test.test !dst-port !method !path !server !src-address
add comment="show deny on winbox" disabled=no dst-host=test.test !dst-port !method !path !server !src-address
[admin@MikroTik] /ip/hotspot/walled-garden> print detail
0 ;;; show allow on winbox
dst-host=test.test hits=0
1 ;;; show deny on winbox
dst-host=test.test hits=0
[admin@MikroTik] /ip/hotspot/walled-garden> add comment="terminal test allow" dst-host="new.test" action=allow
[admin@MikroTik] /ip/hotspot/walled-garden> add comment="terminal test deny" dst-host="new.test" action=deny
[admin@MikroTik] /ip/hotspot/walled-garden> export verbose show-sensitive
/ip hotspot walled-garden
add comment="terminal test allow" disabled=no dst-host=new.test !dst-port !method !path !server !src-address
add comment="terminal test deny" disabled=no dst-host=new.test !dst-port !method !path !server !src-address
Unfortunately such videos or other publications will reach only a tiny number of users, and most MikroTik routers will spend their life on their factory software, even 5 years after critical vulnerabilities have been found in it.Wow, great news! This is perfect for tested and stable versions like v7.2.2. And besides that, if something should happen (god forbid), you may use Netinstall that is a very capable tool that doesn't require any settings and will easily restore your device within minutes. ;-)
I have never seen that error. Does it occur with particular types of clients?btw, I use L2TP with CCR for ~400 clients.. and v6 from time to time give me error, and all still works.
Anyone have it at ros7 ?
ppp,error,critical: 217.67.*.*: Encryption got out of sync - disabling
This is old unsolved by MikroTik case with one we all must live... of course it was reported in past.
I don't think they are getting the point. You can see that in reactions to the video, and also before on this forum.
cetipabo, the key words are "routing cache" - it's removed in recent Kernel versionshas been explained several times already.
But why? More throughput or less?v7 uses more CPU than v6, especially when doing benchmarking like speedtest.
has been explained several times already.
Less fake throughput.But why? More throughput or less?
Thanks
Tss tss tss... some catching up to do then :lol:i'm just starting on Mikrotik world, so sorry for not having read the whole forum in one night, i just received my RB4011 yesterday.
But fake throughput you mean from bandwidth test, or from speedtest ISP?Less fake throughput.
Read: results you see now in ROS7 are closer to real life performance.
Some people say this is a fake result, since it would give a greater speed with Speedtest and services alike in contrast with "real" usage. I disagree: what is "real" usage changes with every case - and SoHo routing is a huge use case for Mikrotik.
By the way, now i don't understand why in V7 it says : route cache : yes
I can't find information on the size of this route cache, when it existed. .... Are we talking about a cache of a dozen routes? Hundreds? Thousands?
so route cache size actually depends on available memory unless set otherwise.As a rule of thumb, two millions entries eat about 500 MiB of memory on a 64-bit system. You should be able to compute the average memory usage and the maximum memory usage from the values of net.ipv4.route.max_size, rhash_entries and net.ipv4.route.gc_elasticity. For example, if the route cache hash table has 262,144 buckets, the maximum allowed number of entries in the cache is 4,194,304 and net.ipv4.route.gc_elasticity is set to 8, the memory usage will be 500 MiB on average and 1 GiB max. If this is too much, you will need to lower some values.
Hence my use of the term 'fake results'So in a test scenario it showed good results, but in practice it did not work. That is why it was removed, and why it won't return.
At what severity level is this message?ppp,error,critical: 217.67.*.*: Encryption got out of sync - disabling
0 Emergency
1 Alert
2 Critical
3 Error
4 Warning
5 Notice
6 Informational
7 DebugLikely the problem is that a complete overhaul of the logging system would make some people (who have invested time in handling the mess as it is) angry...I made this post 2017 and sent support information about this and was told that they will look at it, but nothing has changed.
It worked with far more than a few cached routes. Take a look at this link:
Of course this gets more effective when you have a more complex route table, but also it gets more effective when you have only a small number of addresses involved in traffic at a given time. The route cache can store only a couple of entries, or else the action "see if we have this address in our cache" will take similar time as "lookup in the route table". So maybe it caches 5-10 entries.
When you are doing a speedtest, the router only has to route 2 addresses and all lookups are cache hits.
But when you are visiting a modern website or when multiple users are making multiple connections (e.g. your television, computer, mobile phone etc are all having a connection open), there will be more cache misses than hits, and the extra time spent to check if the address is in the cache is just wasted.
So in a test scenario it showed good results, but in practice it did not work. That is why it was removed, and why it won't return.
One of them is me, since I have to rewrite the Splunk Mikrotik logging.Likely the problem is that a complete overhaul of the logging system would make some people (who have invested time in handling the mess as it is) angry...
Remember it was not MikroTik or me who deemed the cache ineffective and removed it. It happened in the Linux kernel development team, and MikroTik hasYes, probably a small router wouldn't have enough CPU (let alone memory) to do this - but it only need to cache about 10k hashes in order to make a huge difference in a SoHo environment.
I'm not advocating to get it back - it had serious problems. I'm just pointing out that the results of its use weren't fake - they were just faster for some use cases and slower for others.Remember it was not MikroTik or me who deemed the cache ineffective and removed it. It happened in the Linux kernel development team, and MikroTik has
to live with its removal.
But it would be possible to have a "bitmap" that has 1 bit corresponding to every possible IPv4 address in 2 megabytes of RAM
NO! Don't use that. it was for a completely different problem. The problem of upgrading installations with separate packages on 16MB flash devices is already wellknown and is not fixed by that.Maybe the fix_space.npk can help ? Or it could brick a v7 install. I don't know xD - viewtopic.php?t=133420&start=100#p671674
/routing ospf interface-template
add area=backbone-v2 disabled=no interfaces=bridge1 networks=192.168.1.0/24 priority=1
add area=backbone-v2 cost=10 disabled=no interfaces=*F0000A networks=172.16.1.16/30 type=ptp
add area=backbone-v2 cost=10 disabled=no interfaces=*F00012 networks=172.16.1.0/30 type=ptp
add area=backbone-v2 cost=10 disabled=no interfaces=*F0000B networks=172.16.1.8/30 type=ptp
add area=backbone-v2 cost=10 disabled=no interfaces=*F00010 networks=172.16.1.24/30 type=ptp
add area=backbone-v2 cost=10 disabled=no interfaces=l2tp-Roaming_Box networks=172.16.1.20/30 type=ptp
add area=backbone-v2 cost=10 disabled=no interfaces=<l2tp-Jasper_Downs_Shearing_Shed> networks=172.16.1.12/30 type=ptp
The device's CPU frequency has not been manually set, nor changed from the defaults.
Eeek!I think the 7.2 branch should be renamed from "stable" to "vista" ;)
no, I have just EoIP now, but I tried both protocols (separately) and both failed with the same error.You have both IPIP and EoIP tunnels?
Then it will be very important to fully understand the matter and to configure things really carefully.
That points in the direction "not fully understanding the matter"...no, I have just EoIP now, but I tried both protocols (separately) and both failed with the same error.You have both IPIP and EoIP tunnels?
Then it will be very important to fully understand the matter and to configure things really carefully.
upgrade to latest version of ROS 6 - 6.49.6 in winbox you should seen the option of channel upgrade... upgrade to version 7,hi
look true whole post and not seen 1 note how to upgrade my classic wAP 60G AP to 7.2.3 from 6.49.6 factory at 6.41.2
so can somebody that knows the secret let me or as that invested (have 5 old classic wAP 60G AP units)
in development of this wAP 60G AP product line know or what to do next
i have rev3 wAP 60G AP at fac os 6.44.6 that upgrade to 7.2.3 fine no memory size error
thank you
d
