Am I in over my head......

[toddyboman]

I have read a ton of stuff on this forum....WOW....great work by everyone contributing...

My initial question is how should I go about learning/familiarizing myself on how to properly configure cisco products?

Here is what I want to do with what I have.

I have a one asa 5510 and three asa 5505.  The goal is to have the asa 5510 at our main office then the 5505 at each remote office.  Then establish a vpn connection to the server at the main office.

I HAVE ZERO cisco experience.....and only know the basics in network.  So am I way in over my head or can make this happen????

So far I have bridged my isp provided modem to my asa 5510.  On the asa 5510 I have established my outside and inside interfaces.  But I have not been able to establish a simple internet connection thru the asa 5510.....

Any help and suggestions is greatly appreciated.

Thanks!

[toddyboman]

sounds good....

So the default gateway for my isp router is 192.168.1.1.  So this should be the default gateway i should input?

As for configuring dhcp or ppoe I would set this on the outside interface or configure a new interface?

Can I set up ppoe with my verison of asa......My asa version is 7.0(8).......I thought I read somewhere I could only do ppoe for 8.X????

Thanks again!

[Jitendriya Athavale]

since it is a new setup i would recommend you go to the atleast 8.x code, bcoz 7.08 is ancient

coming back to the default gateway question let m egive you an example

if this is your interface ip

asa55(config-if)# ip address 212.115.192.x 255.255.255.248
asa55(config-if)# nameif outside
INFO: Security level for "outside" set to 0 by default.

asa55(config-if)# exit

your default gateway would be the following (basically in the same subnet)

asa5505(config)# route outside 0.0.0.0 0.0.0.0 212.115.192.y

from what you have sent me it looks like your modem has an internal ip in 192.168.1.x range and it is doing natting

so you need to put an ip to the outside interface in the same subnet and give it as the default gateway

asa-----------------------------isp modem/router--------------------------

       192.168.1.x          192.168.1.1                      public ip

correct me if this setup is wrong

[toddyboman]

jathaval wrote:
since it is a new setup i would recommend you go to the atleast 8.x code, bcoz 7.08 is ancient 

WHY did i not do this update earlier......WOW. 

jathaval wrote:
coming back to the default gateway question let m egive you an example
if this is your interface ip

asa55(config-if)# ip address 212.115.192.x 255.255.255.248
asa55(config-if)# nameif outside
INFO: Security level for "outside" set to 0 by default.

asa55(config-if)# exit
your default gateway would be the following (basically in the same subnet)

asa5505(config)# route outside 0.0.0.0 0.0.0.0 212.115.192.y
from what you have sent me it looks like your modem has an internal ip in 192.168.1.x range and it is doing natting
so you need to put an ip to the outside interface in the same subnet and give it as the default gateway
asa-----------------------------isp modem/router--------------------------
       192.168.1.x          192.168.1.1                      public ip
correct me if this setup is wrong

YES my asa is 192.168.1.x

Yes my isp/modem/router is 192.168.1.1

Then my isp has provided me with 2 static ips......we will call them 111.111.111.111 and 222.222.222.222

WOW really missing the boat on this default gateway.......

BEFORE I started this project a simple ipconfig on any machine shows a default gateway of 192.168.1.1....which is the ip of my isp/modem/router......

My isp guys say that gateway is my first static ip.........so IF i configure my outside interface as a ppoe and make it obtain an IP using ppoe then will I make my gateway my first static ip (111.111.111.111).......

[Jitendriya Athavale]

if you configure your asa to get ip from pppoe you can also configure it such that it gets its default gateway from th eisp rputer

so we wont have to bother about default gateway as the modem is going to puch it

if you using static's ip's (which is the current setup), then change the default gateway to 192.168.1.1

and you should be up and running

also when you say you connect your PC to this mdem your PC gets an ip with defaukt gateway as 192.168.1.1, it gives me a feeling that your modem is behaving like a dhcp server

[toddyboman]

Thanks again for all your help.......

jathaval wrote:
also when you say you connect your PC to this mdem your PC gets an ip with defaukt gateway as 192.168.1.1, it gives me a feeling that your modem is behaving like a dhcp server

My modem does have a dhcp option.....should this be diabled?

here is my current config......with my router NOT bridged........giving my asa outside interface a static IP.......no PPOE configurations on my ASA.........

