From: Jeff Woods <kazrak+kernel@cesmail.net>
To: James Miller <jamtat@mailsnare.net>
Cc: Linux-Newbie list <linux-newbie@vger.kernel.org>
Subject: Re: basic networking queries
Date: Thu, 31 Jul 2003 21:13:43 -0700 [thread overview]
Message-ID: <5.2.0.9.0.20030731205941.05fa7168@SpeakEasy.but.no.reading.jeffwoods.us> (raw)
In-Reply-To: <Pine.LNX.4.56.0307311915170.10393@homenet>
James Miller wrote:
>I will use it most of the time at home, where I have static network
>addressing. The card works, and the machine is successfully on my network
>now. When I need to take it away from home, though, different network
>settings will need to be used - almost surely DHCP will be in use where
>I'll use it away from home.
>
>But, the question remains: how to handle those times when I am away from
>home and may need to make the card connect to a DHCP network? What I
>found relevant to this in the PCMCIA how to is something called "schemes"
>that enable one to have alternate network settings for the PCMCIA card.
Rather than trying to change the network configuration manually between
your home/static and elsewhere/DHCP environments, I recommend you simply
always use DHCP for the laptop. Using DHCP at home does *not* mean you
must use DHCP to assign network information to all your home systems,
though you probably can if you like. You can reserve part of your IP
addresses for static systems and part for dynamic/DHCP systems.
In particular, servers should have static addresses so they don't move
around, but desktop/workstation/portable systems can usually be dynamic
without any difficulties. In fact, due to the auto-configuring aspect of
DHCP clients and the ability thereby to prevent duplicate IP addresses, it
makes a lot of sense to me to use DHCP for *all* systems that don't
*require* static addresses, (i.e. servers).
So you "simply" ;) configure a DHCP server on some local system at home
(Mine is built into the DSL router I use.) and then leave the laptop
enabled for DHCP all the time. When home, it gets all the network config
from the home network just like it does when away from home.
--
Jeff Woods <kazrak+kernel@cesmail.net>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2003-08-01 4:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 1:57 basic networking queries James Miller
2003-07-25 3:17 ` Ray Olszewski
2003-07-25 3:33 ` James Miller
2003-07-25 8:03 ` BLOODY CVS John T. Williams
2003-08-01 1:49 ` basic networking queries James Miller
2003-08-01 4:13 ` Jeff Woods [this message]
2003-08-06 20:23 ` James Miller
2003-08-19 19:40 ` Documentation for int 0x80 dante
2003-07-25 23:15 basic networking queries beolach
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5.2.0.9.0.20030731205941.05fa7168@SpeakEasy.but.no.reading.jeffwoods.us \
--to=kazrak+kernel@cesmail.net \
--cc=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.