Yup, matching hello timers between LDP and OSPF generally keeps the IPv4/IPv6 routing tables and MPLS forwarding tables in synch since they'll both clear at the same time if there is a neighbor down or a flap. In Cisco/Juniper/etc there is a protocol for this call LDP/IGP synch but setting the time...

MPLS is definitely not stable as of 7.17 as I posted earlier. Again I suspect its LDP specifically that is the problem and not MPLS itself. Are your IGP/LDP timers matched? The behavior you described could occur even in ROSv6 and setting the LDP/IGP timers to match - especially the hello timer was ...

I don't want to bother you in this thread, but wouldn't it be better to find the safe-mode active by default (maybe it can be disabled with an option when launching winbox) and ask for confirmation of the changes when exiting winbox? I would love to see a preference in winbox to enable safe mode by...

This bug has been around as long as ROS7 has been a thing. I don't see it getting fixed anytime soon.

Maybe one day in a future release.

Right, I never realized that the options were unrelated, even if in the same context, because I never needed it.


**********


And it's a good thing you wrote it because I didn't remember that note... from 2007...

It's quite misleading, especially with the options next to each other in winbox.

Google has been locking this down. Your easiest approach is setting up an app password.

https://wpmailsmtp.com/gmail-less-secure-apps/

I am facing exactly the same issue with RB4011 and 7.17.2, with ports 1 to 5 failing. The problem is fixed temporary with a router reboot. Since I can see the problem has been arround since many versions, is there any workarround? I utilize a ping watchdog to auto reboot the router when this happen...

It would be very useful to have this functionality. We have ping watchdogs setup on our routers to reboot in case of upstream failure. The 4011's currently have an unresolved bug causing port groups (1-5 or 6-10) to lockup randomly, and the ping watchdog eliminates a truck roll. But I feel like havi...

Saw this is the 7.19 beta changelog, and was reminded of this post.

*) bridge - added new STP monitoring fields for bridge and ports (Tx/Rx BPDU, Tx/Rx TC, forward/discard transitions, last topology change, message-age, max-age, remaining-hops, bridge-id);

MPLS Traffic Eng Tunnel Path is still broken in winbox / webui;

Any real world experience with the VPLS fastpath?

Wondering how much CPU improvements are realized on CCR2xxx devices.

Perhaps instead of the dropdown menus, tabs with ctrl+click or shift+click to open in a new window just like most browsers?

Yes, we use these in the 2116

It seems MPLS TE paths have issues in ros7 still? I can create a path from cli, and it works fine, however the path does not display in winbox. Conversely, if I create a path in winbox, it does not work, and export from the cli is broken. See here: KND-PVST-Primary made in CLI, KND-PVST-Pri made in ...

yes L1 is good. also some of the bgp peers that drop are on a separate port and dedicated fiber outside of the ospf L1 the problem happen when a paloalto or fortigate firewall with ospf to the ccr's fail over between the active and the passive firewall device. but fortigate ospf (and unrelated glob...

Downgraded ros to 7.8 with no change. I had to completely disable HW Offload on every bridge port to clear up the issues. May try upgrading to 7.10 again to see if it stays stable with offload disabled.

Downgrade to 7.8 on it's own made no difference. Disabling HW offload on all active bridge ports made the difference though.

Same switch, similar issues here. What FW version? I'm on 7.10. Thinking of reverting

A couple issues 1) CCR2004-16F-2S+PC, "export" fails for me. Seemingly related to the bridge config. Other areas export successfully. [admin@MikroTik] /interface/bridge> export # 2023-06-20 06:33:15 by RouterOS 7.10 # software id = 1839-P0T5 # # model = CCR2004-16G-2S+ # serial number = HD...

Who is your ISP? They are definitely not using that IP space correctly seeing as 100.0.0.0/12 is Verizon public IP space.

Have you reached out to them with this fact?

We ran in to an issue today after replacing a CCR1009 with this CCR2004 in order to add SFP+ ports. A while after replacement, downstream users started having odd issues. We quickly found that it was an MTU issue with our MPLS network. The largest ping we could fit was 1450bytes. After pulling some ...

Seem to be having an auto negotiation issue with SwOS on a CRS312. I am using a FS.com 10G 1310 SFP+ modules and connecting to another ISP via a ETX-220A with matching 10Gb optics. If I set the link to 1G I see "link on" but my carrier still sees it as down. If I set the link to auto negot...

Did you ever resolve this? I had a similar issue and I resolved it by disabling flow control.