From: Divin Mathew John (divinjohn@gmail.com)
Date: Sun Mar 29 2009 - 08:19:01 ART
hey..
I kinda used your topology and got OSPF working.... here's my Config
R1
> interface Loopback1
> ip address 1.1.1.1 255.255.255.0
> !
> interface FastEthernet0/0
> ip address 10.1.1.2 255.0.0.0
> duplex auto
> speed auto
> !
> interface FastEthernet0/1
> no ip address
> shutdown
> duplex auto
> speed auto
> !
> router ospf 1
> log-adjacency-changes
> network 1.1.1.1 0.0.0.0 area 0
> network 10.1.1.2 0.0.0.0 area 0
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
> ip http server
> ip pim bidir-enable
>
R2
> interface Loopback0
> ip address 2.2.2.2 255.255.255.0
> !
> interface FastEthernet0/0
> ip address 10.1.1.1 255.0.0.0
> ip nat inside
> ip ospf network broadcast
> duplex auto
> speed auto
> !
> interface FastEthernet0/1
> ip address 11.1.1.1 255.0.0.0
> ip nat outside
> ip ospf network non-broadcast
> duplex auto
> speed auto
> !
> router ospf 1
> log-adjacency-changes
> network 2.2.2.2 0.0.0.0 area 0
> network 10.1.1.1 0.0.0.0 area 0
> network 11.1.1.1 0.0.0.0 area 0
> neighbor 11.1.1.2 priority 1
> !
> ip nat pool NAT_POOL 192.168.1.1 192.168.1.150 netmask 255.255.255.0
> ip nat inside source list 100 pool NAT_POOL
> ip classless
> ip http server
> ip pim bidir-enable
> !
> access-list 100 deny ip host 11.1.1.1 any
> access-list 100 permit ip any any
> !
>
R3
> interface Loopback0
> ip address 3.3.3.3 255.255.255.0
> !
> interface FastEthernet0/0
> ip address 11.1.1.2 255.0.0.0
> ip ospf network non-broadcast
> duplex auto
> speed auto
> !
> interface FastEthernet0/1
> no ip address
> shutdown
> duplex auto
> speed auto
> !
> router ospf 1
> log-adjacency-changes
> network 3.3.3.3 0.0.0.0 area 0
> network 11.1.1.2 0.0.0.0 area 0
> neighbor 11.1.1.1 priority 1
> !
> ip classless
> ip route 0.0.0.0 0.0.0.0 11.1.1.1 name R2
> ip http server
> ip pim bidir-enable
>
>
Thanking You
Yours Sincerely
Divin Mathew John
divinjohn@gmail.com
divin@dide3d.com
+91 9945430983
+91 9846697191
+974 5008916
PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
On Sun, Mar 29, 2009 at 12:13 PM, Divin Mathew John <divinjohn@gmail.com>
wrote:
> I tried the lab... thing is...before i ping the OSPF neighbourship
> comes up.! but fter NAT it just goes down! no... tell me.! where u
> able to ping from r2 to r3's loopback ..? i couldnt...i tried putting
> a default route in r3 pointing to r2. but no luck...maybe if u cna get
> that to work then i guess....the OSPF neighbourship will come up
> Thanking You
>
> Yours Sincerely
>
> Divin Mathew John
> divinjohn@gmail.com
> divin@dide3d.com
> +91 9945430983
> +91 9846697191
> +974 5008916
> PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
>
>
>
> On Sun, Mar 29, 2009 at 8:12 AM, jeremy co <jeremy.cool14@gmail.com>
wrote:
>> Divin,
>>
>> well if it happened as u described , it wouldn't be interesting NAT
scenario
>> :)
>>
>> u can lab it up. what make me surprise is not involving outside int in
NAT
>> scenario since by general ACL I wrote router's local interface will
involve
>> in NAT process, I know it doesn't make sense but it's what happened :)
what
>> makes me dizzy is wired behavior of NAT regard participating this
interface
>> or not, if I ping befor forming neibour ship translation would add to NAT
>> table and adj never would be formed, but if I leave it with clear ip nat
>> trans * before forming adj, it will form adj!!!!
>>
>>
>> maybe guys , experienced before can help on that
>>
>>
>> Jeremy
>>
>>
>>
>> On Sun, Mar 29, 2009 at 5:38 AM, Divin Mathew John <divinjohn@gmail.com>
>> wrote:
>>>
>>> To add to the explaination OSPF neighbourship's are formed by the
>>> interface connecting the R2 to R3...so i guess NAT doesnt apply here!
>>> Thanking You
>>>
>>> Yours Sincerely
>>>
>>> Divin Mathew John
>>> divinjohn@gmail.com
>>> divin@dide3d.com
>>> +91 9945430983
>>> +91 9846697191
>>> +974 5008916
>>> PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
>>>
>>>
>>>
>>> On Sun, Mar 29, 2009 at 12:05 AM, Divin Mathew John <divinjohn@gmail.com
>
>>> wrote:
>>> > ithin the router R2.. i guess it doesn't get NATed.!
>>> > see
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:08 ART