> 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..
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.
