static routes need some input (policy based routing was the fix) solved
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 09:18 AM - edited 03-04-2019 01:02 PM
hi need some help with static routes.
i have 2 connections a single T1 for voip traffic only and a DSL line for data traffic.
the dsl was migrated to a 2811 with out any issues now comes the time to move the T1 over.
on the T1 side I am able to ping the WAN router and the LAN router IP address but nothing behind it.
currently this is the only statment on the router:
ip route 0.0.0.0 0.0.0.0 Dialer1
as a quick a dirty to remove the above i tried:
no ip route 0.0.0.0 0.0.0.0 Dialer1
ip route 66.55.110.0 255.255.255.0 Dialer1
but the DSL side dropped. we have a 66.55.110.152/29
for the T1 i would use the following statement.. we have a 209.98.53.192/27
ip route 209.98.53.0 255.255.255.255 65.32.70.177
thanks
- Labels:
-
Other Routing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 09:25 AM
Jeremy
It's not clear from your description exactly what you are trying to do.
What are you trying to add routes to ?
If you have a default-route pointing out of the dialer1 interface ie. you DSL then what route do you need for VOIP. If you have 2 default-routes then the router will use them both and you may get VOIP traffic going out of the DSL and data traffic out the T1.
You may well need to do PBR (Policy Based Routing) to get the traffic to go where you need it but we need to understand more about what you are trying to do ie.
1) what IP addresses are you trying to route
2) where are you trying to route them to
etc...
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 09:31 AM
jon,
the 2811 will route the t1 traffic and dsl traffic no nat'ing on the edge.
right now only the DSL is on the 2811 when i tried to get the T1 online only was able to ping the WAN and LAN ips to the router not the voip server it self.
66.55.110.152/29 out the DSL (dialer)
209.98.53.192/27 out the T1 Next hop is 65.32.70.177
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 09:34 AM
66.55.110.152/29 out the DSL (dialer)
209.98.53.192/27 out the T1 Next hop is 65.32.70.177
so are the above the remote networks you are trying to get. That's the key. Because out the DSL interface i suspect you have internet access ? so you would need -
ip route 0.0.0.0 0.0.0.0 dialer1
if so then what network(s) are you trying to get down the T1 line ?
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 09:44 AM
correct to get internet access right now ip route 0.0.0.0 0.0.0.0 dialer1 is being used.
i would say the only networks out the t1 line would be 209.98.53.192/27
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 09:46 AM
if that's the case simply add this route -
ip route 209.98.53.192 255.255.255.224 65.32.70.177
and leave the default-route pointing out of the dialer1 interface.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 10:01 AM
would it make a differance if i tried
ip route 209.98.53.0 255.255.255.255 65.32.70.177
over
ip route 209.98.53.192 255.255.255.224 65.32.70.177
since my morning has started i cant make any changes but i tried using 209.98.53.0 255.255.255.255 65.32.70.177 without success.
I find it odd I was able to ping the WAN and LAN router but not out bound on the 209.98.53.192/27
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 10:04 AM
You need to use the actual subnet mask and not 255.255.255.255 because that doesn't make sense.
If it's not working anyway could you not just add the new route. As long as you leave the default-route out of the dialer1 interface you should be fine.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 10:11 AM
your right about not making sense hoping by sheer luck it would and something else is missing.
i added the route statement and i hope to give it a go later on.
would it be better to specify the netblock on the dsl side vs 0.0.0.0 0.0.0.0 Dialer1 ?
thank you for your insight so far!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 10:15 AM
You can't use the netblock on the dialer interface because the destination IPs could be anything if this is an internet connection.
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-20-2011 10:51 AM
looks like i might have a window to swap the cables is this saturday sooner if i can beat traffic in the mornings.
thanks again
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-28-2011 10:57 AM
hey jon,
gave it a go this morning didnt work out as planned.
called the ISP and they gave me the right encapsulation ppp not hdlc tho i asked 6 times... lovely xo.
if you have a moment... http://pastebin.com/5MeLJ5Ji might you check what i have wrong?
i moved the cables over to the cisco, checked for up/up everything looks OK then tried some pings nothing was working.
from the LAN side i cant ping the cisco gateway tho from the dsl side i can.
i think the route statments are tossing up the curve ball here.
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2011 03:36 PM
the fix to my issue was....
access-list 1 permit any
!
route-map T1_routes permit 10
match ip address 1
set ip next-hop 65.32.70.177
!
