I'm trying to configure split tunneling on a site to site vpn connection using an ASA 5505 at the remote site and a 5520 at the HQ site.
The tunnel is established and both inside networks can communicate but I want users at the remote site to use thier local ISP for internet.
In the ASDM 6.4 I browsed to "Remote Access VPN" and selected "Group Policies" under the "Network (Client) Access" drop down. From there I selected my tunnel group policy, selected edit and under the "Advanced", "Split Tunneling" I de-selected the "Inherit" checkboxes on "Policy" and "Network List".
In the "Policy" drop down I selected "Exclude Network List Below" and in the "Network List" drop down I created an extended ACL with two ACE's. One allowing ANY ANY on http and another allowing ANY ANY on https. I named that ACL "Split_Tunnel" and then selected that name under the "Network List" drop down.
I'm missing something because this in itself doesn't allow clients behind the ASA to get internet access.
I should also mention that the remote site is using DSL with a static IP and the modem is configured with DMZ hosting to pass that public IP over to the outside interface of the ASA. The ASA's outside interface is pulling a DHCP address from the DSL modem and the modem is NATting the traffic between the private IP handed to the ASA and the public IP forwarded from the modem.
As I said, both inside networks on the local and remote inside LAN's are communicating. I just cant get the users of the remote network to use the DSL for internet access.
I think I got it now. The new NATing is taking me a little bit of getting used to but it's making more sense. The concept of object oriented NAT statements within the context of the object configuration is what threw me.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...