Community discussions

MUM Europe 2020

Search found 27 matches: netwatch

Searched query: netwatch

by strods
Thu May 31, 2018 9:49 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Everyone who complained about the Netwatch issue - Please see this topic viewtopic.php?f=2&t=134538
by mt99
Tue May 15, 2018 2:07 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Ive been testing 43RC11.. It addressed a huge number of issues posted in this thread. Good job Mikrotik.

It does not address the short sighted feature neutering of Netwatch tho. I still cannot send a alert or change a LED state based on a ping of a target. Because I use Netwatch for many things, I still cant use firmware past 41.5 because of this.

While im really impressed all the other bugs introduced in 42 have been so quickly addressed, I am upset Netwatch has not been addressed.
Mikrotik at the very least needs to explain what is and what isn't supported after 6.42 in their Netwatch documentation. It's not that much to ask. I got the sense that calling a script which requires certain permissions doesn't work anymore. But if you put the entire script in the Netwatch code block instead of simply calling the script, does that work? I haven't upgraded from 6.41.4 so haven't tested this. Apologies if you've already given this a try.
by Xymox
Mon May 14, 2018 9:12 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Ive been testing 43RC11.. It addressed a huge number of issues posted in this thread. Good job Mikrotik.

It does not address the short sighted feature neutering of Netwatch tho. I still cannot send a alert or change a LED state based on a ping of a target. Because I use Netwatch for many things, I still cant use firmware past 41.5 because of this.

While im really impressed all the other bugs introduced in 42 have been so quickly addressed, I am upset Netwatch has not been addressed.
by Xymox
Fri May 04, 2018 7:00 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

There may be better ways then Netwatch, but, Netwatch worked great for him and Mikrotik deprecated the functionality. I use it to send me alerts via email, is there a better way to do this ?
So the DHCP issue will be addressed in the next RC as per support's replies.
Just curious, how this issue was introduced?
Im curious how all these really varied issues were introduced, DHCP is just one of them. But YEA this DHCP one is really curious. Why would the DHCP code be played with for this stable version release ?
by pe1chl
Fri May 04, 2018 12:40 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

There are better ways to do that than with Netwatch and scripts...
by dsnyder
Thu May 03, 2018 11:51 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

You can add another unhappy customer to the Netwatch limitations. I was calling a script to failover to a secondary internet connection and disable/enable policies and rules for VPNs for the alternate IP address. This morning the primary internet went at an office and they went dead, no failover. So now I have to explain that this fancy contraption that I sold them really does work, just not this one time because they changed the way it works...
by macsrwe
Wed May 02, 2018 11:07 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

What issues will be addressed ? WIll Netwatch be put back ?
Netwatch is available as always. What has been removed is the capability of Netwatch to call scripts that perform actions that require write permission.
I use Netwatch with scripts that do only a /log action and it still works.
I've run into an issue with the newest releases where the scheduler will not invoke a script if given only its name, but will invoke it if given a full command line of /system script run... I'm still working this issue with support.

I've never used netwatch with a script (just with single command lines), so bear with me if I'm off-target, but is it possible you're running into the same bug? If you have specified only the name of the script, have you tried substituting the full "run" command line? If that doesn't work, have you tried invoking an intermediate script that doesn't require write, and having that script invoke the full command line to run the other script that does? (I think that currently does an end-run around the permission chain, as long as the use actually HAS that permission himself.)

Hope one of these suggestions works for you.
by pe1chl
Wed May 02, 2018 10:59 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

What issues will be addressed ? WIll Netwatch be put back ?
Netwatch is available as always. What has been removed is the capability of Netwatch to call scripts that perform actions that require write permission.
I use Netwatch with scripts that do only a /log action and it still works.
by dasvos
Wed May 02, 2018 10:03 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

So the next RC is what will address the long list of issues discussed in this thread ? So no security patched 41.4 ? What issues will be addressed ? WIll Netwatch be put back ? When is the scheduled next RC going to be released ? Does 42.1 stay as the current stable ? Or does it get withdrawn ?
Have you sent emails to support@mikrotik.com to report the issues you have picked up?
by Xymox
Wed May 02, 2018 8:32 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

So the next RC is what will address the long list of issues discussed in this thread ? So no security patched 41.4 ? What issues will be addressed ? WIll Netwatch be put back ? When is the scheduled next RC going to be released ? Does 42.1 stay as the current stable ? Or does it get withdrawn ?
by Xymox
Mon Apr 30, 2018 7:33 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

After having given up on 42.1 for all my clients and moved back to 41.4 I have decided to try out the RC. 43.5.. As Mikrotik has not responded to any of the issues listed in this thread that i know of, I think we might want to assume 42.1 is dead and that the next step will be 43.x ... So I suggest if you can you give that a test and see if that helps or ressolves any of the issues in 42.1..

