Theo. Sean Schulze wrote:
> One change to the information below: I chopped the standard.filter stuff
> off of the end of the /etc/diald.conf file and inserted 'include
> /usr/lib/diald/standard.filter' (without the quotes).
>
> Another question has also come up. How can I find out what version of
> diald is installed on my system?
Have a look in '/usr/doc/packages/diald/'.
>
> TIA,
> Sean
>
> ------------------
> Theo. Sean Schulze
> [EMAIL PROTECTED]
> [...]
> As mentioned above, I added these settings to the top of the stock
> diald.conf file, and that file is at /etc/diald.conf.
>
> local 0.0.0.0
> remote 0.0.0.0
Not very well chosen IP numbers. It's better to take them from the "private
pool", but from that time never use these in your local network or any other
purpose.
I have set local 192.168.1.1
remote 192.168.1.2
It would also be a good idea to take them from "another network", let me explain
this:
You see my diald-relevant addresses above belonging to the
"192.168.1.0-network".
My small LAN at home uses the "192.168.0.0-address-room".
(Note: The last number ".0" in the addresses above are reserved for labelling
the specific network used and, AFAIK, must not be used as an address)
> dynamic
> defaultroute
> # proxyarp
> device /dev/ttyS3
> lock
> speed 38400
> mtu 1524
> connect /etc/suseppp/diald/dialdppp-up
> disconnect /etc/suseppp/dialdppp-down
> modem
> crtscts
>
> This is a snippet of /var/log/messages taken during one of the (many)
> failed attempts to get a ppp link running:
>
> Oct 3 15:35:38 dragoon diald[6605]: Running connect (pid = 6719).
> Oct 3 15:35:38 dragoon syslog: IPX support is not present in the kernel
You could explicitely exclude the usage of IPX by PPPD (see the manpage) to
avoid this message.
> Oct 3 15:35:38 dragoon pppd[6719]: pppd 2.2.0 started by root, uid 0
> [Bunches of negotiation messages snipped.]
> Oct 3 15:36:08 dragoon pppd[6719]: Connect: ppp0 <--> /dev/ttyS3
> Oct 3 15:36:08 dragoon pppd[6719]: sent [LCP ConfReq id=0x1 <mru 1500> <magic
>0x47c98e2e> <pcomp> <accomp>]
>
> [Bunches of negotiation messages snipped.]
>
> Oct 3 15:36:09 dragoon pppd[6719]: rcvd [IPCP ConfAck id=0x1 <addr 192.168.0.3>
><compress VJ 0f 01>]
> Oct 3 15:36:09 dragoon pppd[6719]: local IP address 192.168.0.3
After pppd has negotiated addresses with your ISP you should not have a private
local address from the 192.168.0.0-network, but your private address you
initially have to lie about in "diald.conf" (can be 192.168.0.3, see above)
should have been substituted by an address of your ISP's pool which has been
dynamically given to you.
> Oct 3 15:36:09 dragoon pppd[6719]: remote IP address 195.178.7.130
> Oct 3 15:36:09 dragoon pppd[6719]: rcvd [CCP ConfRej id=0x1]
> Oct 3 15:36:38 dragoon diald[6605]: Connect script timed out. Killing script.
> Oct 3 15:36:38 dragoon pppd[6719]: Terminating on signal 2.
> Oct 3 15:36:38 dragoon pppd[6719]: sent [LCP TermReq id=0x2]
> Oct 3 15:36:38 dragoon pppd[6719]: rcvd [LCP TermAck id=0x2]
> Oct 3 15:36:38 dragoon pppd[6719]: Connection terminated.
> Oct 3 15:36:38 dragoon pppd[6719]: Exit.
> Oct 3 15:36:39 dragoon diald[6605]: Delaying 30 seconds before clear to dial.
> [...]
> This is my dialdppp-up-script:
>
> #!/bin/sh
> #
> # This is my diald ppp dialer script.
> #
> #
> /usr/sbin/chat -v \
> TIMEOUT 40 \
> ABORT '\nBUSY\r' \
> ABORT '\nNO ANSWER\r' \
> ABORT '\nRINGING\r\n\r\nRINGING\r' \
> '' \rAT \
Perhaps you might leave away the '\r'- and '\n'-signs as "chat" is able to
detect the keywords themselves.
> 'OK-+++\c-OK' ATH0 \
What a strange OK-message from your modem.
Normally a Hayes-compatible modem simply sends "OK".
> TIMEOUT 30 \
> OK ATDT$TELEPHONE \
> CONNECT '' \
> ogin:--ogin: tschulze \
> assword: mypassword
>
> Please let me know if I need to send anything else. BTW, I have also
> read man (8) diald, and that is why a number of settings normally
> found in a ppp options file are in the diald.conf and there is no
> reference in this setup to a ppp options file.
Nevertheless PPPD can have an options file, e.g. "/etc/ppp/options" that makes
sense of course as some PPPD-options don't have to be passed on to pppd by diald
(see suggestions with respect to your "/var/log/messages" above).
Regards
Thomas Michalka
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
