anyone tried configuring BGP in ROS7.1beta2 I would love to see some examples ![]()
There is a full example in the doc https://help.mikrotik.com/docs/display/ROS/ROSv7+Basic+Routing+Examples#ROSv7BasicRoutingExamples-BGPConfiguration
yes me too especially with filters. Also it’s been 2 months since last beta release.
Thanks just want i needed ![]()
Fasttrack doesn’t work for me in 7.1beta2 on Chateau. It’s shown as active in IP Settings, but counters there and in dummy rules in Firewall are all zeros.
Config is pretty basic and fasttrack works with the same config in 7.1beta1.
Edit: Also doesn’t work with default config in 7.1beta2 and works in 7.1beta1.

I am seeing the same behaviour on 7.1beta2, the fasttrack counters are indeed not working.
We are also experiencing unstable WiFi in version 7.1beta2 on a RBD53G-5HacD2HnD, clients are not able to receive a DHCP offer on 2G, not sure if 5G is affected though.
It seems wi-fi issue has been fixed in 7.1beta3. Running it for a week without any issues.
PS: not yet available for everyone.
It seems wi-fi issue has been fixed in 7.1beta3. Running it for a week without any issues.
PS: not yet available for everyone.
We still wait for it bcs ppl have two other big problems:
- LTE is slow (30mb instead 140Mbps at the same CellLock 1band)
LTE b7+b7 does not work Chateau 12 - remote SIP not register
Chateau LTE12, No VoIP with RouterOS v7.0beta7 or beta8, works with beta5 and beta6
Both work’s properly in ros7beta5
It seems wi-fi issue has been fixed in 7.1beta3. Running it for a week without any issues.
PS: not yet available for everyone.
Beta 3? How did you get it?
Hi,
In v7.1beta2 I can’t manage to import a private SSH key which is password-protected :
[admin@MikroTik] > /user ssh-keys private import user=admin private-key-file=test.key
passphrase: *******
unable to load key file (incorrect passphrase?) !
Of course no issue at all on v6.x with the exact same key.
Is there a known issue MikroTik support ?
Thank you !
3 months yet next beta is not yet released! waiting for next release that would mitigate the wifi dhcp lease issue on hap ac2
just because already chocolate-santa’s awaiting you in the local supermarket, it doesn’t mean christmas eve has broken !
… maybe it’s a little bit about timing ?! guess your impatient question shows mom and dad they’re do’in fine : )
Hey,
is there anyone who owns a Chateau LTE12 and is able to use LTE mode only?
Currently I’m able to connect to internet only using 3G mode.
I’m in contact via Mikrotik support and I’d like to know if someone else is experiencing the same problem.
matlib
Modem is very unstable and connection after a while drops.
.
I’m in contact via Mikrotik support and I’d like to know if someone else is experiencing the same problem.
And that’s why you write here instead of creating new thread, sorry but this is not a place to speak about APN AT Commands and Log’s changes in LTE.
Hey,
is there anyone who owns a Chateau LTE12 and is able to use LTE mode only?
Currently I’m able to connect to internet only using 3G mode.
I’m in contact via Mikrotik support and I’d like to know if someone else is experiencing the same problem.
Here i am! I always use LTE mode only on Chateau LTE12 (and before on WAP LTE and LHG LTE too). It works well with all 3CA combination (provider 3 Italy, now Wind3)
3 months yet next beta is not yet released! waiting for next release that would mitigate the wifi dhcp lease issue on hap ac2
It appears they again went “under water” with the v7 beta. There is mention of a 7.1beta3 that apparently some people have, and which is mentioned in the feature completeness table on the help site, but which has not been released to the public.
It is a bit unfortunate, because I really would like to test some things and could do so on some routers, but the 7.1beta2 is not good enough for that.
Currently we are having issues with beta3 booting on TILE architecture. Beta3 will be available when we get these issues sorted out.
It would be welcome when you release new v7 betas quickly even if they are only for single architecture, e.g. only for CHR.
That at least enables some testing and evaluation. Getting them to work on all devices is something that can trail after that.
Yes. Don’t block the release just because one platform can’t boot. It’s still in BETA stage so such things can be expected to happen. Release it so new features can be tested and debugged while you are working on the TILE to boot again.