remote network unreachable to Anyconnect clients

cn flag

I have a Cisco 5516 ASA that serves as the VPN Gateway for Anyconnect clients. If I connect to the Anyconnect VPN the ASA will assign me an address in the subnet and that allows me to communicate on our trusted internal networks. Recently we added a remote site with a UDM-PRO that connects to the 5516 ASA via a site to site ipsec tunnel. Anyconnect clients are unable to "talk" to the new remote site. Users inside the trusted network (with normal inside network IP's) have full communication with the remote site, but external users who connect to the network via Anyconnect do not. Is it even possible to configure things to enable the Anyconnect clients to reach the remote site? I'm questioning if it's even possible because it seems to be a tunnel within a tunnel. The Anyconnect client is connected to the ASA via a VPN tunnel and then the ASA and UDM-PRO are connected with a separate ipsec VPN tunnel. Seems messy to me. If it is possible, I would be grateful for some help.

I sit in a Tesla and translated this thread with Ai:


Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.