[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFC: new network config (was: Re: network configuration)

On Thu, Feb 04, 1999 at 11:26:45PM +0000, Christian Hammers wrote:
> On Wed, Feb 03, 1999 at 09:14:08AM +1100, Craig Sanders wrote:
> > > Then who is the one who has the power to change it =;-)
> > you. anyone has the power to change it. all it takes is to write the
> > code to implement it.
> Ok ! 
> I'm a "Brave Debian" (tm) and I try to change something.

Cool. :)

> But I *strongly* need comments. Not for the implemention - I have no
> problems with sed and sh scripts - but I like to know what can be done
> better or what I missed *before* I implement that !
> BTW: Who is the responsible package ? Boot-floppies or netbase ?

Assume netbase for the moment.

> /etc/init.d/interfaces start
> 	foreach $line (<"/etc/interfaces">) {
> 		`ifconfig $line up`
> 		`route add &calc_base_address($ip, $netmask) eth0`
> 	}

(eth0 == $interface, one assumes)

> 3rd thing: does anything apart from NFS need portmap ? I seems so to me and
> if, it should also vanish from netbase, because now it gets started all the
> time, and I have the strange feeling, that I do not need it !

Yellowpages does. So does other stuff. Check /etc/rpc if you're *really*
curious. Add an "exit 0" at the top of /etc/init.d/portmap if you don't
need it, personally.

> ---------------------------------------------------------------
> # /etc/interfaces
> # Add here your interfaces as you would do with ifconfig(8).
> #
> # The netmask must be given. The trailing "up"/"down" can be omitted.
> #
> # /etc/init.d/interfaces which is normally called at boottime reads this file.
> eth0 	netmask
> eth1	netmask

For PCMCIA netcards, you need some way of saying all this stuff,
and also that you don't want to do this automatically at bootup, but
that pcmcia-cs or something will take care of it when a card actually
gets inserted. Possibly a "noauto" option, as per fstab, or something
similar. That way pcmcia can just "mount" it later.

For DHCP, BOOTP and IPv6 (well, DHCPv6) clients, you need some way of
saying "this other package will take care of working out how to deal
with addresses and routing and whatever else, so just run /sbin/foo".

Not requiring a netmask would probably be nice, and having an optional
broadcast address might also be nice.

Note that
	eth0:1  netmask
would be a perfectly reasonable line to have above, btw.

> ----------------------------------------------------------------
> # /etc/gateways:
> # Add here all your gateways.
> # 
> # /etc/init.d/routes which is normally called at boottime reads this file.
> #
> #<net | host> NAME1 gateway NAME2 metric VALUE <passive | active | external> 
> net default 		gateway
> net 	gateway

Adding "metric 1 external" would probably be a good move. (metric 1 means
it's one hop away, external that routed should completely ignore this
route) "man routed" for some info on how /etc/gateways is meant to work.
(Bug#23703, fwiw. *sigh*)

I guess just adding "if there's an interface for this network/host" around
the code to "add this gateway to the routing table" would make this work
for noauto and stuff above too.

Note also that it's just plain not possible to list all routes here,
for clients that use DHCP and friends in particular (where the routes
aren't known in advance and can even change).

I am, btw, currently thinking that the IP aliases / virtual hosting stuff
being discussed in another part of this thread should go in a completely
different package to netbase. netaliases or netvirtual or something,
perhaps. It seems to me that this gets rid of a large part of the "perl,
sed, awk, oh my" problem for boot-floppies.


Anthony Towns <aj@humbug.org.au> <http://azure.humbug.org.au/~aj/>
I don't speak for anyone save myself. PGP encrypted mail preferred.

``Like the ski resort of girls looking for husbands and husbands looking
  for girls, the situation is not as symmetrical as it might seem.''

Attachment: pgph2Q1MiyaDB.pgp
Description: PGP signature

Reply to: