{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 <provider gateway IP>
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: [email protected]
>
> 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: [email protected]
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
