connect issue

connect issue

[Mirco Ellis]

Hi guys, I  am a newbie to all this and desperately need some guidance. I am
using  diald 0.99.1. The problem I am having is that I can not get my
connect script to work. I am using the one in /usr/lib/diald/ connect. To
tell you the truth I have been trying all sorts of chat scripts but none of
them seem to initiate the modem. I don't know what I am doing wrong. I have
even used the init strings that minicom uses to initialize the modem, but no
luck. Obviously if I can't get the chat script or connect script to initiate
the modem I am stuck. I can however dial up with minicom and manually start
pppd, so this proves to me that the modem is working.

When I run the connect script ./connect all I get is the init string on the
command line [root@.....]# ATQ0V1E1S0=0&C1&D2+FCLASS=0

That is where it stays for a minute or so and returns to the prompt. Am I
missing something? I have read the man pages and howto's, but no luck. I see
that there is nowhere in the connect script where it actually tells the chat
program where to go look for the modem egg. DEVICE=ttyS0. I have tried all
sorts of chat scripts but no luck. Can somebody please help me here.

Thanking you in anticipation

Mirco

Re: connect issue

[Andy Hutchinson]

[-- Attachment #1: Type: text/plain, Size: 1689 bytes --]

At 11:45 17/06/2003 +0200, Mirco Ellis wrote:

>Hi guys, I  am a newbie to all this and desperately need some guidance. I am
>using  diald 0.99.1. The problem I am having is that I can not get my
>connect script to work. I am using the one in /usr/lib/diald/ connect. To
>tell you the truth I have been trying all sorts of chat scripts but none of
>them seem to initiate the modem. I don't know what I am doing wrong. I have
>even used the init strings that minicom uses to initialize the modem, but no
>luck. Obviously if I can't get the chat script or connect script to initiate
>the modem I am stuck. I can however dial up with minicom and manually start
>pppd, so this proves to me that the modem is working.
>
>When I run the connect script ./connect all I get is the init string on the
>command line [root@.....]# ATQ0V1E1S0=0&C1&D2+FCLASS=0
>
>That is where it stays for a minute or so and returns to the prompt. Am I
>missing something? I have read the man pages and howto's, but no luck. I see
>that there is nowhere in the connect script where it actually tells the chat
>program where to go look for the modem egg. DEVICE=ttyS0. I have tried all
>sorts of chat scripts but no luck. Can somebody please help me here.
>
>Thanking you in anticipation
>
>Mirco
>
>-
>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

Hi Mirco,

Chat runs to stdin and stdout. Diald sorts out the plumbing for you to 
redirect this to and from the modem device.

Send your diald scripts and config files to the list to we can have a look 
for you.

Andy.

Re: connect issue

[Mirco Ellis]

Thanks Andy but I finally cracked it!
----- Original Message -----
From: "Andy Hutchinson" <andy@extensible.co.uk>
To: <linux-diald@vger.kernel.org>
Sent: Tuesday, June 17, 2003 12:10
Subject: Re: connect issue


> At 11:45 17/06/2003 +0200, Mirco Ellis wrote:
>
> >Hi guys, I  am a newbie to all this and desperately need some guidance. I
am
> >using  diald 0.99.1. The problem I am having is that I can not get my
> >connect script to work. I am using the one in /usr/lib/diald/ connect. To
> >tell you the truth I have been trying all sorts of chat scripts but none
of
> >them seem to initiate the modem. I don't know what I am doing wrong. I
have
> >even used the init strings that minicom uses to initialize the modem, but
no
> >luck. Obviously if I can't get the chat script or connect script to
initiate
> >the modem I am stuck. I can however dial up with minicom and manually
start
> >pppd, so this proves to me that the modem is working.
> >
> >When I run the connect script ./connect all I get is the init string on
the
> >command line [root@.....]# ATQ0V1E1S0=0&C1&D2+FCLASS=0
> >
> >That is where it stays for a minute or so and returns to the prompt. Am I
> >missing something? I have read the man pages and howto's, but no luck. I
see
> >that there is nowhere in the connect script where it actually tells the
chat
> >program where to go look for the modem egg. DEVICE=ttyS0. I have tried
all
> >sorts of chat scripts but no luck. Can somebody please help me here.
> >
> >Thanking you in anticipation
> >
> >Mirco
> >
> >-
> >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
>
> Hi Mirco,
>
> Chat runs to stdin and stdout. Diald sorts out the plumbing for you to
> redirect this to and from the modem device.
>
> Send your diald scripts and config files to the list to we can have a look
> for you.
>
> Andy.
>

Controlling diald remotely

[Rod]

Greetings,

I'm looking for a better solution to control diald from a remote client.
Something that works for Windows and Linux preferred but a Linux only
solution would also be acceptable.  The ability to handle multiple ISP's
would also be good.

I'm currently using dialmon but it's a Windows client only solution and
I've been having trouble with multiple instances of diald being
(intermittently) launched on the server.

I've seen references that dctrl can be used from a remote host but there
doesn't appear to be much documentation on how to configure the
client/server to do this.

Any help/directions would be appreciated.

Cheer's,
Rod

Re: Controlling diald remotely

[Mark Frey]

Hi Rod,

Dctrl should work on any platform that has a TCL interpreter and 
networking.  You can find one for windows here:

http://aspn.activestate.com/ASPN/Tcl/Downloads/

Dctrl can use a fifo localy or a TCP socket for remote access.  You'll 
need something like this in your diald.conf:

linkname <connection name here>
linkdesc <some description of the connection>
tcpport 300
fifo /etc/diald/diald.ctl
authsimple /etc/diald/auth

You can specify the tcp host and port on the dctrl command line or in 
the <file><connect> menu, then you just give it an access name that 
matches an entry in the authsimple file.

The authsimple file maps access names in dctrl to allowed monitor 
functions.  Here's a sample auth file:

# format is:  name  allow,allow,allow..
#        or:  name  0x<hex allow bits>
#   where allow is one or more of: none, control, config, block, unblock,
#                                  force, unforce, down, up, delquit, quit,
#                                  reset, queue, debug, dynamic, monitor,
#                                  message, connect, demand, nodemand, auth.

# eg:
# thisuser up,down,message,connect
# totalaccess 0xFFFFFFFF

biguser        0xFFFFFFFF
joe	control,block,unblock,force,unforce,up,down,monitor,connect


You'll still have to figure out something to switch ISPs.

Hope this helps!

Mark.


Rod wrote:
> Greetings,
> 
> I'm looking for a better solution to control diald from a remote client.
> Something that works for Windows and Linux preferred but a Linux only
> solution would also be acceptable.  The ability to handle multiple ISP's
> would also be good.
> 
> I'm currently using dialmon but it's a Windows client only solution and
> I've been having trouble with multiple instances of diald being
> (intermittently) launched on the server.
> 
> I've seen references that dctrl can be used from a remote host but there
> doesn't appear to be much documentation on how to configure the
> client/server to do this.
> 
> Any help/directions would be appreciated.
> 
> Cheer's,
> Rod
> -
> 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
>