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 = QQQQ-QQQQ
#
/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 Static HREC-EIA
10.0.4.0/27 directly connected - WISP-201
YYY.YYY.YYY.0/24 10.0.4.3 OSPF_ASE WISP-201
XXX.XXX.XXX.24/30 directly 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-ADDRESS PREF-SRC GATEWAY DISTANCE
0 ADo 0.0.0.0/0 - 10.0.4.1 110
2 ADC 10.0.4.0/27 10.0.4.3 ether1-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 <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/
--------------------------------------------------------------------------------
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/
