Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Configuring a Linksys wireless bridge on a Mac Network
I recently purchased a Linksys Wireless Network Bridge (the WET11) in order to put a desktop G3 in a remote part of the house on the network without running wires. The WET11 has the advantage that it connects to your computer (or anything really) via a simple ethernet cable, and turns it into a wireless device capable of communicating with an Airport network (or any other 802.11b wireless network). There are no drivers to install and no compatibility problems.

However, there is a small snag. After playing with the WET11 for several hours, I could simply not get out to the Internet. I could see the DSL router, and all the other computers on the network, but no Internet. This really had me baffled, because the WET11 doesn't really do any filtering; it's supposed to just pass the information through. Hooking up a cable proved that the settings on the Mac weren't the issue, and I spent quite a long time on the phone with Linksys tech support to no avail.

Hooking the WET11 up to a PC worked like a charm. On the Mac, it was restriced to the LAN only. It just didn't make any sense. I finally, out of desperation more than anything else, tried changing my whole network addressing sheme, and lo and behold, now everything works fine. So, if you want to use the WET11, there are a couple of things you need to know.
  1. To set it up with a Mac, you simply hook it up with a cable and type it's address, which happens to be 192.168.1.225 into your browser.

  2. To do this, your own computer's IP address has to be in the same range, i.e. it has to be 192.168.1.(some number between 1 and 255). Go to System Preferences -> Network to set this.

  3. When you configure your network you cannot use 192.168.0.x I haven't tried any other ones, but 192.168.1.x works.
This last part was causing the problem in my setup. It doesn't make sense, it doesn't apply to PC's, but it seems to be a fact.

If you use the 192.168.1.x address range, and if you don't have any other devices at 192.168.1.225, then the WET11 should work right out of the box. You don't even need to set it up, unless you want to enable WEP. WEP, BTW, is not secure, do a web search before you trust any data to it.
    •    
  • Currently 2.75 / 5
  You rated: 5 / 5 (4 votes cast)
 
[34,339 views]  

Configuring a Linksys wireless bridge on a Mac | 21 comments | Create New Account
Click here to return to the 'Configuring a Linksys wireless bridge on a Mac' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
I'm to not too sure about that...
Authored by: smaffei on Nov 25, '02 10:44:45AM

I have WET11 (which is a great little piece of hardware) and was running it with an AirPort Dual Ethernet Base Sation using 10.0.1.x addressing. It worked fine. However, I found the WET11 was much easier to configure using the PC software via VirtualPC (Connectix comes through in a pinch again!).

I only switched to Linksys wireless router because I needed a DMZ function for my XBox (which works fine with the WET11) gaming. The Airport Base Sation doesn't support DMZing.



