Most of my WGB systems utilze old (EOL/EOS) Aironet 340 product. All work just swell. I have started deploying the 1242G AP/WGB systems and have a configuration problem. When a DHCP tries to acquire an address (or release/renew WinXP/Win7) it fails. If I use a static client IP address it is OK.
My WGB config should be (or I want it to be) a transparent bridge - passing any traffic that the client generates seamlessly across the cat5 Ethernet and spitting it out to the Wireless connection - it's access point.
Has anyone solved this problem. I have deployed over 6 of these and all of the configs are generally the same. None allow a DHCP client to work.
Below is basic info (not the config at this point) about the hardware:
Cisco IOS Software, C1240 Software (C1240-K9W7-M), Version 12.4(21a)JA1, RELEASE SOFTWARE (fc1) Compiled Wed 16-Sep-09 19:06 by prod_rel_team
ROM: Bootstrap program is C1240 boot loader BOOTLDR: C1240 Boot Loader (C1240-BOOT-M) Version 12.4(13d)JA, RELEASE SOFTWARE (fc2)
System image file is "flash:/c1240-k9w7-mx.124-21a.JA1/c1240-k9w7-mx.124-21a.JA1"
Part Number : 73-13785-01 PCA Assembly Number : 800-37050-01 PCA Revision Number : A0 PCB Serial Number : FOC1611361G Top Assembly Part Number : 800-29232-02
Top Revision Number : A0 Product/Model Number : AIR-AP1242AG-A-K9
Anyway - this is a reproducible real problem. If I can find the answer to this, I have a couple of other issues with these 1242G AP/WGB configurations, but this problem with DHCP working across the connection is bad.
The upstream access points are all Cisco 1200. This specific problem is only happening when I have a newer 1242Gs as the work-group bridge. I use simple WEP because we still have about 1 dozen Aironet 350 series work group bridges. NO problems with DHCP from those attached clients (ack).
With this particular location (WGB), all the parents allowed are model AIR-AP1230B-A-K9. The same...
I have since changed a few configuration items - but it still exhibits the problem of the attached PC being unable to get a DHCP address. Another issue is from my mangagement PC on the same management IP subnet - I can't always ping it. Specifically I set the arp timeout to maximum. and the dot11 hold-off time to 5. Why age arps out at all because the attached clients (PC, Printer, etc) should never go down and I'm not worried about blocking a DOS where the hold-off time applies.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...