Joan Moreau wrote:
> Well, i attached my diald.conf and ppp.script.
> I work on Suse 6.2 and get the following message in the
> /var/log/message :
>
> (
> /usr/sbin/pppd /dev/modem connect '/usr/sbin/chat -v -f
> /etc/ppp/chat.script' defaultroute 115200 &
> works fine
> )
>
> The pb is that diald never dial my ISP ! (nothing in logs)
>
> Thanks for your help !
>
>
> DIALD.CONF
>
> #
> # The link is normally held up for 2 Minutes
> # Netbios traffic is not allowed to hold up the link
> # any second -- [EMAIL PROTECTED]
> #
> mode ppp
> connect "chat -v -f /etc/ppp/chat.script"
> device /dev/modem
> speed 115200
> modem
> defaultroute
> lock
> crtscts
> local 0.0.0.0
> remote 0.0.0.0
> include /usr/lib/diald/standard.filter
>
> PPP.SCRIPT
>
> REPORT CONNECT
> ABORT 'ERROR'
> ABORT 'BUSY'
> ABORT 'NO CARRIER'
> ABORT 'NO DIALTONE'
> '' ATZ OK AT&F1 OK ATDT16300478683714 CONNECT ''
> ogin: MY_LOGIN
> ssword: MY_PASS
>
> Log message
>
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap0
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap1
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap2
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap3
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap4
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap5
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap6
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap7
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap8
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap9
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap10
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap11
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap12
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap13
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap14
> Oct 21 11:22:52 goyave modprobe: modprobe: Can't locate module tap15
> Oct 21 11:22:52 goyave diald[3478]: start sl0: SIOCSIFDSTADDR: Ne peut
> attribuer l'adresse demand�e
> Oct 21 11:22:52 goyave diald[3478]: start sl0: SIOCSIFBRDADDR: Ne peut
> attribuer l'adresse demand�e
> Oct 21 11:22:52 goyave diald[3478]: start sl0: SIOCSIFNETMASK: Ne peut
> attribuer l'adresse demand�e
> Oct 21 11:22:52 goyave diald[3478]: start sl0: SIOCSIFMETRIC:
> Op�ration non support�e
>
>
My French is not that good, but judging by the errors, I would guess
that the local and remote IP addresses are invalid. 0.0.0.0 cannot be
used as an ip address, try 10.0.0.1 and 10.0.0.2. The SIOCSFMETRIC
error is not harmful.
The tap errors are caused by either tap support not configured into the
kernel or your conf.modules file does not define the aliases for the tap
modules. Something like this should be added to conf.modules:
alias tap0 ethertap
options tap0 -o tap0 unit=0
You will also need ethertap support compiled as a module as part of your
kernel configuration.
Bon chance!
Bob...
--
--------------------------------------------------------
Bob Chiodini [EMAIL PROTECTED]
--------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
