My Diald is working well, but I get the same entries in /var/log/messages
concerning the tap devices. Anyone know what these devices are and how to
correct the error that's causing the log entries?
Rick Knight ([EMAIL PROTECTED])
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<
On 8/6/00, 3:45:35 PM, "Ian Douglas" <[EMAIL PROTECTED]> wrote
regarding Did this get out? weirdness, please help:
> Hey all... Haven't seen any responses to this, let alone my own message
to
> the list:
> Trying to set up diald for dynamic dial-up.
> I downloaded diald from sourceforge (0.99.4), and compiled it and
> installation went fine (by the way, a sample configuration installed as
> /etc/diald.conf might be nice instead of forcing us to make one from
> scratch).
> I run /usr/sbin/diald and see that the process is running:
> 6800 ? S< 0:00 /usr/sbin/diald
> yet when I try to ping the network on the other side that diald is
supposed
> to connect to, it doesn't dial out. Why? Let's peek at /var/log/messages:
> Aug 3 16:52:43 dug modprobe: can't locate module tap0
> Aug 3 16:52:43 dug modprobe: can't locate module tap1
> Aug 3 16:52:43 dug modprobe: can't locate module tap2
> Aug 3 16:52:43 dug modprobe: can't locate module tap3
> Aug 3 16:52:43 dug modprobe: can't locate module tap4
> Aug 3 16:52:43 dug modprobe: can't locate module tap5
> Aug 3 16:52:43 dug modprobe: can't locate module tap6
> Aug 3 16:52:43 dug modprobe: can't locate module tap7
> Aug 3 16:52:43 dug modprobe: can't locate module tap8
> Aug 3 16:52:43 dug modprobe: can't locate module tap9
> Aug 3 16:52:43 dug modprobe: can't locate module tap10
> Aug 3 16:52:43 dug modprobe: can't locate module tap11
> Aug 3 16:52:43 dug modprobe: can't locate module tap12
> Aug 3 16:52:43 dug modprobe: can't locate module tap13
> Aug 3 16:52:43 dug modprobe: can't locate module tap14
> Aug 3 16:52:43 dug modprobe: can't locate module tap15
> Aug 3 16:52:43 dug kernel: CSLIP: code copyright 1989 Regents of the
> University of California
> Aug 3 16:52:43 dug kernel: SLIP: version 0.8.4-NET3.019-NEWTTY-MODULAR
> (dynamic channels, max=256) (6 bit encapsulation enabled).
> Aug 3 16:52:43 dug kernel: SLIP linefill/keepalive option.
> Aug 3 16:52:43 dug diald[6800]: start sl0: SIOCSIFMETRIC: Operation not
> supported
> SLIP is built into my kernel as a module, but from there, I'm kinda lost
as
> to what's happening (or NOT happening, as the case my be).
> Of course, killing diald gives this output in /var/log/messages:
> Aug 3 16:54:39 dug diald[6800]: SIGTERM. Termination request received.
> Aug 3 16:54:39 dug diald[6800]: Diald is dieing with code 0
> I left /usr/lib/diald/standard.filter alone for the most part ...
commented
> out http/https access since we only need this dial-up for FTP access.
> Here's my /etc/diald.conf file:
> mode ppp
> connect /etc/ppp/ppp-on
> device /dev/ppp-modem
> speed 115200
> modem
> lock
> crtscts
> local 192.168.100.118
> remote 1.2.3.4
> defaultroute
> include /usr/lib/diald/standard.filter
> (the remote IP is NOT 1.2.3.4, I don't have permission to let you all
know
> the real IP, but the 192.168.100.118 IP is what I want to assign to the
> modem when it connects)
> The /dev/ppp-modem device is a link to one of a batch of modems... but
it's
> not even getting that far. Trying to ping 1.2.3.4 doesn't do anything at
> all, let alone try to launch my pppd scripts.
> /etc/ppp/ppp-on works, because I was testing it earlier this week, and
> scratching my head, wondering how I'd automate it, and then read about
diald
> so here I am.
> We're running RedHat Linux 6.1 on a P-III system. We have an Equinox
> multi-port board connected to a bank of 12 modems (my ppp-on script
figures
> out which modem is available for use). The modems are for dial-in access
to
> a server in-house, but periodically we need to use a single modem
(whichever
> one is free) to dial out to a new server to download some information
then
> hang-up.
> lsmod:
> Module Size Used by
> slip 7700 0 (autoclean)
> slhc 4328 1 (autoclean) [slip]
> 3c59x 19112 1 (autoclean)
> eqnx 296664 2
> Any help would be appreciated. This is a time-sensitive issue, so any
quick
> answers would be helpful.
> Ian
> -
> 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]
