4402, ASA 5505, Guest Network and DHCP

Answered Question
Mar 17th, 2010

Currently I have a 4402 setup with a guest network vlan. 4402 is connected to a 6509. A port on the 6509 is set as an access port with this guest vlan. This port is directly connected to a Verizon DSL router, which gives out DHCP (192.168.1.X). The DSL router is not set for trunking or does it recognize vlans, everything is going out untagged. This setup works. We are changing providers and I have a spare ASA5505 that I am trying to use. I set it up to the same subnet as the dsl modem was setup (192.168.1.x) and enabled as a  DHCP server. All wired connections work fine. When I connect it to the 6509 the guest wireless can not obtain a DHCP address. I can ping the 4402 from the ASA and the ASA from the 4402. I assumed because the traffic was leaving the ASA untagged this would work. Any ideas.

Thanks

Brian

I have this problem too.
0 votes
Correct Answer by John Cook about 6 years 10 months ago

The ASA won't allow dhcp proxy, so you'll need to either turn it off on the WLC

or move the dhcp server functionality from the ASA to the WLC.

-John

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
John Cook Wed, 03/17/2010 - 13:19

The ASA won't allow dhcp proxy, so you'll need to either turn it off on the WLC

or move the dhcp server functionality from the ASA to the WLC.

-John

Actions

This Discussion

 

 

Trending Topics - Security & Network