[BAWUG] Re: wireless Digest, Vol 1, Issue 4

Alf Watt Tue, 23 Mar 2004 16:01:59 -0800

I poked around and couldn't find a good answer to this, but here are some clues. I've had luck with the airport on-off which you can do at a command line:

        sudo ifconfig en1 down
        sudo ifconfig en1 up

If you look at /System/Library/StartupItems/Network you'll see the script the system uses to start the network, most of which comes up automatically in the kernel. You might also play with ipconfig which allows you to change the interfaces configuration without a trip to the control panel:

        sudo ipconfig set en0 NONE
        sudo ipconfig set en0 DHCP
        sudo ipconfig set en0 MANUAL 10.0.0.5 255.255.255.0

You might also find clues about the problem in the kernel state using sysctl:

sysctl -A net.inet

FWIW I think you have a genuine bug, another OS X user has reported the same problem which only a reboot resolves. Getting to the bottom of it probably means digging into the Darwin kernel code and some very trick debugging sessions.

Best,
Alf

On 23 Mar 2004, at 12:09p, [EMAIL PROTECTED] wrote:

Date: Tue, 23 Mar 2004 08:53:21 -0800
From: DaveC <[EMAIL PROTECTED]>
Subject: [BAWUG] TCP & Airport malfunction
To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

I've got an (original series) Airport card in my PowerBook G3/400
(Firewire) running OS X 10.3.2. Usually, things are fine. Because of
where the Linksys AP is located, signal strength varies, depending on
where I am with the PB in my home.

In one location, signal strength (measured with AP Grapher -
http://www.chimoosoft.com) drops too low to provide a viable
connection.

When I relocate to a place where the signal strength is good (at
least 50 percent according to AP Grapher -- 3 bars by the menu bar
icon), my TCP apps still can't access the internet. (Eudora gives
"Domain does not exist" error; Safari gives "Cannot find the server"
error.) It seems that once signal strength recovers, TCP access
cannot.

I have tried turning off the Airport card and turning it back on; no
joy. I tried restarting each app; no joy. Only a reboot will fix the
trouble. (I'm configured as a single-user system, so I can't log out;
there is no log screen with 1 user.)

Other times, I can boot the computer and see less than 50 percent
signal and have slow but successful TCP service.

Has anyone else experienced this problem? Any solution? Barring a
fix, is there a Terminal command that will restart the TCP/IP daemon
(I'm guessing that there is one -- my UNIX knowledge is pretty
limited)? Or something else I can do from Terminal that would allow
me to kick-start the TCP/IP chain.

Ideas?

Thanks,
Dave


_______________________________________________
BAWUG's general wireless chat mailing list
[unsubscribe] http://lists.bawug.org/mailman/listinfo/wireless

[BAWUG] Re: wireless Digest, Vol 1, Issue 4

Reply via email to