From: James Miller <jamtat@mailsnare.net>
To: Linux-Newbie list <linux-newbie@vger.kernel.org>
Subject: Re: basic networking queries
Date: Wed, 6 Aug 2003 15:23:25 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0308061510010.1066@homenet> (raw)
In-Reply-To: <5.2.0.9.0.20030731205941.05fa7168@SpeakEasy.but.no.reading.jeffwoods.us>
Well, this will likely be my final installment on this DHCP issue and the
PCMCIA "schemes" I wrote about earlier. I have gotten a certain
arrangement to work, though I'm not sure how and why it works. I suppose
this is a little better than not having it work and not knowing why it
won't work, so I shouldn't complain too much. And, the workings of it all
may dawn on me as time passes - if senility doesn't set in first, that is.
It turns out that the "solution" (i.e., the procedure that allows me to
use my old laptop on either my home, statically-addressed LAN, or on a
larger DHCP network) is simple. I don't need any alternate "schemes" or
anything like that. I just boot the thing like normal, let the init
scripts (I think that's what they're called) assign my home network values
to the PCMCIA NIC interface and all that. If I'm at home, all is well and
good and off I go onto my network. If I'm away, I simply issue from the
command line "dhcp," and all the necessary network settings are found and
assigned to the NIC (or wherever they get stored), overriding the static
values I assigned there for the home network. And away I go onto
that network. All the while, I sit there stymied, wondering how I can
cram any further information on networking and DHCP into my head.
Clarifications on why this works, what may have been my misperceptions (as
long as these don't involve statements like "that's what u get fer
thinking u were smart enough to use Linux!") etc, are, as always, welcome.
James
-
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-06 20:23 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
2003-08-06 20:23 ` James Miller [this message]
2003-08-19 19:40 ` Documentation for int 0x80 dante
-- strict thread matches above, loose matches on Subject: below --
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=Pine.LNX.4.56.0308061510010.1066@homenet \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox