11-22-2011 10:48 AM - edited 03-04-2019 02:22 PM
Hello,
I seem to be having an issue with Policy Based Routing on a Dialer interface. I have the following two setups:
A. Cisco router with ADSL WIC - relevant configuration information
interface ATM0/0/0
no ip address
no atm ilmi-keepalive
pvc 0/35
pppoe-client dial-pool-number 1
interface FastEthernet0/1
ip address x.x.x.x x.x.x.x
ip nat inside
ip policy route-map dialer1-access
interface Dialer1
ip address negotiated
ip nat outside
encapsulation ppp
dialer pool 1
route-map dialer1-access permit 10
match ip address acl_dialer1_permit
set default interface Dialer1
B. Cisco router Ethernet interface connected to DSL modem via switch - relevant configuration information
interface GigabitEthernet0/2.220
encapsulation dot1q 220
pppoe enable
pppoe-client dial-pool-number 10
interface GigabitEthernet0/1
ip address x.x.x.x x.x.x.x
ip nat inside
ip policy route-map dialer10-access
interface Dialer10
ip address negotiated
ip nat outside
encapsulation ppp
dialer pool 10
route-map dialer10-access permit 10
match ip address acl_dialer10_access
set default interface Dialer10
There is no static default route (ip route 0.0.0.0 0.0.0.0) on either setup. Setup A works for me successfully. As configured, setup B does not seem to correctly 'route' the traffic (connection fails)? If I add the following command to the Dialer interface,
ppp ipcp route default
then connections succeed but I believe this is because there is now a static default route installed which I don't want.
Questions:
1. Is there a way around this?
2. Is this behaviour different when using PPPoE vs ATM?
Thanks,
Mike