While the script is marked as down it does poll every interval set. The issue here is that the ping is not getting to your host. Maybe Butch's suggestion is why you're unable to? Do you know of another reason why you can't get to that host?
Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 Those who don't understand UNIX are condemned to reinvent it, poorly. --- Henry Spencer On Thu, Oct 2, 2008 at 8:51 PM, Randall Roberts <[EMAIL PROTECTED]>wrote: > Once the netwatch runs the down script and toggles to the other interface, > if it is also down, the status stays at 'down' -- it never goes back to up, > so the script doesn't run again to toggle interface again. > > The ip-address of the bridge is set to the bridge1 interface. > > Randall > > > ----- Original Message ----- > From: "Josh Luthman" <[EMAIL PROTECTED]> > To: "Mikrotik discussions" <mikrotik@mail.butchevans.com> > Sent: Thursday, October 02, 2008 7:45 PM > Subject: Re: [Mikrotik] Script help -- First Problem > > > > I'm not really seeing a problem in your description... > > > > The UP tab should be the script that makes the route in question use the > > primary interface/connection. The DOWN tab should be the script that > > makes > > the route go to the secondary interface/connection. > > > > What I have had a lot myself is forgetting to force the host being pinged > > out of the primary interface - double check your route on this. > > > > Josh Luthman > > Office: 937-552-2340 > > Direct: 937-552-2343 > > 1100 Wayne St > > Suite 1337 > > Troy, OH 45373 > > > > Those who don't understand UNIX are condemned to reinvent it, poorly. > > --- Henry Spencer > > > > > > On Thu, Oct 2, 2008 at 8:33 PM, Randall Roberts > > <[EMAIL PROTECTED]>wrote: > > > >> Only problem I've found is - if the second interface is really down also > >> when it switches to it, then it will stay there, even if the first > >> interface > >> comes back up. > >> If there's someway to reset the status, maybe disable the netwatch rule, > >> then re-enable it, to cause it to start pinging, and after failure > switch > >> again. > >> > >> Any ideas? > >> > >> Thanks, > >> Randall > >> > >> ----- Original Message ----- > >> From: "Sam Tetherow" <[EMAIL PROTECTED]> > >> To: "Mikrotik discussions" <mikrotik@mail.butchevans.com> > >> Sent: Thursday, October 02, 2008 5:34 PM > >> Subject: Re: [Mikrotik] Script help > >> > >> > >> > /tool netwatch is probably what you want. I have not done this type > of > >> > thing, but I did use it when testing some VRRP stuff > >> > > >> > /tool netwatch add host=HOST_TO_PING interval=10s \ > >> > down-script="/interface ethernet;set ON disabled=yes name=DOWN;set OFF > >> > disabled=no name=ON;set DOWN name=OFF" > >> > > >> > Not sure if it is a good idea, but that should at least get you > started > >> > down the road of mysterious network changes in the middle of the night > >> > ;) > >> > > >> > Sam Tetherow > >> > Sandhills Wireless > >> > > >> > Randall Roberts wrote: > >> >> Pardon my lack of scripting .... > >> >> > >> >> I have several towers with multiple backhauls, all on a bridged > >> >> network. > >> >> So I have to keep the SSID changed on the backup backhaul to prevent > >> >> an > >> >> ethernet loop. Sometimes we don't catch problems fast enough. > >> >> > >> >> (Yes, I have a major link using OSPF, but this is on a large bridged > >> >> network with a subnet spread out and can't be changed easily.) > >> >> > >> >> My thought was to put a RB532 or faster 3 ethernet board at a tower > >> >> with > >> >> the ether ports in a bridge- > >> >> Ether1 (to network switch) > >> >> ON (was ether2) disable = no (to main backhaul) > >> >> OFF (was ether3) disable =yes (to backup backhaul) > >> >> > >> >> The script could ping an IP on the other end of backhauls. If it > >> >> fails, > >> >> do this > >> >> find interface disabled and rename "ON" > >> >> find interface enabled and rename "OFF" > >> >> find interface 'ON' and enable it > >> >> find interface "OFF" and disable it. > >> >> > >> >> Might have to have a timer to keep it from switching back before > pings > >> >> start going through > >> >> Might add a email to let us know it did it. > >> >> > >> >> I don't have a clue to thos if's etc in scripting!! > >> >> > >> >> Also, if this idea is bad, please feel free to tell me!!! > >> >> > >> >> Thanks in advance, > >> >> Randall > >> >> -------------- next part -------------- > >> >> An HTML attachment was scrubbed... > >> >> URL: > >> >> > >> > http://www.butchevans.com/pipermail/mikrotik/attachments/20081002/91f61970/attachment.html > >> >> _______________________________________________ > >> >> Mikrotik mailing list > >> >> Mikrotik@mail.butchevans.com > >> >> http://www.butchevans.com/mailman/listinfo/mikrotik > >> >> > >> > > >> > _______________________________________________ > >> > Mikrotik mailing list > >> > Mikrotik@mail.butchevans.com > >> > http://www.butchevans.com/mailman/listinfo/mikrotik > >> > > >> > -- > >> > This message has been scanned for viruses and > >> > dangerous content by Basin Broadband, Inc., > >> > utilizing DefenderMX technology, and is > >> > believed to be clean. > >> > >> > >> > >> > -------------------------------------------------------------------------------- > >> > >> > >> > >> No virus found in this incoming message. > >> Checked by AVG - http://www.avg.com > >> Version: 8.0.173 / Virus Database: 270.7.5/1702 - Release Date: > 10/1/2008 > >> 9:05 AM > >> > >> _______________________________________________ > >> Mikrotik mailing list > >> Mikrotik@mail.butchevans.com > >> http://www.butchevans.com/mailman/listinfo/mikrotik > >> > > -------------- next part -------------- > > An HTML attachment was scrubbed... > > URL: > > > http://www.butchevans.com/pipermail/mikrotik/attachments/20081002/38aecdc9/attachment.html > > _______________________________________________ > > Mikrotik mailing list > > Mikrotik@mail.butchevans.com > > http://www.butchevans.com/mailman/listinfo/mikrotik > > > > -- > > This message has been scanned for viruses and > > dangerous content by Basin Broadband, Inc., > > utilizing DefenderMX technology, and is > > believed to be clean. > > > > -------------------------------------------------------------------------------- > > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.173 / Virus Database: 270.7.5/1704 - Release Date: 10/2/2008 > 9:35 PM > > _______________________________________________ > Mikrotik mailing list > Mikrotik@mail.butchevans.com > http://www.butchevans.com/mailman/listinfo/mikrotik > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.butchevans.com/pipermail/mikrotik/attachments/20081002/4929fc83/attachment.html
