Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello,I have a question regarding use of rsa key pairs for authentication when setting up IPsec tunnels.I have a head-end router and multiple remote routers which are administered by multiple third parties.I want to setup a different key pair on my h...
I have a WAN link between two IOS routers that will be encrypting all traffic via IPsec. I need to prioritise traffic across this link.I'm aware of two methods I can use:a) priority queuing and qos pre-classifyb) manipulation of diffserv bits (TOS) a...
A client we wish to connect to requires an IPsec link that uses AES256 encryption.If I search for AES256 on CCO I get responses for PIX and 3000 series, but nothing for IOS.Is there any plan for AES256 support in IOS?Thanks in advance for any assista...
Hi,I'm running IOS c1700-k9o3sy7-mz.123-3.bin IP/ADSL/FW/IDS PLUS IPSEC 3DES on model 1760 router.The above configuration is inserted automatically into the running config. When the config is saved and the router rebooted, the config line is rejecte...
I have two IOS routers and would like to use the loopback address on the remote router as the peer address as recommended in papers such as "Configuring IPSec with EIGRP and IPX Using GRE Tunneling".On the local router, I identify the remote router v...
Thanks for that.I've worked out how I can set IP Precedence bits on the ingress of the IOS12.1 router via route-map, however, I don't know how to manage the traffic on the egress interface, given that all traffic is within an IPsec tunnel, and I cann...
I raised a TAC case on this yesterday given no solution from the CCO forum. The Case is E521810 and the initial response from the TAC engineer is the following:Request for feature was submitted in CSCin46441 - BREAK signal support for SSH . Des...
Thanks,You were correct. The problem turned out to be a configuration issue at the remote router. There was no ppp chap password config line. Once this was installed, ppp authentication succeeded.
A minimum 76 seconds elapsed (time between keepalive configuration completed and latest log entry) before I issued the sho ip route command and saw the bad route still in the table.
