-boun...@wispa.org] On
>> Behalf Of Josh Luthman
>> Sent: Tuesday, December 01, 2009 4:21 PM
>> To: WISPA General List
>> Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over
>>
>> Lucky you, glad you could have 3.x everywhere!
>>
>> I cou
On Tue, 2009-12-01 at 17:16 -0600, Data Technology wrote:
> This won't work because if the dsl provider is down somewhere within
> their network the dsl modem will still answer ping requests on the local
> interface.
I have not read all of this thread. Here is the approach I use and it
works w
Training
> Author of "Learn RouterOS"
>
>
> -Original Message-
> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
> Behalf Of Data Technology
> Sent: Tuesday, December 01, 2009 5:03 PM
> To: WISPA General List
> Subject: Re: [WIS
009 3:17 PM
To: WISPA General List
Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over
This won't work because if the dsl provider is down somewhere within
their network the dsl modem will still answer ping requests on the local
interface.
Jerry Richardson wrote:
> It
01, 2009 5:06 PM
To: WISPA General List
Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over
It's also likely the gateway doesn't change, just the IP address. Ping
the gateway on WAN1 and if it stops responding activate WAN2
-Original Message-
From: wireless-boun...@wi
nstein
>
>
> On Tue, Dec 1, 2009 at 5:58 PM, Jerry Richardson
> wrote:
>
>
>> just ping the DSL provider's DNS server.
>>
>> -Original Message-
>> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
>> Behalf Of Data Technology
>>
t; WISPA Vendor Member
>>> Office: 314-735-0270 Website: http://www.linktechs.net
>>> LIVE On-Line Mikrotik Training
>>> Author of "Learn RouterOS"
>>>
>>>
>>> -Original Message-
>>> From: wireless-boun...@wispa.org [
WAN1 and if it stops responding activate WAN2
>
> -Original Message-
> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
> Behalf Of Josh Luthman
> Sent: Tuesday, December 01, 2009 3:01 PM
> To: WISPA General List
> Subject: Re: [WISPA] suggestions for
09 3:01 PM
To: WISPA General List
Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over
That's a good idea - find an IP only responsive on that network. I think
DNS servers will respond to pings (but not DNS queries) off network. Test
it with dig/ping. I can tell you if it works
t;> ---
> >>> Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer
> >>> WISPA Board Member - wispa.org
> >>> Link Technologies, Inc -- Mikrotik & WISP Support Services
> >>> WISPA Vendor Member
> >&
ebsite: http://www.linktechs.net
>>> LIVE On-Line Mikrotik Training
>>> Author of "Learn RouterOS"
>>>
>>>
>>> -Original Message-
>>> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
>>> Beh
un...@wispa.org [mailto:wireless-boun...@wispa.org] On
> Behalf Of Data Technology
> Sent: Tuesday, December 01, 2009 2:46 PM
> To: WISPA General List
> Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over
>
> Yes the dsl modem is handing out a dhcp address. I figur
just ping the DSL provider's DNS server.
-Original Message-
From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf
Of Data Technology
Sent: Tuesday, December 01, 2009 2:46 PM
To: WISPA General List
Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail
> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
> > Behalf Of Josh Luthman
> > Sent: Tuesday, December 01, 2009 4:21 PM
> > To: WISPA General List
> > Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over
> >
> > Lucky yo
http://www.linktechs.net
> LIVE On-Line Mikrotik Training
> Author of "Learn RouterOS"
>
>
> -Original Message-
> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On
> Behalf Of Josh Luthman
> Sent: Tuesday, December 01, 2009 4:21 PM
>
No one that works on HPUX is a wimp...
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
"The secret to creativity is knowing how to hide your sources."
--- Albert Einstein
On Tue, Dec 1, 2009 at 5:29 PM, Data Technology wrote:
> Well I have always
Well I have always used the command line for most things
I learned to configure hp-ux systems back in the 80's when the command
line was the only way.
I still configure my linux servers via the command line and laugh at
anyone that wants to us a GUI.
But MT has made configuring via the GUI so eas
ct: Re: [WISPA] suggestions for dual wan dhcp auto fail over
Lucky you, glad you could have 3.x everywhere!
I could be wrong as it may just be my experience, but the command line
for
custom things is necessary as the GUI doesn't show everything. I
started
with GUI and moved a lot to CLI as it
Lucky you, glad you could have 3.x everywhere!
I could be wrong as it may just be my experience, but the command line for
custom things is necessary as the GUI doesn't show everything. I started
with GUI and moved a lot to CLI as it seems easier/faster. Hopefully it's
simply a personal preferenc
Yeah, when I looked at the article you listed it clicked. I don't use
the command line except when I have to so I was a little off on the
command to change the distance setting.
I have version 4.3 so that should not be a problem.
I've been using MT for several years but I have gotten past the 2
First one is definitely not going to work.
Second one is what you need =)
Do keep in mind you need 3.11+. If you're new to Mikrotik there is little
reason to be concerned, but some users such as myself still have 2.9.50 or
51 stuff!
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wa
Josh,
That is what I was trying to do but I was trying to use "/ip route set
ether1 distance=3" instead of "/ip dhcp-client set ether1
default-route-distance=3".
Thanks
LaRoy
Josh Luthman wrote:
> This might help you
> http://stfunoo.be/?p=268
>
> I like using route distance since 3.11 DHCP ca
This might help you
http://stfunoo.be/?p=268
I like using route distance since 3.11 DHCP can do it.
It has worked very well for me.
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
"The secret to creativity is knowing how to hide your sources."
---
Sounds too easy :) I'll give it a try.
Thanks
LaRoy
e...@wisp-router.com wrote:
> Just change the nat to use the other public ip since your already
> masquerading just change that rule to src-nat and set the public ip to
> src-nat to.
>
> /Eje
> --Original Message--
> From: Data Techn
Just change the nat to use the other public ip since your already masquerading
just change that rule to src-nat and set the public ip to src-nat to.
/Eje
--Original Message--
From: Data Technology
Sender: wireless-boun...@wispa.org
To: WISPA General List
ReplyTo: WISPA General List
Subje
25 matches
Mail list logo
