Bookmark this page:
Yahoo!
Windows Live
del.icio.us
digg
Netscape
|
|
|||||||||||||
|
Posted by HangaS on May 8, 2008, 11:01 am
Please log in for more thread options I'm trying to create some rules to route trafic to some GW depending either on the source address or destination address For the source address matching I can use route-maps access-list 1 permit x.x.1.1 0.0.0.0 access-list 1 permit x.x.1.4 0.0.0.0 access-list 1 permit x.x.1.3 0.0.0.0 access-list 1 deny any route-map SERVER permit 10 match ip address 1 set ip next-hop x.y.z.254 and then apply this map to the interface now, for the destination matching the only way I could get it to work is through static routing ip route a.b.c.d1 255.255.255.255 x.y.z.254 ip route a.b.c.d2 255.255.255.255 x.y.z.254 ip route a.b.c.d3 255.255.255.255 x.y.z.254 ip route a.b.c.d4 255.255.255.255 x.y.z.254 Ok this solves it for now, but what I realy wanted was to use some sort of access lists for both destination or origin (I can live with a list for IN and other for OUT) but wanted to be able to apply it to a single interface, which is not possible with global static routing. Any tips on can I do this? Thanks | |||||||||||||
|
Posted by HangaS on May 8, 2008, 5:41 pm
Please log in for more thread options I got it. I guess I was just needing a break after fighing with the thing for hours trying many stratagies in the wrong direction. extendend access-list were real friends in this case. | |||||||||||||

route-maps (again)
Yahoo!
Windows Live
del.icio.us
digg
Netscape 

