From owner-freebsd-questions Tue May 8 8:16:55 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fac13.ds.psu.edu (fac13.ds.psu.edu [146.186.61.98]) by hub.freebsd.org (Postfix) with ESMTP id 0DDA437B422; Tue, 8 May 2001 08:16:51 -0700 (PDT) (envelope-from hawk@fac13.ds.psu.edu) Received: from fac13.ds.psu.edu (localhost [127.0.0.1]) by fac13.ds.psu.edu (8.11.3/8.11.3) with ESMTP id f48FGlx10663; Tue, 8 May 2001 11:16:47 -0400 (EDT) (envelope-from hawk@fac13.ds.psu.edu) Message-Id: <200105081516.f48FGlx10663@fac13.ds.psu.edu> X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: wayne.pascoe@realtime.co.uk Cc: Colin Eric Johnson , freebsd-questions@FreeBSD.ORG, freebsd-mobile@FreeBSD.ORG Subject: Re: Laptop on 2 networks - solutions ? In-Reply-To: Your message of "08 May 2001 15:59:51 BST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 May 2001 11:16:47 -0400 From: "~/.signature" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Colin Eric Johnson writes: > > > > add net 0.0.0.0 gateway 192.168.1.30: File exists) > > > > > > Any tips on this would be great! Thanks :) > > > > Is using DHCP out of the question? That would allow you to not have to > > worry about this at all. > > Forgot to mention my firewall scripts... I have two of those as > well. So DHCP becomes a pain, because with fixed IP's the firewall > scripts are easier ... > > Also, I don't run any DHCP services at home. Too damn lazy. > > -- > - Wayne Pascoe > E-mail: wayne.pascoe@realtime.co.uk > Phone : +44 (0) 20 7544 4668 > Mobile: +44 (0) 788 431 1675 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -- Prof. Richard E. Hawkins, Esq. /"\ ASCII ribbon campaign dochawk@psu.edu Smeal 178 (814) 375-4700 \ / against HTML mail These opinions will not be those of X and postings Penn State until it pays my retainer. / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message