I did some more research. Using radius, the issue doesnt happen. I tested cisco av pairs
auth-proxy:priv-lvl=15 auth-proxy:proxyacl#1=permit ip any any as well as shell:priv-lvl=15 shell:proxyacl#1=permit ip any any and http and telnet both works fine. With Tacacs though, I am still having the issue. To recount, the issue is , if in services, while adding auth-proxy, if protocol ip is added, http proxy doesnt work and telnet proxy works, and if protocol field is left blank, http proxy works and telnet doesnt. Waiting for a feedback from you guys:) Regards On Mon, Mar 15, 2010 at 11:22 AM, Badar Farooq <[email protected]>wrote: > I am having a strange issue. > Using Auth proxy with tacacs+, if I use service auth-proxy without > mentioning the protocol, http proxy works fine. But telnet proxy doesnt > work. > Similarly, I enable auth-proxy with ip protocol, telnet proxy works fine > but http proxy doesnt work. > > Ironically, If i add two proxy services, auth-proxy with protocol ip and > then without it, even then one of the two works are any given time. > > I dont understand it. Looking forward to some feedback... > > Regards > Badar >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
