; 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/262856a4/attachment.html
Butch-
You've changed my life!
I didn't realize that it would use the least hops. I did see the priority
and played with changing that.
I also took the times down to :01 to speed it up. Although I'm sure there's
probably a side effect with that...
I saw some arp problems when I turned it on f
On Thu, 2 Oct 2008, Randall Roberts wrote:
I was under the impression that STP wasn't very reliable. (I
haven't tried it in years...)
It's not unreliable...just harder to engineer traffic than, for
example, OSPF.
I've always seen the STP button in Bridge setup. Didn't know about
what to pu
I was under the impression that STP wasn't very reliable. (I haven't tried
it in years...)
I've always seen the STP button in Bridge setup. Didn't know about what to
put for the settings, I'm going back to lab and try with the defaults.
One other question- Is there a problem with turning this
;> >> 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
uot;
>> 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
>&
On Thu, 2 Oct 2008, Josh Luthman wrote:
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.
The trouble that I see is that it is on a bridge...
--
***
On Thu, 2 Oct 2008, Randall Roberts 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-enabl
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 swi
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/mikrot
ings
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...
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
--- next part --
An HTML attachment was scrubbed...
URL:
http://www.butchevans.com/pipermail/mikrotik/attachments/20081002/91f61970/attachment.html
13 matches
Mail list logo