Re: [NTLK] WiFi setup help

From: Morgan Aldridge <morgant_at_makkintosshu.com>
Date: Sun Jul 26 2009 - 09:52:17 EDT

On Sat, Jul 25, 2009 at 8:34 AM, David Neale<david.neale@telenet.be> wrote:
>
>>> It's got an IP of 192.168.1.1, so is it providing DHCP to your other
>>> machines? It is if they're getting IPs in the 192.168.1.x range and
>>> are set by DHCP.
>
> Well, I have no idea what DHCP is (other than that using the DHCP
> setting in Hiroshi's driver doesn't work), nor how to see which IPs
> the Macs have. Sorry.

Tony Kan has a good description of DHCP in his reply to this thread.

On the Macs, go to  -> System Preferences -> Network and select
AirPort (if they're running Mac OS X 10.5 Leopard, you'll have to
click the "Advanced..." button to see the TCP/IP settings). Under the
TCP/IP settings you should see the IP address. There should also be
something the says "Configure Using" and is probably set to "DHCP". It
may be set to "Manual".

Please report back what the IP address on the Mac is and whether it's
set to "DHCP" or "Manual".

>>> 1) Disable sharing a single IP in the AirPort (that way you don't
>>> have
>>> double-NAT which might cause some issues) by going to the "Network"
>>> tab an unchecking the "Distribute IP addresses" checkbox. Then save
>>> the settings, of course.
>
> This will not affect the WiFi connections from the Macs…?

If the Macs are connecting through the AirPort then no. Not doing this
should actually be causing some Internet access issues on the Macs as
well. Mostly affected will be things like iChat, GoogleTalk, AOL
Instant Messenger, some video streaming services, etc.

It does depend on the IP addresses and the configuration method on the
Macs, though.

>>> 2) Then make sure that the AirPort is plugged into your router via
>>> the
>>> Ethernet (<••>) port, as opposed to the WAN (the little dotted
>>> circle)
>>> port to make sure it's properly picking up DHCP from your router.
>
> The Ethernet cable is connected to the Ethernet port of both devices
> (not the dotted circle).

Aha! That would explain why the AirPort has a self-assigned
(169.254.x.x) IP address! To share a single IP address, as your
AirPort is currently configured, you'd need the ethernet cable to be
connected to the WAN port on the AirPort.

If you switch the cable temporarily, restart the AirPort, does the
AirPort's IP address change to a 192.168.1.x IP address?

If you only do one thing, this simple test will give me a lot of info,
but the IP address info from the Macs would be very helpful as well.

> But I don't have any other problems, and people who visit with their
> laptops are able to get online, too (if I give them the password!). My
> wife bought a MacBook a couple of weeks ago, came home, opened it up
> and, with the Airport network password, is online straight away -- no
> settings at all to be done on the Mac. I realise that the Newton
> operating system and its networking add-ons are not as sophisticated
> as those of MacOS X, but I think this shows that the network setup of
> the Airport is at least functional, if not 100% according to the
> rules. I suppose what I'm really trying to say is, believe me, it works.

I believe you that it works, all I'm saying is that it shouldn't with
the settings you showed on your web site. :)

Morgan Aldridge

---
morgant@makkintosshu.com
http://www.makkintosshu.com/
==================================================================== 
The NewtonTalk Mailing List - http://www.newtontalk.net/
The Official Newton FAQ     - http://www.splorp.com/newton/faq/
The Newton Glossary         - http://www.splorp.com/newton/glossary/
WikiWikiNewt                - http://tools.unna.org/wikiwikinewt/
====================================================================
Received on Sun Jul 26 09:52:25 2009

This archive was generated by hypermail 2.1.8 : Mon Jul 27 2009 - 12:30:00 EDT