v7.0beta8 [development] is released!

No problem - you might potentially be able to extend that script to pull the MAC for the logged in user by pulling the “Caller ID” for that username, and do a /tool fetch to a php page running on the radius server that could capture the mac address plus the lease given at that time and write it to the RADIUS database directly. It shouldn’t be too hard.

Obviously we shouldn’t have to do it, I was hoping for an official solution from MikroTik sooner and it has not appeared yet. However, as of yet we have not yet gotten a single abuse report for an IPv6 address, but I think that is only a matter of time.

Yes I agree with you mudcharme.

IPv6 is at the Implementation stage only so abuse report is still very low compared to IPv4. But Still the Norms and Regulations here force the ISP to collect all the Delegated and Remote Prefix in IPDR for Complaince purpose.

Hope Mikrotik Team will understand the difficulties and will do the needful at the earliest.

As i tested with other brand routers like CISCO, JUNIPER, HUWAAI and all are ready and working only this issue is seen in Mikrotik Routers from very long time.

I also observerd that many request have been done by many ISPs and WISPs in the forum but still it not answered propoerly by anyone yet.

I am also contacting Mikrotik Support for the same, hope something positive may come from their side… :sunglasses:

I understood that for such a feature request to have any impact, you need to go to your MikroTik distributor (where you buy the equipment) and ask them to submit a business case to MikroTik sales where they explain how much business they lose because this (or some other) feature is not available in RouterOS.
That is what counts. Not individuals making requests to MikroTik sales or even less here on the forum.
When the sales people at MikroTik notice they lose some big sales because a minor feature is not available, they will ask the developers to implement it.

When you go to MikroTik as an individual, you get the “nobody is ever asking for this” reply. Of course from a sales standpoint that can be explained, because you already bought your router and you notice a problem, and them fixing it is not going to bring them any money, maybe only some goodwill.
I noticed that before when asking for some IPv6 features, the reply usually is that “the customers do not ask for IPv6” so clearly I am not regarded a customer (as I am asking for it!), the distributors are the customers. Which they confirmed.

I work for a distributor and we have asked for this already last year.

Hi there,

Just wondering if anyone is successfully using BFD as a gateway check on a static route? I am assuming this can be configured as a standalone option (as in, does not require BGP or other protocols as well) but packet captures show no BFD packets are sent (RB1100). Packet captures shows BFD packets are arriving from the other end (Juniper MX960).

Cheers.

In RouterOS, BFD only works in combination with a routing protocol. The setup of BFD only defines parameters like the rate and the number of missed packets before the link is declared down, but the actual activation of BFD takes place in a routing protocol (BGP Peer or OSPF Interface).
The BFD traffic starts when the routing protocol has activated a peer, and the routing protocol is informed when BFD detects a dead peer.

For gateway checks, you can use PING or ARP as config items, or you can use Netwatch or make a custom scheduled script that performs whatever action you want.

You can set it, but functionality is not yet implemented. At the moment reliably you can use only PING check.

Thank you MRZ, I’ll keep an eye out for future releases.

Cheers.

Hi.
is there any chance for wireguard in new kernel ??

Hi Mikrotik Team,

Please add Vendar attribute for “Parnet Queue” so that we can define the parent queues value from radius auth request itself.

This will help so much for QOS

Thanks

Hi Mikrotik Team,
Please add the module ISG available at Cisco to the Mikrotik system
In our country, the regulations are such that traffic separation must be done. ISP Replace the Mikrotik router with Seiko. Please add module ISG Add

[quote=krankins post_id=805608 time=1594633670 user_id=166680]
I just wanted to say thank you very much for all your hard work.
[/quote]

+1

thx Mikrotik, very appreciated

in routing filter the is a bug!
i created two chain: in-v4 and out-v4

Going in templates, the two chain are allowed to be chossen by input.filter but not by out put filter
[admin@test-100G] /routing/bgp/template> set 0 input.filter=
in-v4 out-v4

If I force the chain by writing the name it is not executed by the filter:
[admin@test-100G] /routing/bgp/template> set 1 output.filter=“out-v4”
this doen’t do anything.

regards
Ros

in input.filter chain the rpki-verify is not working, infact in the following chain:

1 chain=in-v4 match-rpki=valid rpki-verify=validator action=accept

2 chain=in-v4 match-rpki=invalid rpki-verify=validator action=reject

3 chain=in-v4 action=accept

the first two rules are ignored. We don’t see any traffic from mikrotik to routinator except when routinator is added as a validator.

regards
Ros



Output requires selection rules:
/routing filter rule
add action=accept chain=xx
/routing filter select-rule
add chain=xx-select do-where=xx
/routing bgp template
set 0 output.filter=xx-select

For RPKI rules to match you need to specify against which group to verify, see example here:
https://help.mikrotik.com/docs/display/ROS/ROSv7+Basic+Routing+Examples#heading-RPKI

But RPKI still has a bug, that prefixes do not have correct state. It will be fixed in next beta.

New version 7.1beta1 has been released in development RouterOS channel:

http://forum.mikrotik.com/t/v7-1beta1-development-is-released/141516/1

Did I miss 7.0 release? %)

I guess we all miss it very much.

I Think We will get ROS v7.5 Stable :laughing: :laughing: :laughing: