Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ip route headache :-(

Status
Not open for further replies.

TalentedFool

Programmer
Joined
Jul 23, 2001
Messages
214
Location
GB

I've got two outside interfaces in my 1750 router(broadband and ADSL)

my IP route list looks like

ip route 0.0.0.0 0.0.0.0 80.10.1.2
ip route 172.30.212.1 255.255.255.0 80.10.1.2
ip route 182.40.110.1 255.255.255.0 81.20.1.1

If I remove the 'ip route 0.0.0.0 ...' line no traffic gets out. Why?

I want to be able to choose which route to take not just throw is all down the one!

HEEEEEELLLPPP!!!!!


~ Remember - Nothing is Fool Proof to a Talented Fool ~
 
That 'IP route 0.0.0.0 0.0.0.0 80.10.1.2' route statement is you're default route statement. In other words, any attempt to going any where that is not specifically defined by another route will you this one. So far all you have is 2 networks defined to 2 separate interfaces. If you have this router accessing other networks ie internet, you would need either your default route or statically define each route.
 
Try this:

ip route 172.30.212.0 255.255.255.0 80.10.1.2
ip route 182.40.110.0 255.255.255.0 81.20.1.1
ip route 0.0.0.0 0.0.0.0 80.10.1.2


By using the network addresses (zero in the last octet, based on your subnet mask), you will be able to route any ip address that has the first three octets the same.

The last octect can be anything between 1 and 254, on either subnet.

Any traffic that is destined for either the 172 or 182 network will be routed by the router, all other traffic that is destined for an unknown IP, (anything not directly connected or learned through a routing protocol) will be sent out the 80.10.1.2 interface.

You just have to take the last octet and set it for the netowrk address, in your case, it's zero.

Your network sounds pretty simple with just two subnets, connected via one router. You don't require a routing protocol. The above commands will resolve your routing issue for your subnets.

Ensure that the 80.10.1.2 interface is in fact connected to the WAN or you won't route the internet as the internet addresses will be unknown to your router.

Good Luck.
 
As you already have a default route via 80.10.1.2, you don't need the additional route 'ip route 172.30.212.0 255.255.255.0 80.10.1.2' as this will be matched by the default route. You can get away with ..

ip route 182.40.110.0 255.255.255.0 81.20.1.1
ip route 0.0.0.0 0.0.0.0 80.10.1.2

Chris.


**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************
 

OK, I tired that .. but when I enter:

conf t <enter>
ip route 182.40.110.0 255.255.255.0 81.20.1.1 <enter>
ip route 0.0.0.0 0.0.0.0 80.10.1.2 <enter>


I get

ip route 0.0.0.0 0.0.0.0 80.10.1.2
ip route 182.40.110.0 255.255.255.0 81.20.1.1

from a show run, which to me - says go to the first in the list e.g. 80.10.1.2 for any IP.



~ Remember - Nothing is Fool Proof to a Talented Fool ~
 
It doesn't matter what order the IP route is in...

All that matters is that it matches something, if you want a preference of one or another, then you need to adjust the router metric weighting...

BuckWeet
 
Route statments don't work like access lists, first match from top to bottom. Do a 'sh ip route' and you will see that you have the correct route to 182.40.110.0 /24.

Chris.

**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************
 

Thanks guys!!! Think I've got that one sorted out!

Have posted another one with my config and the headaches that I've got with ADSL :-(

All you're help is appreciated though!

~ Remember - Nothing is Fool Proof to a Talented Fool ~
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top