Re: modemdevice does not respond after first hangup

Hi,

can you try with the latest version of the HSF modem driver (currently 
7.47.00.00) available at:

http://www.linuxant.com/drivers/hsf/downloads-license.php

to see if there is a difference?

We are also aware of connection stability issues with that version of 
the HSF modem driver for HDA modems and a new version of the driver will 
soon be released with a fix for this problem.

Regards,


Jonathan
Technical specialist / Linuxant
www.linuxant.com
[email protected]



Harald Jung wrote:
> Hi,
> 
> After i have done a hangup after the first successfull connection, the modem 
> device does not respond anymore.
> 
> 
> greetings 
> Harald
> 
> 
> 
> I use a test like this for sending the AT commands:
> 
>  open(MODEM, "+<", $ARGV[0]) or die "can't open modem $modem ($!)";
>  print(MODEM "$ARGV[1]\r");
>         while (<MODEM>)
>            {
>            print "$_\n";
>            }
> close MODEM;
> 
> the connect skript:
> 
> ABORT BUSY
> ABORT 'NO CARRIER'
> ABORT ERROR
> REPORT CONNECT
> TIMEOUT 60
> "" "AT&F"
> OK "AT&c1&k3M0X3"
> OK "ATDT*338"
> CONNECT ""
> 
> the disconnect skript:
> "" "\K"
> "" "+++ath"
> 
> the pppd config file:
> /tmp/dev/ttySL0
> debug
> nodeflate
> nobsdcomp
> refuse-eap
> connect '/usr/sbin/chat -v 
> -f /var/syscfg/etc/ppp/modem.chat.f54068ad120e79565fe64b5aec38d2cc'
> disconnect '/usr/sbin/chat -v -f /etc/ppp/chat.hangup'
> refuse-mschap
> refuse-mschap-v2
> ipparam f54068ad120e79565fe64b5aec38d2cc
> nomppc
> usepeerdns
> user "foobar"
> 115200
> refuse-chap
> refuse-mschap-v2
> nolog
> nobsdcomp
> noauth
> crtscts
> ipcp-accept-local
> ipcp-accept-remote
> lock
> hide-password
> local
> mru 1492
> mtu 1492
> lcp-echo-failure 3
> lcp-echo-interval 5
> password FASELBLAH
> replacedefaultroute
> defaultroute
> 
> _______________________________________________
> hsflinux mailing list
> [email protected]
> https://www.linuxant.com/mailman/listinfo/hsflinux