[ Reply to This | # ]
I'm to not too sure about that...
Authored by: seven5 on Nov 25, '02 02:19:51PM

do you have xbconnect running with your xbox? or are you using the os x app, or are you useing straight xbox live.....



[ Reply to This | # ]
I'm to not too sure about that...
Authored by: Fofer on Nov 25, '02 10:50:44PM

I'm curious to know more about XBox's "incompatibility" with Apple's Airport Base Station. Couldn't you just use "port mapping" to open up the specific ports that XBox uses, and have them go to the XBox's IP address? In this case DMZ would be overkill. The ports in question, according to Microsoft's tech support, are UDP 88, UDP 3074, and TCP 3074.

I just upgraded from my SMC Wireless 7004AWBR wireless router to Apple's - because I wanted to turn off beaconing (in order to create a "closed network.") This way my neighbors can't see my wireless network name being broadcast - which I imagine presents the biggest security risk of all. Beaconing all but taunts a hacker to try and get in. 802.11b isn't secure by any means, but this would be the first line of defense IMHO.

I see that I lost the DMZ function with the ABS, but I now have better range and stability, and the configurator application is a lot nicer/easier than web-based configuration. There are additional funtions, like channel choice, station density, multicast rate, and interference robustness.

The Apple Base Station is certainly more expensive, but works a lot better IMHO.



[ Reply to This | # ]
I'm to not too sure about that...
Authored by: Fofer on Nov 25, '02 11:21:06PM

Oops, as an addendum...
*Can* you open holes for UDP traffic on the Airport? Or just TCP? If not, then that'd be a reason to switch routers. XBox Live compatibility is important!



[ Reply to This | # ]
I'm to not too sure about that...
Authored by: sammaffei on Nov 26, '02 09:22:04AM

And you map a UDP port on an AirPort Base Station how? You can map TCP but you can't map UDP.



[ Reply to This | # ]
Repeater
Authored by: prk on Nov 25, '02 12:38:14PM

I use the WET11 and a WAP11 for repeaters to my WISP. Still a few bugs in it, like I have to turn the WAP11 on before the WET11 or they dont connect to eachother. Other than that, it works well.

Also to configure it, I just make an alias ethernet device on 192.168.1.10 and I can then use the web browser to change the IP.



[ Reply to This | # ]
Subnet mask?
Authored by: stephen007 on Nov 25, '02 01:33:06PM

>When you configure your network you cannot use 192.168.0.x
>I haven't tried any other ones, but 192.168.1.x works.

I think the reason it worked on the PC but not on the Mac was that you were using 255.255.0.0 for the PC and 255.255.255.0 for the Mac. This would restrict the Mac so 192.168.1.x IPs.

I ran into _exactly_ the same situation when I setup my WET11. Baffled me for about an hour until I re-IP-ed the WET11 to be 192.168.0.something. Glad I'm not the only bozo out there ;-)

Stephen



[ Reply to This | # ]
Subnet mask?
Authored by: bakalite on Nov 26, '02 12:16:16PM

stephen007 wrote:
>I think the reason it worked on the PC but not on the Mac was that you were using >255.255.0.0 for the PC and 255.255.255.0 for the Mac. This would restrict the Mac so 192.168.1.x IPs.
--
No, that was not the problem. I first set the WET11 to 192.168.0.225, and my entire network was also on 192.168.0.x Nothing worked.

The PC is ALSO set to 255.255.255.0

I've had reports from other people with this problem, it's not a simple goof on my part as far as I can tell. Also, remember that I was on the phone with Linksys for over an hour. If it was something that simple surely someone would have caught it.



[ Reply to This | # ]
Appletalk
Authored by: jason mark on Nov 25, '02 02:00:45PM

Linksys doesn't support appletalk, which is a bit of a drag. We're probably going to chuck our Linksys router soon for that very reason. It's a pain.

Also, for other people having trouble with WEP protection. Try putting a $ in front of your password. There is an apple knowledgebase item about this somewhere.



[ Reply to This | # ]
Appletalk
Authored by: smaffei on Nov 25, '02 02:09:53PM

Yeah, but isn't AppleTalk supposed to go away soon anyway. At least that's what Apple was saying when they introduced X. AppleTalk is currently a legacy technology they are supporting.



[ Reply to This | # ]
Appletalk
Authored by: macubergeek on Nov 25, '02 02:17:46PM

1. with 10.2.2 you no longer have to put a $ infront of hex
for the wep key
2. just as well the linksys dosn't support appletalk, filesharing across a
wireless link is potentially a very very bad idea.



[ Reply to This | # ]
who cares..
Authored by: seven5 on Nov 25, '02 02:24:40PM

If you run Os X you don't need apple talk. I have a linksys wet11 and i use it with my iBook (800mhz combo :) ) and i connect to my tower and emac just fine. I'm not sure what protocol it uses, but i know its not samba. I see my macs on the wireless network and choose my file system to mount. and voila, i'm in. Appletalk is almost dead, and a very poor protocol at that. Stick with your linksys router that gets regular updates, and has good support.

Remember, the less popular your product, the less help you get on google :)



[ Reply to This | # ]
who cares..
Authored by: Fofer on Nov 25, '02 10:31:59PM

What about AppleTalk printers... you know, laser printers that connect via LocalTalk/Ethernet adapters? Sorry, but for a lot of folks, AppleTalk is NOT dead. Whenever possible I advise clients to go TCP/IP instead... but in some cases, it's just not feasible yet. OS 9 or OS X, it makes no difference.



[ Reply to This | # ]
who cares..
Authored by: Burgoo on Sep 14, '03 09:29:15PM

I am one of those people who still has an old localtalk printer. I currently don't have the resources to buy a network-ready printer, so I have to use AppleTalk, but I'm experiencing some problems seeing the printer.

I'm on an iMac that's connected to a WET11 that connects to a Linksys WRT54G router. The printer is connected using the AsanteTalk Ethernet to LocalTalk Bridge that is also connected to the router.

I think there's something going on with the WET11 only because next the iMac is an eMac that connects to the same router via Airport and I can see and print fine.

Currently AppleTalk is active (checked) in the System Prefs > Network.



[ Reply to This | # ]
IP Networking
Authored by: jasonguin on Nov 26, '02 12:40:06AM

I haven't used the WET11, but your problem revoled around IP networking. An IP address is made up of a network and a host portion. The network mask indicates which part is which. (So if your mask is 255.255.255.0, the first 24 bits of your IP address identify your "network prefix" and the rest your host.)

An IP network is a group of devices that are sharing the same physical link. Since your WET11 and computer constitute an IP network, they must share the same network prefix. So what's important here is that the network mask is the same and you don't assign an IP address that violates it. So, if both devices are set with a network mask of 24 bits, then they must both have IP address of the form 192.168.1.xxx. It they both have a mask of 16 bits, then they'd could take on the form 192.168.xxx.xxx

Either way, you're up and running now. Gotta feel good about that. 8')




[ Reply to This | # ]
IP Networking
Authored by: bakalite on Nov 26, '02 12:23:19PM

Guys, the problem was not one of IP address mismatch, subnet settings, router settings, or any other settings. Let me make this perfectly clear:

All the computers on the network are set to 192.168.0.x
All the routers (including the gateway and the WET11) are set to 192.168.0.x
The subnet mask is 255.255.255.0 on ALL machines.
The gateway router is communicating with the internet as evidenced by net access on other computers in the system.

The PC will work in that setup with the WET11, the Mac will not have any internet access.

I know you are trying to figure out a way that this would make sense....it doesn't. I suspect it's some strange bug between the Mac and the WET11, there is no other explanation anyone has come up with that makes sense.

In any case, setting the whole network to 192.168.1.x fixes the problem....and that's the important part :-)



[ Reply to This | # ]
IP Networking
Authored by: JT on Nov 26, '02 03:23:15PM

Ok, im not fully awake and i could be talking crap, but maybe you have IP forwarding enabled on the Windows PC. I havent put a lot of in depth thought into the idea but isnt that like a software router built into Windows NT OS'es. Could be a bung theory considering I dont even know wot Windows OS youre using.

Yup im going back to bed now...



[ Reply to This | # ]
not likely....
Authored by: Sveto on Dec 10, '02 05:47:38PM

In a few lines jasonguin explains it all. It is a fact though that you don\'t understand it. Just make google search for \"network mask of 24 bits\" and try to read carefully most of the things you find. After understanding the idea you will get the reason for your problem.
Anyways it is no bug, you just miss the point.



[ Reply to This | # ]
Configuring a Linksys wireless bridge on a Mac
Authored by: danielmaui on May 13, '03 01:33:35AM

Just don't try it with Safari. You get an error... must not like the embeded web server in the WET11. Mozilla and IE work just fine.

Daniel



[ Reply to This | # ]
Re: Configuring a Linksys wireless bridge on a Mac
Authored by: sjk on Jun 13, '03 08:06:35PM

Configuring a WET11 works fine for me with Safari 1.0 Beta 2 (v74), but I could only upgrade its firmware from a PC since it's done with a .exe utility.

PS - Greetings from Hawaii.



[ Reply to This | # ]
Configuring a Linksys wireless bridge on a Mac
Authored by: macdudex on Nov 25, '03 02:18:02PM

I just bought a WET11 and have an airport snow. I was able to configure using the web browser in safari and get it working when it was plugged into the hub on my airport and connecting wirelessly via powerbook giving it an address on my network. Now the only issues I have is when i unplug it from the hub and go wireless to wireless between my airport and wet11 so I can connect a pc via dhcp to the wet11. The airport wont assign address though the wet11. Anyone else have this problem or a suggestion?



[ Reply to This | # ]