It's wise for each person to test it as their configuration may be different. You can contact them at sari @ jsof-tech dot com to request the latest scripts.
The scripts only output text, so it wouldn't qualify as a report.
Thanks ChrisSimple solution:
Do not use the devices for testing (well, better: guessing) bandwidths. It's always a CPU bottleneck.
Get yourself two computers, connect them to the switches and run iPerf on them.
Afraid not. It seems that there aren't many people using the Mesh functionality but unfortunately it is a critical requirement to us. So we are just working around the issues at the moment.Just popped in for a similar post, same issue. Did you ever find a resolution?
Thank you floryluc! Very nice of you to post this here. I will definitely give it a bash.As I have seen that several of you are in the same problem, I decided to share it with the whole community
It would not be correct for me to speculate about how a feature works. It should be documented.did you make a test? what your result say?
Unfortunately one big supernet isn't really an option unless I want to risk cutting out a lot of potential Internet IPs.not three tunnels but three policies, or maybe you can "summarize" your 3 remote subnets into one bigger supernet
ppp - added output values for "info" command for finding the GSM base station's location ("LAC" and "IMSI");
Hi BartoszP, could you give a bit more info?A. Try to connect with MAC and check if refreshing works.
B. You need to clear session state of WinBox.
I am using v3.11.Try upgrading Winbox..
What's new in v3.8:
) support RouterOS v6.39;
) fixed problem when table header was hidden if filters were activated;
) after Log window was opened second time, updates were not displayed automatically;
I have filled that in. I am using SMTP elsewhere.Hi
You need to fill out your email settings in
Code: Select all
/tool e-mail set address=smtp.gmail.com from=<email@example.com> password=abc1234 port=587 start-tls=yes firstname.lastname@example.org
There are many other options of communication available. The LEDs, the speaker, the sms functionality, sending an email etc.but where would you see the output? there is no monitor port ...
I'll try that.Make a new logging action=file, then make a new logging rule with this action. after done debugging, delete it.
Mmm, that's probably the best suggestion yet.Is not it easier to use simple queues for these ip and watch traffic there?
Is that a possible solution, or a similar problem?Sounds like VLANs with IPs on bridges to me...
Most definitely! The current "implementation of brute force protection" is a joke. A counter on port visits as opposed to actually checking whether the login succeeds or not.It will be good if RouterOS will have integrated brute force protection and filter.