From: Glen Mabey <glen@mabeys.dsl.aros.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] network scripts debian
Date: Thu, 05 Aug 2004 03:07:08 +0000 [thread overview]
Message-ID: <20040805030708.GA5464@mabeys.dsl.aros.net> (raw)
In-Reply-To: <41100636.5050207@advocap.org>
On Tue, Aug 03, 2004 at 04:40:06PM -0500, John McMonagle wrote:
> Working at setting up some new firewalls with multi-path routing over 2
> isps. Doing it with debian sarge.
>
> Problem is the normal network scripts use ifconfig and route.
>
> In my tests I did a simple setup script.
>
> Feel like I am reinventing the wheel :-)
>
> Is it OK to use the network scripts to setup the interface and then
> remove the routes ifconfig created and add any needed routes with ip
> commands?
>
> Or am I best setting up the connections from scratch?
After struggling with exactly this same issue myself, I simply created
everything from scratch. Otherwise, I couldn't ever get it to work.
> Also related is some of interfaces are dynamic.
> I ran rewrite dhclient-script or just rebuild routes in
> dhclient-exit-hooks.d.
>
> Also dhcpd-script gives
> new_subnet_mask=.........
> new_ip_address=....
> new_network_number=......
> interface=eth2
>
> But for ip route need the length part of new_network_number/length
>
> Is there a simple way to calculate length from new_subnet_mask ?
dunno about that one.
Glen
--
******************************************************************
Glen W. Mabey
Glen.Mabey@usu.edu
http://mabeys.homelinux.com/glen/
******************************************************************
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-08-05 3:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 21:40 [LARTC] network scripts debian John McMonagle
2004-08-05 3:07 ` Glen Mabey [this message]
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=20040805030708.GA5464@mabeys.dsl.aros.net \
--to=glen@mabeys.dsl.aros.net \
--cc=lartc@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.