Re: ISDNUTILS package, Problem with immediate hangup
I have exactly the same problem, sounds like a bug to me...
-AK
>
> I have a problem with the isdnutils 2.1beta1-20 package. Using the
> following script (some phone numbers hidden) I was able to login to my
> provider, after a final "route add default ippp0" after connecting
> using ping my network connections is available and stable:
>
> LOCAL_NUMBER="xxxxxxx"
> REMOTE_NUMBER="yyyyyyy"
> LOCAL_IP="10.0.0.1"
> REMOTE_IP="10.0.0.2"
> DEVICE="ippp0"
> ISDNCTRL="isdnctrl"
> $ISDNCTRL addif $DEVICE
> $ISDNCTRL addphone $DEVICE out $REMOTE_NUMBER
> $ISDNCTRL eaz $DEVICE $LOCAL_NUMBER
> $ISDNCTRL l2_prot $DEVICE hdlc
> $ISDNCTRL l3_prot $DEVICE trans
> $ISDNCTRL encap $DEVICE syncppp
> $ISDNCTRL huptimeout $DEVICE 600
> $ISDNCTRL chargehup $DEVICE off
> $ISDNCTRL secure $DEVICE on
>
> ifconfig $DEVICE $LOCAL_IP pointopoint $REMOTE_IP metric 1 -arp
> route add default dev $DEVICE
>
> ipppd user <my name> remotename <my provider> \
> noipdefault \
> ipcp-accept-remote \
> -vjccomp -ac -pc \
> -detach \
> mru 1524 \
> -bsdcomp \
> debug \
> /dev/ippp0 &
>
> Now I try to achieve the same using the /etc/init.d/isdnutils script.
> I have created the device.ippp0 and ipppd.ippp0 files in /etc/isdn and
> configured them according to the above options. But I have still the
> problem, that after establishing my connection the ipppd is
> terminating my connection. I tried with both nodetach and detach
> options. If you are interested in the complete options files please
> request them via email.
>
> The ipppd seems to behave as the connection is immediatly (well 7-8
> seconds aftrer connection) hangup (like with the isdnctrl hangup ippp0
> command). Here is a part of my daemon.log
>
> Apr 20 20:20:39 marvin ipppd[844]: rcvd [0][IPCP ConfAck id=0x2 <addr
xxx.xxx.xxx.xxx> <compress VJ 0f 00>]
> Apr 20 20:20:39 marvin ipppd[844]: local IP address xxx.xxx.xxx.xxx
> Apr 20 20:20:39 marvin ipppd[844]: remote IP address yyy.yyy.yyy.yyy
> Apr 20 20:20:39 marvin ipppd[844]: rcvd [0][CCP ConfRej id=0x2]
> Apr 20 20:20:46 marvin ipppd[844]: Modem hangup
> Apr 20 20:20:46 marvin ipppd[844]: Connection terminated.
> Apr 20 20:20:46 marvin ipppd[844]: taking down PHASE_DEAD link 0,
linkunit: 0
> Apr 20 20:20:46 marvin ipppd[844]: sent [0][LCP TermReq id=0x2 6c 69 6e
6b 20 63 6c 6f 73 65 64]
> Apr 20 20:20:46 marvin ipppd[844]: LCP is down
> Apr 20 20:20:46 marvin ipppd[844]: link 0 closed , linkunit: 0
> Apr 20 20:20:46 marvin ipppd[844]: reinit_unit: 0 file.
>
> Does anybody have any idea what could be the reason for this hangup?
>
> BTW: The hangup is not a result of the failed ccp negotiation. The
> message prior to the hangup are exactly the same as in the working
> setup.
>
> Thanks,
>
> Torsten
>
>
> --
> To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
listmaster@lists.debian.org
>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: