From owner-freebsd-mobile  Wed Dec 11 01:08:02 1996
Return-Path: <owner-mobile>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA27912
          for mobile-outgoing; Wed, 11 Dec 1996 01:08:02 -0800 (PST)
Received: from shadows.aeon.net (bsdcur@shadows.aeon.net [194.100.41.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA27878;
          Wed, 11 Dec 1996 01:07:50 -0800 (PST)
Received: (from bsdcur@localhost)
          by shadows.aeon.net (8.8.3/8.8.3) id LAA04906;
          Wed, 11 Dec 1996 11:06:03 +0200 (EET)
From: mika ruohotie <bsdcur@shadows.aeon.net>
Message-Id: <199612110906.LAA04906@shadows.aeon.net>
Subject: Re: It works!  Solved my problem wih Etherlink III on AcerNote Light
To: nate@mt.sri.com (Nate Williams)
Date: Wed, 11 Dec 1996 11:06:02 +0200 (EET)
Cc: terry@lambert.org, nate@mt.sri.com, freebsd-mobile@freebsd.org,
        FreeBSD-current@freebsd.org
In-Reply-To: <199612102212.PAA09166@rocky.mt.sri.com> from Nate Williams at "Dec 10, 96 03:12:49 pm"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-mobile@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> > In other words, if I have a local network connection, and I dial
> > up my pop account at my ISP, then Windows95 tends to screw up the
> > routing while the connection is up.
> It certainly shouldn't, and doesn't on any of my boxes.

hmm?

it shouldnt, but does. atleast in some way. i've learned the hard way
that win95 have no idea how to do things freebsd does as a "trivia"

(example, configuring different interfaces totally separatedly, including
the host/domain names known for the interface)

but that's why this is freebsd-* and not windows95-*... =) :P

that's why i run freebsd on many machines, and win95 only on one desktop
at work... my home p133 have never been infected with ms-code.

> Nate


mickey