Multiple adsl links

[mike.f]

I have a 3725 router with 3 seperate atm interfaces connecting to 3 seperate ADSL lines all supplied by the same ISP each ADSL line has a static IP address and all the lines are on the same PVC. I want to use one line for internet access and the other two for point to point. I have setup three virtual-templates and associated each ATM interface with a virtual-template. My problem is the default gateway, when the router boots it sets up three virtual-access interfaces one for each virtual-template., the next hop router is the same on each virtual-access, when my router boots it associates this next hop router as directly connected with the first virtual-access interface to get established. So if i use this next hop router as my default gateway and the internet virtual-access interface is not first to be established, it will send the data out the wrong interface. I have tried putting the default-gateway as the virtual-template but this doesn't seem to work. Anyone come across this or am i doing something silly?

[mike.f]

I think i've sussed this by using ACL's on the interfaces to limit what traffic's allowed where. Sometimes a fresh mind in the morning is what you need. I'm new to this so any info is welcome as i probably going about it the wrong way!

[dinekal]

Hi ,

Yes you need access-list but at different scenario. I suggest you to use PBR (Policy Based Routing).

This is source based routing technique, allows you which subnet should take which gateway. These URLs would address your requirement

http://www.cisco.com/warp/public/cc/techno/protocol/tech/plicy_wp.htm

http://www.cisco.com/en/US/tech/tk826/tk365/technologies_tech_note09186a008009481d.shtml

Good Luck,

Dinesh.K

[mike.f]

Thanks for that Dinesh, i found another solution as well that works, using dialer interfaces instead of virtual-template interfaces. With the dialer interfaces i can use the command "ip route 0.0.0.0 0.0.0.0 dialer1" which i couldn't with the virtual-templates. So now i can direct traffic via interfaces rather than next hop router which solves my problem.