From: nospam on 11 Jun 2010 00:27 In article <michelle-528C63.21111910062010(a)reserved-multicast-range-not-delegated.e xample.com>, Michelle Steiner <michelle(a)michelle.org> wrote: > All wireless routers get IP addresses wirelessly if they're set up to do > so. You'll need to configure the AE to Extend a Wireless Network and use > its own NAT. unfortunately, that doesn't work with any old router.
From: nospam on 11 Jun 2010 00:30 In article <husd2d$s6k$1(a)news.eternal-september.org>, Justin <justin(a)nobecauseihatespam.com> wrote: > > it has one major drawback (other than being discontinued) in that it > > can only join wifi networks that do not require a password. that makes > > sense from a security standpoint, because someone could potentially > > turn a closed network into an open network just by plugging this thing > > in. > > Most networks with theis pash page are unsecured. Besiced when one does > banking it should be done over its own encryption. I won't do VPN, but > I will probably do some sFTP, scp and some IRC. I'm old school. > I don't do torrents. banking will be https, so it doesn't matter if you use it on an open network (although i generally do not). banks are extremely anal about security, sometimes asking the security questions if they see a new ip address for your account. > > fortunately, nearly all hotel networks are open, with a splash page to > > log in. that splash page will get passed to your laptop and you can log > > in from there, with the linksys being seen by the hotel network. you > > can also change the mac address of the linksys, just in case. > > Most hotel syaadmins won't understand that aspect, but its nice to know > it can be changed. they don't need to know. if for some reason you have to use your laptop directly, you can do that and then just switch the mac address of the linksys. i've never needed to do that.
From: nospam on 11 Jun 2010 00:34 In article <michelle-831ACC.21121310062010(a)reserved-multicast-range-not-delegated.e xample.com>, Michelle Steiner <michelle(a)michelle.org> wrote: > > > Ah ha, now we're getting somewhere. > > > Can the Airport Express get an IP address wirelessly, and share that > > > connection wirelessly to other machines? > > > > no, an airport express can only bridge to ethernet or the reverse. > > I think you're wrong about that. it can't associate to a wireless network and rebroadcast on another wireless network. that's what makes the linksys so cool. the airport does do wds, which works great for extending another airport network, but not so much for a random hotel network.
From: Wes Groleau on 11 Jun 2010 07:23 On 06-10-2010 22:25, Justin wrote: > MBP and a few other machines - some are Macs some are Windows 7. > The hotel won't have an ethernet port so I can't share the ehternet port > connection. My answer to that was: >> ...., connect a WiFi AP to the >> Macbook Pro's Ethernet. Set it to a different channel, >> different SSID from the hotel's. In other words: Hotel -> MBP WiFi -> MBP ehternet -> WiFi AP -> other device But if "other device is in other room," isn't WiFi included in the room charge? If not, I guess we are assisting in theft of service. -- Wes Groleau "To know what you prefer, instead of humbly saying Amen to what the world tells you you should prefer, is to have kept your soul alive." -- Robert Louis Stevenson
From: Fred McKenzie on 11 Jun 2010 19:34
In article <hut6bl$dkc$1(a)news.eternal-september.org>, Wes Groleau <Groleau+news(a)FreeShell.org> wrote: > Hotel -> MBP WiFi -> MBP ehternet -> WiFi AP -> other device Wes- I think the original assumptions may be wrong. My experience with hotel WiFi has been that a number (certainly more than one) of users can be connected. Such systems may be distributed across several WiFi base stations located in different wings and on different floors. You can take your laptop from your room to the hotel lobby, and maybe outdoors, without loosing connection. In other words, the disconnect that was originally noted, may have some other cause. But suppose you do set up a re-distribution system as described. That would not keep a second person from logging into the hotel's system and knocking your system off line, if that could occur in the first place. As far as your hookup goes, I would prefer to use the WiFi AP to interface with the hotel system, feeding the MBP via Ethernet, and using the MBP to share the connection via AirPort. Either way, the MBP and WiFi AP may interfere with each other due to overloading, even if on opposite ends of the channels. Therefore, you would need to use a LONG Ethernet cable and separate the units as much as practical. Fred |