Re: plip with mulinux

From: Michele Andreoli (
Date: Wed Aug 30 2000 - 10:43:19 CEST

On Tue, Aug 29, 2000 at 10:00:34PM +0200, Dumas Patrice nicely wrote:
> > What is obscoure for me is that: suppose we have plip0, ppp0, ppp1, eth0, eth1
> > up. What I can put in
> I surely don't understand your question, because you gave the response just above :
> you can put the nameserver and so on !!!

Nameserver is ok, as common value. My question was: has to
handle also connection between interface, i.e. routing beetwing subnetwork, etc?

> I was thinking about something like :
> in info() : "to configure routing statically, choose an interface and choose address
> that are to be reached via this interface"

In or Is it better in,, etc ?

> There is a big difficulty in that case, that is that the .cnf has to have entries
> formatted, because it cannot have a dynamical number of entries. Maybe something
> like:
> ROUTES="iface1:address iface1:net:netmask iface2:net:netmask....."

The array problem.

> It's totally unorthodox, and also not easy to implement (although possible, I think)
> What do you think about that ?
> There also should be a way to shutdown routes.
> Note that actually, there is nothing to del routes in netconfig, perhaps this should
> be added ?

With the set of values relative to any interface, I can ask the user
if defaultroute and gateway is belong this interface. A this point,
rounting is stoppend with normal start/stop Setup functions.

Summarizing (please help me): addr? network? defaultroute? (peer?) nameserver?,hostname?,dhcp? (/etc/hosts, /etc/resolv.conf, etc)

Mmm .. I think /etc/net.conf should be eliminated: it make confusion.


I'd like to conclude with a positive statement, but I can't 
remember any. Would two negative ones do?       -- Woody Allen
To unsubscribe, e-mail:
For additional commands, e-mail:

This archive was generated by hypermail 2.1.6 : Sat Feb 08 2003 - 15:27:15 CET