- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-13-2012 11:45 AM - edited 03-07-2019 08:52 AM
I need a little help figuring out the best way to inject a static route into the OSPF Domain. (Area 0) for access to Internet
Internet Router is not part of OSPF Area 0 (no ospf process running currently)
Internet Router - Interface Fa0/0 is connected into Area 0 Core Switch (Trunk)
Internet Router has a sub-interface created Fa0/0.666
Pix Outside interface is in vlan 666
Layer 2 vlan created in Area 0 core for vlan 666 traffic
Core switch in Area 0 has a default route pointing to the Inside interface of the Firewall
Routing should work as follows (Outbound traffic)
Internal Traffic Outbound (Internet) should route to the inside interface of the firewall, if the traffic is allowed then should pass to the outside interface and out through the core switch to the Internet router.
I've looked at Conditional default route injection but i'm not sure if the internet router needs to be running the OSPF process to be able to inject the routes using a route-map back into Area 0.
If additional details are needed please let me know.
Thanks
Solved! Go to Solution.
- Labels:
-
Other Switching
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 02:58 PM
John
so i've gotten almost everything working as well. I have 1 last challenge
On the Inet router i am recieving provider ip via dhcp. I can ping / tracert to google on fa0/1 interface but i can not pass traffic from fa0/0.666 - 192.168.1.253 interface to the ISP, need a little help with a static route statement. I'm not sure what to use as the next hop, also is it a requirement to run NAT on this router if the Pix is doing NAT/PAT?
Gateway of last resort is 208.79.77.129 to network 0.0.0.0
208.79.77.0/25 is subnetted, 1 subnets
C 208.79.77.128 is directly connected, FastEthernet0/1
10.0.0.0/32 is subnetted, 1 subnets
S 10.0.20.65 [254/0] via 208.79.77.129, FastEthernet0/1
S* 0.0.0.0/0 [1/0] via 208.79.77.129, FastEthernet0/1
C 192.168.0.0/23 is directly connected, FastEthernet0/0.666
snet-internet-r1#sh run | in ip route
ip route 0.0.0.0 0.0.0.0 FastEthernet0/1 dhcp
Message was edited by: Jay Stants

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 03:20 PM
You'll need to nat on your internet router. If you can ping google from the outside interface, it's because the link is up and your isp knows how to get back to you. Since you have internal addresses on the internet router, you won't be able to pass traffic without natting.
Try this:
access-list 100 permit ip 192.168.0.0 0.0.1.255 any
ip nat inside source list 100 interface fa0/1 overload
int fa0/1
ip nat outside
int fa0/0.666
ip nat inside
Try to ping again after doing this...
HTH,
John

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 03:33 PM
Jay,
That's the problem in your design unfortunately. Your isp doesn't know how to get to your 192.168.1.0/23 addresses, so the traffic being sourced from that interface is dropped. If you had a public ip block, you could put the public address on the inside interface and the isp would know how to get to it because they'd be routing for it. You could then put a public address on your pix and then nat there.
The problem is that currently you're natting from your pix to another private address space (192.168.1.0/23) from what I'm seeing, so everything is going to look like it's coming out of the pix as a 192.168.1.0 address. If you were to put the acl into effect on the router that I gave earlier, it should nat out again as your assigned address from the isp.
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 03:44 PM
I figured this was a flaw - If i were like you said using a "Public" block and perhaps running some sort of dynamic protocol (bgp) with the provider then i wouldn't have to double nat.
I believe atleast with the design i have implemented i can use a pool within the 192.168.0.0 network as a "static" nat assignment to mask the inside address but still have to specify an acl on the internet router inbound to that assignement which should pass through the pix and to the host.
This was more of a lab to learn the design and understand the routing. I'm new to OSPF so seeing through-out this design how i've gone from a single area to a multi-area topology and learning route-maps / redistribution and so on i've managed to get a better grasp on what's going on behind the scenes
I'll test out the NAT on the inet router shortly and get back to you, Thanks for all your advice/help thus far i highly appreciate the time and effort you have put into this with me.
Regards,
Jay

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 03:56 PM
No problem! I look forward to hearing the outcome
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 04:02 PM
All looks good after adding the NAT config on the Internet Router
I can browse to Internet from area 1 with no issues .. I'm watching FW log as i'm doing various tasks outbound and everything seems to work correctly at the moment.
Here's a trace to show the path
Tracing route to google.com [74.125.226.228]
over a maximum of 30 hops:
1 2 ms <1 ms 1 ms 10.50.100.2 (Area 1 - vlan 100)
2 1 ms 1 ms 1 ms 10.50.1.7 (snet-abr-r1)
3 1 ms 1 ms 1 ms 172.16.1.1 (Area 0 - snet-core-s1)
4 2 ms 2 ms 2 ms 192.168.1.253 (snet-internet-router | LAN Interface)
5 10 ms 8 ms 13 ms 10.11.25.1 - ISP Network
6 14 ms 14 ms 11 ms 67.97.247.73 - ISP Network
7 22 ms 222 ms 215 ms 4.53.194.29 - Offnet - other carrier network
8 23 ms 16 ms 15 ms 4.69.132.202
9 19 ms 18 ms 16 ms 4.69.136.185
10 24 ms 24 ms 27 ms 4.69.136.190
11 26 ms 26 ms 23 ms 4.69.134.134
12 24 ms 27 ms 27 ms 4.69.149.69
13 40 ms 29 ms 29 ms 4.79.168.6
14 27 ms 29 ms 28 ms 209.85.252.80
15 27 ms 30 ms 39 ms 72.14.236.146
16 31 ms 36 ms 30 ms 72.14.239.92
17 29 ms 30 ms 143 ms 209.85.252.3
18 38 ms 30 ms 30 ms 72.14.239.252
19 32 ms 28 ms 33 ms 74.125.226.228 - Google.com
Trace complete.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 04:19 PM
Awesome Jay! Glad to hear it's all working for you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2012 04:41 PM
Thanks Again John - I'm sure we'll be in touch again in the future as we are always learning when it comes to design/implementation and troubleshooting various topologies
Regards,
Jay

- « Previous
-
- 1
- 2
- Next »