This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Trouble with /28 static routed to UTM IP

My colo provider has issued me an IP from one of their routed pools to my UTM, and then made a static route for my /28 to that IP. On the UTM I have the WAN set as their routed IP with their gateway and it works with external connectivity. My internal interface is set to the first IP from the /28 which I then use as the gateway IP for the servers behind the UTM. The servers can traceroute out a few hops but stop at the provider's edge router. Does this sound like an issue on the UTM or their router config?

This thread was automatically locked due to age.

Parents

0 BAlfson over 13 years ago

It sounds like they haven't completed their work and that the only IP correctly routed is the primary one.

Cheers - Bob

Sophos UTM Community Moderator
Sophos Certified Architect - UTM
Sophos Certified Engineer - XG
Gold Solution Partner since 2005

MediaSoft, Inc. USA
Cancel
Vote Up 0 Vote Down

Cancel
0 netfreak over 13 years ago in reply to BAlfson

I will check with them further about that. The syntax used to create this static route on their Cisco 6509 was:

ip route a.a.a.a 255.255.255.240 b.b.b.b (where b.b.b.b is the existing routed WAN IP of the UTM)

My company does identical deployments but using Cisco Nexus routers so the syntax we use is:

ip route a.a.a.a/28 b.b.b.b
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 netfreak over 13 years ago in reply to BAlfson

I will check with them further about that. The syntax used to create this static route on their Cisco 6509 was:

ip route a.a.a.a 255.255.255.240 b.b.b.b (where b.b.b.b is the existing routed WAN IP of the UTM)

My company does identical deployments but using Cisco Nexus routers so the syntax we use is:

ip route a.a.a.a/28 b.b.b.b
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data