Can you post what did change?due to bridge configuration changes
It was a masquerade rule that was configured to allow access to the next router, the rule was disabled and showed an error I modified the output device from a specific ether within the bridge to the parent bridge itself.Can you post what did change?due to bridge configuration changes
*) discovery - correctly create neighbors from VLAN tagged discovery messages;
*) wireless - include last frequency when manually setting frequency step in "scan-list";
what exactly will do for us?
routeros-smips-6.43.7.npk 7434 KB routeros-smips-6.44.5.npk 7522 KB routeros-smips-6.45.5.npk 7510 KB routeros-smips-6.45.6.npk 7550 KB
Now you can try to upgrade to 6.45.6. Since 6.43.7 takes less space compare to your previous version was larger, 6.45.6 may now fit.Downgrade to 6.43.7 went fine.
Same problem. I have a nAP ac. I can’t even update using the netinstall utility from 6.45.5 to 6.45.6.Dear MikroTik team,
Please try to make 6.45.x bundles smaller for smips devices (hAP lite, hAP mini) without sacrificing the functionality. Upgrade from 6.45.5 to 6.45.6 failed on one of my hAP lite due to insufficient free space (20 KiB free out of 16 MiB). And yes, I had no other files, just the .npk, and rebooted the router before the upgrade.
I could not switch to long-term channel 6.44.5 - the same space problem (48 KiB free out of 16 MiB).
Downgrade to 6.43.7 went fine.
Here is the list of npk for mentioned versions with their file size:Code:Select allrouteros-smips-6.43.7.npk 7434 KB routeros-smips-6.44.5.npk 7522 KB routeros-smips-6.45.5.npk 7510 KB routeros-smips-6.45.6.npk 7550 KB
That worked well, thanks. So the upgrade path for this hAP lite was:Now you can try to upgrade to 6.45.6. Since 6.43.7 takes less space compare to your previous version was larger, 6.45.6 may now fit.Downgrade to 6.43.7 went fine.
It will become better since 6.46 is smaller than 6.45. It was just some version of 6.45 that was on the limit of what was possible to add and to do upgrade from.Doing the upgrade to the subsequent version via the downgrade first does not look like a straightforward way. And that seems to be the only way for this device, unless npk becomes smaller in size.
You can route the vlan to a bridge and set neighbor discovery onto that bridge that way you'll still have neighbor discovery enabled.Since the release of 6.45.1, neighbor discovery on our networks don't show IP addresses; only MAC addresses and other information.
I suspect it's because we carry our admin traffic on a VLAN, and the default VLAN is unused. My suspicion is, thanks to:
introduced in 6.45.1, we are "correctly" seeing the neighbor information for the default VLAN (with no IP addresses), instead of the IP information from our management VLAN.Code:Select all*) discovery - correctly create neighbors from VLAN tagged discovery messages;
I discovered this (pun intended) while downgrading to 6.44.5 for suspected OSPF issues. Very inconvenient when I don't have all of our IP addresses committed to memory...
Same for me.There is no statistic in all CAP interface on CCR1009-8G-1S-1S+.
Code: Select all
11:36:27 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:36:37 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:37:07 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:37:18 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:37:47 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:37:58 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:38:27 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:38:39 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:39:08 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:39:20 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:39:48 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:40:01 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:40:28 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:40:42 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:41:08 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:41:22 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:41:48 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:42:02 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:42:28 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:42:43 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:43:08 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:43:23 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:43:48路线,ospf OSPFv2邻居10.9.0.1信息:state change from Loading to 2-Way
11:44:04 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:44:28 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:44:45 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:45:08 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:45:26 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:45:48 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:46:07 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:46:29路线,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:46:48 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:47:09 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
11:47:29 route,ospf,info OSPFv2 neighbor 10.9.0.1: state change from Loading to 2-Way
downgrade 6.44, ospf works :[
about 20 routers, half was updated, all updated did this. downgrade fixes ;[
ospf with backbone and 23 nssa areas.
two links from bbone to nssa.♂️
vrf.
edit.
added a nokia to the mix:
"LCL_RTR_ID 10.9.0.1: Neighbor 0.0.0.6 on TEST-NBR router state changed to exchangeStart (event SEQ_MISM)"
Is that not like saying "The surgery went well but he died"?更新时平稳,但NAT规则不再工作。
I setup yesterday Kid Control on 6.45.6 on RB4011 and it was working well (IP Firewall rules went on and off according to setup),KID control NOT WORKING after update to 6.45.6.
firewall filter rules not installed
My router is RB2011UiaS
First, check the Log after reboot.What am I doing wrong?
Thankyou very much, was my fault, error in user name.I setup yesterday Kid Control on 6.45.6 on RB4011 and it was working well (IP Firewall rules went on and off according to setup),KID control NOT WORKING after update to 6.45.6.
firewall filter rules not installed
My router is RB2011UiaS
also used TIKApp for pause/resume.
Maybe your setup from pre-6.45.6 does not migrate correctly to 6.45.6?
Maybe your setup from pre-6.45.6 does not migrate correctly to 6.45.6?
:local localIP [:pick [/interface pppoe-client monitor PPPoE-Digi as-value] 6;];
:local localIP [:pick [/interface pppoe-client monitor PPPoE-Digi once as-value] 6;];
This makes it even more future-proof:The correct line is:works again.Code:Select all:local localIP [:pick [/interface pppoe-client monitor PPPoE-Digi once as-value] 6;];
:local localIP ([/interface pppoe-client monitor PPPoE-Digi once as-value]->"local-address");
Have you done that already?contact support, system failure, please send supout file to mikrotik support.
Yes I’ve done it alreadyHave you done that already?contact support, system failure, please send supout file to mikrotik support.
22:10:41 ipsec,info new ike2 SA (R): 192.168.100.6[500]-94.254.xxx.xxx[55669] spi:836b5e5dbcfcb0ee:407ceb47da6f8661 22:10:41 ipsec,info,account peer authorized: 192.168.100.6[4500]-94.254.xxx.xxx[22112] spi:836b5e5dbcfcb0ee:407ceb47da6f8661 22:10:41 ipsec,info acquired 192.168.13.253 address for 94.254.xxx.xxx, iPhone.client
[asurkov@m66.officeburg.ru] /interface> bonding eoip l2tp-client mesh ppp-server pptp-server virtual-ethernet blink enable print bridge ethernet l2tp-server ovpn-client pppoe-client sstp-client vlan comment export reset-counters detect-internet gre list ovpn-server pppoe-server sstp-server vpls disable find set dot1x ipip lte ppp-client pptp-client traffic-eng vrrp edit monitor-traffic [asurkov@m66.officeburg.ru] /interface>
[...] > file print detail where name~"wireless*" 0 name="wireless-fp-6.45.6-mipsbe.npk" type="package" size=2748.1KiB creation-time=oct/17/2019 18:53:42 package-name="wireless@" package-version="6.45.6" package-build-time=sep/10/2019 09:06:31 package-architecture="mips" 1 name="wireless-6.45.6-mipsbe.npk" type="package" size=2748.1KiB creation-time=oct/17/2019 18:54:18 package-name="wireless@" package-version="6.45.6" package-build-time=sep/10/2019 09:06:31 package-architecture="mips" [...] >
[...] > /system resource print uptime: 5h31m20s version: 6.45.6 (stable) build-time: Sep/10/2019 09:06:31 free-memory: 75.6MiB total-memory: 128.0MiB cpu: MIPS 74Kc V4.12 cpu-count: 1 cpu-frequency: 600MHz cpu-load: 9% free-hdd-space: 26.5MiB total-hdd-space: 128.0MiB write-sect-since-reboot: 9874 write-sect-total: 8580777 bad-blocks: 0% architecture-name: mipsbe board-name: RB2011UiAS-2HnD platform: MikroTik
/system package print Flags: X - disabled # NAME VERSION SCHEDULED 0 routeros-mmips 6.45.6 1 system 6.45.6 2 X ipv6 6.45.6 3 X wireless 6.45.6 4 X hotspot 6.45.6 5 X mpls 6.45.6 6 routing 6.45.6 7 X ppp 6.45.6 8 dhcp 6.45.6 9 security 6.45.6 10 advanced-tools 6.45.6 11 ntp 6.45.6
Because since 6.45.whatever, package security requires package dhcp to provide a route list to windows IKEv2 clients.After upgrading from 6.44.1 to 6.45.6 it's not possible to disable dhcp package. RouterBOARD 750G r3. Why?
Thanks! It would be nice to see such things in changelogs or somewhere in wiki like 'package dependencies'.Because since 6.45.whatever, package security requires package dhcp to provide a route list to windows IKEv2 clients.After upgrading from 6.44.1 to 6.45.6 it's not possible to disable dhcp package. RouterBOARD 750G r3. Why?
Look again, it is there (in the changelog of the release which has introduced this dependency) and it has also been mentioned multiple times in these "x.xx.x has been released" topics.It would be nice to see such things in changelogs or somewhere in wiki like 'package dependencies'.
Ok. Got it. It was introduced in the 6.44. But in my router with 6.44.1 dhcp was disabled (though security was enabled). Interesting...Look again, it is there (in the changelog of the release which has introduced this dependency) and it has also been mentioned multiple times in these "x.xx.x has been released" topics.It would be nice to see such things in changelogs or somewhere in wiki like 'package dependencies'.