AlpineDragon wrote:
> Greetings,
> I've installed diald on a client's Slackware 7.0 machine. The
> kernel is 2.2.13, and pppd 2.3.10.
Current kernel is 2.2.14, current ppp is 2.3.11 and current diald is 0.99.4.
How about a clue as to your configuration information and the version of
diald in use?
> I have both PPP and SLIP compiled
> directly into the kernel, and not installed as modules.
No problem so far
> Here's my
> problem: diald will start, and cause modprobe to complain
> that it cannot
> find some tap* modules -- but it appears to start up ok.
Diald 0.9x prefers the use of ethertap devices over slip devices. So it
will check to see if any of the 16 possible tap devices are available before
trying to check the slip devices.
It appears you did compile in ethertap support but you have not created the
ethertap devices /dev/tap# (ethertap compiled directly into kernel) or the
conf.modules/modules.conf entries (ethertap as module). See README.ethertap
from the diald tarball for more information on conf.modules entries, see
$KSRC/Documentation/networking/ethertap.txt and/or
$KSRC/Documentation/devices.txt for more information on creating the
/dev/tap# entries.
In some cases both device entries and conf.modules entries are needed.
If you do not want ethertap support (or diald is picking it up when it
shouldn't exist) you'll need to 'alias tap# off' etc for tap0 through tap15
in conf.modules. (Doing this won't make any difference in diald
functionality, it will slightly speed things up and avoid needless entries
in the log files.)
> A network
> request is made for it to dial, and it does start dialing.
> It appears to
> dial in, and log in just fine -- but at that point I get a bunch of
> strange sl0 errors, and it fails to finish the connection.
> Below is an
> excerpt from my /var/log/messages:
>
> Mar 27 06:03:02 gateway modprobe: can't locate module tap0
> Mar 27 06:03:03 gateway modprobe: can't locate module tap1
> Mar 27 06:03:05 gateway modprobe: can't locate module tap2
> Mar 27 06:03:07 gateway modprobe: can't locate module tap3
> Mar 27 06:03:08 gateway modprobe: can't locate module tap4
> Mar 27 06:03:10 gateway modprobe: can't locate module tap5
> Mar 27 06:03:12 gateway modprobe: can't locate module tap6
> Mar 27 06:03:13 gateway modprobe: can't locate module tap7
> Mar 27 06:03:15 gateway modprobe: can't locate module tap8
> Mar 27 06:03:16 gateway modprobe: can't locate module tap9
> Mar 27 06:03:18 gateway modprobe: can't locate module tap10
> Mar 27 06:03:20 gateway modprobe: can't locate module tap11
> Mar 27 06:03:21 gateway modprobe: can't locate module tap12
> Mar 27 06:03:23 gateway modprobe: can't locate module tap13
> Mar 27 06:03:25 gateway modprobe: can't locate module tap14
> Mar 27 06:03:26 gateway modprobe: can't locate module tap15
> Mar 27 06:03:27 gateway diald[5661]: start sl0:
> SIOCSIFMETRIC: Operation not supported
> Mar 27 06:04:10 gateway diald[5661]: Trigger: icmp
> 0.0.0.0/257 2
> Mar 27 06:04:10 gateway diald[5661]: Calling site 127.0.0.3
> Mar 27 06:04:12 gateway connect: Initializing Modem
> Mar 27 06:04:12 gateway connect: Dialing system
> Mar 27 06:04:28 gateway connect: Connected
> Mar 27 06:04:28 gateway connect: Logging in
> Mar 27 06:04:29 gateway connect: Protocol started
> Mar 27 06:04:29 gateway diald[5661]: Connected to site 127.0.0.3
> Mar 27 06:04:29 gateway diald[5661]: Running pppd (pid = 5692).
> Mar 27 06:04:31 gateway modprobe: can't locate module char-major-108
By itself this is a harmless message (char-major-108 only exists in kernel
2.3+). But this should only be triggered if there is a pppd error when
using pppd 2.3.10 (unlike pppd 2.3.9 when it was always triggered or 2.3.11
where it never triggers).
Set debugging in pppd so we can see what the error is.
> Mar 27 06:04:32 gateway diald[5661]: start sl0:
> SIOCSIFMETRIC: Operation not supported
Yes, diald uses the same command to start slip in kernels 2.2 as 2.0.
Unfortunately you can't add metric information using that command in kernel
2.2 (this is an informative message only, slip was started)
> Mar 27 06:04:32 gateway diald[5661]: start sl0: SIOCADDRT: File exists
kernel 2.2 automatically adds routes so the route that diald is trying to
add already exists. no problem
> Mar 27 06:04:32 gateway diald[5661]: start sl0: SIOCDELRT: No
> such process
tried to remove the default route to ppp# (which does not exist)
> Mar 27 06:04:32 gateway diald[5661]: start sl0: SIOCADDRT: File exists
since there was an error message on the last route command it tries again
> Mar 27 06:04:33 gateway diald[5661]: Delaying 30 seconds
> before clear to dial.
>
> Any ideas? Thanks.
> -Tom Wittke
> -Computer Management Systems
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
>
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
