🚀 go-pugleaf

Hello again,

>This is isdn4k-utils-3.0beta2-2 on Red Hat 5.2. It seems that ipppd
>makes an unnecessary call to ioctl for the slave link. The above log is
>a successful 2 channel connection. The important thing is that you get
>the "valid bundle" message - do you?

This is what I get:

Jul 19 17:15:44 beltd ipppd[18651]: PHASE_WAIT -> PHASE_ESTABLISHED, ifunit: 
1, linkunit: 0, fd: 7
Jul 19 17:15:44 beltd ipppd[18651]: ioctl(SIOCSIFMTU): No such device, 6 ippp1 
1500.
Jul 19 17:15:45 beltd ipppd[18651]: Remote message:
Jul 19 17:15:45 beltd ipppd[18651]: MPPP negotiation, He: Yes We: Yes
Jul 19 17:15:45 beltd ipppd[18651]: ipppd[0]: discr: 2
Jul 19 17:15:45 beltd ipppd[18651]: ipppd[0]: passed 1
Jul 19 17:15:45 beltd ipppd[18651]: ipppd[0]: passed 2
Jul 19 17:15:45 beltd ipppd[18651]: ipppd[0]: pap/chap-check passed
Jul 19 17:15:45 beltd ipppd[18651]: ok, found a valid bundle with linkunit 1
Jul 19 17:15:45 beltd ipppd[18651]: bundle: -1

The 'bundle: -1' bit is a tad worrying. Could that be that I don't have MPPP 
in the kernel options?

>What command are you using to force the second line to connect? And what
>is in your config file for both the interface and the slave? The correct
>command is "isdnctrl addlink <interface>" where <interface> is the
>primary not the slave. This isn't in the man page I have (it does warn
>that it isn't complete).

Whenever I type isdnctrl addlink ippp0, I get an error

ippp0: operation not permitted

This is the file I'm using to set up the two interfaces (excuse long lines)

/sbin/isdnctrl reset force

/sbin/isdnctrl addif  $DEVICE            # Create new interface 'DEVICE'
/sbin/isdnctrl addslave ippp0 ippp1
/sbin/isdnctrl verbose 1
/sbin/isdnctrl eaz $DEVICE $LOCAL_NUMBER             # Set local EAZ ..
/sbin/isdnctrl l2_prot $DEVICE hdlc      # for sync PPP: set Level 2 to HDLC
/sbin/isdnctrl l3_prot $DEVICE trans     # not really necessary, 'trans' is 
defau
/sbin/isdnctrl encap $DEVICE syncppp
/sbin/isdnctrl chargehup $DEVICE off     # Hangup before next Charge-Info
/sbin/isdnctrl ihup $DEVICE off          # Hangup incoming call
/sbin/isdnctrl secure $DEVICE on         # Accept only configured phone-number
/sbin/isdnctrl dialmode $DEVICE auto
/sbin/isdnctrl huptimeout $DEVICE 10
/sbin/isdnctrl addphone $DEVICE out $REMOTE_NUMBER

/sbin/isdnctrl addif ippp1
/sbin/isdnctrl verbose 1
/sbin/isdnctrl eaz ippp1 $LOCAL_NUMBER
/sbin/isdnctrl l2_prot ippp1 hdlc
/sbin/isdnctrl l3_prot ippp1 trans
/sbin/isdnctrl encap ippp1 syncppp
/sbin/isdnctrl chargehup ippp1 off
/sbin/isdnctrl ihup ippp1 off
/sbin/isdnctrl secure ippp1 on
/sbin/isdnctrl dialmode ippp1 auto
/sbin/isdnctrl addphone ippp1 out $REMOTE_NUMBER


/sbin/isdnlog -Dv -l1015 -x1015 /dev/isdnctrl0

/sbin/ipppd +mp user $MYUSER $LOCAL_IP:$REMOTE_IP name $MYUSER lcp-restart 1 
/dev/$DEVICE /dev/ippp1
sleep 1
/sbin/route add default $DEVICE

$DEVICE is ippp0

Where should the 'addslave' command go? It seems relatively critical where it 
is positioned, as sometimes it fails. Does it have to be before the second 
interface is actually created (with addif)?

Thanks again for all the help.

Andy

-- 
Andrew Hawkins            | Audiosoft Ltd,
AudioPC Product Manager   | 3 Longwood Court, Love Lane, Cirencester
                          | Gloucestershire GL7 1YG
                          | Tel: +44 1285 883800 Fax: +44 1285 883801