I moved my home router, a CCR1009 over to 43.5.. As expected Netwatch is still dead and the LED On script command does not work. But I dont seem to be having any immd issues with a simple home router setup. Its been up for 3 days and seems to be doing OK so far in my limited home use.. NAT, some firewall rules, DHCP client and server. NTP client and server.. All that seems to be working OK.

So that was a upgrade from 41.4 to RC43.5 and everything seemed to move over well. BUT, its a very limited SOHO use.
by Xymox
Sat Apr 28, 2018 11:45 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

This has cost a lot of people time and money..

BUT.. We should all step back and think about how stable RouterOS has been for many years. For me its like 10 years of very stable and very reliable operation. So in my mind, its OK to have a accidental mess like this. Its just fine as long as they work hard to fix it very quickly. Its also important to step forward and admit the mistake and provide a plan on what they are going to do to fix the issue.

Why did they cripple Netwatch ? This needs to be put back in any fix they are working on now. It was crazy to remove this.

My 2 cents on what should happen.. Take 41.4 and apply a security patch for this new issue. Turn that into stable release 44.0.. Push that out right away.. Make RC 43.x into 45.1 and FIX IT. Then release 45 once its at like RC45.30 and all these issues are worked out...
by Xymox
Sat Apr 28, 2018 11:09 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Ive got 2 older routers I can't downgrade. There is not enough disc space. 42.1 seems to have taken up so much space I cant transfer firmware in. I will have to go on site and Netinstall them.. Thats annoying.. Both are RB1000AHx2

Looking thru the thread,, jeeze,, I think this "stable" 42.1 broke, well, everything. It even broke UPnP.. Killed off Netwatch... Caused DHCP to not work.. Everyday there is a new post here about something completly different that is broken..

Also, so far, there are no official Mikrotik posts about this faceplant and what they are going to do about it.

Ive never seen a RC this bad,, and this is a STABLE release... What a mess...

I am happy tho on 41.4.. Ive disabled everything but WInbox and put that on a random port and restricted it LAN side use only. So I guess im mostly safe from the security issue..
by Xymox
Sat Apr 28, 2018 10:58 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

@Xymox
Ive spent the morning downgrading all my clients from 6.42.1 to 6.41.4.. Over the last few days ive seen a number of weird things on client systems that are previously reported on this thread. I do not consider 42.1 "stable"... The other BIG deciding factor to revert to 41.4 is Netwatch.

Should you be using Release (Current) branch instead of Bugfix (Stable) branch for business of any kind?
When the Release (Current) branch has the exploit patch available, and the Bugfix (Stable) branch still does not... sometimes you do. But never again, my friend.
I have only been using stable. 42.x is not stable. 41.x is stable but not secure now. 43.x does not have Netwatch or a fixed LED ON script command.

I made sure the routers are not available to the outside world, so the security issue should not effect me.

I now wait for a solution to the debacle.
by macsrwe
Sat Apr 28, 2018 8:15 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

@Xymox
Ive spent the morning downgrading all my clients from 6.42.1 to 6.41.4.. Over the last few days ive seen a number of weird things on client systems that are previously reported on this thread. I do not consider 42.1 "stable"... The other BIG deciding factor to revert to 41.4 is Netwatch.

Should you be using Release (Current) branch instead of Bugfix (Stable) branch for business of any kind?
When the Release (Current) branch has the exploit patch available, and the Bugfix (Stable) branch still does not... sometimes you do. But never again, my friend.
by coylh
Fri Apr 27, 2018 7:29 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

It looks like netwatch is in the advanced-tools package.
by squeeze
Fri Apr 27, 2018 7:10 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

@Xymox
Ive spent the morning downgrading all my clients from 6.42.1 to 6.41.4.. Over the last few days ive seen a number of weird things on client systems that are previously reported on this thread. I do not consider 42.1 "stable"... The other BIG deciding factor to revert to 41.4 is Netwatch.

Should you be using Release (Current) branch instead of Bugfix (Stable) branch for business of any kind?
by Xymox
Thu Apr 26, 2018 8:03 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Ive spent the morning downgrading all my clients from 6.42.1 to 6.41.4.. Over the last few days ive seen a number of weird things on client systems that are previously reported on this thread. I do not consider 42.1 "stable"... The other BIG deciding factor to revert to 41.4 is Netwatch. I use this extensively to monitor lots of gear on the clinet network and send email alerts & update DDNS or take other network actions. As Mikrotik decided to take away Netwatch without any reason or notice I have been forced back to a insecure version of RouterOS. I also use the on/off functions of the LED controls to control a relay that I can do various things with like power cycle the modem. As ON does not work from command line or scripting I also need to roll back. bugs and issues.

Ive been doing Mikrotik a LONG time, back when they only had PC boards, and ive never seen a stable release this riddled with bugs and issues like 42.1 is. I would hope Mikrotik is working very hard to correct this issue. Its cost me a bunch of time and money.
by coylh
Wed Apr 25, 2018 10:01 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

