Here is my configuration, and a problem description follows, ANY suggestions are welcome! Distribution: Mandrake 7.0 Kernel: 2.2.14 pppd version: 2.3.10 # /etc/ppp/options noauth debug name "ronsmith" noccp noaccomp nobsdcomp nodeflate nopcomp novj novjccomp hide-password privgroup trusted # /etc/diald.conf debug 0x0008 linkname PPP linkdesc Remote authpam /etc/auth.pam mode ppp accounting-log /var/log/diald.log demand device /dev/modem connect /etc/ppp/connect lock speed 38400 modem crtscts local 10.0.0.1 remote 10.0.0.2 dynamic sticky defaultroute demasq redial-timeout 3 retry-count 60000 died-retry-count 60000 up The /etc/ppp/connect script is the stock diald connect script thru the Dialing system / Connected session, at which point I don't use the rest of it since I need PAP authentication (however, auth is not a problem yet, I don't get nowhere near that far). I have a dual-channel ISDN account, using a 3Com Impact IQ with a SIIG PCI high speed serial card. I have defined the spd_cust (38400) to be the 230400, that is why that speed is in my config file (I did try a setting of 230400, the true port speed, in diald.conf, no-go). This setup works fine IF I use pppd (even pppd dial on demand works). However, I am not happy with it. I used diald long ago, and loved it, so have reinstalled it. IT DOES NOT WORK! LOL, and I can't figure out why. I have tried using stripped down versions of my config files, tried changing the device entry in diald.conf (using ttyS3, moved modem to ttyS2 and tried it there too). Here are the log entries: diald: Proxy device established on interface tap0 diald: running '/sbin/ifconfig tap0 10.0.0.1 pointopoint 10.0.0.2 broadcast 0.0.0.0 netmask 255.255.255.255 metric 1 mtu 1500 up' diald: start tap0: SIOCSIFMETRIC: Operation not permitted diald: SIGCHLD[1]: pid 9061 system, status 256 diald: running '/sbin/route add 10.0.0.2 metric 1 dev tap0' diald: SIGCHLD[2]: pid 9062 system, status 0 diald: running '/sbin/route del 10.0.0.2 metric 0 dev tap0' diald: SIGCHLD[3]: pid 9063 system, status 0 diald: running '/sbin/route add default metric 1 netmask 0.0.0.0 dev tap0' diald: SIGCHLD[4]: pid 9064 system, status 0 diald: Changed snoop device to tap0 diald: Diald initial setup completed. diald: Calling site 10.0.0.2 diald: running '/etc/ppp/connect' connect: Initializing Modem chat: Can't get terminal parameters: Invalid argument connect: Failed to initialize modem diald: SIGCHLD[6]: pid 9069 dial, status 256 diald: Connect script failed. diald: Closing /dev/modem diald: Delaying 3 seconds before clear to dial. and on and on.. always that chat gets invalid argument, whatever that may be. I tried connect '/usr/sbin/chat -v -f /etc/ppp/chatscript' using my standard dialup chat script (which works normally), with the same results with diald. I tried using a "chatscript:" that had ONLY 2 sets of expect/send: "" "ATZ" OK "ATDblehbleh" Same thing happens, chat pukes. The ethertap kernel module is loaded, and there are 2 /dev/tap? entries: crw-r--r-- 1 root root 36, 16 Apr 4 08:37 /dev/tap0 crw-r--r-- 1 root root 36, 17 Apr 4 08:37 /dev/tap1 Could anyone shed some light on what I need to do to get this thing going? Thanks very much! Ron L. Smith - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
