12-09-2013 12:04 PM
I have a remote vpn configured that I can connect to with my laptop. The switch the firewall is connected to has a few vlans on it, all of which except one is accessible from the vpn client just fine. The one that isn't is the same network as what the management interface of the ASA is connected to. My assumption is that the vpn is trying to route through the management interface when I'm trying to access something else on that network from my vpn client. Does that sound right? How can I get it to either not do that or make it so I can access that network from the vpn client?
Accessible networks:
10.28.1.0
10.28.200.0
etc
Inaccessible network
10.28.199.0
Thanks!
Config of the ASA.
dmh01-5510asa# sh run
: Saved
:
ASA Version 8.2(5)
!
hostname dmh01-5510asa
names
!
interface Ethernet0/0
nameif inside
security-level 100
ip address 10.28.194.2 255.255.255.252
!
interface Ethernet0/1
description main internet connection
nameif outside
security-level 0
ip address <outside ip> 255.255.255.248
!
interface Ethernet0/2
description backup internet
nameif backup
security-level 0
ip address <backup ip> 255.255.255.240
!
interface Ethernet0/3
nameif dmz
security-level 50
ip address <dmz ip> 255.255.255.0
!
interface Management0/0
nameif management
security-level 100
ip address 10.28.199.11 255.255.255.0
management-only
!
banner login Authorized Use Only
ftp mode passive
clock timezone PST -8
clock summer-time PDT recurring
object-group service DM_INLINE_TCP_1 tcp
port-object eq 3389
port-object eq 5010
port-object eq 7051
port-object eq 7777
port-object eq 9000
port-object eq 9003
port-object eq ftp
port-object eq www
port-object eq https
port-object eq ftp-data
port-object eq ssh
object-group service lacerte_tax tcp
port-object eq 10010
port-object eq 10020
port-object eq 10030
port-object eq 10040
port-object eq 10050
port-object eq 10051
port-object eq 10052
port-object eq 10060
port-object eq 10070
port-object eq 10099
object-group network DM_INLINE_NETWORK_1
network-object host <dns>
network-object host <dns>
network-object host <dns>
network-object host <dns>
object-group service DM_INLINE_SERVICE_1
service-object tcp eq domain
service-object udp eq domain
object-group network DM_INLINE_NETWORK_2
network-object host 10.28.15.10
network-object host 10.28.15.11
object-group network DM_INLINE_NETWORK_3
network-object host 10.28.15.10
network-object host 10.28.15.11
object-group service DM_INLINE_TCP_2 tcp
port-object eq 5061
port-object eq 5062
port-object eq sip
object-group network DM_INLINE_NETWORK_4
network-object host <outside>
network-object host <outside>
access-list inside_access_in extended permit ip 192.168.28.0 255.255.255.0 any log warnings
access-list inside_access_in extended permit ip 10.28.32.0 255.255.255.0 any log warnings
access-list inside_access_in extended deny tcp object-group DM_INLINE_NETWORK_3 any object-group DM_INLINE_TCP_2 log warnings
access-list inside_access_in extended permit ip 10.0.0.0 255.0.0.0 10.254.28.0 255.255.255.240
access-list inside_access_in extended permit ip object-group DM_INLINE_NETWORK_2 any log warnings
access-list inside_access_in extended permit tcp 10.28.0.0 255.255.0.0 any object-group DM_INLINE_TCP_1 log warnings
access-list inside_access_in extended permit tcp 10.28.0.0 255.255.0.0 198.31.208.128 255.255.255.224 object-group lacerte_tax log warnings
access-list inside_access_in extended permit object-group DM_INLINE_SERVICE_1 host 10.28.200.10 object-group DM_INLINE_NETWORK_1 log warnings
access-list outside_access_in extended permit tcp any host <outside> eq 3389 log disable inactive
access-list outside_access_in extended permit ip any object-group DM_INLINE_NETWORK_4 log warnings
access-list RemoteAccess_splitTunnelAcl standard permit 10.0.0.0 255.0.0.0
access-list inside_nat0_outbound extended permit ip 10.0.0.0 255.0.0.0 10.254.28.0 255.255.255.240
access-list inside_nat0_outbound_1 extended permit ip 10.0.0.0 255.0.0.0 10.254.28.0 255.255.255.240
pager lines 24
logging enable
logging list acl-drop message 106023
logging asdm acl-drop
mtu inside 1500
mtu outside 1500
mtu dmz 1500
mtu management 1500
mtu backup 1500
ip local pool vpn_ip_pool 10.254.28.0-10.254.28.10 mask 255.255.255.0
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm history enable
arp timeout 14400
global (inside) 201 interface
global (outside) 101 interface
global (dmz) 101 interface
global (backup) 101 interface
nat (inside) 0 access-list inside_nat0_outbound_1
nat (inside) 101 192.168.28.0 255.255.255.0
nat (inside) 101 10.28.0.0 255.255.0.0
static (inside,outside) <outside> 10.28.15.10 netmask 255.255.255.255
static (inside,outside) <outside> 10.28.15.11 netmask 255.255.255.255
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route outside 0.0.0.0 0.0.0.0 <outside> 1 track 1
route backup 0.0.0.0 0.0.0.0 <backup> 254
route management 10.0.0.0 255.0.0.0 10.28.199.1 1
route inside 10.28.0.0 255.255.0.0 10.28.194.1 1
route inside 192.168.28.0 255.255.255.0 10.28.194.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
aaa authentication enable console LOCAL
http server enable
http server idle-timeout 60
http 10.0.0.0 255.0.0.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
sla monitor 100
type echo protocol ipIcmpEcho 74.125.239.16 interface outside
num-packets 3
frequency 10
sla monitor schedule 100 life forever start-time now
crypto ipsec transform-set ESP-3DES-SHA esp-3des esp-sha-hmac
crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac
crypto ipsec transform-set ESP-DES-SHA esp-des esp-sha-hmac
crypto ipsec transform-set ESP-DES-MD5 esp-des esp-md5-hmac
crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac
crypto ipsec transform-set ESP-3DES-MD5 esp-3des esp-md5-hmac
crypto ipsec transform-set ESP-AES-256-SHA esp-aes-256 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-SHA esp-aes esp-sha-hmac
crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac
crypto ipsec transform-set ESP-AES-128-MD5 esp-aes esp-md5-hmac
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set pfs
crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 set transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA ESP-3DES-MD5 ESP-DES-SHA ESP-DES-MD5
crypto map outside_map 65535 ipsec-isakmp dynamic SYSTEM_DEFAULT_CRYPTO_MAP
crypto map outside_map interface outside
crypto isakmp enable outside
crypto isakmp enable dmz
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash sha
group 2
lifetime 86400
!
track 1 rtr 100 reachability
telnet timeout 5
ssh 10.0.0.0 255.0.0.0 management
ssh timeout 60
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
ntp server 10.200.1.41 source management
webvpn
group-policy RemoteAccess internal
group-policy RemoteAccess attributes
dns-server value 10.28.200.10 8.8.8.8
vpn-filter value RemoteAccess_splitTunnelAcl
vpn-tunnel-protocol IPSec
split-tunnel-policy tunnelspecified
split-tunnel-network-list value RemoteAccess_splitTunnelAcl
default-domain value
split-tunnel-all-dns disable
vlan none
tunnel-group RemoteAccess type remote-access
tunnel-group RemoteAccess general-attributes
address-pool vpn_ip_pool
default-group-policy RemoteAccess
tunnel-group RemoteAccess ipsec-attributes
pre-shared-key *****
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
inspect pptp
!
service-policy global_policy global
prompt hostname context
no call-home reporting anonymous
12-10-2013 09:36 AM
Management interfaces doesnt allow routing.
Sent from Cisco Technical Support iPhone App
12-10-2013 09:43 AM
Hi Ryan,
if you want to reach destinations on the interface management 0 you just have to remove "management-only" command from the config. Just make sure that your NAT policies allow communication between the VPN and interface m0.
And you should be aware, that you might loose security if you allow routing and firewall functionality on m0.
Rgds,
MiKa
12-10-2013 09:55 AM
Thanks for the replies. However I think my question was misunderstood.
I am not looking to route traffic through the management interface. The problem is that I think traffic is trying to route through the management interface and I don't want it to.
My issue is that over the VPN connection, I can see everything I want to on my remote network EXCEPT the network that is attached to the management interface. So, my guess is that the firewall is trying to route the VPN through the management interface to get to that network for some reason. I don't want it to do that, so I can access that management network from the VPN also.
Thanks
Sent from Cisco Technical Support iPhone App
12-10-2013 10:05 AM
Hi Ryan,
As the mgmt interface with 10.28.199.x/24 pops up in ASA routing table as directly connected, that will always be preferred route. I believe, if you add host specific routes to inside (ex: 10.29.199.20 255.255.255.255
Thx
MS
12-10-2013 10:41 AM
Ok, I could give that a try. Kind of messed up that it's doing that, though. You would think that the "management only" command on that interface would prevent it from wanting to route traffic through it.
Thanks
Sent from Cisco Technical Support iPhone App
12-10-2013 12:04 PM
Hi Ryan,
don't be too hasty about "messed up": IP addressing has to be unique for a good reason, the routing table. Even if the ASA will not route "data plane traffic" to and from the mgmt interface it has to be in the routing table so that the ASA can determine the outbound interface. That's how IP works. And a connected interface always has precedence over entries in the routing table.
I would strongly recommend to configure a new address on the managment interface (and also on all management stations on that segment) if it collides with one of your production networks.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: