It's strange, isn't it? The Marvell ASICs that MikroTik uses supports MPLS/VXLAN/EVPN in hardware, but MikroTik decided it was a terrible idea to support these three on the ASICs.There is no hardware MPLS support in RouterOS v7 at this point.
Why? NAT-PMP was already obsoleted by RFC6887. It would've made more sense to implement PCP, which is also usable in 464xlat, NAT64 and MAP-T.*) firewall - added "nat-pmp" support;
Disagree. We route to blackhole even on expensive high-end Juniper MXes and PTXes.I think it is a mistake to apply techniques developed for business-on-budget applications to prosumer cases which my firewall is for.
viewtopic.php?t=176358#p864371I actually disabled all the other rules as well. Is there a base ruleset I should be using? The implicit drop at the bottom is disabled as well.
Works fine on v7.11.2. No problems here for months/weeks now. Even cross-vendor.When is really ready and works...Or even better, BFD. It was made for this purpose.
How small is the market for this? What are some modern-day use-cases for it in carrier networks? I just can't think of any because of EVPN.MPLS-TP is not legacy, but its a niche market.
What's the market share of MPLS-TP anyway? I have not seen it in production.MPLS-TP is a very different concept. It often requires and specialized hardware and provisioning concepts to make any sense of it.
is-is is not TCP/IP, it's CLNP. Why would it require IPv4 or IPv6 addressing to function?If I have to wait to 7.14, 7.16 for a IPv4 is-is implementation.
What you should be doing is exporting your /routing config and post it here for people to review.If you could give me a BGP session configuration that would 100% announce the default route correctly in a routing table already filled with several million routes, I'd love it.
Don't confuse ROA data and ROV data. Even if ROA data is 100% compliance, it is useless if there's no ROV implementation.there is journey remaining towards full ROA compliance
Nothing personal, at all, from my POV. Strictly business here. And as far as “technical message”, that's what MANRS is for.i am pretty sure there is a way to give the technical message without going into personal affairs
Exactly. I don't know how to properly align the antennas on hAP ax3, MikroTik made sure to keep this a secret for reasons I cannot understand.And for hAP ax³, why would sticks rotate around second axis, if it's doughnut shape?
Translation = I don't need praise from people in this forum. Money doesn't reach my bank account from here. Some people have appreciated my comments in this forum, some have not, doesn't matter to me either way.Translation = F*** I'm Good, Just Ask Me !
You are not supposed to be using multiple bridges, read this:The IGMP/MLD snooping can be set only for ports on the same bridge, which it doesn't seem to be my case.
Fair argument. MikroTik can sell reasonably priced support agreement. 1/2 the price of Cisco or Juniper.On the other hand - you really can't buy a Nexus or QFX without a pricey support agreement (except for second hand)
Many people are willing to pay that cost, though, is the point. A MikroTik box won't cost me $400k.Some of these would come for free as they can be done in software on the existing hardware, but others such as a larger TCAM come at a cost.
I'm no expert, I'm just educated and literate is all.Mate, some could find you not only an expert in networking but also in arrogance ... could you stay at networking?
Good luck, have fun.work like a charm with BGP![]()
Are you sure you're an engineer, mate? This fundamental stuff in MikroTik.Hmmmm.... firmware to 1:1 between peers or current-firmware: upgrade-firmware ?
/system routerboard settings
set auto-upgrade=yes
/system/routerboard> print
routerboard: yes
factory-firmware: 6.45.9
current-firmware: 7.11.2
upgrade-firmware: 7.11.2
/system ntp client
set enabled=yes
/system ntp client servers
add address=time.cloudflare.com
This is an anti-innovation mindset, usually smells of USSR and fascist regimes' origin.If ain't broke, don't fix it.
Yeah keep telling yourself that, good luck, have fun.Nobody actually requires XDP or DPDK or VPP or any other acronym.
If the big vendors don't have it, you can't really expect MikroTik to have it, on priority. Not going to happen anytime soon.Not that I'm aware of.
I don't think it's worth anybody's time, we should all just move to native IPv6 and get it over with.I was hoping he was going to tackle endpoint NAT next.![]()
if (dst==0.0.0.0/0) {accept} else {reject}
Ah that's typo lol, I edited the comment.If RouterOS did at all what you claim, that would produce a bad configuration
Theory, yes. What about practice? Did someone's grandson go to jail for increasing Wi-Fi power output using hAP ax3?Belgium
Italy
2 examples right out of my head.
For Belgium, check site of bipt.be (and it's even in English !!)
Lol, what did you expect from MikroTik software quality assurance team? Of course there's kernel failure.When using Endpoint-Independent NAT currently, there is a kernel failure after creating a large number of UDP connections.
Please share your testing methodology with us that confirms ANY external IP can reach. And why isn't TCP also supported?In my test any external IP address can reach the port, I haven't used that testing tool, just directly opened connections.
It's broken, it's not full-cone, it's port restricted cone with EIM.Thank you for bringing Endpoint-Independent NAT through RouterOS 7.10.
It allows game consoles to support Full Cone NAT through simple configuration.