Linksys WRT54G bridge to AirPort Extreme Base Station

Is this possible?

The Linksys WRT54G appears to be one of the very few non-AirPort routers that may be WDS-compatible with the AirPorts. If you do a quick Google-search on the keywords: Linksys AirPort WDS, you will find at least a dozen articles on those who have been successful on doing so.

Similar Messages

Connect to Linksys Cable Gateway via AirPort Extreme Base Station?

Thank you in advance for any replies.
I have the following new setup:
A G3 Blue tower running OS X 10.4.10 is successfully connected to the internet via a Linksys WCG200 Cable Gateway connected to RCN's cable internet service. The WCG200 unit has wireless capacity though it's connected to the G3 tower via ethernet cable.
A second Mac (G3 iMac DV running OS X 10.4.10) is in another room in the office. I'd like to set it up with internet by wirelessly connecting with the existing WCG200 unit using an Airport Extreme Base Station (AEBS) I've recently acquired. To ensure a smooth process, I reset the AEBS to factory settings and installed the AEBS software (version 4.2) onto the iMac DV. Finally I plugged in the AEBS into the iMac DV using an ethernet cable plugged into the AEBS's WAN port (AirPort Admin Utility advised me to do so).
That's the hardware configuration. Working out the software and configuration details is proving 'niggly'.
First, I used the AirPort Setup Assistant to configure the AEBS. I told it to Set up a new Base Station, then to set it up as connecting to the internet using a Cable modem (the top option of two—the second was to set it up with internet through a LAN). I set up the name and passwords for the Base Station and had the utility configure the AEBS accordingly.
No internet connection occurred. I tried using the Internet Connect utility in the Applications folder, but no button or visible option for connecting via AirPort appeared, as the Setup Guide indicated it should, only a button for a VPN appeared.
I called Apple and asked whether it was even possible to connect to the internet using the AEBS talking wirelessly to the WCG200 unit. A tech told me it could be done by going into the AirPort Administration Utility, going into Configuration, clicking on the WDS tab and inputting the MAC address for the WCG200 unit, then going into the Airport tab and typing in the channel that the WCG200 is using. Note that the WCG200 unit has 3 MAC addresses listed; one each for “modem MAC address,” “WAN-MAN MAC address,” and “WAN-DATA MAC address”. I used the “modem MAC address.
The Apple tech added that it might need further tweaking, but that Apple couldn’t provide this tweaking and that I might check various forums if need be.
I followed the Tech’s advice, at which point the utility informed me that it couldn't use DHCP or NAT with this setup’ and to make sure that the "Distribute IP Addresses" checkbox was deselected under the Internet tab. This I did, but it was already deselected. I told the utility to update the AEBS accordingly, and restarted everything, including the 2 Macs and the WCG200.
Result:
No connection.
Tried it again with the Ethernet plugged into the AEBSs LAN port, still no connection.
Help! Can’t I get the AEBS to even see the WCG200? I know wireless is properly functioning in the WCG200 because another user with a Windows laptop connects to it wirelessly. The Mac Tech also mentioned that this could be relatively easy with an AirPort Express piece of hardware (Card? Base station?) but that it would be difficult with the Airport Extreme Base Station.
At this point we’re willing to spend $100 on getting this up. What would be our best option in terms of equipment, or can connectivity be accomplished with what we have?
Thanks again,
skyheart

skyheart, Welcome to the discussion area!
In theory using WDS would provide what you need.
In reality the Linksys device is not compatible with Apple's WDS and therefore this will not work.

Airport Extreme Base Station and 2wire Modem / Router

I have Yahoo DSL with a 2wire modem / wireless router combo. I have an iMac and a MacBook both running Leopard. I can't seem to get the Back to my Mac feature to work. I'm currently running the trial version of .Mac. I'd like to get a full .Mac account but I want to be sure I can utilize the Back to my Mac feature. If I were to bridge an Airport Extreme Base Station to the 2wire would that solve my issue with Back to my Mac. Additionally I like the idea of being able to plug a printer of external hard drive into the Airport Extreme.
Any advice is greatly appreciated.

I got it to work. I purchased the Airport Extreme Base Station and took the following steps which I found here http://forums.macosxhints.com/archive/index.php/t-68141.html
First connect directly to the 2Wire with the Ethernet cable.
Instructions from 2Wire:
1. Clear the HomePortal to Factory State –can be accomplished two ways
2. Go to http://homeportal/management
3. Click on Resets
4. Click on Reset to Factory State
5. Click Continue
6. Have customer press Hardware Reset button with paperclip (HG products only and BellSouth HWs)
7. Have customer unbend a paperclip
8. Have customer insert paperclip into recess for Hardware Reset button (outlined with Red circle) on back of HomePortal.
9. Hold paper clip in for ten (10) full seconds
Next steps:
1. Go to http://homeportal/management again
2. Click on Configure under Broadband Link
3. Enter VPI 0 and VCI 35
4. Click on Disable PVC Search
5. Set Connection Type to Direct IP
6. Click Submit/Save
7. Have cu go to http://homeportal/management
8. Click on Configure Services
9. Have cu Uncheck Enable Routing
10. Click Submit
Airport configuration:
1. Open the AirPort Admin Utility and select your Base Station.
2. Click Configure and enter your password.
3. Click the Internet tab.
4. Choose PPP over Ethernet (PPPoE) from the Connect using pop-up menu.
5. If required by your ISP, enter your user name, password and service name in the appropriate fields. ( Your name and password is you full email including the @sbcglobal.net part and your email password)
6. Click Update.
7. After the base station restarts itself, quit the AirPort Admin Utility.
If that doesn’t work call apple and they should be able to help with the airport configuration.
Back to My Mac now works. Hope this helps someone else.
Message was edited by: WalrusBoy

Airport Extreme base station vs. Linksys router

