public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: starting and stopping networking
Date: Sun, 4 Jan 2004 14:43:52 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0401041431470.681@debian-opt> (raw)
In-Reply-To: <5.1.0.14.1.20040101154809.02021888@celine>

Lemme see if I can frame this question coherently.  I've got a Debian Sid
machine on a LAN behind a firewalling router (router does dhcp offers,
too).  That router's acting really flaky (it was given to me as a freebie
because it was acting flaky).  I'm thinking of just hooking that machine
directly to the 'net (university network) for the next week or so while
await the arrival of a router that works normally.  Of course I don't wish
for the machine to be on the WAN unprotected.  At the same time, I don't
want to install a firewall on it because that could complicate setting up
the LAN, once the normally-operating router/firewall arrives.  What I'm
thinking of doing is maybe creating a script that will start/stop network
services and make a dhcp request, that could be run in the interim while
I'm awaiting the new router.  In other words, I would stop networking when
I'm not actively doing something on the 'net, restart it when I need to do
something on the 'net.  So my basic question is: how do I stop networking
services on Debian Sid (I know how on Slackware, but Debian differs)?
How do I restart them later, and send a new dhcp request at the same time?
Any input on my interim networking method for this machine would be
appreciated, as would pointers for accomplishing what I've outlined above,
if that proves advisable/feasible.

Thanks, 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

  parent reply	other threads:[~2004-01-04 20:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 19:33 disabled system speaker: how to enable? James Miller
2004-01-01  3:33 ` caszonyi
2004-01-01 23:44   ` Debian network reconfigure jamtat
2004-01-01 23:54     ` Ray Olszewski
2004-01-02  0:38       ` James Miller
2004-01-04 20:43       ` James Miller [this message]
2004-01-04 20:49         ` starting and stopping networking caszonyi
2004-01-04 21:07           ` James Miller
2004-01-04 21:14             ` Jacob Langley
2004-01-04 21:19             ` caszonyi
2004-01-04 21:28               ` James Miller
2004-01-04 21:41                 ` James Miller
2004-01-04 22:24                   ` Ray Olszewski
2004-01-04 21:32               ` Alan Bort
2004-01-04 23:26                 ` Ray Olszewski
2004-01-04 23:51                   ` Alan Bort
2004-01-05  0:28                     ` Ray Olszewski
2004-01-05  3:11                       ` Alan Bort
2004-01-05  3:55                         ` Juan Facundo Suárez

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.58.0401041431470.681@debian-opt \
    --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