From owner-freebsd-mobile Tue May 8 12:35:11 2001 Delivered-To: freebsd-mobile@freebsd.org Received: from gilmore.nas.nasa.gov (gilmore.nas.nasa.gov [129.99.32.17]) by hub.freebsd.org (Postfix) with ESMTP id C93FC37B424; Tue, 8 May 2001 12:35:04 -0700 (PDT) (envelope-from tweten@nas.nasa.gov) Received: from gilmore.nas.nasa.gov (IDENT:/kV5a9A7FN2xhAjn2AFrYDnM0c/UICWi@localhost.nas.nasa.gov [127.0.0.1]) by gilmore.nas.nasa.gov (8.11.3/8.11.3) with ESMTP id f48JYv094797; Tue, 8 May 2001 12:34:57 -0700 (PDT) (envelope-from tweten@gilmore.nas.nasa.gov) Message-Id: <200105081934.f48JYv094797@gilmore.nas.nasa.gov> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: wayne.pascoe@realtime.co.uk Cc: freebsd-questions@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Laptop on 2 networks - solutions ? In-Reply-To: Message from Wayne Pascoe of "08 May 2001 15:50:24 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 May 2001 12:34:55 -0700 From: Dave Tweten Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org wayne.pascoe@realtime.co.uk said: >This all seems far more clumsy than needs be. Is there any better >solution than this out there? If you can't use DHCP, you might at least be able to draw inspiration from it. Check out /sbin/dhclient-script and its handling of the TIMEOUT "reason." It finds out if it is on the net it thinks it is by pinging the presumed default router. It should be possible to use that effect in a script called from pccard.conf on connection. It should be able to decide what net you are connected to and configure your machine appropriately. -- M/S 258-5 | 1024-bit PGP fingerprint: | tweten@nas.nasa.gov NASA Ames Research Center | 41 B0 89 0A 8F 94 6C 59 | (650) 604-4416 Moffett Field, CA 94035-1000 | 7C 80 10 20 25 C7 2F E6 | FAX: (650) 604-4377 We each earn what freedom of speech we defend for those who most offend us. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message