: Saved
:
ASA Version 8.0(5)
!
hostname L
domain-name default.domain.invalid
enable password m encrypted
passwd U encrypted
names
dns-guard
!
interface Ethernet0/0
nameif outside
security-level 0
ip address 111.111.111.111 255.255.255.252
!
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.10.1 255.255.255.0
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.5 255.255.255.0
management-only
!
ftp mode passive
clock timezone CST -6
clock summer-time CDT recurring
dns server-group DefaultDNS
domain-name default.domain.invalid
pager lines 24
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu management 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-631.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 192.168.1.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
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
http server enable
http 192.168.1.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd dns 192.168.10.1
!
dhcpd address 192.168.10.5-192.168.10.25 inside
!
dhcpd address 192.168.1.6-192.168.1.10 management
dhcpd enable management
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
username admin password vx8BkOWfWwvYuBKw encrypted
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns migrated_dns_map_1
parameters
  message-length maximum 512
policy-map global_policy
class inspection_default
  inspect dns migrated_dns_map_1
  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 icmp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:6db9429f9cba9424fccd50647514ae9a
: end
asdm image disk0:/asdm-631.bin
no asdm history enable

According to the ARP table on the ASDM some of my office pc's where connected to the mgmt interface.....and not the inside interface.  (Which I thought was odd?)  ........but those pc's couldn't establish an internet connection.....

[Antonio Knox]

toddyboman,

From what I see, you seem to have an ASA behind a DHCP-serving DSL modem.  In this case, you should be able to configure (update) your outside interface as a dhcp client and take out all of the guesswork with trying to address your outside interface and to figure out what your default route should be and such (let dhcp do it for you):

no route outside 0.0.0.0 0.0.0.0 192.168.1.1 1

interface Ethernet0/0
nameif outside
security-level 0
no ip address 111.111.111.111 255.255.255.252
ip address dhcp setroute

Also, I've gotta ask what the point is of this:

dhcpd address 192.168.1.6-192.168.1.10 management
dhcpd enable management

You have enabled your management port as a DHCP server.  If this was not your intention, which I'm certain it isn't ;), the two dhcpd lines above should be removed (leave the dhcpd address inside as it is).   Finally, if your PCs are arping up on your management port, you should  take that cable plugged into management (which from the sound of it goes to your switch) and plug it into Ethernet0/1, which is your inside interface (where your user PCs belong).  All should work after that.

Please rate my post if it helps.

[toddyboman]

dhcpd address 192.168.1.6-192.168.1.10 management
dhcpd enable management

Not sure the point of that.......In the craziness of trying to making this thing work I am sure got this going......

Should I have enabled dhcp on my inside interface?

  When I try to enable that I get the following error.......

      Dhcp:Interface "inside" is currently configured as CLIENT and cannot be changed to a SERVER by a SERVER feature

I am a bit confused on the arping with my mgmt port.....

Currently this pc I am using is plugged into my switch.
Then I have plugged my asa5510 mgmt port into my isp provided dsl modem/router.......

IF i unplug that then I won't have access to my asdm.....

My outside interface plugs into my my isp provided dsl modem/router

My inside interface plugs into my switch.

Thanks for your help!

[Antonio Knox]

According to your latest posted config, you already have dhcp server enabled on your inside interface.

dhcpd address 192.168.10.5-192.168.10.25 inside

As far as how things are wired, it should look something like this:

For internet connectivity

Internet------>DSL Modem-------->ASA Outside (E0/0)

Outside interface config:
interface Ethernet0/0
nameif outside
security-level 0
ip address dhcp setroute

For Internal network PC's
PC------>Internal Switch------>ASA Inside (E0/1)

Inside interface config (what you have here is good):
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.10.1 255.255.255.0

Now, you should be able to configure your management port with an ip in your Inside range (like 192.168.10.30 for instance) and can be plugged into your switch as well.  Not sure, but you can try it:

Management0/0------->Internal Switch

Management interface config:
interface Management0/0
nameif management
security-level 100
ip address 192.168.10.30 255.255.255.0
management-only

Make sure you've allowed ASDM access to your inside network

http 192.168.10.0 255.255.255.0 management
http 192.168.10.0 255.255.255.0 inside

As for DHCP, you should be good with what you have (minus the removals from my previous post):

dhcpd dns 192.168.10.1
dhcpd address 192.168.10.5-192.168.10.25 inside

Give this a try and let me know how it works for you.

Please rate my post if helpful.

[toddyboman]

antonioknox wrote:
Now, you should be able to configure your management port with an ip in your Inside range (like 192.168.10.30 for instance) and can be plugged into your switch as well.  Not sure, but you can try it:
Management0/0------->Internal Switch
Management interface config:
interface Management0/0
nameif management
security-level 100
ip address 192.168.10.30 255.255.255.0 
management-only
Make sure you've allowed ASDM access to your inside network
http 192.168.10.0 255.255.255.0 management
http 192.168.10.0 255.255.255.0 inside
     .

