Ok, Thanks. I have enough to get started. Will cross the next problem when I get to it. Well I guess I am going home. I'll play around a little with this tonight.
Dennis Burgess wrote: > It will work, but there is other work to be done. > > ----------------------------------------------------------- > Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer > WISPA Board Member - wispa.org > Link Technologies, Inc -- Mikrotik & WISP Support Services > 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 [mailto:wireless-boun...@wispa.org] On > Behalf Of Data Technology > Sent: Tuesday, December 01, 2009 5:03 PM > To: WISPA General List > Subject: Re: [WISPA] suggestions for dual wan dhcp auto fail over > > > Josh Luthman wrote: > >>> I was thinking that if I just change the distance value to a higher >>> >>> >> value then I could leave the interface up and nat should use the route >> with the lowest distance value. (not tested yet) >> >> That is how static routing works - it picks the lowest distance. If >> > you > >> have two routes identical except the distance, then the lower distance >> > is > >> used. >> >> >> >>> Then I could ping with a source address of the dsl interface and it >>> >>> >> should go out the dsl line even though the distance is set higher than >> the backup. (not tested yet) >> >> I have always had one interface a static IP/route so this was easy. >> > Not > >> sure how to force a certain destination when it is using dhcp-client. >> >> > I know the netwatch will not work for this but I saw a script (inproved > netwatch) that will use the ping command to check an ip address. Ping > has an option (that was broke until 3.28) to use "source-address". I > figure if it is using a source address of the dsl interface that went > down it should try to ping out that interface instead of the one with > the lowest distance. This is my thinking of how this might work. > Hopefully it will work this way. I will know soon. > > > > >> 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:45 PM, Data Technology <w...@dtisp.com> >> > wrote: > >> >> >>> Yes the dsl modem is handing out a dhcp address. I figure I will >>> > have > >>> to ping way back upstream to check the connection vs just pinging the >>> dhcp modem. >>> I was thinking that if I just change the distance value to a higher >>> value then I could leave the interface up and nat should use the >>> > route > >>> with the lowest distance value. (not tested yet) >>> Then I could ping with a source address of the dsl interface and it >>> should go out the dsl line even though the distance is set higher >>> > than > >>> the backup. (not tested yet) >>> >>> Dennis Burgess wrote: >>> >>> >>>> There are other things to also keep in mind when dealing with DHCP, >>>> > i.e. > >>>> is your DHCP being handed out locally. sSo if you have a DSL line >>>> > is > >>>> the DSL modem handing this out? if so, then watching that >>>> > connection is > >>>> useless, you will have to do some policy based routing and checks to >>>> verify that it is up and bring it down if it is not up. >>>> >>>> ----------------------------------------------------------- >>>> Dennis Burgess, CCNA, A+, Mikrotik Certified Trainer >>>> WISPA Board Member - wispa.org >>>> Link Technologies, Inc -- Mikrotik & WISP Support Services >>>> 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 [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 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 preference! >>>> >>>> There are places like wireless where the GUI is almost required as >>>> > the > >>>> CLI >>>> is difficult to navigate and may not even have some values. >>>> >>>> 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:17 PM, Data Technology <w...@dtisp.com> >>>> > wrote: > >>>> >>>> >>>>> 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.9.x. > >>>>> I think oldest is 3.25. >>>>> >>>>> >>>>> Josh Luthman wrote: >>>>> >>>>> >>>>> >>>>>> 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 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 4:29 PM, Data Technology <w...@dtisp.com> >>>>>> >>>>>> >>>>>> >>>> wrote: >>>> >>>> >>>> >>>>>>> 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 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." >>>>>>>> --- Albert Einstein >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Dec 1, 2009 at 4:01 PM, Data Technology <w...@dtisp.com> >>>>>>>> >>>>>>>> >>>>>>>> >>>>> wrote: >>>>> >>>>> >>>>> >>>>>>>> >>>>>>>> >>>>>>>>> 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 Technology >>>>>>>>>> Sender: wireless-boun...@wispa.org >>>>>>>>>> To: WISPA General List >>>>>>>>>> ReplyTo: WISPA General List >>>>>>>>>> Subject: [WISPA] suggestions for dual wan dhcp auto fail over >>>>>>>>>> Sent: Dec 1, 2009 15:30 >>>>>>>>>> >>>>>>>>>> I am trying to configure an rb450 v4.3 to connect to 2 >>>>>>>>>> > different > >>>>>>>>>> providers with dhcp using 1 as the primary and the other as a >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>> backup. >>>> >>>> >>>> >>>>>>>>>> I would like it to switch over to the backup if the primary >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>> service >>>> >>>> >>>> >>>>> is >>>>> >>>>> >>>>> >>>>>>>>> down. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>>> I want to nat local users to either service. >>>>>>>>>> >>>>>>>>>> I assume I will need to use netwatch to check the servcie >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>> availability >>>>> >>>>> >>>>> >>>>>>>>>> so I can check all the way thru the providers service and not >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>> just >>>> >>>> >>>> >>>>> the >>>>> >>>>> >>>>> >>>>>>>>>> local physical connection. >>>>>>>>>> >>>>>>>>>> The question is what do I need to do when the primary goes >>>>>>>>>> > down? > >>>>>>>>>> I thought I could just change the distance on the route but I >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>> found >>>> >>>> >>>> >>>>> out >>>>> >>>>> >>>>> >>>>>>>>>> it will not let you change the distance if the default route >>>>>>>>>> > is > >>>>>>>>>> >>>>>>>>>> >>>> set >>>> >>>> >>>> >>>>> by >>>>> >>>>> >>>>> >>>>>>>>>> the dhcp-client. >>>>>>>>>> >>>>>>>>>> I have looked at some of the examples on the wiki but they all >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>> use >>>> >>>> >>>> >>>>>>>>>> static ip address and I am wanting to use dhcp. >>>>>>>>>> Anyone have any pointers? >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> >>>>>>>>>> LaRoy McCann >>>>>>>>>> Data Technology >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>>>> WISPA Wants You! Join today! >>>>>>>>>> http://signup.wispa.org/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>>>> WISPA Wireless List: wireless@wispa.org >>>>>>>>>> >>>>>>>>>> Subscribe/Unsubscribe: >>>>>>>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>>>>>>> >>>>>>>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Sent via BlackBerry from T-Mobile >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>>>> WISPA Wants You! Join today! >>>>>>>>>> http://signup.wispa.org/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>>>> WISPA Wireless List: wireless@wispa.org >>>>>>>>>> >>>>>>>>>> Subscribe/Unsubscribe: >>>>>>>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>>>>>>> >>>>>>>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>>>>>>> >>>>>>>>>> ---------- >>>>>>>>>> >>>>>>>>>> This message has been scanned for viruses and >>>>>>>>>> dangerous content by the Data Technology >>>>>>>>>> MailScanner, and is believed to be clean. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>>> WISPA Wants You! Join today! >>>>>>>>> http://signup.wispa.org/ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>>> WISPA Wireless List: wireless@wispa.org >>>>>>>>> >>>>>>>>> Subscribe/Unsubscribe: >>>>>>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>>>>>> >>>>>>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>> WISPA Wants You! Join today! >>>>>>>> http://signup.wispa.org/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>>> WISPA Wireless List: wireless@wispa.org >>>>>>>> >>>>>>>> Subscribe/Unsubscribe: >>>>>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>>>>> >>>>>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>>>>> >>>>>>>> ---------- >>>>>>>> >>>>>>>> This message has been scanned for viruses and >>>>>>>> dangerous content by the Data Technology >>>>>>>> MailScanner, and is believed to be clean. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>> WISPA Wants You! Join today! >>>>>>> http://signup.wispa.org/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>>> WISPA Wireless List: wireless@wispa.org >>>>>>> >>>>>>> Subscribe/Unsubscribe: >>>>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>>>> >>>>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>> WISPA Wants You! Join today! >>>>>> http://signup.wispa.org/ >>>>>> >>>>>> >>>>>> >>>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>>> WISPA Wireless List: wireless@wispa.org >>>>>> >>>>>> Subscribe/Unsubscribe: >>>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>>> >>>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>>> >>>>>> ---------- >>>>>> >>>>>> This message has been scanned for viruses and >>>>>> dangerous content by the Data Technology >>>>>> MailScanner, and is believed to be clean. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>> WISPA Wants You! Join today! >>>>> http://signup.wispa.org/ >>>>> >>>>> >>>>> >>>>> >>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> >>>> >>>>> WISPA Wireless List: wireless@wispa.org >>>>> >>>>> Subscribe/Unsubscribe: >>>>> http://lists.wispa.org/mailman/listinfo/wireless >>>>> >>>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>>> >>>>> >>>>> >>>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> >>>> > ------------------------------------------------------------------------ > >>>> -------- >>>> >>>> WISPA Wireless List: wireless@wispa.org >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>> >>>> >>>> >>>> >>>> > ------------------------------------------------------------------------ > -------- > >>> >>> >>>> WISPA Wants You! Join today! >>>> http://signup.wispa.org/ >>>> >>>> >>>> > ------------------------------------------------------------------------ > -------- > >>> >>> >>>> WISPA Wireless List: wireless@wispa.org >>>> >>>> Subscribe/Unsubscribe: >>>> http://lists.wispa.org/mailman/listinfo/wireless >>>> >>>> Archives: http://lists.wispa.org/pipermail/wireless/ >>>> >>>> ---------- >>>> >>>> This message has been scanned for viruses and >>>> dangerous content by the Data Technology >>>> MailScanner, and is believed to be clean. >>>> >>>> >>>> >>>> >>>> >>> >>> > ------------------------------------------------------------------------ > -------- > >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> >>> >>> > ------------------------------------------------------------------------ > -------- > >>> WISPA Wireless List: wireless@wispa.org >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >>> >>> >>> >> >> > ------------------------------------------------------------------------ > -------- > >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> >> > ------------------------------------------------------------------------ > -------- > >> >> WISPA Wireless List: wireless@wispa.org >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> ---------- >> >> This message has been scanned for viruses and >> dangerous content by the Data Technology >> MailScanner, and is believed to be clean. >> >> >> >> > > > > ------------------------------------------------------------------------ > -------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > ------------------------------------------------------------------------ > -------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: wireless@wispa.org > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > ---------- > > This message has been scanned for viruses and > dangerous content by the Data Technology > MailScanner, and is believed to be clean. > > > -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: wireless@wispa.org Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
