cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3332
Views
5
Helpful
2
Replies

Configuring DHCP pool on ASA in packet tracer

cisconotdisco
Level 1
Level 1

I'm very, very new to working with packet tracer/configuring firewalls and I'm having problems getting my DHCP pool to work properly. I moved it from my router to my ASA. I've posted the configuration of the ASA below. Any help is very much appreciated, I've spent a lot of time on this!

branchASA#sho run
: Saved
:
ASA Version 8.4(2)
!
hostname branchASA
enable password hxG7F/4eupjTnxQQ encrypted
names
!
interface Ethernet0/0
switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
!
interface Ethernet0/4
!
interface Ethernet0/5
!
interface Ethernet0/6
!
interface Ethernet0/7
!
interface Vlan1
nameif inside
security-level 100
ip address 35.32.17.254 255.255.255.0
!
interface Vlan2
nameif outside
security-level 0
ip address 32.35.17.1 255.255.255.0
!
!
!
access-list inside extended permit icmp any any
access-list outside extended permit icmp any any
!
!
access-group inside in interface outside
access-group outside in interface inside
!
!
!
!
!
!
!
telnet timeout 5
ssh timeout 5
!
!
dhcpd address 35.32.17.50-35.32.17.99 inside
dhcpd dns 17.35.32.153 interface inside
dhcpd enable inside
!
!
!
!
!
branchASA#

1 Accepted Solution

Accepted Solutions

Hi

Your config looks fine, I assume you are connecting the host to the port 1 to 7 and setting up the host to obtain IP automatically, Also you can fix this configuration:

access-group inside in interface outside 
access-group outside in interface inside 

 

it should be

 

access-group inside in interface inside
access-group outside in interface outside 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

View solution in original post

2 Replies 2

Hi

Your config looks fine, I assume you are connecting the host to the port 1 to 7 and setting up the host to obtain IP automatically, Also you can fix this configuration:

access-group inside in interface outside 
access-group outside in interface inside 

 

it should be

 

access-group inside in interface inside
access-group outside in interface outside 




>> Marcar como útil o contestado, si la respuesta resolvió la duda, esto ayuda a futuras consultas de otros miembros de la comunidad. <<

Thank you very much for your help!

Review Cisco Networking for a $25 gift card