Re: [WISPA] Routing Help [Default Route to OSPF]
Was this OSPF v3? What's new in 3.22: *) added WinBox OSPFv3 support to routing-test package; There are several mentions of OSPF on 3.x and two on 4.x. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Fri, Feb 12, 2010 at 6:15 PM, Jeremy Parr wrote: > On 12 February 2010 17:29, Paul Gerstenberger wrote: > > Ok, I feel stupid and smart at the same time. I had it set up right the > whole time. I don't know WHY it wasn't working on the test bench with a > smaller router (RB450G, with the same software, on the same network), but I > attached those public IPs to the production mikrotik router (RB1000) and it > works perfect. > > > > I don't know exactly what it was, but whatever was amiss is in that > RB450, not the Riverstone. > > > > Thanks for the responses. I'm glad it's finally working, but irritated > that it took me this long to figure it out... > > Same RouterOS version of both MTs? > > > > > 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
On 12 February 2010 17:29, Paul Gerstenberger wrote: > Ok, I feel stupid and smart at the same time. I had it set up right the whole > time. I don't know WHY it wasn't working on the test bench with a smaller > router (RB450G, with the same software, on the same network), but I attached > those public IPs to the production mikrotik router (RB1000) and it works > perfect. > > I don't know exactly what it was, but whatever was amiss is in that RB450, > not the Riverstone. > > Thanks for the responses. I'm glad it's finally working, but irritated that > it took me this long to figure it out... Same RouterOS version of both MTs? 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Ok, I feel stupid and smart at the same time. I had it set up right the whole time. I don't know WHY it wasn't working on the test bench with a smaller router (RB450G, with the same software, on the same network), but I attached those public IPs to the production mikrotik router (RB1000) and it works perfect. I don't know exactly what it was, but whatever was amiss is in that RB450, not the Riverstone. Thanks for the responses. I'm glad it's finally working, but irritated that it took me this long to figure it out... -Paul On Feb 11, 2010, at 9:22 PM, Paul Gerstenberger wrote: > It's an RS3000 running ROS 9.1.2.8. > > I did try disabling OSPF and set up static routes. The behavior was exactly > the same. I had inbound connectivity, but not outbound. So our ISP is routing > those IPs to our gateway, and the riverstone knows where to go with them from > there - to the mikrotik. But when originating from inside our network, it > hits the riverstone at 10.0.4.1, but goes no further. > > I'm not running HRT. > > I appreciate the assistance. I'll be back at it tomorrow morning to try out > any suggestions... > > -Paul > > On Feb 11, 2010, at 8:56 PM, Faisal Imtiaz wrote: > >> Which Riverstone Box is it ? RS3000 or RS8000 also what is the ROS version >> you (Paul) are running ? >> >> >> If it is an OSPF issue or Routing issue... >> >> You should be able to set up the routing (static) and confirm if it is one >> or the other ? >> >> Are you by any chance running " hrt enable" command on any of the cards ? >> (temp. comment those commands out). >> >> I have noticed that with HRT enabled, system does not take new routes into >> the RIB rightaway.. >> >> >> >> Faisal Imtiaz >> Computer Office Solutions Inc. /SnappyDSL.net >> Ph: (305) 663-5518 x 232 >> -----Original Message----- >> From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On >> Behalf Of Butch Evans >> Sent: Thursday, February 11, 2010 11:39 PM >> To: WISPA General List >> Subject: Re: [WISPA] Routing Help [Default Route to OSPF] >> >> On Thu, 2010-02-11 at 23:31 -0500, Josh Luthman wrote: >>> It's a Riverstone and Mikrotik. No Cisco from what I caught. >> >> Yeah...I decided to go back and look in the earlier messages in the thread. >> I had already put my foot in my mouth...thanks for keeping me from chewing >> with vigor. ;-) >> >> -- >> >> * Butch Evans * Professional Network Consultation* >> * http://www.butchevans.com/* Network Engineering * >> * http://store.wispgear.net/* Wired or Wireless Networks * >> * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * >> >> >> >> >> >> >> 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/ 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
It's an RS3000 running ROS 9.1.2.8. I did try disabling OSPF and set up static routes. The behavior was exactly the same. I had inbound connectivity, but not outbound. So our ISP is routing those IPs to our gateway, and the riverstone knows where to go with them from there - to the mikrotik. But when originating from inside our network, it hits the riverstone at 10.0.4.1, but goes no further. I'm not running HRT. I appreciate the assistance. I'll be back at it tomorrow morning to try out any suggestions... -Paul On Feb 11, 2010, at 8:56 PM, Faisal Imtiaz wrote: > Which Riverstone Box is it ? RS3000 or RS8000 also what is the ROS version > you (Paul) are running ? > > > If it is an OSPF issue or Routing issue... > > You should be able to set up the routing (static) and confirm if it is one > or the other ? > > Are you by any chance running " hrt enable" command on any of the cards ? > (temp. comment those commands out). > > I have noticed that with HRT enabled, system does not take new routes into > the RIB rightaway.. > > > > Faisal Imtiaz > Computer Office Solutions Inc. /SnappyDSL.net > Ph: (305) 663-5518 x 232 > -Original Message- > From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On > Behalf Of Butch Evans > Sent: Thursday, February 11, 2010 11:39 PM > To: WISPA General List > Subject: Re: [WISPA] Routing Help [Default Route to OSPF] > > On Thu, 2010-02-11 at 23:31 -0500, Josh Luthman wrote: >> It's a Riverstone and Mikrotik. No Cisco from what I caught. > > Yeah...I decided to go back and look in the earlier messages in the thread. > I had already put my foot in my mouth...thanks for keeping me from chewing > with vigor. ;-) > > -- > > * Butch Evans * Professional Network Consultation* > * http://www.butchevans.com/* Network Engineering * > * http://store.wispgear.net/* Wired or Wireless Networks * > * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * > > > > > > > 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Which Riverstone Box is it ? RS3000 or RS8000 also what is the ROS version you (Paul) are running ? If it is an OSPF issue or Routing issue... You should be able to set up the routing (static) and confirm if it is one or the other ? Are you by any chance running " hrt enable" command on any of the cards ? (temp. comment those commands out). I have noticed that with HRT enabled, system does not take new routes into the RIB rightaway.. Faisal Imtiaz Computer Office Solutions Inc. /SnappyDSL.net Ph: (305) 663-5518 x 232 -Original Message- From: wireless-boun...@wispa.org [mailto:wireless-boun...@wispa.org] On Behalf Of Butch Evans Sent: Thursday, February 11, 2010 11:39 PM To: WISPA General List Subject: Re: [WISPA] Routing Help [Default Route to OSPF] On Thu, 2010-02-11 at 23:31 -0500, Josh Luthman wrote: > It's a Riverstone and Mikrotik. No Cisco from what I caught. Yeah...I decided to go back and look in the earlier messages in the thread. I had already put my foot in my mouth...thanks for keeping me from chewing with vigor. ;-) -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://store.wispgear.net/* Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
On Thu, 2010-02-11 at 23:31 -0500, Josh Luthman wrote: > It's a Riverstone and Mikrotik. No Cisco from what I caught. Yeah...I decided to go back and look in the earlier messages in the thread. I had already put my foot in my mouth...thanks for keeping me from chewing with vigor. ;-) -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://store.wispgear.net/* Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
On Wed, 2010-02-10 at 16:43 -0800, Paul Gerstenberger wrote:
> {provider} <---[ static 0.0.0.0/0 xxx.xxx.xxx.xxx ]---> {riverstone ASBR}
> <---[10.0.4.1 OSPF
> Backbone 10.0.4.2]---> {mikrotik} <--- x.x.x.x/24 public addresses
Ok. What we need to know:
With the public/24 on the MT "inside" interface:
FROM a machine with another ip in that range (of course attached to the
"inside" MT interface, ping the MT's public/24. Ping the MT's 10.0.4.2
IP, and ping the Riverstone 10.0.4.1. ONE of those is likely to fail
(assuming you have a real routing problem). Which one will give us a
clue as to what the problem actually is. What would be helpful is an
output of the routing table on both the MT and Riverstone.
> I can attach those public addresses directly to the riverstone and they
> work fine. However if I attach them to the mikrotik they get advertised
> over OSPF and have local connectivity, but they stop at the border router
> on a traceroute. However, if you ping a device using one of those addresses
> from an external network, you get a response. So I'm missing something to
> make the route bi-directional, if that's the right term.
Is either the MT or the riverstone running some sort of proxy arp on any
interface? It is possible that is giving you a false impression that
the device is responding from outside?
--
* Butch Evans * Professional Network Consultation*
* http://www.butchevans.com/* Network Engineering *
* http://store.wispgear.net/* Wired or Wireless Networks *
* http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! *
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/
Re: [WISPA] Routing Help [Default Route to OSPF]
It's a Riverstone and Mikrotik. No Cisco from what I caught. Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373 “Success is not final, failure is not fatal: it is the courage to continue that counts.” --- Winston Churchill On Thu, Feb 11, 2010 at 11:27 PM, Butch Evans wrote: > On Thu, 2010-02-11 at 10:20 -0800, Paul Gerstenberger wrote: > > I'm using one of the new public IPs right now, but I had to attach > > it to the riverstone (which holds the default gateway to our ISP). > > I just caught this thread. I don't know all of the details, but looking > through the rest of this message, I am presuming you are having trouble > with a Cisco<->MT OSPF. One thing about Cisco (at least some of the IOS > versions) is that it will/can not do OSPF using a secondary IP on the > interface. If I am way off base, having not read the entire thread, > I'll try to catch up and see if there is something I can do to assist. > > -- > > * Butch Evans * Professional Network Consultation* > * http://www.butchevans.com/* Network Engineering * > * http://store.wispgear.net/* Wired or Wireless Networks * > * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * > > > > > > > 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
On Thu, 2010-02-11 at 10:20 -0800, Paul Gerstenberger wrote: > I'm using one of the new public IPs right now, but I had to attach > it to the riverstone (which holds the default gateway to our ISP). I just caught this thread. I don't know all of the details, but looking through the rest of this message, I am presuming you are having trouble with a Cisco<->MT OSPF. One thing about Cisco (at least some of the IOS versions) is that it will/can not do OSPF using a secondary IP on the interface. If I am way off base, having not read the entire thread, I'll try to catch up and see if there is something I can do to assist. -- * Butch Evans * Professional Network Consultation* * http://www.butchevans.com/* Network Engineering * * http://store.wispgear.net/* Wired or Wireless Networks * * http://blog.butchevans.com/ * ImageStream, Mikrotik and MORE! * 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
I just added the network to the riverstone this morning to double-check it's outbound connectivity, it was not attached to both riverstone and the mikrotik at the same time. -Paul On Feb 11, 2010, at 11:19 AM, Data Technology wrote: > You said that you have one of the public ip's assigned to the > riverstone. That might be causing the problem. What netmask did you > use on the riverstone for the public ip? If you used a /24 then the > riverstone thinks that whole subnet is attached to it and is probably > ignoring the routing for the /24 back to the MT. > > > Bret Clark wrote: >> At this point I think I would just port mirror on a port on the >> Riverstone and see what Wireshark is showing. I see nothing wrong with >> the routing statements and I know it works as we have a fair number of >> Mikrotiks running with RS3000's and RS8000's using OSPF's. >> >> >> On Thu, 2010-02-11 at 10:20 -0800, Paul Gerstenberger wrote: >> >> >>> I have public IPs, the 10.0.4.0 network is my OSPF backbone network. I'm >>> not trying to go out with those addresses. What I've put down as >>> yyy.yyy.yyy.0/24 signifies my new public IPs. >>> >>> I'm using one of the new public IPs right now, but I had to attach it to >>> the riverstone (which holds the default gateway to our ISP). >>> >>> -Paul >>> >>> On Feb 11, 2010, at 10:12 AM, Dennis Burgess wrote: >>> >>> >>>> NAT. your 10.x is privates, you may need to nat them out. >>>> >>>> --- >>>> Dennis Burgess, CCNA, Mikrotik Certified Trainer, MTCNA, MTCRE, MTCWE, >>>> MTCTCE, MTCUME >>>> Link Technologies, Inc -- Mikrotik & WISP Support Services >>>> 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 Paul Gerstenberger >>>> Sent: Thursday, February 11, 2010 11:56 AM >>>> To: WISPA General List >>>> Subject: Re: [WISPA] Routing Help [Default Route to OSPF] >>>> >>>> I have the new network permitted in my ingress and egress ACLs for our >>>> outbound interface. I've also tried using a smaller subnet of IPs from a >>>> different pool that we've been using for years. And I briefly disabled >>>> the ACLs altogether to test. >>>> >>>> And when I attach this network direct to the riverstone, everything >>>> works. That's why I though it was an internal routing misconfiguration. >>>> >>>> -Paul >>>> >>>> On Feb 11, 2010, at 9:47 AM, Data Technology wrote: >>>> >>>> >>>>> Could it be a firewall rule? >>>>> >>>>> >>>>> Paul Gerstenberger wrote: >>>>> >>>>>> Same story, I disabled OSPF on both devices (but both are still on >>>>>> >>>> the 10.0.4.0 network) put this route in the riverstone: >>>> >>>>>> ip add route yyy.yyy..0/24 gateway 10.0.4.3 >>>>>> >>>>>> and this in the mikrotik: >>>>>> >>>>>> ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty >>>>>> >>>> sure, I did it from WinBox) >>>> >>>>>> Again, I can ping out to all local resources off the riverstone, but >>>>>> >>>> I time out when trying to get outside, but I can ping into those publics >>>> from an external network. >>>> >>>>>> MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 >>>>>> traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets >>>>>> 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms >>>>>> 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms >>>>>> 3 * * * >>>>>> >>>>>> -Paul >>>>>> >>>>>> On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Paul Gerstenberger wrote: >>>>>>> >>>>>>> >>>>>>>> There are a number of blackhole routes and ACL li
Re: [WISPA] Routing Help [Default Route to OSPF]
You said that you have one of the public ip's assigned to the riverstone. That might be causing the problem. What netmask did you use on the riverstone for the public ip? If you used a /24 then the riverstone thinks that whole subnet is attached to it and is probably ignoring the routing for the /24 back to the MT. Bret Clark wrote: > At this point I think I would just port mirror on a port on the > Riverstone and see what Wireshark is showing. I see nothing wrong with > the routing statements and I know it works as we have a fair number of > Mikrotiks running with RS3000's and RS8000's using OSPF's. > > > On Thu, 2010-02-11 at 10:20 -0800, Paul Gerstenberger wrote: > > >> I have public IPs, the 10.0.4.0 network is my OSPF backbone network. I'm not >> trying to go out with those addresses. What I've put down as >> yyy.yyy.yyy.0/24 signifies my new public IPs. >> >> I'm using one of the new public IPs right now, but I had to attach it to the >> riverstone (which holds the default gateway to our ISP). >> >> -Paul >> >> On Feb 11, 2010, at 10:12 AM, Dennis Burgess wrote: >> >> >>> NAT. your 10.x is privates, you may need to nat them out. >>> >>> --- >>> Dennis Burgess, CCNA, Mikrotik Certified Trainer, MTCNA, MTCRE, MTCWE, >>> MTCTCE, MTCUME >>> Link Technologies, Inc -- Mikrotik & WISP Support Services >>> 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 Paul Gerstenberger >>> Sent: Thursday, February 11, 2010 11:56 AM >>> To: WISPA General List >>> Subject: Re: [WISPA] Routing Help [Default Route to OSPF] >>> >>> I have the new network permitted in my ingress and egress ACLs for our >>> outbound interface. I've also tried using a smaller subnet of IPs from a >>> different pool that we've been using for years. And I briefly disabled >>> the ACLs altogether to test. >>> >>> And when I attach this network direct to the riverstone, everything >>> works. That's why I though it was an internal routing misconfiguration. >>> >>> -Paul >>> >>> On Feb 11, 2010, at 9:47 AM, Data Technology wrote: >>> >>> >>>> Could it be a firewall rule? >>>> >>>> >>>> Paul Gerstenberger wrote: >>>> >>>>> Same story, I disabled OSPF on both devices (but both are still on >>>>> >>> the 10.0.4.0 network) put this route in the riverstone: >>> >>>>> ip add route yyy.yyy..0/24 gateway 10.0.4.3 >>>>> >>>>> and this in the mikrotik: >>>>> >>>>> ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty >>>>> >>> sure, I did it from WinBox) >>> >>>>> Again, I can ping out to all local resources off the riverstone, but >>>>> >>> I time out when trying to get outside, but I can ping into those publics >>> from an external network. >>> >>>>> MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 >>>>> traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets >>>>> 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms >>>>> 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms >>>>> 3 * * * >>>>> >>>>> -Paul >>>>> >>>>> On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: >>>>> >>>>> >>>>> >>>>>> Paul Gerstenberger wrote: >>>>>> >>>>>> >>>>>>> There are a number of blackhole routes and ACL lines for >>>>>>> >>> unallocated IPs, that's why it's so long. Probably overkill. >>> >>>>>>> I'm not running NAT on the mikrotik, but I'm planning doing so with >>>>>>> >>> some of these IPs. >>> >>>>>>> [ad...@mikrotik] > /routing ospf export >>>>>>> # feb/11/2010 05:34:32 by RouterOS 4.5 >>>>>>> # softwar
Re: [WISPA] Routing Help [Default Route to OSPF]
At this point I think I would just port mirror on a port on the Riverstone and see what Wireshark is showing. I see nothing wrong with the routing statements and I know it works as we have a fair number of Mikrotiks running with RS3000's and RS8000's using OSPF's. On Thu, 2010-02-11 at 10:20 -0800, Paul Gerstenberger wrote: > I have public IPs, the 10.0.4.0 network is my OSPF backbone network. I'm not > trying to go out with those addresses. What I've put down as yyy.yyy.yyy.0/24 > signifies my new public IPs. > > I'm using one of the new public IPs right now, but I had to attach it to the > riverstone (which holds the default gateway to our ISP). > > -Paul > > On Feb 11, 2010, at 10:12 AM, Dennis Burgess wrote: > > > NAT. your 10.x is privates, you may need to nat them out. > > > > --- > > Dennis Burgess, CCNA, Mikrotik Certified Trainer, MTCNA, MTCRE, MTCWE, > > MTCTCE, MTCUME > > Link Technologies, Inc -- Mikrotik & WISP Support Services > > 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 Paul Gerstenberger > > Sent: Thursday, February 11, 2010 11:56 AM > > To: WISPA General List > > Subject: Re: [WISPA] Routing Help [Default Route to OSPF] > > > > I have the new network permitted in my ingress and egress ACLs for our > > outbound interface. I've also tried using a smaller subnet of IPs from a > > different pool that we've been using for years. And I briefly disabled > > the ACLs altogether to test. > > > > And when I attach this network direct to the riverstone, everything > > works. That's why I though it was an internal routing misconfiguration. > > > > -Paul > > > > On Feb 11, 2010, at 9:47 AM, Data Technology wrote: > > > >> Could it be a firewall rule? > >> > >> > >> Paul Gerstenberger wrote: > >>> Same story, I disabled OSPF on both devices (but both are still on > > the 10.0.4.0 network) put this route in the riverstone: > >>> > >>> ip add route yyy.yyy..0/24 gateway 10.0.4.3 > >>> > >>> and this in the mikrotik: > >>> > >>> ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty > > sure, I did it from WinBox) > >>> > >>> Again, I can ping out to all local resources off the riverstone, but > > I time out when trying to get outside, but I can ping into those publics > > from an external network. > >>> > >>> MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 > >>> traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets > >>> 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms > >>> 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms > >>> 3 * * * > >>> > >>> -Paul > >>> > >>> On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: > >>> > >>> > >>>> Paul Gerstenberger wrote: > >>>> > >>>>> There are a number of blackhole routes and ACL lines for > > unallocated IPs, that's why it's so long. Probably overkill. > >>>>> > >>>>> I'm not running NAT on the mikrotik, but I'm planning doing so with > > some of these IPs. > >>>>> > >>>>> [ad...@mikrotik] > /routing ospf export > >>>>> # feb/11/2010 05:34:32 by RouterOS 4.5 > >>>>> # software id = - > >>>>> # > >>>>> /routing ospf instance > >>>>> set default comment="" disabled=no distribute-default=never > > in-filter=ospf-in metric-bgp=20 \ > >>>>> metric-connected=20 metric-default=1 metric-other-ospf=auto > > metric-rip=20 metric-static=20 \ > >>>>> name=default out-filter=ospf-out redistribute-bgp=no > > redistribute-connected=as-type-1 \ > >>>>> redistribute-other-ospf=no redistribute-rip=no > > redistribute-static=no router-id=10.0.4.3 > >>>>> /routing ospf area > >>>>> set backbone area-id=0.0.0.0 comment="" disabled=no > > instance=default name=backbone type=default > >>>>> /routing ospf interface > >>>>> add authentication=none authentication-key="" >
Re: [WISPA] Routing Help [Default Route to OSPF]
I have public IPs, the 10.0.4.0 network is my OSPF backbone network. I'm not trying to go out with those addresses. What I've put down as yyy.yyy.yyy.0/24 signifies my new public IPs. I'm using one of the new public IPs right now, but I had to attach it to the riverstone (which holds the default gateway to our ISP). -Paul On Feb 11, 2010, at 10:12 AM, Dennis Burgess wrote: > NAT. your 10.x is privates, you may need to nat them out. > > --- > Dennis Burgess, CCNA, Mikrotik Certified Trainer, MTCNA, MTCRE, MTCWE, > MTCTCE, MTCUME > Link Technologies, Inc -- Mikrotik & WISP Support Services > 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 Paul Gerstenberger > Sent: Thursday, February 11, 2010 11:56 AM > To: WISPA General List > Subject: Re: [WISPA] Routing Help [Default Route to OSPF] > > I have the new network permitted in my ingress and egress ACLs for our > outbound interface. I've also tried using a smaller subnet of IPs from a > different pool that we've been using for years. And I briefly disabled > the ACLs altogether to test. > > And when I attach this network direct to the riverstone, everything > works. That's why I though it was an internal routing misconfiguration. > > -Paul > > On Feb 11, 2010, at 9:47 AM, Data Technology wrote: > >> Could it be a firewall rule? >> >> >> Paul Gerstenberger wrote: >>> Same story, I disabled OSPF on both devices (but both are still on > the 10.0.4.0 network) put this route in the riverstone: >>> >>> ip add route yyy.yyy..0/24 gateway 10.0.4.3 >>> >>> and this in the mikrotik: >>> >>> ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty > sure, I did it from WinBox) >>> >>> Again, I can ping out to all local resources off the riverstone, but > I time out when trying to get outside, but I can ping into those publics > from an external network. >>> >>> MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 >>> traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets >>> 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms >>> 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms >>> 3 * * * >>> >>> -Paul >>> >>> On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: >>> >>> >>>> Paul Gerstenberger wrote: >>>> >>>>> There are a number of blackhole routes and ACL lines for > unallocated IPs, that's why it's so long. Probably overkill. >>>>> >>>>> I'm not running NAT on the mikrotik, but I'm planning doing so with > some of these IPs. >>>>> >>>>> [ad...@mikrotik] > /routing ospf export >>>>> # feb/11/2010 05:34:32 by RouterOS 4.5 >>>>> # software id = - >>>>> # >>>>> /routing ospf instance >>>>> set default comment="" disabled=no distribute-default=never > in-filter=ospf-in metric-bgp=20 \ >>>>> metric-connected=20 metric-default=1 metric-other-ospf=auto > metric-rip=20 metric-static=20 \ >>>>> name=default out-filter=ospf-out redistribute-bgp=no > redistribute-connected=as-type-1 \ >>>>> redistribute-other-ospf=no redistribute-rip=no > redistribute-static=no router-id=10.0.4.3 >>>>> /routing ospf area >>>>> set backbone area-id=0.0.0.0 comment="" disabled=no > instance=default name=backbone type=default >>>>> /routing ospf interface >>>>> add authentication=none authentication-key="" > authentication-key-id=1 comment="" cost=10 \ >>>>> dead-interval=40s disabled=no hello-interval=10s instance-id=0 > interface=ether1-gateway \ >>>>> network-type=broadcast passive=no priority=1 > retransmit-interval=5s transmit-delay=1s \ >>>>> use-bfd=no >>>>> /routing ospf network >>>>> add area=backbone comment="" disabled=no network=10.0.4.0/27 >>>>> >>>>> >>>>> >>>>> Here are the relevant routes: >>>>> >>>>> RS-1# ip show routes >>>>> >>>>> Destination Gateway Owner Netif >>>>> --- ---
Re: [WISPA] Routing Help [Default Route to OSPF]
NAT. your 10.x is privates, you may need to nat them out. --- Dennis Burgess, CCNA, Mikrotik Certified Trainer, MTCNA, MTCRE, MTCWE, MTCTCE, MTCUME Link Technologies, Inc -- Mikrotik & WISP Support Services 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 Paul Gerstenberger Sent: Thursday, February 11, 2010 11:56 AM To: WISPA General List Subject: Re: [WISPA] Routing Help [Default Route to OSPF] I have the new network permitted in my ingress and egress ACLs for our outbound interface. I've also tried using a smaller subnet of IPs from a different pool that we've been using for years. And I briefly disabled the ACLs altogether to test. And when I attach this network direct to the riverstone, everything works. That's why I though it was an internal routing misconfiguration. -Paul On Feb 11, 2010, at 9:47 AM, Data Technology wrote: > Could it be a firewall rule? > > > Paul Gerstenberger wrote: >> Same story, I disabled OSPF on both devices (but both are still on the 10.0.4.0 network) put this route in the riverstone: >> >> ip add route yyy.yyy..0/24 gateway 10.0.4.3 >> >> and this in the mikrotik: >> >> ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty sure, I did it from WinBox) >> >> Again, I can ping out to all local resources off the riverstone, but I time out when trying to get outside, but I can ping into those publics from an external network. >> >> MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 >> traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets >> 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms >> 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms >> 3 * * * >> >> -Paul >> >> On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: >> >> >>> Paul Gerstenberger wrote: >>> >>>> There are a number of blackhole routes and ACL lines for unallocated IPs, that's why it's so long. Probably overkill. >>>> >>>> I'm not running NAT on the mikrotik, but I'm planning doing so with some of these IPs. >>>> >>>> [ad...@mikrotik] > /routing ospf export >>>> # feb/11/2010 05:34:32 by RouterOS 4.5 >>>> # software id = - >>>> # >>>> /routing ospf instance >>>> set default comment="" disabled=no distribute-default=never in-filter=ospf-in metric-bgp=20 \ >>>> metric-connected=20 metric-default=1 metric-other-ospf=auto metric-rip=20 metric-static=20 \ >>>> name=default out-filter=ospf-out redistribute-bgp=no redistribute-connected=as-type-1 \ >>>> redistribute-other-ospf=no redistribute-rip=no redistribute-static=no router-id=10.0.4.3 >>>> /routing ospf area >>>> set backbone area-id=0.0.0.0 comment="" disabled=no instance=default name=backbone type=default >>>> /routing ospf interface >>>> add authentication=none authentication-key="" authentication-key-id=1 comment="" cost=10 \ >>>> dead-interval=40s disabled=no hello-interval=10s instance-id=0 interface=ether1-gateway \ >>>> network-type=broadcast passive=no priority=1 retransmit-interval=5s transmit-delay=1s \ >>>> use-bfd=no >>>> /routing ospf network >>>> add area=backbone comment="" disabled=no network=10.0.4.0/27 >>>> >>>> >>>> >>>> Here are the relevant routes: >>>> >>>> RS-1# ip show routes >>>> >>>> Destination Gateway Owner Netif >>>> --- --- - - >>>> default ZZZ.ZZZ.ZZZ.25 StaticHREC-EIA >>>> 10.0.4.0/27 directly connected - WISP-201 >>>> YYY.YYY.YYY.0/2410.0.4.3 OSPF_ASE WISP-201 >>>> XXX.XXX.XXX.24/30directly connected - HREC-EIA >>>> >>>> [ad...@mikrotik] > ip route print >>>> >>>> Flags: X - disabled, A - active, D - dynamic, >>>> C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, >>>> B - blackhole, U - unreachable, P - prohibit >>>> >>>> # DST-ADDRESSPREF-SRCGATEWAY DISTANCE >>>> 0 ADo
Re: [WISPA] Routing Help [Default Route to OSPF]
I have the new network permitted in my ingress and egress ACLs for our outbound interface. I've also tried using a smaller subnet of IPs from a different pool that we've been using for years. And I briefly disabled the ACLs altogether to test. And when I attach this network direct to the riverstone, everything works. That's why I though it was an internal routing misconfiguration. -Paul On Feb 11, 2010, at 9:47 AM, Data Technology wrote: > Could it be a firewall rule? > > > Paul Gerstenberger wrote: >> Same story, I disabled OSPF on both devices (but both are still on the >> 10.0.4.0 network) put this route in the riverstone: >> >> ip add route yyy.yyy..0/24 gateway 10.0.4.3 >> >> and this in the mikrotik: >> >> ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty sure, I >> did it from WinBox) >> >> Again, I can ping out to all local resources off the riverstone, but I time >> out when trying to get outside, but I can ping into those publics from an >> external network. >> >> MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 >> traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets >> 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms >> 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms >> 3 * * * >> >> -Paul >> >> On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: >> >> >>> Paul Gerstenberger wrote: >>> There are a number of blackhole routes and ACL lines for unallocated IPs, that's why it's so long. Probably overkill. I'm not running NAT on the mikrotik, but I'm planning doing so with some of these IPs. [ad...@mikrotik] > /routing ospf export # feb/11/2010 05:34:32 by RouterOS 4.5 # software id = - # /routing ospf instance set default comment="" disabled=no distribute-default=never in-filter=ospf-in metric-bgp=20 \ metric-connected=20 metric-default=1 metric-other-ospf=auto metric-rip=20 metric-static=20 \ name=default out-filter=ospf-out redistribute-bgp=no redistribute-connected=as-type-1 \ redistribute-other-ospf=no redistribute-rip=no redistribute-static=no router-id=10.0.4.3 /routing ospf area set backbone area-id=0.0.0.0 comment="" disabled=no instance=default name=backbone type=default /routing ospf interface add authentication=none authentication-key="" authentication-key-id=1 comment="" cost=10 \ dead-interval=40s disabled=no hello-interval=10s instance-id=0 interface=ether1-gateway \ network-type=broadcast passive=no priority=1 retransmit-interval=5s transmit-delay=1s \ use-bfd=no /routing ospf network add area=backbone comment="" disabled=no network=10.0.4.0/27 Here are the relevant routes: RS-1# ip show routes Destination Gateway Owner Netif --- --- - - default ZZZ.ZZZ.ZZZ.25 StaticHREC-EIA 10.0.4.0/27 directly connected - WISP-201 YYY.YYY.YYY.0/2410.0.4.3 OSPF_ASE WISP-201 XXX.XXX.XXX.24/30directly connected - HREC-EIA [ad...@mikrotik] > ip route print Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, B - blackhole, U - unreachable, P - prohibit # DST-ADDRESSPREF-SRCGATEWAYDISTANCE 0 ADo 0.0.0.0/0 -10.0.4.1 110 2 ADC 10.0.4.0/2710.0.4.3ether1-gateway 0 30 ADC yyy.yyy.yyy.0/24 zzz.zzz.zzz.1 ether2-local 0 44 ADo xxx.xxx.xxx.24/30 -10.0.4.1 110 -Paul >>> Strange...everything looks right to me. Routing tables are as I would >>> expect. You don't happen to have any ACL's being applied to the >>> interface that the Mikrotik is attached too? What happen if you >>> eliminate using OSPF for now and just setup the configuration using >>> static routes? Does it work then? >>> >>> >>> >>> 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 >> >>
Re: [WISPA] Routing Help [Default Route to OSPF]
Could it be a firewall rule? Paul Gerstenberger wrote: > Same story, I disabled OSPF on both devices (but both are still on the > 10.0.4.0 network) put this route in the riverstone: > > ip add route yyy.yyy..0/24 gateway 10.0.4.3 > > and this in the mikrotik: > > ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty sure, I > did it from WinBox) > > Again, I can ping out to all local resources off the riverstone, but I time > out when trying to get outside, but I can ping into those publics from an > external network. > > MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 > traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets > 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms > 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms > 3 * * * > > -Paul > > On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: > > >> Paul Gerstenberger wrote: >> >>> There are a number of blackhole routes and ACL lines for unallocated IPs, >>> that's why it's so long. Probably overkill. >>> >>> I'm not running NAT on the mikrotik, but I'm planning doing so with some of >>> these IPs. >>> >>> [ad...@mikrotik] > /routing ospf export >>> # feb/11/2010 05:34:32 by RouterOS 4.5 >>> # software id = - >>> # >>> /routing ospf instance >>> set default comment="" disabled=no distribute-default=never >>> in-filter=ospf-in metric-bgp=20 \ >>>metric-connected=20 metric-default=1 metric-other-ospf=auto >>> metric-rip=20 metric-static=20 \ >>>name=default out-filter=ospf-out redistribute-bgp=no >>> redistribute-connected=as-type-1 \ >>>redistribute-other-ospf=no redistribute-rip=no redistribute-static=no >>> router-id=10.0.4.3 >>> /routing ospf area >>> set backbone area-id=0.0.0.0 comment="" disabled=no instance=default >>> name=backbone type=default >>> /routing ospf interface >>> add authentication=none authentication-key="" authentication-key-id=1 >>> comment="" cost=10 \ >>>dead-interval=40s disabled=no hello-interval=10s instance-id=0 >>> interface=ether1-gateway \ >>>network-type=broadcast passive=no priority=1 retransmit-interval=5s >>> transmit-delay=1s \ >>>use-bfd=no >>> /routing ospf network >>> add area=backbone comment="" disabled=no network=10.0.4.0/27 >>> >>> >>> >>> Here are the relevant routes: >>> >>> RS-1# ip show routes >>> >>> Destination Gateway Owner Netif >>> --- --- - - >>> default ZZZ.ZZZ.ZZZ.25 StaticHREC-EIA >>> 10.0.4.0/27 directly connected - WISP-201 >>> YYY.YYY.YYY.0/2410.0.4.3 OSPF_ASE WISP-201 >>> XXX.XXX.XXX.24/30directly connected - HREC-EIA >>> >>> [ad...@mikrotik] > ip route print >>> >>> Flags: X - disabled, A - active, D - dynamic, >>> C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, >>> B - blackhole, U - unreachable, P - prohibit >>> >>> # DST-ADDRESSPREF-SRCGATEWAYDISTANCE >>> 0 ADo 0.0.0.0/0 -10.0.4.1 110 >>> 2 ADC 10.0.4.0/2710.0.4.3ether1-gateway 0 >>> 30 ADC yyy.yyy.yyy.0/24 zzz.zzz.zzz.1 ether2-local 0 >>> 44 ADo xxx.xxx.xxx.24/30 -10.0.4.1 110 >>> >>> -Paul >>> >>> >> Strange...everything looks right to me. Routing tables are as I would >> expect. You don't happen to have any ACL's being applied to the >> interface that the Mikrotik is attached too? What happen if you >> eliminate using OSPF for now and just setup the configuration using >> static routes? Does it work then? >> >> >> >> 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Same story, I disabled OSPF on both devices (but both are still on the 10.0.4.0 network) put this route in the riverstone: ip add route yyy.yyy..0/24 gateway 10.0.4.3 and this in the mikrotik: ip route add dst-address=0.0.0.0/0 gateway=10.0.4.1 (pretty sure, I did it from WinBox) Again, I can ping out to all local resources off the riverstone, but I time out when trying to get outside, but I can ping into those publics from an external network. MacBook-Pro:~ pgerst$ traceroute 4.2.2.1 traceroute to 4.2.2.1 (4.2.2.1), 64 hops max, 52 byte packets 1 yyy.yyy.yyy.1 (yyy.yyy.yyy.1) 0.673 ms 0.132 ms 0.165 ms 2 10.0.4.1 (10.0.4.1) 0.406 ms 0.365 ms 0.358 ms 3 * * * -Paul On Feb 11, 2010, at 3:57 AM, Bret Clark wrote: > Paul Gerstenberger wrote: >> There are a number of blackhole routes and ACL lines for unallocated IPs, >> that's why it's so long. Probably overkill. >> >> I'm not running NAT on the mikrotik, but I'm planning doing so with some of >> these IPs. >> >> [ad...@mikrotik] > /routing ospf export >> # feb/11/2010 05:34:32 by RouterOS 4.5 >> # software id = - >> # >> /routing ospf instance >> set default comment="" disabled=no distribute-default=never >> in-filter=ospf-in metric-bgp=20 \ >>metric-connected=20 metric-default=1 metric-other-ospf=auto metric-rip=20 >> metric-static=20 \ >>name=default out-filter=ospf-out redistribute-bgp=no >> redistribute-connected=as-type-1 \ >>redistribute-other-ospf=no redistribute-rip=no redistribute-static=no >> router-id=10.0.4.3 >> /routing ospf area >> set backbone area-id=0.0.0.0 comment="" disabled=no instance=default >> name=backbone type=default >> /routing ospf interface >> add authentication=none authentication-key="" authentication-key-id=1 >> comment="" cost=10 \ >>dead-interval=40s disabled=no hello-interval=10s instance-id=0 >> interface=ether1-gateway \ >>network-type=broadcast passive=no priority=1 retransmit-interval=5s >> transmit-delay=1s \ >>use-bfd=no >> /routing ospf network >> add area=backbone comment="" disabled=no network=10.0.4.0/27 >> >> >> >> Here are the relevant routes: >> >> RS-1# ip show routes >> >> Destination Gateway Owner Netif >> --- --- - - >> default ZZZ.ZZZ.ZZZ.25 StaticHREC-EIA >> 10.0.4.0/27 directly connected - WISP-201 >> YYY.YYY.YYY.0/2410.0.4.3 OSPF_ASE WISP-201 >> XXX.XXX.XXX.24/30directly connected - HREC-EIA >> >> [ad...@mikrotik] > ip route print >> >> Flags: X - disabled, A - active, D - dynamic, >> C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, >> B - blackhole, U - unreachable, P - prohibit >> >> # DST-ADDRESSPREF-SRCGATEWAYDISTANCE >> 0 ADo 0.0.0.0/0 -10.0.4.1 110 >> 2 ADC 10.0.4.0/2710.0.4.3ether1-gateway 0 >> 30 ADC yyy.yyy.yyy.0/24 zzz.zzz.zzz.1 ether2-local 0 >> 44 ADo xxx.xxx.xxx.24/30 -10.0.4.1 110 >> >> -Paul >> > Strange...everything looks right to me. Routing tables are as I would > expect. You don't happen to have any ACL's being applied to the > interface that the Mikrotik is attached too? What happen if you > eliminate using OSPF for now and just setup the configuration using > static routes? Does it work then? > > > > 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Paul Gerstenberger wrote: > There are a number of blackhole routes and ACL lines for unallocated IPs, > that's why it's so long. Probably overkill. > > I'm not running NAT on the mikrotik, but I'm planning doing so with some of > these IPs. > > [ad...@mikrotik] > /routing ospf export > # feb/11/2010 05:34:32 by RouterOS 4.5 > # software id = - > # > /routing ospf instance > set default comment="" disabled=no distribute-default=never in-filter=ospf-in > metric-bgp=20 \ > metric-connected=20 metric-default=1 metric-other-ospf=auto metric-rip=20 > metric-static=20 \ > name=default out-filter=ospf-out redistribute-bgp=no > redistribute-connected=as-type-1 \ > redistribute-other-ospf=no redistribute-rip=no redistribute-static=no > router-id=10.0.4.3 > /routing ospf area > set backbone area-id=0.0.0.0 comment="" disabled=no instance=default > name=backbone type=default > /routing ospf interface > add authentication=none authentication-key="" authentication-key-id=1 > comment="" cost=10 \ > dead-interval=40s disabled=no hello-interval=10s instance-id=0 > interface=ether1-gateway \ > network-type=broadcast passive=no priority=1 retransmit-interval=5s > transmit-delay=1s \ > use-bfd=no > /routing ospf network > add area=backbone comment="" disabled=no network=10.0.4.0/27 > > > > Here are the relevant routes: > > RS-1# ip show routes > > Destination Gateway Owner Netif > --- --- - - > default ZZZ.ZZZ.ZZZ.25 StaticHREC-EIA > 10.0.4.0/27 directly connected - WISP-201 > YYY.YYY.YYY.0/2410.0.4.3 OSPF_ASE WISP-201 > XXX.XXX.XXX.24/30directly connected - HREC-EIA > > [ad...@mikrotik] > ip route print > > Flags: X - disabled, A - active, D - dynamic, > C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme, > B - blackhole, U - unreachable, P - prohibit > > # DST-ADDRESSPREF-SRCGATEWAYDISTANCE > 0 ADo 0.0.0.0/0 -10.0.4.1 110 > 2 ADC 10.0.4.0/2710.0.4.3ether1-gateway 0 > 30 ADC yyy.yyy.yyy.0/24 zzz.zzz.zzz.1 ether2-local 0 > 44 ADo xxx.xxx.xxx.24/30 -10.0.4.1 110 > > -Paul > Strange...everything looks right to me. Routing tables are as I would expect. You don't happen to have any ACL's being applied to the interface that the Mikrotik is attached too? What happen if you eliminate using OSPF for now and just setup the configuration using static routes? Does it work then? 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
There are a number of blackhole routes and ACL lines for unallocated IPs,
that's why it's so long. Probably overkill.
I'm not running NAT on the mikrotik, but I'm planning doing so with some of
these IPs.
[ad...@mikrotik] > /routing ospf export
# feb/11/2010 05:34:32 by RouterOS 4.5
# software id = -
#
/routing ospf instance
set default comment="" disabled=no distribute-default=never in-filter=ospf-in
metric-bgp=20 \
metric-connected=20 metric-default=1 metric-other-ospf=auto metric-rip=20
metric-static=20 \
name=default out-filter=ospf-out redistribute-bgp=no
redistribute-connected=as-type-1 \
redistribute-other-ospf=no redistribute-rip=no redistribute-static=no
router-id=10.0.4.3
/routing ospf area
set backbone area-id=0.0.0.0 comment="" disabled=no instance=default
name=backbone type=default
/routing ospf interface
add authentication=none authentication-key="" authentication-key-id=1
comment="" cost=10 \
dead-interval=40s disabled=no hello-interval=10s instance-id=0
interface=ether1-gateway \
network-type=broadcast passive=no priority=1 retransmit-interval=5s
transmit-delay=1s \
use-bfd=no
/routing ospf network
add area=backbone comment="" disabled=no network=10.0.4.0/27
Here are the relevant routes:
RS-1# ip show routes
Destination Gateway Owner Netif
--- --- - -
default ZZZ.ZZZ.ZZZ.25 StaticHREC-EIA
10.0.4.0/27 directly connected - WISP-201
YYY.YYY.YYY.0/2410.0.4.3 OSPF_ASE WISP-201
XXX.XXX.XXX.24/30directly connected - HREC-EIA
[ad...@mikrotik] > ip route print
Flags: X - disabled, A - active, D - dynamic,
C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESSPREF-SRCGATEWAYDISTANCE
0 ADo 0.0.0.0/0 -10.0.4.1 110
2 ADC 10.0.4.0/2710.0.4.3ether1-gateway 0
30 ADC yyy.yyy.yyy.0/24 zzz.zzz.zzz.1 ether2-local 0
44 ADo xxx.xxx.xxx.24/30 -10.0.4.1 110
-Paul
On Feb 10, 2010, at 5:40 PM, Bret Clark wrote:
> Paul Gerstenberger wrote:
>> {provider} <---[ static 0.0.0.0/0 xxx.xxx.xxx.xxx ]---> {riverstone ASBR}
>> <---[10.0.4.1 OSPF Backbone 10.0.4.2]---> {mikrotik} <--- x.x.x.x/24
>> public addresses
>>
>> I can attach those public addresses directly to the riverstone and they work
>> fine. However if I attach them to the mikrotik they get advertised over OSPF
>> and have local connectivity, but they stop at the border router on a
>> traceroute. However, if you ping a device using one of those addresses from
>> an external network, you get a response. So I'm missing something to make
>> the route bi-directional, if that's the right term.
>>
>> This is what I have in the Riverstone:
>>
>> 325 : ip add route default gateway
>> 362 : ip-router policy redistribute from-proto static to-proto ospf network
>> default
>> 363 : ip-router policy redistribute from-proto direct to-proto ospf network
>> all
>> 365 : ospf create area backbone
>> 367 : ospf add interface WISP-201 to-area backbone
>> 368 : ospf start
>>
>> -Paul
>>
>> On Feb 10, 2010, at 2:47 PM, Bret Clark wrote:
>>
> Hseems okay in the Riverstone, nothing blatant standing out.
> You're not running NAT on the Mikrotik by any chance? What is the print
> out from the Mikrotik when you run "/routing ospf export"?
>
> Otherwise I would need to see what the route tables look like in the RS
> and Mikrotik.
>
> BTW...that must be one heck of a config on that RS if your OSPF config
> doesn't start till line 365!
>
>
>
> 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Got a default route on the MikroTik pointing to your riverstone box?
/Eje
Sent via BlackBerry from T-Mobile
-Original Message-
From: Paul Gerstenberger
Date: Wed, 10 Feb 2010 16:43:14
To: WISPA General List
Subject: Re: [WISPA] Routing Help [Default Route to OSPF]
{provider} <---[ static 0.0.0.0/0 xxx.xxx.xxx.xxx ]---> {riverstone ASBR}
<---[10.0.4.1 OSPF Backbone 10.0.4.2]---> {mikrotik} <--- x.x.x.x/24 public
addresses
I can attach those public addresses directly to the riverstone and they work
fine. However if I attach them to the mikrotik they get advertised over OSPF
and have local connectivity, but they stop at the border router on a
traceroute. However, if you ping a device using one of those addresses from an
external network, you get a response. So I'm missing something to make the
route bi-directional, if that's the right term.
This is what I have in the Riverstone:
325 : ip add route default gateway
362 : ip-router policy redistribute from-proto static to-proto ospf network
default
363 : ip-router policy redistribute from-proto direct to-proto ospf network all
365 : ospf create area backbone
367 : ospf add interface WISP-201 to-area backbone
368 : ospf start
-Paul
On Feb 10, 2010, at 2:47 PM, Bret Clark wrote:
> Paul Gerstenberger wrote:
>> I'm having a heck of a time setting up OSPF for my network. We've been
>> running a switched network with a Riverstone router on the border, but we've
>> long outgrown that configuration. I have a Mikrotik RB1000U in the rack
>> running v4.5 that we're going to use for our expansion and convert existing
>> subscribers over to. If I can get the dang thing to work anyway.
>>
>> So, here's what I got:
>>
>> The Riverstone is still on the border, and will be until I can talk the
>> higher-ups into replacing it. It still works and has plenty of capacity for
>> us still, it's just that Riverstone Networks went under some time ago and
>> there is no support for these things anymore. Anyway, it's here, and it has
>> the default route to our provider. I have a new range of public IPs, and I
>> need to have those public IPs accessible from the Mikrotik[s].
>>
>
> Having a hard time following exactly what you are doing...can you
> attached a network drawing with the routes? We use Riverstones and
> Mikrotiks in our backbone with no problems at all and I have quite a bit
> of familiarity with Riverstone networks (I once worked for them :).
>
> Bret
>
>
>
> 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Paul Gerstenberger wrote:
> {provider} <---[ static 0.0.0.0/0 xxx.xxx.xxx.xxx ]---> {riverstone ASBR}
> <---[10.0.4.1 OSPF Backbone 10.0.4.2]---> {mikrotik} <--- x.x.x.x/24
> public addresses
>
> I can attach those public addresses directly to the riverstone and they work
> fine. However if I attach them to the mikrotik they get advertised over OSPF
> and have local connectivity, but they stop at the border router on a
> traceroute. However, if you ping a device using one of those addresses from
> an external network, you get a response. So I'm missing something to make the
> route bi-directional, if that's the right term.
>
> This is what I have in the Riverstone:
>
> 325 : ip add route default gateway
> 362 : ip-router policy redistribute from-proto static to-proto ospf network
> default
> 363 : ip-router policy redistribute from-proto direct to-proto ospf network
> all
> 365 : ospf create area backbone
> 367 : ospf add interface WISP-201 to-area backbone
> 368 : ospf start
>
> -Paul
>
> On Feb 10, 2010, at 2:47 PM, Bret Clark wrote:
>
Hseems okay in the Riverstone, nothing blatant standing out.
You're not running NAT on the Mikrotik by any chance? What is the print
out from the Mikrotik when you run "/routing ospf export"?
Otherwise I would need to see what the route tables look like in the RS
and Mikrotik.
BTW...that must be one heck of a config on that RS if your OSPF config
doesn't start till line 365!
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/
Re: [WISPA] Routing Help [Default Route to OSPF]
On 10 February 2010 19:43, Paul Gerstenberger wrote:
> {provider} <---[ static 0.0.0.0/0 xxx.xxx.xxx.xxx ]---> {riverstone ASBR}
> <---[10.0.4.1 OSPF Backbone 10.0.4.2]---> {mikrotik} <--- x.x.x.x/24
> public addresses
>
> I can attach those public addresses directly to the riverstone and they work
> fine. However if I attach them to the mikrotik they get advertised over OSPF
> and have local connectivity, but they stop at the border router on a
> traceroute. However, if you ping a device using one of those addresses from
> an external network, you get a response. So I'm missing something to make the
> route bi-directional, if that's the right term.
>
> This is what I have in the Riverstone:
>
> 325 : ip add route default gateway
> 362 : ip-router policy redistribute from-proto static to-proto ospf network
> default
> 363 : ip-router policy redistribute from-proto direct to-proto ospf network
> all
> 365 : ospf create area backbone
> 367 : ospf add interface WISP-201 to-area backbone
> 368 : ospf start
Can you paste `ip route print` and `routing ospf neighbors print` from
the Mikrotik, and whatever the Riverstone's equal is?
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/
Re: [WISPA] Routing Help [Default Route to OSPF]
{provider} <---[ static 0.0.0.0/0 xxx.xxx.xxx.xxx ]---> {riverstone ASBR}
<---[10.0.4.1 OSPF Backbone 10.0.4.2]---> {mikrotik} <--- x.x.x.x/24 public
addresses
I can attach those public addresses directly to the riverstone and they work
fine. However if I attach them to the mikrotik they get advertised over OSPF
and have local connectivity, but they stop at the border router on a
traceroute. However, if you ping a device using one of those addresses from an
external network, you get a response. So I'm missing something to make the
route bi-directional, if that's the right term.
This is what I have in the Riverstone:
325 : ip add route default gateway
362 : ip-router policy redistribute from-proto static to-proto ospf network
default
363 : ip-router policy redistribute from-proto direct to-proto ospf network all
365 : ospf create area backbone
367 : ospf add interface WISP-201 to-area backbone
368 : ospf start
-Paul
On Feb 10, 2010, at 2:47 PM, Bret Clark wrote:
> Paul Gerstenberger wrote:
>> I'm having a heck of a time setting up OSPF for my network. We've been
>> running a switched network with a Riverstone router on the border, but we've
>> long outgrown that configuration. I have a Mikrotik RB1000U in the rack
>> running v4.5 that we're going to use for our expansion and convert existing
>> subscribers over to. If I can get the dang thing to work anyway.
>>
>> So, here's what I got:
>>
>> The Riverstone is still on the border, and will be until I can talk the
>> higher-ups into replacing it. It still works and has plenty of capacity for
>> us still, it's just that Riverstone Networks went under some time ago and
>> there is no support for these things anymore. Anyway, it's here, and it has
>> the default route to our provider. I have a new range of public IPs, and I
>> need to have those public IPs accessible from the Mikrotik[s].
>>
>
> Having a hard time following exactly what you are doing...can you
> attached a network drawing with the routes? We use Riverstones and
> Mikrotiks in our backbone with no problems at all and I have quite a bit
> of familiarity with Riverstone networks (I once worked for them :).
>
> Bret
>
>
>
> 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/
Re: [WISPA] Routing Help [Default Route to OSPF]
Paul Gerstenberger wrote: > I'm having a heck of a time setting up OSPF for my network. We've been > running a switched network with a Riverstone router on the border, but we've > long outgrown that configuration. I have a Mikrotik RB1000U in the rack > running v4.5 that we're going to use for our expansion and convert existing > subscribers over to. If I can get the dang thing to work anyway. > > So, here's what I got: > > The Riverstone is still on the border, and will be until I can talk the > higher-ups into replacing it. It still works and has plenty of capacity for > us still, it's just that Riverstone Networks went under some time ago and > there is no support for these things anymore. Anyway, it's here, and it has > the default route to our provider. I have a new range of public IPs, and I > need to have those public IPs accessible from the Mikrotik[s]. > Having a hard time following exactly what you are doing...can you attached a network drawing with the routes? We use Riverstones and Mikrotiks in our backbone with no problems at all and I have quite a bit of familiarity with Riverstone networks (I once worked for them :). Bret 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] Routing Help [Default Route to OSPF]
I'm having a heck of a time setting up OSPF for my network. We've been running
a switched network with a Riverstone router on the border, but we've long
outgrown that configuration. I have a Mikrotik RB1000U in the rack running v4.5
that we're going to use for our expansion and convert existing subscribers over
to. If I can get the dang thing to work anyway.
So, here's what I got:
The Riverstone is still on the border, and will be until I can talk the
higher-ups into replacing it. It still works and has plenty of capacity for us
still, it's just that Riverstone Networks went under some time ago and there is
no support for these things anymore. Anyway, it's here, and it has the default
route to our provider. I have a new range of public IPs, and I need to have
those public IPs accessible from the Mikrotik[s].
At this point, I have OSPF running between the routers, both the Riverstone and
the Mikrotiks are advertising their attached networks, and the Riverstone
appears to be redistributing it's default route in OSPF. Everything works
locally, but I'm not able to get OUT to the internet from our public addresses
when attached to the Mikrotik.
BUT, I do have connectivity from an outside network IN to those addresses.
Something is not working/configured to make the routing bidirectional. I don't
understand what else I need to do.
If I directly attach the public addresses to the Riverstone, everything works.
I have allowed that network it in the applicable ACLs, etc.
Can anyone offer me some tips and suggestions? I've worn myself out
troubleshooting it, I just don't know what else to look for!
Thanks!
---
Paul Gerstenberger
Hood River Electric Cooperative
Communications Access Cooperative
[provider] - We have three Class-C networks of Public IPs assigned to us
--
{default gateway}
--
[riverstone] - Our core router, runs NAT and has directly connected networks of
private and public IPs, uses static route / default gateway to our upstream
provider. Two of the Class-C public ranges are used directly on the riverstone.
--
{ospf}
--
[RB1000 w/ v4.5] - Runs user manager, planning on running PPPoE over vlans to
our access points. I want to be able to assign addresses from our third Class-C
as needed and run NAT for the bulk of customers.
--
{PPPoE}
--
[subscribers] - Using a consumer router (D-Link, Netgear, TrendNet, etc) as
PPPoE client.
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/
