I'm having somewhat of a time-critical problem with diald. Here's all the
environment details:
Redhat 6.0, Linux 2.2.5, Diald 0.99
/etc/diald.conf:
[root@gw samba]# cat /etc/diald.conf
mode ppp
connect '/usr/sbin/chat -v -f /etc/ppp/chat-pipex'
device /dev/ttyS1
speed 115200
debug 127
lock
crtscts
local 10.0.0.254
remote 10.0.0.253
dynamic
defaultroute
include /usr/lib/diald/standard.filter
aaand, the chat script:
[root@gw samba]# cat /etc/ppp/chat-pipex
ABORT "NO CARRIER"
ABORT "NO DIALTONE"
ABORT "ERROR"
ABORT "NO ANSWER"
ABORT "BUSY"
"" ""
"" "at"
OK "at&d0&c1"
OK "atdt908450885056"
TIMEOUT 120
"ogin:" "__mumble__"
"word:" "__mumbleagain__"
"MTU is"
This chat script works with 'pppd call pipex', with these options in
/etc/ppp/peers/pipex:
[root@gw samba]# cat /etc/ppp/peers/pipex
ttyS1 57600 crtscts defaultroute
bsdcomp 15,15
debug
connect '/usr/sbin/chat -v -f /etc/ppp/chat-pipex'
noauth
Now, here's the problem. I installed diald, set up the conf file as
above, made sure 'slip' modules were loaded and the ethertap module was
loaded. Typed 'diald', and got:
May 24 12:01:06 gw diald[997]: keepup parsing error. Got token 'tcp.ssl'.
Not a known tcp service port.
May 24 12:01:06 gw diald[997]: parse string: 'tcp 120 tcp.dest=tcp.ssl'
May 24 12:01:06 gw diald[997]: keepup parsing error. Got token 'tcp.ssl'.
Not a known tcp service port.
May 24 12:01:06 gw diald[997]: parse string: 'tcp 120 tcp.source=tcp.ssl'
May 24 12:01:06 gw diald[998]: Proxy device established on interface tap0
May 24 12:01:06 gw diald[998]: running '/sbin/ifconfig tap0 10.0.0.254
pointopoint 10.0.0.253 broadcast 0.0.
0.0 netmask 255.255.255.255 metric 0 mtu 1500 up'
May 24 12:01:06 gw diald[998]: SIGCHLD[1]: pid 999 system, status 256
May 24 12:01:06 gw diald[998]: start tap0: Establishing routes for tap0
May 24 12:01:06 gw diald[998]: running '/sbin/route add 10.0.0.253 metric
0 dev tap0'
May 24 12:01:07 gw diald[998]: SIGCHLD[2]: pid 1000 system, status 0
May 24 12:01:07 gw diald[998]: running '/sbin/route add default metric 0
netmask 0.0.0.0 dev tap0'
May 24 12:01:07 gw diald[998]: SIGCHLD[3]: pid 1001 system, status 0
May 24 12:01:07 gw diald[998]: Changed snoop device to tap0
May 24 12:01:07 gw diald[998]: Diald initial setup completed.
May 24 12:01:07 gw diald[998]: --- tick --- state 0 block 0 state_timeout
-1
May 24 12:01:38 gw last message repeated 30 times
Okay so far, i can fix the ssl problems...
So I 'kill -USR1' to tell diald to go online... and i get:
May 24 12:01:48 gw diald[998]: SIGUSR1. External link up request received.
May 24 12:01:48 gw diald[998]: new state CONNECT action 0x8050dc8 timeout
60
May 24 12:01:48 gw diald[998]: Calling site 10.0.0.253
May 24 12:01:49 gw diald[998]: running '/usr/sbin/chat -v -f
/etc/ppp/chat-pipex'
May 24 12:01:49 gw diald[998]: --- tick --- state 1 block 0 state_timeout
59
May 24 12:01:49 gw chat[1006]: Can't get terminal parameters: Invalid
argument
May 24 12:01:49 gw diald[998]: SIGCHLD[4]: pid 1006 dial, status 512
May 24 12:01:49 gw diald[998]: Connect script failed.
May 24 12:01:49 gw diald[998]: new state CLOSE action 0x8051518 timeout -1
May 24 12:01:49 gw diald[998]: Closing /dev/ttyS1
May 24 12:01:50 gw diald[998]: Delaying 30 seconds before clear to dial.
Note the 'can't get terminal parameters' error. I think that's the
indicator. Am i mismatching my tty's or something?
This is very imporant, as I am only in England for aboutanother day to get
this set up...
Help?
-------------------. Web-based problem management: www.stonekeep.com
Dave Belfer-Shevett >----------------------------------------------------.
[EMAIL PROTECTED] / You Know You're a coffee addict when (#22) : You've \
------------------< worn out the handle on your favorite mug. |
\______________________________________________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
