Re: Demand dial doesn't raise ISP connection

["Mirco Ellis" <mirco.ellis@isoftpe.co.za>]

Howzit, I am not such a fundi on this but experienced the same problem with
kernel 2.4.x and diald 1.0 recently. I found that if my named service wasn't
running it would just sit there and blink. Once I started the named service,
all was up and running. Hope this helps.

Regards
Mirco

----- Original Message -----
From: "Planetarium WEBMASTER" <webmaster.planetarium@btopenworld.com>
To: <linux-diald@vger.kernel.org>
Sent: Friday, July 18, 2003 15:33
Subject: Demand dial doesn't raise ISP connection


> Hi,
>
> Wonder if anyone could help please.  I'm running RedHat 6.0 (kernel
2.2.5),
> as it comes straight out of the box, and diald 0.99.1 (tried 1.0 but
> couldn't make it do anything - probably my fault!).  When I use the front
> end tool dctrl on a fifo I can control diald making it raise and lower the
> ISP
> connection (ISP is BTOpenWorld, U.K. using CHAP authentication) or I can
> force the link up and down.  However with the daemon just sat there
waiting
> for a request such as ping, traceroute or web-browse it carries on just
> sitting there doing nothing.  I thought it could be a SLIP problem but
lsmod
> shows slip is in the kernel and sl0 devices appear on the routing tables.
> I'm trying to set this up as a router for a network that is Windows
oriented
> as I find that the Win2k server RRAS & NAT protocols are just rubbish.
When
> I manually raise the link our network users are very happy :-) so it
should
> be great if I could only make the demand component work.
>
> I have included my diald.conf file:
>
> ##########################
> # /etc/diald.options
>
> # Device where your modem is connected
> device /dev/ttyS3
>
> # Log file
> accounting-log /var/log/diald.log
>
> # Monitoring queue
> fifo /var/run/diald/diald.fifo
>
> # Debug activation
> # Activating debug reduces performance
> # debug 31
>
> # We use PPP as encapsulator
> mode ppp
>
> # Local IP (when you connect this address is automatically modified
> # with the ip assigned by your ISP if you use the dinamic option).
> local 192.168.0.5
>
> # Remote IP (when you connect this address is automatically modified
> # with the ip of the remote server that receives our call).
> remote 192.168.0.7
>
> # Subnet mask for the wan link
> netmask 255.255.255.0
> # netmask 0.0.0.0
>
> # The IP addresses will be asigned when connection starts.
> dynamic
>
> # If link goes down by remote end, start it again only if there is
> # outgoing packets.
> two-way
>
> # When link is up, route directly to the real ppp interface, not the proxy
> # interface. Not to do this is a performance lost of about 20 per cent.
> # There are old kernels that do not support reroute. See diald manual for
> # more information
> reroute
>
> # Diald will set up the default route the the SLIP interface used as proxy
> defaultroute
>
> # Script to set up personalized routes
> # addroute "/etc/diald/addroute"
> # delroute "/etc/diald/delroute"
>
> # Scripts to execute when the link is up and ready or down and closed.
> # In Diald versions 0.9x there is another option called ip-goingdown that
> # can be used to run commands when the link is going to be down but is
> # still up.
> # ip-up /etc/diald/ip-up
> # ip-down /etc/diald/ip-down
>
> # Scripts used to connect or disconnect the interface
> connect "/etc/diald/diald.connect"
> # connect "/usr/sbin/chat -v -T <BTOpenWorld number> -f
> /etc/ppp/chat-default"
> # disconnect "/etc/diald/diald.disconnect"
>
> # Use UUCP lock to signal the device is being used
> lock
>
> # We connect over a modem. WARNING: Do not especify this options in the
> # ppp options file, because they will conflict with the diald options. To
> # see what ppp options that you can not use in the pppd-options option,
> # see the diald man page and search for pppd-options
> modem
> crtscts
> speed 115200
>
> # Some timers and retry options
> # See Diald man page for more information
> connect-timeout 120
> redial-timeout 10
> start-pppd-timeout 120
> died-retry-count 0
> redial-backoff-start 4
> redial-backoff-limit 300
> dial-fail-limit 10
>
> # Options to be passed to pppd
> # This options can be included in the /etc/ppp/options file, that are the
> # default options for pppd, but if you need to use different
> # configurations of diald for more than one instance, you must put it here
> # noauth - do not ask remote for authenticaion.
> #          "Infov&iacute;a Plus" (Spain) do not identify to our machine
> # user - our username and isp. Ask your isp for the sintaxis. Some isps,
> #        do not need the @isp
> pppd-options noauth noipdefault asyncmap 0 user
planetarium@btopenworld.com
> remotename bto usepeerdns
> # pppd-options noauth user planetarium@btopenworld.com
>
> # Hour restriccions.
> # This section must be before filters.
> # The restrict command is experimental, and can change in other versions
> # of diald. Check the man page. (this example has been checked for 0.16,
> # but i think it runs in later versions).
> # Example: only use in the night from monday to friday, and all day in
> # saturday and sunday.
> # restrict 8:00:00 18:00:00 1-5 * *
> # down
> # restrict * * * * *
>
> # No special tarificaion considerations
> # (first seconds included in the setup cost, tarify unit in seconds,
> # time in seconds to check if it is good to go down)
> # impulse 0,0,0
> # Bononet Noche (Spain-Telef&oacute;nica) is billed in seconds after the
160
> # first seconds
> # impulse 160,0,0
> # if it would be billed in minuttes and the first 10 will be billed
> # always:
> # impulse 600,60,10
>
> # Standard filters
> include /etc/diald/standard.filter
> # or personal filters
> # include /etc/diald/personal.filter
>
> The file /etc/diald/diald.connect does this:
>
> /usr/sbin/chat -v -T <BTOpenWorld number> -f /etc/ppp/chat-default
>
> The file /etc/ppp/chat-default does this :
>
> TIMEOUT 5
> ABORT "BUSY"
> ABORT "ERROR"
> ABORT "NO CARRIER"
> ABORT "NO DIAL TONE"
> ABORT "NO DIALTONE"
> ABORT "WAITING"
> "" "AT&F1"
> "OK" "ATDT\T"
> TIMEOUT 45
> "CONNECT" '\c'
>
> I'm assuming that the previous two files are irrelevant information as I
can
> force the link and it's O.K.
>
> Routing information:  the following come from netstat -i, route and
ifconfig
> in the waiting state (listening for a request) and when I force the
> connection using dctrl (connected) ....
>
> netstat ... waiting
>
> Kernel Interface table
> Iface   MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP
TX-OVR
> Flg
> eth0   1500   0    14541   3448      0      0    14118      1      0
0
> BRU
> lo     3924   0     1693      0      0      0     1693      0      0
0
> LRU
> sl0    1500   0        0      0      0      0        0      0      0
0
> OPRU
>
> netstat ... connected
>
> Kernel Interface table
> Iface   MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP
TX-OVR
> Flg
> eth0   1500   0    14591   3453      0      0    14229      1      0
0
> BRU
> lo     3924   0     1699      0      0      0     1699      0      0
0
> LRU
> ppp0   1500   0       25      0      0      0       27      0      0
0
> OPRU
>
> ifconfig ... waiting
>
> eth0      Link encap:Ethernet  HWaddr 00:50:FC:64:86:E0
>           inet addr:192.168.0.5  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:14548 errors:3448 dropped:0 overruns:0 frame:0
>           TX packets:14144 errors:1 dropped:0 overruns:0 carrier:1
>           collisions:1046 txqueuelen:100
>           Interrupt:11 Base address:0xec00
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:1693 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1693 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>
> sl0       Link encap:Serial Line IP
>           inet addr:192.168.0.5  P-t-P:192.168.0.7  Mask:255.255.255.0
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10
>
> ifconfig ... connected
>
> eth0      Link encap:Ethernet  HWaddr 00:50:FC:64:86:E0
>           inet addr:192.168.0.5  Bcast:192.168.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:14531 errors:3448 dropped:0 overruns:0 frame:0
>           TX packets:14091 errors:1 dropped:0 overruns:0 carrier:1
>           collisions:1046 txqueuelen:100
>           Interrupt:11 Base address:0xec00
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:1693 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:1693 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:213.122.172.71  P-t-P:213.120.208.165
> Mask:255.255.255.0
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:10
>
> route ... waiting
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 192.168.0.5     *               255.255.255.255 UH    0      0        0
eth0
> 192.168.0.0     *               255.255.255.0   U     0      0        0
eth0
> 192.168.0.0     *               255.255.255.0   U     0      0        0
sl0
> 127.0.0.0       *               255.0.0.0       U     0      0        0 lo
> default         192.168.0.5     0.0.0.0         UG    0      0        0
eth0
> default         *               0.0.0.0         U     1      0        0
sl0
>
> route ... connected
>
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 192.168.0.5     *               255.255.255.255 UH    0      0        0
eth0
> 192.168.0.0     *               255.255.255.0   U     0      0        0
eth0
> 213.120.208.0   *               255.255.255.0   U     0      0        0
ppp0
> 127.0.0.0       *               255.0.0.0       U     0      0        0 lo
> default         *               0.0.0.0         U     0      0        0
ppp0
> default         192.168.0.5     0.0.0.0         UG    0      0        0
eth0
>
> The proxy slip interface, sl0, appears to be there and is converted to a
> physical ppp0 upon connection.  This is probably a trivially stupid
question
> based upon my lack of experience in linux in which case I hope that
there's
> a simple answer?
>
> TIA,
> Ed Restall.
>
> Snail mail:
>                 CEW Planetarium & Observatory,
>                 Castle Eden Walkway Country Park,
>                 Thorpe Thewles,
>                 Stockton-on-Tees.  TS21 3JG.  U.K.
> E-mail:
>                 planetarium@btopenworld.com
>                 webmaster.planetarium@btopenworld.com
> Web:
>                 www.planetarium.btinternet.co.uk
> Tel/Fax:
>                 +44 (0) 1740 630544
>
> The CEW Planetarium and Observatory is a joint
> venture between the Cleveland & Darlington
> Astronomical Society and Stockton Borough Council,
> providing science education to Teesside & the
> North East of England.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html