Upgrade to 7.5.2 broke WDS network

For the past 6 months I have used a Time Capsule and 2 Airport Express to configure a WDS network. The TC is the Main station and then I have one AE as a relay and one as a remote station. It has worked perfectly fine until I was prompted to upgrade.
For what I can tell, both the TC and the Relay are now running on the firmware 7.5.2 but the Relay is no longer working. It no longer shows up in the Airport Utility and if I reset it and reconfigure it, the update ends up with the cryptic message "An error occurred while reading the configuration. Make sure your AirPort wireless device is plugged in and in range of your computer or connected via Ethernet and try again. (-6753)"
I'm not sure what to do at this point. I tried to revert to the previous firmware but that didn't work either, I'm getting a similar error... Has anybody run into the same issue or has a suggestion on what to do to get it back working again?
Thanks

I came across the same issue.
I have a simple set up: just have two AE, one main and the other relay. (I used to have four AEs previously, but got rid of those when N version came out, though configured them as WDS in case I needed to add an extra)
Anyways, I read on another thread that one should update firmware to 7.5.2 of all relay(s) and remote(s) first, before updating the main station's firmware.
Not sure if that's true, but if it is, it's a real shame AU doesn't just stop you from screwing it up, as it knows which base is doing what in the WDS you've set up.
So.. I had just updated the main, and upon updating the relay, AU failed to "see it" appear again - never came back from reboot. And from that point onwards my WDS was dead.
I tried a full reset, reconfigured everything from scratch, both AEs now being in 7.5.2, but WDS would refuse to work - checked the log file and found the main station complaining with the following line over and over (ie. kept on associating/disassociating):
Dec 28 19:49:30 Severity:5 Deauthenticating with station XX:XX:XX:XX:XX:XX (reserved 2).
So, after checking other threads, and googling some more, I just gave up (for now) and put the main AE as Wifi network creator, and the other AE set to join&extend the network.
I really wish the team @ Apple could make some improvements on WDS... or check if something's wrong with latest firmware. I mean, it could be me goofing up somewhere, but I reset both boxes 3 times (ie. redid the whole steps for WDS creation from scratch thrice..) and I've set up WDS before — until this last "rogue" 7.5.2 update came along, it was working perfectly.. kinda wish I didn't update sometimes
Anyways, for now I'm staying away from WDS, cuz for me it's broken

Similar Messages

Just upgraded to Leopard and it broke my network

I tend to work on a Thinkpad (T61) running Windows XP SP2 using my iMac as a file server. I had the mac drive as a drive loaded onto my windows desktop automatically. I was never able to access the T61 from my mac but that's an issue for another time.
I have another Thinkpad (T41) running Windows XP SP2 that I never got onto the mac's desktop. I can now see the T41 in the Shared section of my Finder windows; I do not see the T61.
When I open the T41, it seems I can only move data to the SharedDocs folder for some reason.
So, my questions are as follows:
o Why did my mounted volume break on my Windows machine (the T61 never changed; it was only the Mac that changed so it's something on the Mac)? How do I fix this?
o How do I get the T61 to show up in the Shared section of Finder windows?
o How can I access any part of the Windows machines from the Mac, not just their SharedDocs?
TIA,
David

OK, as I was gathering more information, it started to work! I can now access the iMac from the T61 and T41 (truly don't know how/why).
The T61 still doesn't show up on the Mac and the T41 is still inaccessible other than in the SharedDocs.
I noticed that the Network Preferences panel is entirely disabled; why would this be?
Again, TIA,
David

Can I set up a WDS network with two main base stations?

I have an AEBS in the main part of the house and a time capsule in the office in the back of the house, currently with one internet connection (it's cable modem) into to the AEBS. I have tried to use relays (two airport expresses) in a WDS to have the internet connection reach the time capsule, but unfortunately the distance is too great and it won't make it.
I can move the internet connection and AEBS into the middle of the house and everything would be fine (one internet connection into the house, no need for relays to reach the time capsule), but this requires rewiring the cable connection and adding a power outlet, which seems like a lot of work.
My other option is to simply have another internet connection hardwired into the office. This would be using the same cable that comes into the house and is split outside. If I go this route--my question is--can I get the time capsule and the AEBS be on the same WDS network (same name, same passwords?), or will I have two separate networks in the house? If it is the former--how do I set it up? Can I have a WDS with two main base stations? Or is there an easier route?
Thanks the help and advice...

My other option is to simply have another internet connection hardwired into the office. This would be using the same cable that comes into the house and is split outside. If I go this route--my question is--can I get the time capsule and the AEBS be on the same WDS network (same name, same passwords?), or will I have two separate networks in the house? If it is the former--how do I set it up? Can I have a WDS with two main base stations? Or is there an easier route?
Just run the Ethernet cable from one of the LAN ports on the AEBS to the WAN port on the Time Capsule. Configure the Time Capsule to operate as a bridge.
You do not use WDS when they are wired together.
Then configure the AEBS and Time Capsule to use the same SSID, wireless encryption type/level/password. Have them operate on different channels as far apart as possible.

Airport WDS Network and the 5GHz Option

Setting up any Airport base station with basic settings is simple but there always seem to be options that are not well covered in the 'manual' when setting up slightly more complex networks. I'm hoping someone can provide some clarification on our configuration or parhaps some advice.
For many years we have used a series of generations of Aiport basestations to create a WDS (wireless distributed) network. This is where one base station is the master and other base stations extend the range of the network wirelessly. This is not a set of wireless basestations creating an extended network by sitting on an ethernet backbone - that's a different configuration.
Anyway, we now have a Time Capsule, an Airport Extreme, and an Airport Express. The Time Capsule is the master and the other two base stations extend the network. By default, the basestations select the channel automatically but we have selected manual channels because we have neightbours that all seem to want to sit on channel 1. We've opted for channel 13, a less used channel.
[Internet ADSL Modem]
|
[Airport Extreme] ---- [Time Capsule] ---- [Airport Express]
The Extreme and the Express both operate in Bridge Mode only, that is, they simply extend the configuration of the master basestation and do not ditribute private addresses or do any NAT. I reckon this keeps it simple. Any changes made on the Time Capsule - such as Access Control changes - are pushed out to the other two stations automatically. This seems to be a significant improvement over version 5 of the airport software.
My main question relates to the 5GHz network option. I can turn on a 5GHz discrete network on the Time Capsule. It receives a unique name so it's clearly distinguished from the 2.4GHz network when connecting to it on our Macs. You would expect the other two base stations to be able to extend the 5GHz network too but their 5GHz options remain turned off by default. I can turn them on manually but I'm not sure if they should all be configured to work on the same channel or even if turning them on at all is a good idea.
Over the years, the setup of a WDS network has become easier (if only for the reason that Apple has removed some of the more confusing options and simply enables them in background). But the 5GHz network configuration is far from clear. Any advice anyone might have would be much appreciated. Thanks.

My main question relates to the 5GHz network option. I can turn on a 5GHz discrete network on the Time Capsule. It receives a unique name so it's clearly distinguished from the 2.4GHz network when connecting to it on our Macs. You would expect the other two base stations to be able to extend the 5GHz network too but their 5GHz options remain turned off by default.
It appears as if your Time Capsule is a simultaneous dual band version which produces both a a 2.4 GHz and 5 GHz network.....and you have enabled the option to assign a separate name to the 5 GHz network.
If both your AirPort Extreme and AirPort Express are also simultaneous dual band versions, they can extend both the 2.4 GHz and 5 Ghz signals from the Time Capsule.......but only if the Time Capsule is configured to use the same wireless network name for both bands.
The simultaneous dual band version of the AirPort Express is easy to identify......it looks like a miniature AirPort Extreme. Check the Model No on the bottom of the AirPort Extreme and report back with that to find out if your AirPort is simultaneous dual band.
Earlier versions of the AirPort Extreme could produce a 5 GHz or 2.4 GHz network, but not both at the same time.
Once we have clarification on your AirPort Extreme and AirPort Express, we can decide on the options that will be available to you as far as "extending" both bands.

Solution for Poor signal in a wireless WDS network with two Airport Extreme

I have just bought my second Airport Extreme to create a wireless network with the best possible signal. I have one Airport Extreme in my office and the second one (supposedly the remote base) in the living room, two brick walls and 7 meters away. I have follow Apple instructions for the setup, main base "Create a Wifi Network" and Extend network option selected. The remote "join an existent network" and Allow wifi clients selected. According to Apple this is a WDS network between two Airport Extreme.
The network is working and the signal from my iMac is very good in my Office. In the living room the signal with my PC laptop is also very good.
Problem is that my iPod Touch OS 3.0 (I use it as a remote control in my living room with a twonky media server) gets now a very weak wifi signal in my living room, in many cases I lose the wifi sgnal although I sit two meters away from the remote Airport Extreme in the Living Room. If I go to my office with the iPod, then I get a good signal.
I think that only the first Airport Extreme in my Office (Main Base) is emitting a wifi signal and the second Airport Extreme (remote) is only receiving the wifi signal not making a repetition of the wifi signal. (Sorry for my explanation, I am not technical on this.)
I thought that, in a WDS configuration, the remote Airport Extreme WAS suppose to also replicate the wifi signal in my living room.
I have also tried a WDS manual setup with the two airport with the same results.
Is there a solution for this?. Do I have to connect the two Airport Extreme with a wire ethernet in order to be able to have a wifi signal strong enough in my living room for my iPod Touch?.
Thank you for your time.

Thank you Bob for your time.
I understand from your words that with a DHCP reservation I can force de Airport Extreme Main Base to assign an specific IP to a particular client in the network. Is that correct?. If that is the case, I will reserve the 10.0.1.3 to the Twonky Media Server (I need this to be fixed to this IP) and I will change the configuration of the remote Airport Extreme to DHCP automatic.
I will give it a try in a few days. I have spent so many hours with this set up that I am a bit terrified to start again today, to tired from work.
Just one last question. Setting up the remote Airport was very difficult with the Airport Utility. I had to reset and start many times as I always got two errors in the set up:
1.- Internet not connected.
After a minute or so, most of the time the problem was corrected automatically as the remote found the main base that is connected to the internet. I got a confirmation message for this.
2.- Second problem was that Airport Utility said that it could no connect the remote to the specified network. Sometimes (not always) the remote light turn green both in the Airport Extreme and in the Airport Utility, BUT I never got confirmation of a successful installation. Nevertheless, the connection was established because the wifi network exist.
Do I have to "disable the WAN port" during the installation of the remote Airport to avoid the problems?.
Best Regards,
Fernando

WDS Network setup Issues

I'm trying to setup a WDS Network with two APEBS's. One is in a small bedroom with the cable modem (no choice as to it's placement) and the other is in my office, with all of my printers connected. I've done hard resets on all stations. I setup the Main AEBS, WDS enabled with the Remote AEBS ID entered. Then I setup the remote base station, entering the same network name/password, enabling WDS and entering the ID for the Main station.
Upon updating the Remote station, the Main station disappears from the Airport Utility. The only way I can get it to come back is to unplug the Remote station, and turn off/on Airport capabilities.
I simply cannot have both setup and functioning at the same time. I've tried it with and without network security, double-checking every setting meticulously. I've successfully set this up before and after six hours of fighting this I'm at a total loss.
HELP!

Put both Base Stations, and the Mac you are using to run the configuration, in the same room - preferably the room with the Base Station connected to the cable modem. Don't try to take a shortcut by not doing this. This way you eliminate any chance of wireless communications problems messing with the process. You can move the remote base station anywhere you want after you are done - its configuration settings will be retained even if you have to unplug it from power.
Do a hard reset of the Base Station that is going to be the remote, to get it back into its default configuration state.
Run the Airport Utility, and rather than trying to set everything up manually as you are doing now, let the Airport Utility guide you through the process of configuring the second base station as a remote base station that "extends" the wireless network of the main base station. Letting the Airport Utility take care of the setup shouldn't take you more than a few minutes.

Upgrade to itunes 7.6 now error "network connection timed out"

Upgrade to itunes 7.6 now error "network connection timed out" when i try to connect to itunes store and podcast

I did a manual install of itunes 7.6 (it refused to install through the automatic update) and now I get the same problem - itunes store won't connect.

Mixed security settings on WDS network

I posted this under the 802.11n topic; many views but no responses. I apologize if dual posting is bad form, but I really would like to get some help with this issue.
I have a wireless network consisting of an Airport Extreme N and three Airport Expresses, one of which is N-capable. They are set up as a WDS network with the Extreme as the main, the Express N as a relay and the two other Expresses as remotes. One of the remotes is linked to the main, the other accesses the network through the Express N relay.
My question: How do I set up security so that a device which only supports WEP can access the network while other devices, including my laptop and my wife's desktop Mac Pro can use WPA2? The Extreme and the Express N use WEP Transitional, while the other two Expresses use either WPA2 or WEP.

See the reply on the AX 802.11n forum.

Connecting to specific routers within a WDS network

I have two routers that are successfully operating on a WDS network.
The primary router is a linksys WRT54G v2.2 with dd-wrt firmware and the secondary router is an airport express. The express has my xbox connected to it allowing me to connect to the network and i have it configured to play videos from my macbook and desktop pc.
I know that because the primary router is not the airport extreme that the WAN connection is bottlenecked by the ISP, however i would like to be able to stream HD video - as well as transfer large files between my xbox, pc, and macbook - while utilizing the 802.11n functionality of the airport extreme.
Is it possible to force my macbook to selectively connect to the airport extreme in order to acheive the higher data transfer rates while bypassing the linksys router?

+I've concluded that the firmware in the newer version of the AX must ave been enhanced to permit the use of the ethernet port when it's extending a network.+
The AirPort Express 802.11n has a feature called ProxySTA which allows the ethernet port to be enabled when the device "joins" virtually any wireless network. The Express does not "extend" the wireless network when it "joins"
The 802.11n AirPort Express also works in conjunction with another Apple "n" router to allow the wireless network to be extended without the speed loss and bandwidth drop associated with WDS. The "extend" feature only works among Apple devices on a network.
When the Express is setup to "extend a wireless network", the ethernet port is also active.

Airport Extreme WDS network setup

I'm new to Apple stuff. I have a Dell Desktop running XP and a Dell laptop and IBM laptop running the same. I tried setting up a WDS network, I have an Extreme and 3 Expresses to connect to my receivers, Slingbox, etc. My desktop gets internet through the Extreme using an Ethernet cable, and we can see the network on our laptops, but when it tries to connect it gives us the "limited or no connectivity" issue. We've connected to it before wirelessly and had it work, but very rarely. Also, in the Airport Utility, it does not seem to pick up any of the Expresses even though I added their Airport IDs to the WDS network. Please help, I've definitely hit a dead end on this one. Thanks.

Time Capsule, 1TB. (0x168C, 0x9A) 80211n
Apple Express (I can't find the model number!! Though I know it is "newer" than my Time Capsule Extreme.
Both using 7.6.4
Three Apple TV's.
Sonos Music system setup in the house...separate network.
Internet service provided by ARRIS modem...from Comcast.
My goal? To have the fastest and most stable system in my house. To take advantage of the Airport Express for extending my network, physically.
Thanks!

Problems with getting WDS network to work - TimeCapsule + AirportExtreme

Hi There, Apologies if this has been answered somewhere else but I have searched and still havent managed to solve my problem.
I have a TC plugged into our cable modem which is broadcasting wirelessly fine. What I am trying to do is extend the network by using a Airport Extreme BaseStation in another room which has a PC computer plugged into the Airport Extreme via ethernet cable that (the PC doesn't have wireless capability).
so this is what I am trying to do:
Internet - (ethernet) - TimeCapsule - (wifi) - Airport Extreme - (ethernet) - PC
The Time Capsule is running version 7.4.2 software
The Airport Extreme is running version 5.7
What I have tried so far is to set the TC to "Participate in a WDS network" on channel 1 using WPA/WPA2 Personal passwords. In the WDS settings it is set to WDS main and I have allowed the Airport ID of the AE.
In the settings on the AEI have the wireless network name set to the same as the TC, I have the radio mode on 802.11g only (i have tried the others too but didn't seem to work). The wireless mode is set to Participate in WDS network, channel set to 1 and under WDS settings I have it set as WDS relay and the ID of the TC in WDS main settings.
The TC when i look at its set up occasionaly flashes up WDS error, all it says is The device is set up as WDS network but no other Apple Wireless devices were found.
Im really scratching my head on this one, Im not an expert on networks at all but normally configuring apple stuff has caused a lot less headaches that this.
Can anyone tell me if I am doing anything obviously wrong or any suggestions as to what I can do to get this working. (I personally blame the PC for not having wireless!!!)
Cheers
D

Welcome to the discussion area!
WDS can be tricky. Instead of setting up the second device as a relay, you might try setting it up as a remote. Normally, a relay is used between a base and a remote. Take a look at the excellent instructions previously posted by expert Tesserax as follows:
http://discussions.apple.com/thread.jspa?threadID=2355832&tstart=0
And you could also refer to Apple's instructions on pages 42-44 in the Designing AirPort Networks Guide

Can't extend my existing Express b/g WDS network with new Express n

Hi all,
For the past 2 years I have been using a very simple Airport Express b/g wireless network setup. I have two of the older generation b/g Expresses and I've created a WDS network where the main Express is connected to my broadband modem and participates to my WDS as "main" and the relay Express is configured to participate to this WDS as "relay". This setup works flawlessly and I was very happy with it. Note: the firmware version on both units is 6.3.
Recently, I wanted to extend the range of this network. I've bought and received the newer generation Express n. To my surprise, setting it up to extend my already existing b/g WDS is simply impossible. Below is a summary of the situation:
1) The firmware was updated to 7.3.1 as soon as I opened the Airport Utility.
2) The automatic setup wizard in Airport Utility was incapable of extending my current b/g WDS with the Express n. (Green light on but no wifi coming from the new Express n).
3) I've tried countless times to reset and manually reconfigure the new Express n as "remote" in the WDS configuration panel and connect it to either my "main" Express (b/g) or the "relay" Express (b/g). Both "main" and "relay" Expresses (b/g) were also configured to extend WDS to the new "remote" Express n. I've tried to scrupulously follow instructions found in other posts/discussion forums on how to do that.
4) I then tried to make the new Express n as the "main" base station in the WDS. I could successfully connect it to the Internet (Express n connected to broaddand modem via ethernet) and receive wifi from it, but it was impossible to establish a working WDS with my other two b/g Expresses, both reconfigured as "relay" and "remote" in the WDS (again using the instructions from people who succeeded in having both b/g and n units in the same WDS).
5) Adding to all the difficulties in configuring, hard-reseting and reconfiguring each Express, I would very often be in a situation where Airport Utility only sees 1, 2 or none of my 3 Expresses. Rebooting my Mac was the only thing that enabled me to see them again.
6) After about 7 hours trying to figure out how to work this thing without any good results, I've decided to call out for help. In my situation, there seems to be an intrinsic incompatibility between older b/g Express and the newer Express n, at least for WDS network setup.
If anyone is in the same situation and has found a solution to the problem your help will be much appreciated.
Thanks in advance.

Good news everyone: don't despair, there is hope! After nearly 10 hours of configuration, I finally have a WDS with all three AXs (two b/gs and one n). woohoo!
OK, so here's how I did it:
The main idea here was to replace my "relay" b/g AX with the new n AX.
1) The first thing I did was to reconfigure my "main" b/g AX (the one connected to my modem) so that it can transmit to the new n AX: I simply added the Airport ID of my new n AX in the WDS "remotes" list inside the WDS configuration panel of the "main" b/g AX. I then did an Update Reboot on the "main" b/g AX.
2) After that, I did a Hard reset on the new n AX and plugged it near my old "relay" b/g AX. I then went in Airport Utility, scanned for the new n AX and asked the wizard to "Replace an existing Base Station". It gives you a list of all the base stations your computer has interacted with. I selected the old "relay" b/g AX. The wizard then asked to unplug the base station that is going to be replaced. Did that, and then I did an Update Reboot on the newly configured "relay" n AX.
3) I've rechecked the configuration of the new "relay" n AX, and to my surprise, it wasn't exactly the same as the one for my old "relay" b/g AX. Specifically, I had to manually reconfiguring the whole WDS settings. I had to tell it to "Participate in a WDS", re-input the Aiport ID of the "main" AX and also put the Airport ID of the "remote" AX (the old b/g I'd replaced see below - 5) in the "remotes" list. Once that was re-configured, I updated and rebooted.
4) At that point I had wifi coming from: my "main" b/g AX and now my new "relay" n AX. Yeay! that was the first time I had interaction between b/g and n units.
5) I then went to reconfigure the old "relay" b/g AX and set it up as "remote" and connected it via WDS to the new "relay" n AX. Configuring a b/g AX is a piece of cake compared to the newer n AX!
6) I am very happy to report that it all simply works now! All three AXs are happily talking to each other now. Hooray!
I am almost clueless on why performing these specific steps made it work but it did. My reasoning is that by letting Airport Utility automatically configure the n AX with the configuration data of an old b/g AX it might have changed some settings that were too hidden from view when done manually.
Thanks to dchao99 for input, and Mike hang in there. Try to follow my steps, it might also work for you!
Good luck to all of you.

No more WDS networking in the new dual band airport extreme?

we had a network of 3 airport extremes in our small 2 story design studio, we bought a new dual band to see if it would help with our DSL problem [it did], but there is no more WDS networking option available. this unit replaced our MAIN WDS unit. so now we are left with 'extending the network' option. it seems to be working, but what is the reason behind no more WDS?

WDS gives you more control over your network. You can set-up certain base stations as relays and others as remotes. Using the "Extend a network" option just tells the base stations to try and find other base stations. It is much easier for a novice to set-up, and I think this is probably why Apple has highlighted this feature as opposed to WDS (where you have to specify MAC addresses for all base stations and remotes).
WDS is nice if you have a mixed network with older b/g base stations since they don't have the option to "Extend a network" or "Allow this network to be extended".

Connecting an 802.11n Express to an older WEP-enabled WDS network

I have a domed 802.11g Extreme base station connected to an older (802.11g) Express in a 128-bit WEP enabled WDS network - works great.
I recently purchased a new 802.11n Express and would like to add it as another remote in my WDS. The new Airport Setup Utility will not allow me to set up the new Express as a remote in a WDS network with 128-bit WEP. The closest I can get is WEP Transitional Security Network. When setting it up this way, it demanded a 13-character password -- which I dutifully supplied AFTER changing the password on my domed Extreme to the same thing. After all this effort - the new Express won't get past the blinking yellow light thus requiring me to reset it using the manual reset button.
I can get this same unit to "join" my existing network just fine. In that case, it accepts 128-bit WEP without a whimper.
Is there a basic compatibility problem here? Can I get the new unit to connect to the old 128-bit WEP network by using Transitional Security Network? Do I need to update the whole network to WPA? Or is there some other issue here that has nothing to do with the security issue?
Thanks for any help.

Hello Tim Hopmann. Welcome to the Apple Discussions!
You should be able to access the "earlier" WEP modes by first changing the radio mode on the 802.11n AirPort Express Base Station (AXn) to one of the non-"n" modes. To do so, just be sure to hold down the <Option> key before making the radio mode selection in the AirPort Utility. Once you choose one of these non-"n" modes, the WEP 40 & 128-bit options become available.

Airport Extreme setup problems on existing WDS network - Please help!

I just bought a Time Capsule and have setup a WDS network for the house. The Airport Express joins the network just fine as a remote WDS device. I cannot get the Airport Extreme (v5.7) to join the same network. It just continues to make a *separate network with the same name* despite the Channel being the same, the WDS being set to remote, and the main ID of the Time Capsule has been put in correctly. In other words, since I setup the airport Express correctly, I cannot figure out for the life of me why the Airport Extreme is not joining correctly.
PLEASE HELP. I've been trying this for 6 hours now and countless total restarts by hard resets of all the equipment.

Hello arthung. Welcome to the Apple Discussions!
Let's double-check your WDS setup ...
(Note: To facilitate the WDS set up, place the base stations within near proximity of each other during the set up phase, and then relocate them to their desired locations when complete. Also, jot down the AirPort IDs for each of the base stations to be used in the WDS.)
o Perform a "hard" reset on the Time Capsule (TC) and a "hard" reset on the 802.11b/g AirPort Extreme Base Station (AEBS).
Main Base Station Setup - TC
o Click the AirPort status menu in the menu bar and choose the wireless network created by the TC.
o Open AirPort Utility.
o Select the TC, and then, choose Manual Setup from the Base
Station menu.
o Click Wireless in the toolbar, and then choose “Participate in a WDS network” from the Wireless Mode pop-up menu.
o Click WDS and then choose “WDS main” from the WDS Mode pop-up menu.
o Select the “Allow wireless clients” checkbox if you want client computer to connect to this base station.
o Click the Add "+" button and enter the AirPort ID of the AX.
o Click Update to send the new settings to the base stations in the WDS.
Remote Base Station Setup - AEBS
o Click the AirPort status menu in the menu bar and choose the wireless network created by the AX.
o Open AirPort Utility.
o Select the AX, and then, choose Manual Setup from the Base Station menu.
o Click AirPort in the toolbar and click Wireless. Choose “Participate in a WDS network” from the Wireless Mode pop-up menu, and choose the same channel as the main base station from the Channel pop-up menu.
o Click WDS and choose “WDS remote” from the pop-up menu.
o Enter the AirPort ID of the main base station in the WDS Main field.
o Click Update to transfer the settings to the base station.
(ref: Pages 42-46 of "Designing AirPort Networks.)

Upgrade to 7.5.2 broke WDS network

Similar Messages

Maybe you are looking for