<\/div>\n

I<\/span>t’s a shame but my brand new Cisco ASA 5505 has just been sitting on my desk untouched for two weeks. The only think I’ve noticed about it is that it still had the old Cisco logo. Basically I’ve watching it from time to time without having time to play with it.<\/p>\n

Finally I had some time to spare and I connected it to my cable modem, I have an ADSL connection with a few DHCP addresses so at first I just connected the device with the default configuration. The intelligent network seemed nowhere in sight and nothing worked. <\/p>\n

A DHCP lease was missing in action, I turned on the debugging for the DHCP client and could see that the ASA device was sending out broadcasts but a reply never came. Instead I connected the device to my internal network where the ASA got an address instantly.<\/p>\n

I’ve had some trouble in the past with getting an IP address from the ISP when I was using a Cisco 1811 router, if I just used the “ip address dhcp” command on an interface the router would just broadcast requests without getting a reply. What I had to do there was to use “ip address dhcp client-id fastethernet 0”, then I got an address from the ISP.<\/p>\n

I tried looking for a similar command on the ASA5505 but I couldn’t find anything. I did however find a page<\/a> on the Cisco site confirming my suspicions. It said some ISP’s require the client-id field of the DHCPDISCOVER request to be filled.<\/p>\n

Hoping for an answer, expecting to be disappointed I called my ISP to see if they required the client identifier to be set to the MAC address. To make a long story short they didn’t have a clue as to what I was talking about. “I’m sorry this is just technical support, we don’t have the answer to that.” Apparently they didn’t even know of anyone in that company who could answer my question. Far too often I end up feeling like a blonde girl at the library<\/a> when I call support.<\/p>\n

I fired up Wireshark to take a look at the packets, and sure enough the client identifier did not contain the MAC address but\u00c2\u00a0 “Cisco -mac-address interface”, as described in the Cisco document I found.<\/p>\n

\u00c2\u00a0 $\"DHCPDISCOVER$ <\/p>\n

A packet from my Vista machine show it uses the MAC address in the client identifier field by default:<\/p>\n

$\"Vista$ <\/p>\n

I connected the Cisco 1811 to my network to see what happens. Without the “client-id fastethernet 0”:<\/p>\n

$\"Cisco$ <\/p>\n

With “client-id fastethernet 0”:<\/p>\n

$\"Cisco$ <\/p>\n

I also checked on a ASA 5510 and it uses the same client identifier as the ASA 5505. I have contacted Cisco about this and they are working on a solution. At least I still have my trusty ol’ PIX 501. For your reference the latest release I’ve tested this on is 7.2(2)14.<\/p>\n

Update:<\/strong> This issue has beed fixed since a few weeks, but you had to ask Cisco to get it. Now they have released version 7.2(2).22 where you can define “dhcp-client client-id interface outside” in global configuration mode.<\/p>\n

[tags]cisco,asa,networking,dhcp[\/tags]<\/p>\n","protected":false},"excerpt":{"rendered":"