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