Hi all -- I have a tech choice to make and I'm soliciting advice and war stories from those who have been in my place.
I have a DSL connection, G5 Mac and a Windows laptop. I've been connecting to the Internet via a Linksys WRT54G router -- the Mac is connected to the router via Ethernet, and the Windows machine connects wirelessly -- and I've been happy with this setup. I have it on good authority that I'll be getting an Airport Express in my stocking this year; I had done a little research and found that it is possible to make the WRT54G and the Airport Express work together, and was planning on doing some hacking and fiddling to make that happen in the new year.
However, last night my WRT54G seems to have died a horrible death -- all its lights started blinking at once, the Internet connection went away, then all the lights went out except for the "diagnostic" light, and now no lights come on at all. No idea what happened, but it seems pretty kaput.
So! I'm in need of a new wireless base station. I could get an Airport Extreme base station, or I could get another Linksys (or another off-the-shelf 802.11 router, but we'll just use "Linksys" as the catch-all phrase here to mean "not an Airport Extreme base station"). The most obvious difference is price -- the Airport Extreme station is $200, while the Linksys is more like $65. Another thing that irks me about the AE station is that it only has one LAN port. I do like being able to plug in my laptop to the wired network to do some diagnostics once in a while and it'd be a pain to have to disconnect my Mac to do so. And then there's nagging worries that the AE base station might not work as well with my Windows laptop.
On the other hand, I'm sure that setting up the Airport Express would be much, much easier with the AE base station. And I do like the idea of the base station being able to dial up if my DSL goes down (as it does from time to time). Basically, I am tempted by the AE base station feature-wise, but I'm kind of balking at paying three times the price and not getting even a second LAN port. Any advice, particularly from people who have used both types of routers in a mixed network, would be appreciated.

Replace your Linksys with another WRT54G. Then you can hook up your anticipated AX as either a client (connected like a computer), a wireless access point (connected using ethernet with DHCP disabled on the AX), or using WDS:
http://discussions.apple.com/click.jspa?searchID=-1&messageID=607414

AirPort Extreme base station as bridge - is WPA allowed?

Hello,
I have an AirPort Extreme base station that is connected to the Internet via an older Linksys wired router. The Linksys is connected to a cable modem and acts as a router (so it's the DHCP host), while the AirPort acts as a bridge between wireless computers and the Linksys (so "Distribute IP addresses" is unchecked).
When using WEP or no security, everything works great. However, when using WPA, my laptop constantly cycles as it tries to get an IP address without any real success. I've tried all combinations of open/closed networks, different wireless channels, and wireless security types, but WPA just won't work. It's definitely supported by the wireless card and I've entered the password correctly, but no dice.
Does anyone know if WPA is supposed to work in this configuration? I noticed that another post recommended connecting cable modem -> AirPort -> wired router, but other posts recommend cable modem -> wired router -> AirPort. Not sure if it matters or not.
Thanks for any advice!

Hi Felix, thanks for your reply.
I have a Linksys wireless card (which I cannot find right now) and an Airnet AWN154 wireless card. When the Linksys didn't work, I purchased the Airnet, which also didn't work. This is on several Windows laptops.
To answer your other question, I don't think I've ever successfully gotten WPA to work with these cards, but of course I only have my own base station to test against. My fiance's laptop (with built-in wireless) worked briefly, but was very slow and every couple minutes the connection would drop.
The reason I originally asked if WPA is possible in this configuration is because I ran across some articles indicating that WPA might not work across bridged networks, although that was for different hardware than my Airport Extreme base station.
Jeff

Multipmultiple Airport Extreme Base Stations: WDS Or "Extend Wireless Network" To Have Wired -- Wireless Bridge?

Hello there!
I've been looking for this info, but have as yet been unable to find it. Here's my scenario:
I have two Airport Extreme Base Stations (both are dual band) and 3 airport expresses. The main internet connection in my house is in one room, where I have an AEBS as the main wireless router. In another room, I have a bunch of ethernet-only devices. I'd like to use the 2nd AEBS in this room, plug the ethernet devices into it and have the 2nd AEBS act as a wired <--> wireless bridge (connected to the same wireless network as the 1st AEBS). I've attempted this via "extend a wireless network," but the ethernet devices don't get past the AEBS they're plugged into. Should I instead be implementing WDS?
I mention the airport expresses as I'd like to have airtunes & wireless signal in other areas, but would like to keep the set-up as simple as possible (i.e., not config the AXes for WDS unless it's required).
Thanks in advance for any help!

Unlike the 802.11n AirPort Express Base Station (AXn), the 802.11n AirPort Extreme Base Station (AEBSn) cannot be configured as a wireless Ethernet bridge.
However, there are at least two ways to configure it to provide wired clients access:
Connect the second AEBSn back to the first by Ethernet; reconfigure the second AEBSn as a bridge and disable its wireless radios, or
Reconfigure both AEBSns into an extended wireless network. For 802.11n AirPorts, this would be called a dynamic WDS. The AEBSn, connected to the Internet would be the "main" base station and it would only require that you enable the "Allow this network to be extended" option in the AirPort Utility. The extending AEBSn would need to be configured with the option, Wireless Mode = Extend a wireless network, enabled.
In both configurations, the second AEBSn's Ethernet ports would be enabled for wired clients.

Airport Extreme Base Station as bridge for Westell DSL router

I have searched the forums & internet and for the life of me cannot get my network to work properly! I hope you can help.
Here is the situation (I rent so chances are we will not be moving hardware anywhere):
- Westell (Verizon) DSL wireless router downstairs connected to the internet, 1 iMac via ethernet, and 2 ibooks via Airport cards
- One lonely Powermac G4 upstairs that does not have a wireless card
- One extra Airport Extreme Base Station with firmware version 5.7 installed & connected via ethernet/LAN to the G4
I figured the "easy" thing to do would be to use the AEBS as a wireless bridge to get the G4 online. The network utility has occasionally thought that the G4 was connected to the internet, but the internet didn't work at all when it said that!
I have been configuring the AEBS using my wireless ibook (G3). I "unchecked" distribute IP addresses, and "checked" connect to network via WDS. I used the Westell's MAC address as the main WDS source. Under the "WDS" tab, I said to configure the AEBS as a remote station and the Westell router as the main station, and to allow wireless users to connect.
I have tried using the same Network name for each. WEP/WAP is NOT set up on either modem, so passwords aren't a problem. They are both set to channel 6. I am configuring the TCP/IP settings manually.
When the network names are the same, the internet either stops working, or the computers can't find the AEBS.
I don't understand why the AEBS seems unable to see the DSL network.

Hi,
Well, what I have been able to do is this:
I have a Westell Wireless DSL router, just like the one mentioned here, and just like the one mentioned in the article I made reference to, the one started by Mr. Müller.
As was mentioned in the Mr. Müller article, there are some possibilities that will work. They were submitted by a guy named Duane, from Texas. He gives three alternate possibilities, which he entitled "Solution #1, Solution #2, and Solution #3. He says all three of these alternatives will work, and in reading them over I came to the following conclusions: First, he really knows his stuff, and second, his proposed solutions would probably work.
Based on his comments I decided to take a risk yesterday - I put my older Mac Base Station in a drawer and invested in a new Airport Extreme.
Anyway, I digress...
What I've done is follow Solution #3. And it works! I now have a connection from my laptop to the Airport Extreme base station and the internet. I am typing this message using that connection. All I had to do was disable the wireless connection of the DSL router (using their software, of course), and connect the Airport Extreme, via the LAN Ethernet connector, to the Westel DSL router.
Now, all that remains for me is to extend the range of the base station, using an Airport Express. I haven't had any success with that yet, but I see no reason why I shouldn't get it to work eventually. If you can help me out with that, though, I'd sure appreciate it.
Best regards,
Patrick
Macintosh G5, Powerbook G4 Mac OS X (10.4.7)

Macbook w/Airport Extreme Base Station

I have a Macbook that I just bought 3 days ago. Like everyone else, I am having the same problem with wireless encryption.
However, when I turn off the WPA and just use WEP, I can connect but it seems to lag. What I mean is everytime I browse, it's almost like my computer needs to "reconnect" with the router. If I stay a a site for more than a couple of minutes the connection kind of goes to sleep. It shows I am connected but it just sits there, sits there, and then connects. When I am on WPA or wired I do not get this.
So, for my actual question, does the Airport Extreme Base Station have issues like this?
On Apple.com, people are giving it glowing reviews. On the net, the reviews are marginal at best.
Current Setup:
Macbook
Linksys WRT54GX4 w/SRX400
Thanks in advance!

I have several Linksys routers and also an Airport Extreme Base Station. I like the Linksys better. The AEBS has arguably better output power than my Linksys, but in my 1600 square foot house, it doesn't matter.
I also have a Macbook c2duo running OSX 10.4.10, and it drops off the AEBS just as much as any other router.
The downside of the AEBS is that it doesn't have a native web based management system. You've got to use the management tool to deal with the AEBS using SNMP protocol. It'd be nice if you had to manage 100 AEBS, but is a nuisance for home use. I found the latest realase of Airport utility (v5.2) to be very buggy on Windows XP - it killed my PC's abaility to negotiate a DHCP lease until I downgraded back to version 5.1. I ultimately went back to using my WRT54GS. The Linksys has lower throughput, but that only matters for specsmanship. The other thing is that Linksys can do multiple PPTP VPN pass through, but VPN pass through doesn't work on the AEBS unless you use bridge mode and static IPs.
I spent the cash for the AEBS, but in retrospect I would have rather put it towards memory upgrades, etc.
Bill

Configure TC and Airport Extreme Base Stations with different channels

I had to do some serious workarounds to use the Airport Extreme Base Stations as an access point with the same wireless network name primarily due to channel overlap. I thought I would post my results here since I didnt' find a good article online.
Also, I found the Snow Leopard verison (5.4.2) of the Airport Setup Utility far superior to Lion's Airport Utility (6.x) in terms of advanced setup.
Setup is a 3 flloor house where the 3 wired network locations have wireless overlap. The problem was that the access points would not hand off the wireless signal because the channels for each airport/TC were automatically set to the same channel. In non-apple setups, this is how you force a wireless client to switch access points (since the wireless software on your client/mac/windows can detect which access point is stronger and moves to the alternate channel.
Using apple's "Extend this wireless network" option removes any ability to manually configure wireless channels. I am writing this from memory, so feel free to ask questions and I will track this topic:
Procedure
Setup time capsule as your base station. Do all the setup for your wireless and guest networks. Manually configure the network and change the wireless channel to a specific channel for a/b/g networks (e.g., 3) and n networks (e.g, 167).
Plug your first airport extreme/access point into your wired network. Do not plug it into the "internet" ethernet plug, use one of the 3 ethernet switch locations
Use the airport utility to first configure it to "extend" your wired network.
Then, go in and reconfigure it manually in the airport utility. Choose the option to setup a "new network" and name the network the same as the TC wireless network name, security, etc.
Change the channel from "auto" to a different channel than the TC (e.g., 6 and 137).
Now go to the top tab and click on the "internet" icon
Go to the DHCP tab and change it to "bridge mode." This will tell the AE to not give out IP addresses (the TC will do this for you). If you get an error that the IP ranges conflict, you have not done this
Note that if you have a guest network setup, you will need to set this up on the AE as well.
Now test your airport setup. Take your client (macbook, iOS device) and connect to your network. Move to a spot near the TC and pull up a web page. Keep an eye on the signal strength and beginv moving toward the AE. Refresh the page as you move around. You should at some point see the signal strength increase. Refresh your page again. You should be now connected to to the AE. I have found that Macbooks do a better job than iOS devices because you get an extra signal bar to measure strength, and they have larger antennas which allows you to better measure problems with handoff
Another test you can do is to start backing up on your TC and then test the move. The handoff will truly show you that the TC is handling the process but the AE is relaying to the TC for backup.
If you need to setup another AE, simply follow setups 3-10.
I hope this helps others. I've done this setup 100 times on Linksys devices and although they are cumbersome, they at least allow me to do this setup much more quickly and easily than the apple products.

I had to do some serious workarounds to use the Airport Extreme Base Stations as an access point with the same wireless network name primarily due to channel overlap. I thought I would post my results here since I didnt' find a good article online.
Also, I found the Snow Leopard verison (5.4.2) of the Airport Setup Utility far superior to Lion's Airport Utility (6.x) in terms of advanced setup.
Setup is a 3 flloor house where the 3 wired network locations have wireless overlap. The problem was that the access points would not hand off the wireless signal because the channels for each airport/TC were automatically set to the same channel. In non-apple setups, this is how you force a wireless client to switch access points (since the wireless software on your client/mac/windows can detect which access point is stronger and moves to the alternate channel.
Using apple's "Extend this wireless network" option removes any ability to manually configure wireless channels. I am writing this from memory, so feel free to ask questions and I will track this topic:
Procedure
Setup time capsule as your base station. Do all the setup for your wireless and guest networks. Manually configure the network and change the wireless channel to a specific channel for a/b/g networks (e.g., 3) and n networks (e.g, 167).
Plug your first airport extreme/access point into your wired network. Do not plug it into the "internet" ethernet plug, use one of the 3 ethernet switch locations
Use the airport utility to first configure it to "extend" your wired network.
Then, go in and reconfigure it manually in the airport utility. Choose the option to setup a "new network" and name the network the same as the TC wireless network name, security, etc.
Change the channel from "auto" to a different channel than the TC (e.g., 6 and 137).
Now go to the top tab and click on the "internet" icon
Go to the DHCP tab and change it to "bridge mode." This will tell the AE to not give out IP addresses (the TC will do this for you). If you get an error that the IP ranges conflict, you have not done this
Note that if you have a guest network setup, you will need to set this up on the AE as well.
Now test your airport setup. Take your client (macbook, iOS device) and connect to your network. Move to a spot near the TC and pull up a web page. Keep an eye on the signal strength and beginv moving toward the AE. Refresh the page as you move around. You should at some point see the signal strength increase. Refresh your page again. You should be now connected to to the AE. I have found that Macbooks do a better job than iOS devices because you get an extra signal bar to measure strength, and they have larger antennas which allows you to better measure problems with handoff
Another test you can do is to start backing up on your TC and then test the move. The handoff will truly show you that the TC is handling the process but the AE is relaying to the TC for backup.
If you need to setup another AE, simply follow setups 3-10.
I hope this helps others. I've done this setup 100 times on Linksys devices and although they are cumbersome, they at least allow me to do this setup much more quickly and easily than the apple products.

Problem consistently printing via new (summer 2011) AIRPORT EXTREME BASE STATION and Brother wireless printer (model HL5370DW). What am I doing wrong?

Thanks in advance for any help you folks can offer. I'm a newb here and will try to offer as much detail as I can about the dilemma at hand.
Scenario: Home network has been recently set up for wireless internet access via NEW Airport Extreme Base Station (purchased September 2011). Units accessing the network include: 2011 Macbook Pro, 2011 Macbook Air, 2007 Macbook, 2009 Macbook Pro, 2 iPhone 3GSs, and a 1st-gen iPad (and a partridge in a pear tree AEBS is configured to run WPA2 encrypted network, as well as a WPA2 guest network. I am attempting to yoke a BROTHER HL5370DW wireless B or G/ ethernet / usb-capable printer to the main network such that any and all units can print wirelessly or its equivalent (i.e., via printer hooked to AEBS through USB hub)
Problem: Despite configuring the Brother printer to recognize the main WPA2 network I created, I am unable to get wireless printing to work. My workaround was to physically connect Brother printer to AEBS via USB, specifically using a Belkin USB hub (after all, I wanted access to usb drives, as well as the printer). This workaround works ONLY SOME OF THE TIME. Generally, after a fresh boot of any computer or after a restart of the AEBS, any given computer will be able to print (i.e., any computer wirelessly connected to the main WPA2 network recognizes the printer). HOWEVER, at random times, printer access is gone (as is access to USB drives connected to AEBS's usb hub). Wireless networks are still up and running when that happens. IS THERE A WAY TO GET THE USB HUB's devices (i.e., printer and usb drives) to ALWAYS REMAIN AVAILABLE AS LONG AS THEY STAY CONNECTED TO THE AEBS? In other words, what accounts for the intermittent loss of the usb peripherals?
Sometimes, I just shut the airport off on whatever computer is having this problem, and the problem goes away. Sometimes, the problem is present across all computers in the house, sometimes only a few are affected. I can ALWAYS see the AEBS in the Airport Utility if the AEBS is connected to the particular computer via ETHERNET CABLE.
My theories:
- true wireless printing (i.e., without usb hub workaround) doesn't work because the N network somehow isn't backwards compatible with the Brother printer, which, i believe, is B/G. Although...isn't Wireless N networking supposed to work with BG devices? I did find a thread (https://discussions.apple.com/thread/2570774?start=0&tstart=0 ) that explains some of the particulars of WPA2 encryption and Wireless B/G issues, but it was beyond my level of comprehension (I'm a psychologist, but not an Apple Genius
- The usb workaround is only intermittently viable because of some flaw in the Airport or Airport Utility that causes dropouts to happen when a Macbook Pro or Air's lid gets closed or one gets opened after having been at a different network (e.g., at my office).
QUESTIONS:
- Should I try to use my old router (7 year old Linksys WRT54G) as an access point and connect the Brother printer to that G-router? How do I do that?
- I wouldn't mind just relying on the usb hub method if I could just insure more consistency (i.e., no random dropouts of peripherals). How could I do this?
Rule out:
- wireless printing works on my printer - it was being recognized back before the AEBS. I had the Linksys router running a WEP network and had the wireless printer talking with no cables to the router and the computers. (I just don't want to revert to using WEP encryption given its lack of security and my trying to protect HiPAA related health information on behalf of patients)
Any help will be greatly appreciated.
Thanks in advance!

13 ASCII characters = 104 (aka 128)-bit WEP
encryption
If turning off WEP works, then you just need to
provide the cameras with the "Equivalent Network Password".
One of the problems with WEP is that the actual
standard relies on a 10 character HEX key for 40bit
WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier, vendors use certain
algorithms to convert simple alphanumeric passwords
(or passphrases) into HEX keys, thus enabling the use
of simple easy to remember WEP password rather than
lengthy HEX keys. The problem is that different
vendors use different algorithms to generate the HEX
key and therefore a ASCII password on an AEBS will be
hashed differently on a non-Apple client and vice
versa.
You may find the following article helpful:
- Apple article, especially the part about
"Third-party client to Airport".
Brilliant idea about trying the system with No encryption on... that DID solve the problem... almost.. once I turned off the encryption option, and restarted the Airport, I got a dialog box showing that the "Base station needs attention" but it didn't indicate WHAT kind of "assistance" it needed. Nonetheless, I closed out of the Airport program only to find that the indicator light, which had been Green, was now, flashing Yellow and I could not connect anything, including my computer. I opened the Airport program again and found the ONLY way I could get the Green light on was to select some sort of encryption option... then the light would go Green again but my cameras would not hook up again, and when I went back in and ONLY changed the option to NO encryption, I got the yellow flashing light and the "this base unit needs attention" warning...
I think your suggestions are almost on the mark... is there any way of reconciling the WEP coding between the cameras and the Airport??? Or turning off the encryption option and STILL have Airport work?
Thanks again for your help and suggestions... I really appreciate it.
geoff

Power Mac G3 Pismo with Airport wireless card in Mac OS X 10.4 won't connect to wireless network with newest Airport Extreme Base Station set at WPA Personal/WPA 2 Personal encryption.

My Power Book G3 Pismo with an Airport wireless card running Mac OS X 10.4.11 will not connect to my new Airport
Extreme Base Station using WPA Personal/WPA 2 Person encryption. The Airport firmware is version 9.52. From
posts I've read online at different places indicates the Airport card should support the WPA encryption. Perhaps the problem
is the Base Station is using a combination setting and the fault is in the base station?
Thanks for any suggestions

Perhaps an inexpensive usb wireless adapter would work as well?
This is probably the simplest way to get the G3 connected to the wireless network.
I'll have to read up on getting an express and using it as a wireless bridge as I am unfamiliar with the concept.
The new AirPort Extreme is broadcasting a wireless signal.
A new AirPort Express could be located close to the G3. The Express will pick up the wireless signal from the AirPort Extreme, then provide an Ethernet connection to the G3 though a short Ethernet cable.
This can work very well......IF.....you keep the G3 at a fixed location, since it will always be connected to the AriPort Express using an Ethernet cable.
I do have an old Linksys Wireless G router. I wonder if that would work?
In theory, yes. But it would have to use much older WEP "security", which is easily cracked in minutes using free tools available on the Internet. So, anyone who really wanted to get on the network could do so. It's an option, but not a very good one.

Vonage, AirPort Extreme Base Station, and Comcast

I just picked up an Airport Extreme Base Station, and wanted to use it to get my MacBook Pro on my home network. However, I can't get it to actually provide an network connection to the MacBook. In the Network pane of System Preferences, under the Network Status, AirPort has a yellow icon, and the following message: "AirPort is connected to the network HulkNet. AirPort has a self-assigned IP address and may not be able to connect to the Internet."
Here's my current setup:
Comcast > Cable Modem > LinkSys RTP300 > PowerMac, PC, AEBS
I have the "Distribute IP addresses" disabled on the AirPort, and the internet for the PowerMac & the PC work fine. In the network status of the RTP300, the AEBS is listed as having an IP address of it's own.
Any gurus out there that can help me figure this out? I just want to be able to access my home network from anywhere in the house!

All,
I recently posted what I believe to be a similar/identical issue. See my post here: http://discussions.apple.com/thread.jspa?threadID=1378849
I have not changed my AEBS to "Off (Bridge Mode)" yet, because everything currently 'works' but I continue to get the occasional "Double NAT" warning suggesting I switch the AEBS to bridge mode. When this happens, I lose connection to the internet and need to unplugged both the AEBS and my modem to re-establish a connection to the internet and the external HD I have connected to the AEBS.
My question for Jmiller1138, do you continue to get the "Double NAT" warning even when you changed your AEBS to "Off (Bridge Mode)"? I am hesitant to change my AEBS to bridge mode since I'm assuming I'll need to totally reconfigure my entire network (meaning both the AirPort Extremes, my wireless HP printer, and my firewalls on my PCs).
The ignoring of the warning (i.e. closing the AirPort Utility without updating the AEBS) is what triggers the need to reset my AEBS and modem. Not fun.
I guess I'll just need to bite the bullet and set the AEBS to bridge mode . . . yes?

Airport Extreme Base Station Internet Connection issue

I have a connection question for Airport Extreme Base Station.
I have Comcast cable broadband. I connect that to a Linksys router for
use with my Vonage phone, and then from the Linksys router I connect
via Ethernet to my iMac. I like the direct Ethernet connection for
performance reasons.
In order to set up a home network to connect my Tivo's (and eventually
my PC and printer), I have set up an Airport Extreme Base station and
connected it to the Linksys router from it's ethernet connection to the
WAN (cable modem) input on the Extreme.
I have connected to the Airport network with my iMac, but since I am
connected to the Internet via Ethernet, I cannot tell if my Airport is
connected to the Internet so that I can use it for my Tivo. My PC is
still in storage from a move, so I can't check with that.
My question: How can I tell if my Airport is connected to the Internet
without disabling my Ethernet connection on my iMac?
A few more info points/questions in case it helps answer:
1) I previously used this Airport to connect this iMac wirelessly.
2) Should I be connecting it to the LAN port since it's coming out of
the router?
3) If the connection issue is because I am going through the Linksys
first, can I connect the modem to the airport and then use the LAN port
to connect to the Linksys router?
4) If I have to disable the ethernet connection to test the Airport,
how do I do it? Just unplug it?
I appreciate any help as the online and manual help from Apple is not
quite up to par with such a complex configuration.
Regards
Bill

2) Should I be connecting it to the LAN port since it's coming out of
the router?
No, connecting to the WAN port is fine.
3) If the connection issue is because I am going through the Linksys
first, can I connect the modem to the airport and then use the LAN port
to connect to the Linksys router?
The issue is that you have two routers which effectively creates two networks. Unless this was your original intent, you will want to setup the AEBS as a bridge.
To set up the AirPort Extreme Base Station (AEBS) as a bridge, using the AirPort Admin Utility, connect your computer directly (using an Ethernet cable) to the LAN port of the AEBS, and then, make these settings:
Network tab
- Distribute IP addresses (unchecked)
- Apply the new settings.
- Wait at least 5 minutes.
4) If I have to disable the ethernet connection to test the Airport,
how do I do it? Just unplug it?
Well, that's certainly one way, but an easier way is to temporarily disable the "Built-in Ethernet" in your network configuration.
System Preferences > Network > Show > Network Port Configurations
- Built-in Ethernet (unchecked)

Solution to Airport Extreme Base Station + Airport Express networking probs

I've been investigating this for 3 straight days after inadvertently destabilizing my network. There are tons of posts discussing a variety of issues, all of which seem related. My goal here is to provide links to other relevant posts and explain what I ended up doing to get things to work.
First, the background. You can skip below to SOLUTION if you don't really care... However, I highly recommend you take the time to read everything, as you'll get other useful information in the BACKGROUND section. I'm guessing many of you have similar, related problems so BACKGROUND might help provide context (and solutions) to some things you are seeing...
MY SETUP:
AirPort Extreme Base Station (AEBS) of type b/g (round one, not square one), connects to the cable modem, and creates a WDS network that is then shared across two standard AirPort Express (AEX) units (100megabit, not the gigabit ones). One AEX serves as a relay unit that accepts clients, the other serves as a remote unit that also accepts clients. The intent is to show a single network throughout the house and let users log on to one network and move between networking units without having to switch from network to network.
I have a variety of networked devices throughout the house all running on the same network (2 Mac Pros, a Powerbook G4, a Mac Mini, an Apple TV, a Windows XP laptop, two iPhones, two wifi printers, and a 5-unit Sonos system, plus the AEBS and two AEXs). Yeah, I'm a geek.
The Mac Pros are both running 10.4.11, and the Powerbook is running 10.5.2.
AEBS is running firmware 5.7
AEXs are running firmware 6.3
All Macs were initially accessing configs via the recently released AirPort Utility 5.3.1. More on that later.
BACKGROUND:
I've had this network setup working for about a year now. Recently, I've been having poor network performance problems and came to the conclusion it was a LAN problem (ie. problem with my home network, as opposed to with my ISP). Upon initial investigation, I began by looking at my networking logs (via AirPort Utility 5.3.1). You get to those by selecting the unit in question, choosing "Manual Configuration", the selecting the "Advanced" tab up top with the "Logging and SNMP" sub-tab. Click the "Logs and Statistics" button therein for log details from that unit.
The first thing I noticed was "Administrative access denied to ff80::xxxxxxxxx" messages - a lot of them. I didn't recognize the ff80:: address in question, and so became concerned it was someone outside the network trying to hack one (or all) of the AEBS/AEX units. You can see threads discussing that investigation here:
"Hack or panic?" - http://discussions.apple.com/thread.jspa?threadID=1438486
"Administrative access denied" - http://discussions.apple.com/thread.jspa?threadID=1438865
Long and short of it is that the recent AirPort Utility 5.3.1 release (current as of March 13) seems to have problems (keychain) when attempting to access the AEBS and AEX units. The "Administrative access denied" logs actually refer to the client machine you are using when you try to read the logs. The ff80::xxxxxx address is simply the IPv6 address for the machine you are using; if you turn off IPv6 on your client machine, that address should switch over to begin showing a regular IP address instead (something like 10.0.1.xxx), which makes it easier to associate the IP to the machine. I explain how to deactivate IPv6 on both Tiger (10.4.x) and Leopard (1.5.x) here:
http://discussions.apple.com/thread.jspa?messageID=6814978#6814978
Anyway, in the process of investigating the "Administrative access denied" problem, I began tinkering with my AEX settings. Specifically, I ended up performing a hard factory reset (unplug unit, plug back in while holding down the little button with paper click/pen for ~10-15 seconds until light flashes green 4x then reverts to amber/yellow/orange). I began reconfiguring my entire WDS network using the newly updated AirPort Utility 5.3.1, and that's when the trouble started.
(If you are having problems seeing either your AirPort Extreme Base Station or AirPort Express, read this:)
In short, each time I thought I had properly configured things and then confirmed settings (kicking off a reboot on the AEX unit) the unit would restart with new settings but not properly join the WDS and not show up in the AirPort Utility list of units. More specifically, I would start with a "wiped" AEX and see both the AEBS and the AEX in my AirPort Utility list, but upon confirm/reboot the AEX would disappear and the AEBS would remain. However, that's not 100% correct. It seems that sometimes I would end up with the AEX and NOT the AEBS. Because both the AEX and AEBS were theoretically "hosting" the same network name (remember, WDS shares the network name across units) my auto-login feature for my client computer's wifi seemed to "jump on" whichever unit it first saw hosting the default network name for my house. In other words, it seems what was really happening was that I was ending up with two separate networks in my house, both with the same name but not talking to each other (as opposed to two units sharing the same network name and internet connection). The AEX would continue to blink orange/amber/yellow (whichever color it is to your eyes ) because it could not grab an internet connection -- and if I was on the network through that AEX unit I would not get internet. But if i was connected through the AEBS I would continue to have internet access. As far as my client computer (my Mac Pro) was concerned, I was on the home wifi network even if I was on the AEX rather than the AEBS -- it would show the home wifi network name as the name of the network it had connected to. But when I opened the AirPort Utility 5.3.1 I would see only the AEX (if I was connected through it) or the AEBS (if connected through it) -- a clear indication that the units were not truly sharing the same network.
I tried rebooting and reconfiguring the AEBS and AEX about 50 times (literally). I even tracked down an older version of the AirPort Utility 5.2.1 via this thread (see Tesserax post):
http://discussions.apple.com/thread.jspa?threadID=1067565
One interesting thing re: 5.2.1 is that the "Administrative access denied" errors summarized above disappeared. As explained in a post reference above, the going theory is that this a permissions/keychain problem new and unique to AirPort Utility 5.3.1. However, even though 5.2.1 does have a slightly different interface with different settings, I still couldn't get the WDS to work.
EVENTUALLY, I came across this post:
http://discussions.apple.com/thread.jspa?threadID=1422527
MuaddibOfArrakis walks through setting up a WDS from scratch, and the workflow is different than what is possible with either AirPort Utility 5.3.1 or 5.2.1. He's doing it with the old version of AirPort Admin Utility, which I fortunately saved a copy of many moons ago when I had somewhat-related problems with my WDS (since forgotten). In fact, it's a lot easier. What's nice about this older app is that it literally does the heavy lifting of "connecting" the AEBS and AEX units during the configuration -- it reboots both at the same time as the config is happening, and lets you choose from a list of available units to "add" to your WDS network. In short, it's a FAR SUPERIOR workflow even though some of the GUI isn't as intuitive as the newer AirPort Utilities that were designed to replace it.
SOLUTION:
If still have a copy of the AirPort Admin Utility follow the instructions from MuaddibOfArrakis here:
http://discussions.apple.com/thread.jspa?threadID=1422527
If not, try setting up your WDS network using AirPort Utility (hereafter AU), with these configs (take from my now-working network), as viewed through AirPort Utility 5.3.1.
I. Configure your AEBS.
Select the AEBS from AU, and choose "Manual Setup"
1. Under the AirPort tab up top:
a. Under "Base Station" sub-tab:
i.) assign a name for that specific unit, so you can later identify the specific unit from the list of units -- this is the name that will show up beside the unit in the AU list of configurable units. You can name it something like "kitchen", or "office". I have mine numbered, so XXXXXv1, XXXXXv2 etc where the XXXXX is the name of the shared network and the numbers help me tell the units apart. Just be sure you name each uniquely, and if you have several you might write the name on the unit itself.
ii.) pick a password for logging into that unit. This is different from the network password, its a security check to get in and change the configs on this unit later. Be sure to remember it in your keychain for the sake of simplicity, and write it down somewhere secure.
iii.) if you choose to set time automatically, pick a location that you will use consistently across all your units. I use time.apple.com.
iv.) uncheck "Allow configuration over Ethernet WAN port" unless you want to be able to remotely mess with settings -- which you almost certainly do not need to do.
v.) I left the "Options" button alone - no settings there.
b. Under the "Wireless" sub-tab:
i.) Wireless Mode: "Participate in a WDS network"
ii.) Network Name: this will be the name of your wifi network shared by all units, so be sure to remember what you pick. If you are already connected to this AEBS via wifi while you are making these changes, then you can use the same wifi name you already have set up -- you don't have to change it. Note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
iii.) pick a Radio Mode. I'm using b/g compatible. You'll want to do the same, unless you are on the new gigabit AEX. I'm pretty sure about this, but not 100% -- others post if I'm wrong.
iv.) choose a Channel. This can be a more complicated procedure, but for now just pick something consistent across all your units. If you get everything working and find that you're having intermittent network problems, you could later try changing your Channel -- it can pick up interference from phones, microwaves, etc and changing it can help.
v.) I have wireless security set to WPA/WPA2 Personal.
vi.) Wireless Password is the password for access to your wifi network (not your unit itself). If you are connecting to your AEBS via wifi while doing this config, then you can use the same password you have already set up. Pick a good one unless you want other folks jumping on your wifi and stealing your bandwidth and/or credit card numbers . Remember it in your keychain and write it down someplace secure, because you'll need it for the other units too. As noted above, note that if you DO change it, after reboot your will LOSE connection to the network and have to reset your wifi settings on your client machine to match the new network/password in order to be able to access the network.
vii.) Click the "Wireless Options" button. I have my multicast rate set to 2mbps, transmit at 100%, timeout at 1 hour, and i have checked the "Create a closed network". This last step keeps your network from advertising itself to the outside world. Users can only find it by explicitly typing the network name into their wifi settings (e.g. AirPort -> Other... then enter Network Name, Security and Password). I leave interference robustness unchecked.
c. Under the "WDS" sub-tab:
i.) the AEBS should have it's WDS Mode set to "WDS main".
ii.) Check the "allow wireless clients" box on the AEBS; this lets you connect client machines to it directly too.
iii.) hit the plus button to add the Remote system (AEX). There are two types of configs for the AEX's - "remote" and "relay". Assuming you have 3 units like me (2 AEX and 1 AEBS) the key question is whether you will place each AEX within direct reach of the AEBS (remotes), or if you will have one AEX in the middle connecting to an AEBS on one side and an AEX on the other -- where the furthest AEX is out of reach from the AEBS (remote) and connects only to the AEX in the middle (relay). I'm using a relay setup. If you are using relay, you can still set up the AEX relay to serve client computers too -- it doesnt have to JUST relay. More on that later. For now, you want to add only AEX units that will talk DIRECTLY to the AEBS. So if you have a setup like mine, just add one (the one in the middle - the relay). If you have two remotes connecting directly to the AEBS, you will add them both here. When you hit the '+' button it will ask for both an ID and description. For description I use the name I'm assigning to each unique unit (as above, "kitchen" or XXXXXv1 or whatever you use). For AirPort ID, use the number listed on the AEX unit itself (not the number for "Ethernet", also on the AEX unit).
d. Under the "Access" sub-tab:
i.) I have it set to "Not Enabled". I'd suggest you start that way too, and you can go change it later if you get everything working correctly.
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: Ethernet
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Share a public IP address
b. Under the "DHCP" sub-tab:
i.) DHCP Beginning Address: 10.0 . 1 . 2
ii.) DHCP Ending Address: 10.0.1.200
DHCP Lease: 4 hours
c. Under the "NAT" sub-tab:
i.) nothing should be checked;
ii.) nothing under Port Mappings either
3. Under the "Printers and Advanced" tabs up top:
Nothing special needs to be configured there.
THAT'S IT.
=============
I. Configure your AEX(s)
Select the AEX from AU, and choose "Manual Setup"
1. Under the "AirPort" tab up top:
a. Under "Base Station" sub-tab:
i.) pick a unique name for this unit, same logic as for AEBS
ii.) pick a password specific for accessing this unit, same logic as for AEBS
iii.) Set time automatically: be sure to use the same settings used on your AEBS
iv.) Options: no need to set any
b. Under "Wireless" sub-tab:
i.) Wireless Mode: Participate in a WDS network
ii.) Network Name: same name used for AEBS, this is the name of your wifi network
iii.) Channel: same as AEBS
iv.) All settings here (those above, plus Security and Password & in Options button) should be the same as for AEBS settings on this tab
c. Under the "WDS" sub-tab:
...if AEX is "in the middle" (as described above):
i.) WDS Mode: WDS relay
ii.) Allow wireless clients: check (unless you only want to bridge between the edges without letting folks connect on this AEX in the middle)
iii.) WDS Main: set to the AirPort ID (aka MAC address) for the AEBS. You can find it on the bottom of the AEBS, either labeled as such or at the bottom beside the logo of a wireless signal (square logo, with semi-circles mimicing a radio signal).
iv.) WDS Remotes: click the '+' to add any AEX's that will connect to this relay rather than directly to the AEBS. Same deal as above, use the name in the description and use the AirPort ID from the side of the AEX (not the Ethernet ID).
.....if AEX is connecting to a relay ("on the end", as above) or if there is no relay and AEX connects directly to the AEBS:
i.) WDS Model: WDS remote
ii.) Allow wireless clients: checked
iii.) WDS Main: if connected to a relay, use the AirPort ID of the relay AEX. If connected to the AEBS directly, use the AirPort ID of the AEBS
d. Under the "Access" sub-tab:
i.) MAC Address Access Control: Not Enabled (for now, you can change later)
2. Under the "Internet" tab up top:
a. Under the "Internet Connection" sub-tab:
i.) Connect Using: AirPort (WDS) -- should be selected and gray'ed out.
ii.) Configure IPv4: Using DHCP
iii.) Ethernet WAN Port: Automatic (Default)
iv.) Connection Sharing: Off (Bridge Mode)
3. Under the Music, Printers and Advanced tabs up top:
Nothing special needs to be configured there. You can worry about AirTunes settings later...
That should be it. I'd recommend setting up the AEBS first, then the relay (if applicable), then the remotes. Initially, you can bring each unit in the same room with you for configuring. After configured and restarted the AEX should blink then turn solid green. If it turns green you should be good to go.
HOPE THIS HELPS. As noted above, I did not config through AirPort Utility 5.3.1 so I haven't tested this procedure through that app. However, after getting my network to work I went back and transposed all settings into this post to help others. Please provide feedback on whether or not this is working, so we can collectively try to move towards a setup procedure that works for everyone....
Good luck!
Message was edited by: b.byrd

