Have u fix bgp-path-len mrz?That does not qualify as "completely broken".
+1The rather skimpy content in the newsletter does suggest MT is working on software ;)
Testing is fun, but for production I would be much happier with some kind of long term supported ROS 7 release...
Dont hope too.much as they said, 99% problems caused by miss configuration.Not so fast, first there will be a release candidate.i got feeling that the stable version will come very very so0n
Advertise any prefix originately from the router itself.what do you want to achieve?anyone have problem with bgp filtering for local as?
regexp ^$ or bgp-path-len < 1 did not works
True word or gossip?It might actually happen sooner than you'd expect. Word is Mikrotik has recently brought on about 15 people, supposedly working full-time on developing business-oriented features.
*) route-filter - fixed the "blackhole" option setting process;Set blackhole yes on routing filter broken on 7.19.beta6
Last known work 7.18.2
Reported SUP-183157 with supout from both version.
Thx
+1 6vpe, 6pe hope they listen+1 to vpnv6 over IPv4.
We are still waiting for VPNv6 support over IPv4 infrastructure.
UpVPNv6 does indeed work, but only partially, as it does not support an IPv4 backbone as a transport layer.
UpCould you please share an example config with at least 4 devices RouterOS, being at least one on P.Router Only, with the v7.18rc ?LDP signaled VPLS works
BGP signaled VPLS works
VPNv6 works
either misconfiguration or very specific setup.
Hi mrz, any reason why MT still hide vpn6 afi from winbox?LDP signaled VPLS works
BGP signaled VPLS works
VPNv6 works
either misconfiguration or very specific setup.
-U- b 2001:db8::/48&65000:105 ::ffff:10.0.0.1 vpn6 200 40 30
Ub 2001:db8::/48&65000:105 ::ffff:10.0.0.1 vpn6 200 40 30viewtopic.php?p=1123531#p1123531
Flags: U - UNREACHABLE; b - BGP
Ub 2001:db8::/48&65000:105 ::ffff:10.0.0.1 vpn6 200 40 30
Which row contains "U"nreachable flag?
This is a important BGP bugs, it s not a new feature, its a bug, i dont think we need to wait new major version to fix this.waiting for this
viewtopic.php?t=213301
that kind of problem in MPLS/VPLS happen since v6 anywaySpeaking about MPLS / VPLS, did someone try to see if the last versions are still losing packets on CCR2216? As far as I know, it is still an unresolved issue.
Agree, we are hoping years to get MT v7 stable , the hardware seem promising thoughWould not make sense to me. Winbox 4 is early beta and that should not be any priority for any stable ROS version right now.polish behavior with new Winbox 4, but - who knows...
Not too fast, rc2 still have bugs with cpu 100%Final release without an RC to check if memory leak was corrected?Quite some time passed since rc2. I can smell final release already...😂
Sounds like a bad choice.
Sounds like 7.15.1 will be launched before we would like.
Hi normis,Check debug logs, see what is the error
So could u tech me or maybe us how?You will have to understand that v7 bgp is different from v6 bgp, many commands are different and some things are no longer there.
This command missing in v7 /routing/bgp/advertisements printmay you explain the issue you experience about bgp advertisement?When you will fix bgp advertisement?
Thx
I have just a delay in advertisement, delay that icrease over time.
i tried to enable disable that line, result is the same.Check line 50 in the PE-5-V7.rsc
Are you certain, you want that disabled?
I have tested,Check v7.9beta4
Let we see together what he s promised in 7.9We are working of BFD support.
From brief look over reported BGP issues in the this topic, they should be polished and fixed in 7.9.
pe1chl, do you have any issue with BGP in 7.8?
Can u explain more exactly what you have fixed for bpg vpn4?It is already fixed in v7.7 and v7.8betas
BGP cosmetic progress onlystill no progress on VPNV4 and BFD :-(
When will you fix this BGP issue?BGP VRF MPLS L3 (PE-CE) in v7.6 beta7
still having problem with routing propagation.
route sent from PE did not propagate correctly to Other PE's, missing AS-PATH
capture-7.6beta7.jpg
thx
This problem still exist in 7.6beta8BGP VRF MPLS L3 (PE-CE) in v7.6 beta7
still having problem with routing propagation.
route sent from PE did not propagate correctly to Other PE's, missing AS-PATH
capture-7.6beta7.jpg
thx
And it will be a new router series will released CCR3xxxxWith recent release numbering scheme, I wonder if there is enough numbers left to get stable before we get to 8.0 ;-)
Hi,BGP vrf problem is acknowledged and will be fixed in one of the next versions.
unfortunately v7 is not beta anymore, and still not all BGP feature are worksI think the BGP daemon was written from scratch... before new features are added, let's first make the existing features working to the level of RouterOS v6.
You made a good decision.I wanted to update all my routers, because MT said it is stable. I was in the middle of another project, so I didn’t have time. I’m glad I didn’t update.
Any status for MPLS L3?Soon
have u simulate vrf / L3 vpn on your mpls? BGP vpn4My RouterOS v7 test lab consists of 3x RB3011.Rb3011 uias-rm
after 23h, it is frozen
They are all happily running with OSPF + LDP with no lockups or reboots.
agree, make stable and release it.I'm a bit disappointed, would like to see more focus on stability and features that not in V7 but are available in V6 instead of brand new features.
up, still brokenSystem - auto-upgrade broken since 6.46.1 please fix it.
thx
still waiting, hope can fix soon in v6One problem with both protocols? Are you sure?the problem with BGP and OSPF?![]()
not yetA lot of days without New firmware... Is It a Ros 7 signal?
it's now march 2019 and still no news regarding v7, poor mikrotik support, so many people hope with ros 7 years.I only want Ros v7 o New full firm arm!!
This is the first question from this thread in 2015.Hi,
When RouterOS v7 beta1 is gonna to be released?
true endeedAfter these years, I do not expect any serious answers to come from the Mikrotik. .... Ubiquity is much more flexible in communication ... another region, another morality