11-29-2012 06:55 AM - edited 03-04-2019 06:16 PM
We have two sites Site A and Site B
Site A has internet and Site B needs to access the internet from site A
I am using OSPF and both sites can see routes to the other site
Site B has the IP address of site A's end of the point to point as the Gateway of last resort however Site B cant access the internet still
When I do show ip route 0.0.0.0 it points towards the ip of site A's end of the point to point
I need to urgently solve this
Thanks in advance for you help
11-29-2012 07:07 AM
Can you do a trace from Site B to any internet address and check where is it getting dropped
Raju
11-29-2012 07:10 AM
traceroute 209.244.0.3
Type escape sequence to abort.
Tracing the route to 209.244.0.3
VRF info: (vrf in name/id, vrf out name/id)
1 10.120.20.22 0 msec 9 msec 0 msec
2 * * *
3 * * *
this is the address of Site A's end of the point to point
11-29-2012 07:14 AM
Hi Jonny
What is the next device after
10.120.20.22
Raju
11-29-2012 07:07 AM
What does site A go through to get to the internet? Does it redirect traffic to another device like a firewall or another router? What's site A's gateway of last resort?
11-29-2012 07:52 AM
It goes through a firewall and Site A's gateway of last resort the IP of the firewall.
11-29-2012 07:52 AM
The next device after 10.120.20.22 is the core switch.
11-29-2012 07:54 AM
Your firewall needs a route back to site B. Does it have that? If not, you'll want to create a route on it pointing to it's next hop internally..possibly switch?
HTH,
John
**** Please rate all useful posts ****
11-29-2012 08:21 AM
Site B core switch is conncted to switch 10.120.20.22 which is in site A and is then connected to the core switch in site A. The firewall is also connected to 10.120.20.22. Would I put the next hop as core switch or 10.120.20.22 ?
11-29-2012 08:34 AM
Yes. Put your route pointing to site b and the next hop as the .22 address. If your core knows how to get to site b, you should be good to go.
John
Sent from Cisco Technical Support iPhone App
11-29-2012 08:17 AM
1. Check if your Firewall has route back to Site B
2. Check if FW is configured to Allow the Site B IPs and configured to NAT those IP Addresses
Raju
11-29-2012 09:26 AM
It would be best if you can post a diagram of your network with IP's and connections.
12-03-2012 03:22 AM
I can ping IPs on site B from the core switch and firewall on Site A
The firewall does not have any restrictions to stop Internet access from any range
12-03-2012 03:40 AM
Is your firewall natting? Do you have the range that site B hosts listed in the firewall to be natted? What type of firewall is it? Since you can ping from the firewall to site B, it's not a routing issue...
HTH,
John
*** Please rate all useful posts ***
12-03-2012 03:41 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide