> Is there anything in the ethertap interface that prevents more than one
> diald process from running? At the moment I can start up one fine, and
> it grabs tap0. I was expecting that subsequent diald processes would use
> tap1, tap2, etc. as the older slip code did with sl0, sl1, sl2, etc.
> (linux 2.2.1 kernel on a redhat 5.2 based distribution with diald
> 0.98.3)
This held me up for a moment, too. The problem isn't diald, it's the
instructions in the diald Makefile for setting up the tap devices. What you
really need in /etc/conf.modules is
alias tap0 ethertap
options tap0 unit=0
alias tap1 ethertap
options tap1 unit=1
etc. I'm running 2 dialds quite happily with this. My system is very similar to
yours, BTW, except I'm now on 2.2.2.
---
Jim Hague - [EMAIL PROTECTED] (Work), [EMAIL PROTECTED] (Play)
Never trust a computer you can't lift.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
