Nope, "reset to default" only resets configuration to defaults ... for the packages installed. "reset to default" doesn't install/remove packages them selves.
How do you know everything is gone ?
How do you connect to the device to make that conclusion ?
I have normal L009 and didn't have problems running this version.
Either create separate thread so we can investigate further or create support ticket.
Maybe the LEDs on his ethernet ports are off so that is how he made the conclusion, on the other hand maybe the power LED is off too because his PSU is off 
Anyways some more info would be appreciated…
2 Likes
I have to admit, my ethernet ports were not gone but this showed up in my config:
/interface ethernet
set [ find default-name=ether2 ] l2mtu=1600 name=ether1
set [ find default-name=ether3 ] name=ether2
set [ find default-name=ether4 ] name=ether3
set [ find default-name=ether5 ] name=ether4
set [ find default-name=ether6 ] name=ether5
set [ find default-name=ether7 ] name=ether6
set [ find default-name=ether8 ] name=ether7
set [ find default-name=sfp1 ] name=ether8
Also the A* thing and path cost were added:
add bridge=bridge comment=defconf interface=ether2 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=ether3 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=ether4 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=ether5 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=ether6 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=ether7 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=ether8 internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=*A internal-path-cost=10
path-cost=10
add bridge=bridge comment=defconf interface=wifi1 internal-path-cost=10
path-cost=10
I forgot to make backups before upgrading, in order to get things working again have reset my router and pieced my former config back together.
???
Are you sure that's not something from previous config ?
For me /interface ethernet shows simply ... nothing.
The fact something shows for you is an indication it deviates from default config.
[xyz@L009] /interface/ethernet> export
# 2025-10-13 16:19:19 by RouterOS 7.20.1
# software id = N8ZH-846B
#
# model = L009UiGS
# serial number = <edit>
Anyone tried 7.20.1 in crashing (self-rebooting, kernel panic) machines like 3011 ?
After upgrading to RouterOS 7.20.1, I noticed abnormal VLAN behavior when using a bridge with vlan-filtering=yes.
On my setup (CCR2116), PPPoE discovery (PADI) frames started leaking between all VLANs configured on the same bridge — even though each VLAN was properly isolated. This caused multiple PPPoE connection attempts to appear in the log from the same MAC on different VLANs, showing messages like “connection from MAC already active”.
Downgrading back to 7.19 immediately resolved the issue: PADI frames stay within their correct VLAN and VLAN isolation works as expected again.
It seems to be a regression introduced in 7.20.1, possibly related to the new bridge hardware offload or fast-path VLAN filtering changes.
Hardware: CCR2116
Configuration affected: bridge with vlan-filtering=yes, multiple VLANs (11–16) on bridge, multiple PPPoE servers (one per VLAN).
Hopefully this can be reviewed and fixed in the next stable release.
2 Likes
There’s some problem with certificate / containers leading pulling from docker.io impossible.
I’ve seen those problem after downgrade from v721b2 (which also resulted in inability for container to run, so i’ve decided to simply repull them)
Personally i’ve fixed this with /certificate/settings/set builtin-trust-anchors=trusted but today I’ve seen other people with this problem (they trying to use containers for a first time)
supout provided as part of SUP-201086
From which version have you upgraded from?
Wireless issue on my wireless wire (60GHz p2p link) is still here - updated ticket SUP-200592 with new supout. Downgrading main node to 7.19.6 will probably mitigate the issue.
That’s because docker decided to go with Let’s Encrypt CA authority. Previously is was production.cloudflare.docker.com certificate. So, if you want to use SSL certifcate with container pulls. You need to use the builtin-trust-anchors or import them manually to your certificate store.
There was also a docker certificate with a large list of Subject Alt. Names which was revoked and no longer being renewed. I no longer have it since I deleted it.
IPsec still has some hiccups. ~once a day the router goes into a state where the tunnel constantly restarts phase2 negotiation. policy disable -> enable fixes it for some time.
running on an CCR2004-1G-12S+2XS
here the tunnel config
/ip ipsec mode-config
set [ find default=yes ] use-responder-dns=no
/ip ipsec profile
set [ find default=yes ] dh-group=modp8192 dpd-interval=2m \
dpd-maximum-failures=5 enc-algorithm=aes-256 hash-algorithm=sha256 \
lifetime=30m
add dh-group=ecp521 dpd-interval=1m dpd-maximum-failures=5 enc-algorithm=\
aes-256 hash-algorithm=sha512 name=secure-profile
/ip ipsec peer
add address=tunnel.endpoi.nt exchange-mode=ike2 name=tunnelendpoint \
profile=secure-profile
/ip ipsec proposal
set [ find default=yes ] disabled=yes
add auth-algorithms="" enc-algorithms=aes-256-gcm name=not_so_secure-proposal \
pfs-group=modp8192
/ip ipsec identity
add auth-method=digital-signature certificate=tunnel-cert-local match-by=\
certificate peer=tunnelendpoint remote-certificate=tunnel-cert-remote
/ip ipsec policy
set 0 disabled=yes dst-address=0.0.0.0/0 src-address=0.0.0.0/0
add comment=tunnel dst-address=10.0.0.0/16 peer=tunnelendpoint proposal=\
not_so_secure-proposal src-address=172.16.0.0/16 tunnel=yes
Had some similar symptoms with 7.20.0.
This shows the cpu load. starting at 20:00 it got into the looping state, in the morning a policy reset fixes it. For now…
1 Like
i am replacing a router with os7 between two os6 routers. Before i would just set 2 or 3 bridges up with ip address and use RIP to connect all the routers. I don’t want to mascaraed anything. How to I get the new os7 router connected in the network ?
Same here. Downgrade to 7.19.6 fixes it
1 Like
Hello i have this one —→ RB951G-2HnD
the upgrade process goes very well
but i think its a little ‘heavy’ cause of the hardware its old i am not complain
Also when i downgrade it i had to figure out a version of netinstall through a wireshark debug
and i notice a different message and data communication through different version of RouterOS and netinstall
xD
keep it in mind if need it for the future
anyway thanks
Hello, I have the following problem on a ccr1036 on many clients, it occurs on both 7.20 and 7.20.1, going back to 7.19.6 works correctly.
Oct/14/2025 09:58:47 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:47 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:48 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:48 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:48 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:48 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:48 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:48 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:48 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:48 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:49 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:49 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:49 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:49 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:49 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:49 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:49 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:49 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:50 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:50 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:50 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:50 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:50 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:50 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:50 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:50 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:51 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:51 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:51 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:51 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:51 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:51 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:51 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:51 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:52 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:52 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:52 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:52 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:52 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:52 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:52 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:52 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:53 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:53 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:53 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:53 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:53 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:53 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:53 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:53 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:54 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:54 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:54 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:54 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:54 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:54 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:54 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:54 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:55 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:55 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:55 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:55 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:55 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:55 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:55 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:55 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:56 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:56 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:56 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:56 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:56 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:56 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:56 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:56 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:57 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:57 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:57 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:57 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:57 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:57 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:57 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:57 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:58 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:58 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:58 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:58 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:58 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:58 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:58 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:58 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:58:59 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:58:59 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:58:59 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:58:59 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:58:59 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:58:59 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:58:59 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:58:59 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:59:00 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:59:00 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:59:00 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:59:00 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:59:00 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:59:00 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:59:00 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:59:00 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:59:01 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:59:01 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:59:01 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:59:01 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:59:01 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:59:01 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:59:01 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:59:01 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:59:02 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:59:02 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:59:02 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:59:02 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:59:02 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:59:02 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:59:02 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:59:02 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:59:03 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:59:03 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:59:03 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:59:03 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:59:03 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:59:03 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Oct/14/2025 09:59:03 pppoe,info PPPoE connection established from XX:XX:XX:42:95:23
Oct/14/2025 09:59:03 pppoe,info PPPoE connection from XX:XX:XX:42:95:23 was already active - closing previous one
Oct/14/2025 09:59:04 pppoe,info PPPoE connection established from XX:XX:XX:42:94:E5
Oct/14/2025 09:59:04 pppoe,info PPPoE connection from XX:XX:XX:42:94:E5 was already active - closing previous one
Oct/14/2025 09:59:04 pppoe,info PPPoE connection established from XX:XX:XX:DC:B0:BC
Oct/14/2025 09:59:04 pppoe,info PPPoE connection from XX:XX:XX:DC:B0:BC was already active - closing previous one
Oct/14/2025 09:59:04 pppoe,info PPPoE connection established from XX:XX:XX:98:6B:A4
Oct/14/2025 09:59:04 pppoe,info PPPoE connection from XX:XX:XX:98:6B:A4 was already active - closing previous one
Usually I use
ssh ROUTEROS < some_config.txt
to load or resume lots of configuration.
But in 7.20.x, it seems only can accept the first line , isn’t it? A bug or a new feather?
Here we go again. its actually two days, quite exactly. => SUP-201748
We have same problem and device, but with ROS 7.19.6. Do you see any significant RAM usage? Can you share your RAM graphs too?
Ram graph is dead flat @400m since forever.