asked on

CISCO ASA 5510 Lan to Lan split tunnel

Howdy Folks,

I'm stuck with an irritating problem, far away from home and help.

I want the remote computers at the far end of an IPSEC LAN to LAN tunnel to be able to get directly to the internet, bypassing the tunnel.

I have my config for the remote end below, at the moment everything is working but the internet access. We have a proxy issue that needs more firewall holes created for a permanent solution, but if I can't get this sorted before the users get back then they will revolt.

Any questions or suggestions I will be monitoring the thread and will answer as soon as possible.

Cheers

Ash asa-as-at-monday-night---ready-f.txt

InfrastructureBAI

ASKER

some more details, I am suffering from severe lack of sleep and pizza.

The local pcs are all on CCC.CCC.202.0 255.255.255.0
the asa has an inside address of CCC.CCC.202.1 and an outside of AAA.AAA.221.133
and the other main address range is the end at the head office: BBB.BBB.31.234

We had planned for the internet traffic to hit the proxy server at CCC.CCC.202.200, then to go through the tunnel and head to our regular internet gateway address, but this doesn't want to work. For interests sake the regular internet gateway address is CCC.CCC.122.254.

I have the head office address range being CCC.CCC.0.0/16 and the remote end is CCC.CCC.202.0/24

I am open to any suggestions and will try just about anything, but my proxy guy is asleep, and our gateway company has stopped working on the problem for the night so I can only really change things on the asa's at either end (I can citrix back to our head office and change the ASA there if need be.

Both ASA's are 5510's.

Cheers

Ash

Fidelius

Hello,

To be able have access to internet from that ASA, you need global NAT command:
global (outside) 1 AAA.AAA.221.133

This way, you will be able to go directly to internet from remote site.
Current configuration doesn't allow internet access even in case you don't have tunnel.

Regards!

InfrastructureBAI

ASKER

Howdy,

Thanks for your response,

I have tried to add that and get " AAA.AAA.221.133-AAA.AAA.221.133 overlaps with outside interface address.

I have tried changing the address to the default gateway, without success. Any thing else you can see im missing?

Cheers Ash

InfrastructureBAI

ASKER

howdy again, I just had a thought and took down my tunnel, but it still won't allow direct access to the net.

I think I'm missing something to tell it to avoid trying the tunnel all together, but I can't work out what.

Cheers

Ash

Fidelius

Also, I forgot to mention, you will have to change crypto access list to:
access-list 100 extended permit ip SITENAME 255.255.255.0 CCC.CCC.0.0 255.255.0.0

You will also need to modify routing for networks on head site.

For proxy scenario you originally planned, you will have to change crypto access list to:
access-list 100 extended permit ip host CCC.CCC.202.200 any
access-list 100 extended permit ip SITENAME 255.255.255.0 CCC.CCC.0.0 255.255.0.0

and also need to configure default route to internet gateway address:
route outside 0.0.0.0 0.0.0.0 CCC.CCC.122.254 1

Regards!

Fidelius

Try this for global:

global (outside) 1 interface

Regards!

ASKER CERTIFIED SOLUTION

Fidelius

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

InfrastructureBAI

ASKER

worked when global (outside) 1 interface was added to config.