Not sure this is possible........
When I try to change the mgmt ip address I get:

Error: Failed to apply IP address to interface mgmt0/0, as the network overlaps with interface ethernet0/1.  Two interfaces cannot be in the same subnet.

here is my most current config......

: Saved
:
ASA Version 8.0(5)
!
hostname L
domain-name default.domain.invalid
enable password m encrypted
passwd m encrypted
names
dns-guard
!
interface Ethernet0/0
nameif outside
security-level 0
ip address dhcp setroute
!
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.10.1 255.255.255.0
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.5 255.255.255.0
management-only
!
ftp mode passive
clock timezone CST -6
clock summer-time CDT recurring
dns server-group DefaultDNS
domain-name default.domain.invalid
pager lines 24
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu management 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-631.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 192.168.1.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
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
http server enable
http 192.168.1.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd dns 192.168.10.1
!
dhcpd address 192.168.10.5-192.168.10.25 inside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
username admin password vx8BkOWfWwvYuBKw encrypted
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns migrated_dns_map_1
parameters
  message-length maximum 512
policy-map global_policy
class inspection_default
  inspect dns migrated_dns_map_1
  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 icmp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:3fd6c86d2cce815cffb5062f814d1b5c
: end
asdm image disk0:/asdm-631.bin
no asdm history enable

[Antonio Knox]

Copy/paste this to your config

This will ensure that you keep ASDM access, you'll just have to get to it through 192.168.10.1

no http 192.168.1.0 255.255.255.0 management
http 192.168.10.0 255.255.255.0 inside

Add this so that when we resolve the issue with the Management interface (which I think will require a router) you will have access from the inside network:

http 192.168.10.0 255.255.255.0 management

Go ahead and disconnect the Management0/0 from the Internal switch.

Before we troubleshoot further, make sure that these configs enable you to access the internet fom the PC, which should now be arping up on the inside interface if you cabled it according to spec.

[toddyboman]

How will copying and pasting that into my config file work......Don't those commands need to be inputed via CLI???

I think I input the commands correctly via CLI........There is my config file now...

: Saved
:
ASA Version 8.0(5)
!
hostname L
domain-name default.domain.invalid
enable password m encrypted
passwd m encrypted
names
dns-guard
!
interface Ethernet0/0
nameif outside
security-level 0
ip address dhcp setroute
!
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.10.1 255.255.255.0
!
interface Ethernet0/2
shutdown
no nameif
no security-level
no ip address
!
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
nameif management
security-level 100
ip address 192.168.1.5 255.255.255.0
management-only
!
ftp mode passive
clock timezone CST -6
clock summer-time CDT recurring
dns server-group DefaultDNS
domain-name default.domain.invalid
pager lines 24
logging asdm informational
mtu outside 1500
mtu inside 1500
mtu management 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-631.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 192.168.1.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:0
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
dynamic-access-policy-record DfltAccessPolicy
aaa authentication ssh console LOCAL
http server enable
http 192.168.10.0 255.255.255.0 inside
http 192.168.10.0 255.255.255.0 management
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd dns 192.168.10.1
!
dhcpd address 192.168.10.5-192.168.10.25 inside
!
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
username admin password vx8BkOWfWwvYuBKw encrypted
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns migrated_dns_map_1
parameters
  message-length maximum 512
policy-map global_policy
class inspection_default
  inspect dns migrated_dns_map_1
  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 icmp
!
service-policy global_policy global
prompt hostname context
Cryptochecksum:60d693c3586a102e5f989b7740fcee9e
: end

[Antonio Knox]

I assumed that it was understood that when I say 'paste into your config' that I meant the command line, as I've never heard of anyone pasting into a config file.  Perhaps I should have been a bit clearer?????

[Jitendriya Athavale]

ok use this

ExampleASA(config-if)#interface e0/0

ExampleASA(config-if)# ip address dhcp setroute
ExampleASA(config-if)# nameif outside

ExampleASA(config-if)# no shut

that's it... if your modem is a dhcp server, which i belive it is because when you connct your pc u get default gateway and ip automatically

[toddyboman]

tried this as well.......

Should i just set the ASA back the the factory default settings and start over.........I (we) have changed so much stuff I am fearful it is so messed up we could have more problems than we ever imagined......OR can this not be true.....

Thanks again for everyone's help!!!

[Antonio Knox]

It would probably make life easier for you to blow away the config and start fresh.  You don't seem to have the connectivity you seek anyway, so it definitely wouldn't hurt.  Future reference, you should never have to play around with a config file.  At the worst you could type configs into notepad and copy/paste to command line.  I don't think anyone will ever advise you to paste to the config file.  If they do they probably don't know what they're doing