Cisco Wireless :: Two WET200s Bridge Not Passing DHCP Requests
Dec 15, 2010
We have setup a bridge between two of our offices using two WET200's in adhoc mode. Everything is connected fine and the signal strengh is good. All traffic pass's over the bridge correctly but DHCP requsts/replys seem to be failing to traverse the bridge. Our DHCP server is hosted on site A and the computers on site B fail to obtain thiers IP's from the dhcp over the bridge requiring us to use static IP's.Firmware is currently the latest.
I have 2 1242AG APs setup with one SSID and no vlans configured. The APs are connected to a switch along with my DHCP server. Clients are able to connect to the SSID but are unable to get an IP from the server. Clients can plug into the switch and get an IP. If I configure a static IP on the wireless card, the client works fine.
Is there something I'm missing on the AP to allow DHCP requests to pass through? IPhelper?
Here is the AP info: AIR-AP1242AG-A-K9 12.4(21a)JA1
Cisco Small Business Switch POE ESW-520-24P with a Wireless Access Point Cisco Aironet AP1141. Both the devices are upgraded to the latest firmware.
Connected to the ESW-520-24P is a Windows 2008 SBS 2011 with DCHP and Domain Controller. Along with the server I have a number of wired computers connected to the switch which do not have any issues and connect to the DHCP server without any problems.
When connecting two wireless devices to the AP1141, they get the IP address and DHCP from the server; but when connecting other devices apart the first two they will fail to connect to the DHCP server and do not get any IP Address. They manage to connect to the Wireless access point but they cannot contact the DHCP server.
A little background on me: I do performance testing for a large corporation, so networking is like an old hat for me - but this has me spinning because it makes no logical sense to me.Here's the layout of my home network:CableModem(passthrough) -> WRT120N -> ENH200 (Access point) -> ENH200 (Client Bridge) -> Netgear N600Both the WRT120N and the Netgear N600 are providing wireless access to clients at both locations. N600 is set not to route or DHCP, and the WAN port isn't used.Initially the WRT120N wasn't in play because the cable modem was serving DHCP, but it wouldn't successfully send DHCP to most clients on the other side of the client bridge. So I installed the WRT120N (old, I know) and it was able to serve up DHCP to any and all systems... for a while. Now DHCP doesn't appear to be working fully again on the Netgear side of the bridge. One device registers in the WRT120N, the client list shows the mac as getting assigned an ID, but the device never actually pulls the address. Static works fine. Those that already have DHCP addresses work like a charm, so I know the link is stable. pingtest.net reports near perfection.
Just setup two WAP200E's, the bridge is "Connected" as I look Status > System Performance in both WAP's. However, I cannot get to the LAN from one network to the next. Cannot even ping the WAP's from either side.
I already have two WAP200E's on this network, that have been working well for month (164 day uptime), and they are configured with a wireless bridge between them, both networks on the same LAN (same 192.168.2.x network on either side). The bridge names are different, different from the main WiFi in the building, too (if it makes a difference), and the static IPs the WAPs have don't appear to have any conflicts on the network.
This is actually three buildings, one is the main one with a Cisco SR520 for a router, and a Cisco SF 200-24P switch. So two WAP200E's go into this switch now, and I see them both fine when going into the management interface. Then each of the other buildings has one WAP200E, and a small Netgear 8 port PoE gigabit switch at each building to power the WAP.
The Netgear switches aren't managed, and I've made sure any features like STP, VLANs, etc. are turned off. And the Cisco SF 200 switch is set at auto and all the defaults mostly, particularly for the ports. I tried doing a SmartPort for this latest WAP200E and that didn't change anything, tried disabling STP for it too, and no change. The PoE port for the working WAP200E is identical in config to the PoE port for the new WAP200E, and both show forwarding, all VLANs admitted (none are enabled, no VLAN tagging, etc.).
So now I am wondering if I can have two WAP200E's into one switch? Or two bridges on the same LAN subnet? Or is there something else I am missing or should configure?
We have an 1140N AP connected to a switch and our "network partner" controls the router and will hand out DHCP and do the NAT for this WLAN. How can I configure the AP to forward DCHP requests through.
I have WPA2 PSK (TKIP) setup and the client is able to authenticate however we fail to get an address. In this case the Ethernet interface was left alone so it has the default config and it gets a DHCP address fine. How can I configure this AP to enable the rest of the WiFI clients to get an IP?
I have a school with 550 iPads. We are using two 5508 WLCs sharing the number of APs. The DHCP server and the default gateway for the network are on the firewall. The clients are able to get a DCHP. After some time, maybe about longer than a month, the clients are no longer able to get DCHP addresses. A reboot of both controllers takes care of this. Presently we are runing 7.2.110 OS. I am going to upgrade to the latest 7.4.100, and reload tonight.
I have a Linksys WAP200 Wireless-G Access Point problem. It is SW version 2.0.4.0. I have it configured for a small network and the problem seems to be that it is not forwarding DHCP requests onto my DHCP server. I know that it is not a SSID or Key issue as when I give my devices static IP addresses, they communicate fine within my system. The only issue seems to be when the devices make DHCP client requests. I also know that the problem is not my DHCP server as it has the device's IP / mac addresses in its configuration file and other wired devices are able to communicate with it to get their IP address through DHCP.
I have seen that there was talk in some blogs about WAP200 no forwarding DHCP requests and I was hoping that updating the device to the latest release would have resolved the problems.
My company AP 1231G is not passing the DHCP address to the client from the DHCP server, my config listed below basicly the AP is on its own VLAN 10.1.123.1 and the DHCP server is 10.1.10.2 -- trying to use iphelper to pass DHCP to clients and the AP is on static IP 10.1.123.2--
! ! Last configuration change at 13:15:56 +0800 Fri May 25 2012 by root ! NVRAM config last updated at 13:15:56 +0800 Fri May 25 2012 by root !
I have the bridge working but I have to assign a static IP address to devices connected to it. I can't get it to pick up an address from my DHCP server. Here's what I have:
Cisco ASA5505 (Firewall & DHCP server) WAP54G - Access Point WET610N - This Wireless Bridge
The ASA5505 successfully gives DHCP address to ALL wired and wireless computers. The WET610N has connectivity to the WAP54G. The status page indicates it's connected and I can get on the internet if I set a static address. However, once I configure my computer to automatically get an IP from DHCP, it just times-out and says limited or no connectivity. Again, when I set a static IP, I have connectivity to everything. I know the AP is working because I can get an address from my DHCP server (ASA5505) with my other laptops and even my cell phone. Why can't I get a DHCP address through this bridge (WET610N)?
I have a Cisco RV220W running the latest firmware (currently 1.0.4.17), and I have noticed that after about a week of use, wireless clients can no longer acquire IP addresses via DHCP.
I have used Network Monitor on both the DHCP server, and the WiFi client, and can see that the server is receiving the requests and sending a reply, but the client never sees the response from the server. So far the only way to resolve this is to reboot the router.
I am trying out a DAP-1513 unit but there is no forum section for this? My question seems to be general and might cover the other models also. Do the DHCP request, from the attached LAN devices on the DAP, get pass to the DHCP "server?"
I have a sg200-18 connected via one of the ports to my ISP's router/modem. Using an unmanaged switch everything works as expected, but after a few days on my sg200 my two computers fail to get assigned IP's and cannot connect to anything. I also have a couple printers that seem to have no problems getting their IP's passed through to the router as I can use them fine from my machines when connected to the unmanaged switch.
Is there a possibility I don't have my switch setup properly to know that all outgoing data must go to the router, or UDP traffic is being dropped somehow?
We've got 5 remote offices with cisco 881 routers, Win Clients behind them and all routers connected via vpn site-to-site to central software router.
Mostly all clients recieve ip addresses from routers in their subnets 192.168.x.024 We have Win DHCP Server in subnet 192.168.181.024
The problem is that some of clients,physically sutuated in 192.168.10.024 subnet, recieve ip addresses from Win DHCP server from 192.168.181.024 subnet.
Here's part of cisco cfg:
interface FastEthernet0 no ip address ! interface FastEthernet1
I'll start out with the fact I work mostly with Wi-Fi and not a lot in the security realm... If I plug my workstation into the 3560, my wired client adapter can get an IP address. But the WLAN adapter will not when associated to WLAN.Usually this is not a problem since you may only have two access points on the controller and a dozen or so hosts. In my case, however, I want to put a few of the ports on the 3560 into the same VLAN as the WLAN on the 2106 so I can give them the same guest access as the WLAN. The hosts plugged into the 3560 get an IP address without issue from the ASA. When I disable dhcp proxy, the WLAN clients get an IP address, but then the APs cannot get an IP address from the internal DHCP server on the WLAN controller, and cease to function when rebooted since they cannot get to the controller without an IP address.
Any way to configure the ASA to accept the modified DHCP packets from the WLAN controller? It appears to me that the ASA is not able to accept DHCP relayed packets.
I have two 3560x Catalyst switches setup between two different locations. They link via a PTP line (Layer 2). I have setup Intervlan routing between the switches and that works fine.Each location has a separate subnet and a Windows DHCP server for each subnet.I want to block any DHCP requests to be sent from hosts on one subnet to the DHCP server on the other side (i.e across the PTP link) What is the best method to do this?
We currently have a cisco 4402 with firmware version 6.0.182.0 and 4 WLANs currently running on it, we found the need to add an additional WLAN and after the configuration was completed and I tried to connect to it I found that we are not getting an address. If i connect a laptop to the VLAN I can get an IP and am able to browse. If i hard code an IP into a device and connect to the wireless i am able to connect and browse.
I have several Cata 3500XL switches connected to one 1 HP L3 switch which is connected Sonicwall router. Vlan1 has subnet of 10.10.0.0/24 and Microsoft DCHP server lays inside VLAN1.
Now i want to add VLAN11 (192.168.10.0/24) as second data VLAN but DHCP requests should go to microsoft DCHP server.
This is what i did: Configured VLAN11 IP on each cisco switch IP default gateway with IP from other subnet (i guess this is bad since maybe it should be IP of VLAN11 on HP L3 switch?) Trunk ports are configured to pass everything on cisco switches On VLAN11 i configured IPhelper IP to be MS DHCP server on each Cisco switch
I haven't tested this yet but i have problem in process.I can't ping VLAN11 IPs between switches (i configured VLAN1 and VLAN11 with IP). When client plugs computer to a port that belongs to VLAN11 will i be sure that client will get IP from the 192.168 range or there is possiblity that he gets IP from the management VLAN range?
Setting up a stand-alone WDS/PXE server.Current we have helper addresses setup to forward the DHCP requests from the different VLAN's to the DHCP server. The WDS/PXE server we are setting up is on its server. How do we craft the helper addresses so DHCP requests go to the proper server hosting DHCP and PXE requests go the WDS server?
Everything I seen on Microsoft Technet, lists using Helper Address as the recommended way, but assume both services are on the same server. Our helper address is as follows on each VLAN interface in router: ip helper-address X.X.X..This is a Cisco 3750.
I am seeing a problem with our Cisco 300 switches. We use these switches as access switches, with a stacked 3750-G at the core, two 2960-S at the distribution layer, and about 10 300 Series switches at the access layer (10 port and 28 ports, all PoE).
We use Voice VLAN (VLAN 14) for our Mitel phones – there is a DHCP server on the Mitel system. Phones come up, get tagged VLAN 14 (LLDP), Traffic flows (including Broadcast for DHCP etc…). The system works, and has worked for months.
One day, suddenly, I find that all the Mitel phones on a particular access switch are not working. I look on the Mitel system and the lease on DHCP has expired, and the phone is stuck on renewing its DHCP IP address. I run port mirroring on the switch for VLAN 14 to see what is happening. The phones are stuck on DHCP discover, and I see the DHCP Discover broadcast packets on the switch but nothing else, no DHCP offer packets – hence the phone stuck at boot cycle.
I then do a port mirror from another access switch (that is currently working) – I can see the broadcast packets from the Mitel phones on the broken switch, but on this switch I can also see the DHCP offer packets from the Mitel system. I run two port mirrors simultaneous from the two switches (one working, one not) and I can see that the DHCP offer packets are not coming through to the broken switch. Panic ensues – I look at the distribution layer and there is no problem what so ever.
For some strange reason, the Cisco 300 28 port has stopped passing DHCP broadcast packets on a particular VLAN, even though they are being sent. I power cycle the switch – and hey presto, DHCP offer packets are coming through, and the phones get an IP address and boot properly.
Forward a couple of weeks later, and to today. I have another phone that is showing the same symptoms, luckily it is the only phone on this particular Cisco 300 28 port. The same issue is occurring as described above. I gather as much diagnostic information I can then reboot the switch – but still no joy. I then remember that this switch is not directly attached to the distribution layer and instead gets trunked to another Cisco 300 28 port. I give that a reboot and 5 minutes later, DHCP broadcast offers are passing and the phone boots.
I am listing this problem as not just a ‘one off’ now, and is recurring. It has happened to two of my 300 28 port switches.
All Switches running 1.1.2.0. No link to up time – first instance of the problem, switch was up for 14 days – second instance (another switch) uptime of 39 days LLDP is working fine on the switches, as is Voice-VLAN (Port is tagged and broadcasts out DHCP Discover which is seen by other devices throughout network) Nothing in the log file on the access switch Nothing on the Dist/Core regarding STP – Spanning tree set up is fine throughout.
I have two WAP4410N plugged into my Catylist 3560 switches.One of these switches is my Default Gateway for the LAN.The only way I can get a device to connect to the WAP4410N is by assigning it a static IP. Then it works perfectly.
At customer site we have a wireless lan installed with wireless lan controller 5508. This works fine but the customer wants to add wireless bridge WET200 into the network. The problem is that the bridge seems to authenticate and associates with the LWAPP but does not get an ip-address.
At my work we have Comcast Business Class, and our LAN uses the Comcast's SMC static 10'net addressing. Our two POS computers are connected to wall ports that connect to the SMC router (unsure its model number, it's screwed to the wall). There is only 1 LAN port for each POS computer, I am trying to setup a 3rd computer up by the POS stations for dedicated web searching of products, emails between HQ and the other stores.
Like I said our LAN is using the 10'net addressing, and only a single port I can use. I would like to use the E1200 as a bridge/switch to connect: POS computer, network label printer. and network printer/copier/scanner/FAX .. and also have wifi available. The POS & printers need to have their static 10'net IPs .. but I want the wifi to use DHCP from the E1200.
WET546 successfully authenticates and looks pretty healthy on controller (see below) , however neither of computers plugged to WET546 was unable to obtain ip address from dhcp server , nor working with static ip. I was under impression what it might be related to some default policies on WLC2100. Logs (warning) on WLC2100 looks clean.
Region : UnitedStates Model : TL-WR702N Hardware Version : V1
Trying to use TL-WR702N in bridge mode at a hotel. For some reason, every time I set the DHCP parameters to enable DHCP, then save and reboot, upon reboot DHCP is disabled. Of course, without DHCP then bridge mode is useless because I cannot then share the hotel wifi connection with multiple devices.Am I missing something obvious, or is there a trick to getting DHCP to be accepted?
I am trying to determine the best way to setup my E4200 V2 so that it is “uplinked” correctly to a Comcast Dory Modem/router. Currently we have the E4200 V2 router plugged into the Comcast Dory Modem/Router using a CAT6 cable from one of the Ethernet ports on the Comcast device to the WAN port on the E4200. The E4200 is set to “Automatic Configuration - DHCP.”
We are trying to do two things. First better WIFI in the center of the house and for a TV located next to the Comcast device, and second, have all devices in this house see and access all other devices including the Samsung SmartTV, my son’s two systems upstairs, the 3 systems in the room with the E4200, and the one network printer. In the room with the E4200 we have 3 computers and one network printer. 3 of those 4 devices support WIFI so we don’t have to use all 4 Ethernet ports on the E4200.
I see others talking about running the CAT6 cable to an Ethernet port on the E4200 instead of the WAN port and setting it to “Bridge Mode.” Right now the system appears to be working fine although we are sometimes experiencing brief dropped connections with the devices hardwired into the E4200.
Should I be running the E4200 in “Bridge” mode or “Automatic DHCP” mode and which port on E4200 should the CAT6 from Comcast be plugged into?
Network 1: EOC connection. We use this for Internet access, office computers, a POS server and our POS systems. Mostly windows xp and some win 7 systems. Server is Windows 2008 server, but is not controlling DHCP nor a domain. It's just a computer on the network. Directly behind the EOC box is a router using DHCP to manage a 192.168.1.x network. All computers on this network are using 192.168.1.x addresses via DHCP.
Network 2: Comes in on a separate DSL line. Primarily a Linux network controlling several linux based machines. This network has it's own router behind the DSL modem managing DHCP using 175.69.1.x (or something close to that) addresses.
Someone decided to "bridge" these networks by simply plugging each network into the same switch via Cat 5 cable. Bad idea.
The first problem we had (of course) was that the DHCP servers conflicted immediately, so we had to set half of this "mongrel" network to static IPs like 192.168.1.x, and the other computers are getting their addresses via DHCP from the 176.68.1.x network router.
This works - badly. The second router keeps "resetting" the server address on network 1, screwing up our POS systems. But we still need to access the linux machines on network 2 (via http) from the office machines on network 1.
I am thinking the solution to this issue is to place a 3rd router as a bridge between the two networks. Is this correct?
The goal is to be able to be sitting at machine 192.168.1.x on one network, open a web browser, type in a 176.67.1.x address and have the linux web-based application come up from the other network.
I'm working on a project where a wi-fi client is tracked and located using RADIUS authentication requests. The problem I'm running into is that the WLC (5508) sends an RADIUS authentication request to my freeradiusd, which is ok so far, but if the client roams to another accesspoint (3602AG, 1131AG, 1252AG), the WLC does not send a further RADIUS auth. request - and the client is allowed to connect to the next ap.Is there an option like RADIUS-cache which I can disable, so that the WLC sends everytime an authentication request when a client tries to connect to an ap or roams from one ap to another one?
I am having connectivity/stability problems with wifi clients, using 14 accesspoints (Cisco AP1252). All wifi clients are impacted, no matter which AP they are associated with.
Symptoms : ------------------ - client associates to a ssid, everything runs fine - all of a sudden, the client begins having problems contacting certain LAN servers, while others still work. - after a little while, situation comes back to normal
After hours (and days..) of testing and troubleshooting, I have nailed the problem to be at the AP1252 level. When the client experiences problems, he does not receive Broadcast traffic (thus, he cannot respond to the ARP requests from the server he is trying to contact).
While the client was experiencing the problem, I have configured a port on same switch, to act as a monitor port for the AP he was associated to at the time : it seems to me that the accesspoint DOES receive the broadcasts ARP at all times. Only sometimes it prevents them from reaching the wireless clients.. I did a tcpdump on 2 different clients who were associated to the same accesspoint : both were not getting the broadcasts from the lan.
Tcpdump arp from a wireless client (172.30.2.32) :
I have 5x WAP4410N Cisco access points, the wireless is not responding to join request from wireless clients and i can only access the admin page from the LAN side.
reboot does not work the only way to make it accept join requests is by changing parameters in the AP and save it, it will work for few hours then stops again.
I am using a linksys wrt600N with easylink advisor version 1.6.0042. I am trying to install a video camera and the instruction manual says under "known issues": LinkSys routers have a factory default setting in the firewall menu called "filter anonymous internet requests". If you want to access your camera from the internet you have to uncheck this option."I see this option in the WRT600N manual, but it references a software choice that I don't have.I have gone to the website and downloaded the latest compatible software version, and I still don't have the choice to uncheck this option.
I have to upgrade a WCS from version 6 to 7, here we have a MSE having a 6.0.85.0, the matrix document indicates that you can map or well,having installed only one version or release from MSE to WCS, my question is, do i have to upgrade first the mse to the compatible version to the new wcs version we want to upgrade?
Our brand new WAP321 is configured manually because the setup wizard would not complete, just hangs at the end.
Anyway, when a client connects to the AP, it cannot get an IP address. It is able to connect to the AP but does not pickup an IP from our internal DHCP server. I've been up and down tthe config screens and even tried hard resetting the AP and starting from scratch to no avail. This happens with 2.4Ghz and 5 Ghz modes.
I've tried laptops and smartphones with the same result.
