Network stack: three strikes and you're out....

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

David Lesher - 27 Jun 2008 17:08 GMT

I keep getting bitten by an annoying bug in the TCP/IP system.

You can change from say a DHCP network configuration to a static
IP address. No rebooting needed; this is a real OS.

You can change it again, great...

But somewhere about the third or 4th time; the GUI says it's the new
settings.... but it is not..it is still the old ones.

At that point; your only solution is to reboot.

Now, you might think no one ever has to reset their addresses more than
once; but if you are doing network testing or working with a device you
configure via a browser....

Two things make this a PITA. First, it's silent. Second, it's existed
since at least OS9. In fact the only reason I thought to reboot was my
past grief with OS9....

I wonder if Apple will ever fix this..

Signature

A host is a host from coast to coast.................wb8foz@nrk.com
& no one will talk to a host that's close........[v].(301) 56-LINUX
Unless the host (that isn't close).........................pob 1433
is busy, hung or dead....................................20915-1433

Reply to this Message

Jolly Roger - 27 Jun 2008 17:42 GMT

> I keep getting bitten by an annoying bug in the TCP/IP system.
>
[quoted text clipped - 17 lines]
>
> I wonder if Apple will ever fix this..

Have you filed a bug report giving Apple engineers detailed steps to
reproduce the problem?

Signature

Please send all responses to the relevant news group rather than directly
to me, as E-mail sent to this address may be devoured by my very hungry
SPAM filter. Due to Google's refusal to prevent spammers from posting
messages through their servers, I often ignore posts from Google Groups.
You'll need to use a real news reader if you want me to see your posts.

JR

Reply to this Message

David Lesher - 28 Jun 2008 01:22 GMT

>> I wonder if Apple will ever fix this..

>Have you filed a bug report giving Apple engineers detailed steps to
>reproduce the problem?

Oh, about 5 or 6 years ago....

Signature

Reply to this Message

Jolly Roger - 28 Jun 2008 02:39 GMT

> >> I wonder if Apple will ever fix this..
>
> >Have you filed a bug report giving Apple engineers detailed steps to
> >reproduce the problem?
>
> Oh, about 5 or 6 years ago....

Maybe you should do it again.

Signature

Reply to this Message

Gregory Weston - 27 Jun 2008 18:53 GMT

> I keep getting bitten by an annoying bug in the TCP/IP system.
>
[quoted text clipped - 17 lines]
>
> I wonder if Apple will ever fix this..

I wonder if anyone has ever reported it to Apple.

G

Signature

"Harry?" Ron's voice was a mere whisper. "Do you smell something ... burning?"
- Harry Potter and the Odor of the Phoenix

Reply to this Message

Bob Harris - 27 Jun 2008 21:34 GMT

> I keep getting bitten by an annoying bug in the TCP/IP system.
>
[quoted text clipped - 17 lines]
>
> I wonder if Apple will ever fix this..

Your mileage apparently varies. I switch between a DHCP assigned
address and a fixed IP address twice a day, 5 days a week. At
work I use a DHCP address, at home I use a fixe IP address. I
have 2 network locations which I switch between and it works all
the time. I have a few other locations for when I'm at Mom's and
when I'm in a free WiFi hotspot or on vacation using the hotel's
WiFi (or ethernet).

Are you creating multiple locations, or are you just changing the
default location? Differences between how you make your changes
and the way I make mine, might lead to a working solution for you.

Bob Harris

Reply to this Message

David Lesher - 28 Jun 2008 01:40 GMT

>Your mileage apparently varies. I switch between a DHCP assigned
>address and a fixed IP address twice a day, 5 days a week. At
[quoted text clipped - 3 lines]
>when I'm in a free WiFi hotspot or on vacation using the hotel's
>WiFi (or ethernet).

>Are you creating multiple locations, or are you just changing the
>default location? Differences between how you make your changes
>and the way I make mine, might lead to a working solution for you.

I've done both. I have DHCP and static locations, and sometimes change
that way. But the braindead scheme for locations, where you can't lock
the data in place, means sometimes I'll overwrite what was there, so I
end up with manual changes.

Next time I get caught, I'll do dumps of /sbin/ifconfig to see what show
there. But I just had a DCHP set address of 172.16.73.201 showing in the
control panel, and the box was at 192.168.1.1, pinging away.

Signature

Reply to this Message

Kevin McMurtrie - 28 Jun 2008 22:25 GMT

> I keep getting bitten by an annoying bug in the TCP/IP system.
>
[quoted text clipped - 17 lines]
>
> I wonder if Apple will ever fix this..

There is a bug in multiple network interfaces. I have 68.183.205.100
for global access, 10.0.1.20 for wireless LAN, 10.0.0.20 for wired LAN,
and 192.168.2.10 DHCP devices. Sometimes MacOS tries to talk across the
interfaces even when it violates the netmask settings, like accessing
192.168.2.5 through 10.0.1.20. Remote devices get confused by this and
don't reply reliably. Usually turning the interface off and on again
fixes it. Sometimes a reboot is needed. In rare cases the system locks
up dead.

My Iomega wireless NAS has this problem very badly. It has one
interface for wired and one for wireless and it can't keep them straight
at all. I can tell it to turn the 10.0.0.xx wired interface off and its
IP address still shows up in wireless packets. It confuses the Macs
then they quit working too.

Signature

I will not see your reply if you use Google.

Reply to this Message

Mac Forum / General / Networking / June 2008

Network stack: three strikes and you're out....