I'm seeing two things:

1. ssh keys are being regenerated as part of the upgrade.
2. Looks like netwatch is gone. Was this planned, or part of vulnerability mitigation?
by Xymox
Wed Apr 25, 2018 5:23 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

I assume someone is keeping track of this epic list of serious faults with a production "stable" release ?

Does Mikrotik have any bug tracker web URL ?

I have a suggestion, apply the security patch to 6.41.3 and lets roll back to 6.41 and skip 6.42.. There are really serious issues covered and confined in this thread, its time to take a serious stand and get things fixed.

Ive been doing Mikrotik a LONG time and ive never seen a mess like this. Normally even the Release Candidates are way more stable then this.

Im also really unhappy they took away the ability to use netwatch to monitor things and send a email alert.. This loss of functionality is honestly unfathomable. I want a official response here on the forum please.
by Xymox
Wed Apr 25, 2018 7:49 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

This change to Netwatch MUST BE REVERSED... Im REAALY UNHAPPY... I use this for a great many things. This change in what it can run seems, well, STUPID and POORLY THOUGHT OUT.. Mikrotik can't just take away features like that.

I cant even imagine a reason to do that.

Put this back ASAP or im gonna be REALLY VOCAL about this.

If your going to take away this big a feature that has been present in RouterOS for so many years at least provide a rationale for implimenting such a devastating reduction in functionality.
by Xymox
Wed Apr 25, 2018 4:59 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

I wanted to follow up... Yes my Netwatch is not working.. This is really annoying as its sets up my DDNS. we need a 42.2 that fixes this..

Im not sure what happened last night, but, somehow none of my scripts would run from scheduler. I could run them manually. Its like scheduler somehow was not running, or did not have permissions to run scripts.. I always use 2 partitions and flipped back to 41.3 and all was well. Netwatch also worked of course.

I copied over 41.3, overwriting the 42.1.. Then switched to that.. All was well.. Then upgraded 41.3 to 42.1.. I lost Netwatch but gained back scheduler.

Ive gained a even weirder issue... I cant get around this...

/system leds> add leds=user-led type=on
input does not match any value of type

I can do off,,, but not on.. It seems to have lost on...
by mt99
Wed Apr 25, 2018 3:24 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Just updated one of our Metal G-52SHPacn to new v6.42.1 RouterOS.

tools/netwatch does not work anymore. When the tested server is "up", we run [:global srvstat "up"] to set the variable srvstat. Did work with 6.41.2
Looks like up event is not working.
Version 6.42 has this changelog entry:
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
I guess that breaks your use case.
Yes, netwatch is no longer usable to start scripts. Even to write to global variables fails. Only write to .txt files works. On up event, I need to write the server status up to a variable or file and start a script.

Still did not find a solution for that use. A high interval schedule is no option.
I haven't installed 6.42.x yet but I use Netwatch to run scripts on all my devices. I use local variables in these scripts, will they no longer work after this update?
by Xymox
Tue Apr 24, 2018 5:34 pm
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Yea thats repeatable for me..

I take 6.41.3 in a partition and that works great.. Update it to 6.41.1 and the scheduler stops.. It might also be that Netwatch triggered scripts stopped too..
by heydude
Tue Apr 24, 2018 11:24 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Just updated one of our Metal G-52SHPacn to new v6.42.1 RouterOS.

tools/netwatch does not work anymore. When the tested server is "up", we run [:global srvstat "up"] to set the variable srvstat. Did work with 6.41.2
Looks like up event is not working.
Version 6.42 has this changelog entry:
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
I guess that breaks your use case.
Yes, netwatch is no longer usable to start scripts. Even to write to global variables fails. Only write to .txt files works. On up event, I need to write the server status up to a variable or file and start a script.

Still did not find a solution for that use. A high interval schedule is no option.
by eworm
Tue Apr 24, 2018 10:33 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Just updated one of our Metal G-52SHPacn to new v6.42.1 RouterOS.

tools/netwatch does not work anymore. When the tested server is "up", we run [:global srvstat "up"] to set the variable srvstat. Did work with 6.41.2
Looks like up event is not working.
Version 6.42 has this changelog entry:
*) netwatch - limit to read, write, test and reboot policies for Netwatch script execution;
I guess that breaks your use case.
by heydude
Tue Apr 24, 2018 10:28 am
Forum: Announcements
Topic: v6.42.1 [current]
Replies: 272
Views: 48859

Re: v6.42.1 [current]

Just updated one of our Metal G-52SHPacn to new v6.42.1 RouterOS.

tools/netwatch does not work anymore. When the tested server is "up", we run [:global srvstat "up"] to set the variable srvstat. Did work with 6.41.2
Looks like up event is not working.