Using PBR you're setting the way traffic leaves your network (i.e. from client to server). Return traffic will follow path what your upstream routers think will lead to your client. So if packets leave with unmodified IP address that routed from your provider over your T1 interface, then traffic from server will return over T1 link.
Your access-list 100 matches only FE0/0 address, so only traffic sources from IP of FE 0/0 (literally single IP that configured on FE 0/0) will be NAT'ed to Dialer1 address, however all PC behind your router will not be NAT'ed. I'd allow everything that goes out of that interface to be NAT'ed.
This appears the only reason why your HTTP traffic returns over main line. Change access-list 100 appropriately and all should work.
So you need to ensure that packets leave with source IP that would lead return traffic back over the same interface. One possibility is to apply NAT to such client connections, so the source of the packets is modified to become WAN IP of your DSL link.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...