I'm not convinced that the problem lies in Airport Utility. This same thing was happening to me, nearly exactly as you describe it. The thing is that with me, the problems clearly started when I updated the firmware in my Airport Express (n). That's when all the wacky stuff started happening. Sometimes it would show up in AU, sometimes it didn't and even if it didn't, I could still access the internet through it.
But as you said, the problems got really bad when another Express (b/g) was put on the network with it. Even when it did work, the (b/g) would make it impossibly slow.
You know more about this than me, and clearly have more patience if you've restarted the network fifty times. I gave up at about ten.
In any case, your solution is more of a work around and if you're still having that slow connection problem, I'm not sure you've got it. But thanks for your reporting of this. At least I know I'm not crazy.

Define static IP for both LAN and W-LAN devices with an Airport Extreme Base Station

Hey guys,
I have a lot of different devices connected to my Airport Extreme Base Station (5th Gen) either wirelessly or via ethernet cable. Since I control some of them via VNC and currently have to find the corresponding IP-addresses through trial-and-error, I'd like to define static IP-addresses for the computers in question. My network consists of a cable modem connected to a TP-Link WR1043ND router in the basement, from which an ethernet cable leads to the WAN-port of the aforementioned Airport Extreme Base Station on the 2nd floor. Two of the devices I want to remote-access are wired to a D-Link DES-1005D switch, which in turn is connected to the 1st ethernet port of the Airport Base Station. The remaining 3 remote clients are connected over 802.11n. All computers run Windows.
My problem now is that even though I was able to define static IP-addresses employing the "DHCP only" router mode, this didn't seem to work for the two computers connected via ethernet. Not only did I lose any internet connectivity with those, I even lost the ability to remote-connect to them using the VNC-viewer.
The question now is: how do I specify static IP-addresses for my ethernet devices correctly?
I hope you can help me.

My network consists of a cable modem connected to a TP-Link WR1043ND router in the basement, from which an ethernet cable leads to the WAN-port of the aforementioned Airport Extreme Base Station on the 2nd floor.
If you read the information in the other post, my answer would be the same here.
The Router Mode of DHCP Only is rarely used, and would only really be appropriate if your ISP was providing you with a fixed bank of multiple fixed or static IP addresses to use. This does not appear to be the case in your post.
If this were the case, the first IP address would be used as a Static IP address for your connection, and other devices on your network would receive the other fixed IP addresses.
99%+ of the time, you would use the Router Mode setting of DHCP and NAT on a network when you want the AirPort to perform as the main router for the network.
But......your post also indicates that you have another router upstream on your network from the AirPort Extreme. You would not want to run two routers in series on a network. That explains the problems that you are having.
The AirPort Extreme needs to be configured in Bridge Mode. It cannot be the "main" router on your network when you already have another router on the network. That is a fundamental networking rule.

Linksys WRT54G bridge to AirPort Extreme Base Station

Similar Messages

Maybe you are looking for