🚀 go-pugleaf

Andrew Hawkins <andrew.hawkins@audiosoft.co.uk> wrote:

> However, when we connect we get the following:

> MPPP negotiation, He: No We: No

> I take this to mean that the demon end is saying it can't support MPPP. Is 
> this the way to configure it? Is it just saying it can't because we can't?

Have you 
a) got MPPP compiled in?
b) got +mp in the options file?

Hi,

In article <dev0l8.c21.ln@anacon.demon.co.uk>, Mark Evans 
<mpe@anacon.demon.co.uk> wrote:

>a) got MPPP compiled in?

That's a very good question, I'll try re-compiling to make sure I have. 

Ah, where is the option for that? I've done a 'make config' and all I get 
under ipppd options is some stuff about CHAP and RADIUS. Where do I look to 
get this option?

>b) got +mp in the options file?

Yes, tried that. I would have at least expected to see He: No We: Yes in that 
case. It could be the compilation options. Thanks for the pointer.

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

Hi,

Bad form to follow up my own article but:

In article <8l3p94$2jo$1@beltd.demon.co.uk>, andrew.hawkins@audiosoft.co.uk 
(Andrew Hawkins) wrote:
>>b) got +mp in the options file?
>
>Yes, tried that. I would have at least expected to see He: No We: Yes in that 
>case. It could be the compilation options. Thanks for the pointer.

Just tried that again, and now both ends are reporting MPPP support. However, 
when I force dialling of the second channel, I'm now getting an error saying 
that it can't load a module for ippp1.

It also say then that it can't find the device ippp1.

The /dev/ippp1 exists and appears to be correct, what else am I missing?

Many thanks.

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

Andrew Hawkins wrote:
> 
> Hi,
> 
> Bad form to follow up my own article but:
> 
> In article <8l3p94$2jo$1@beltd.demon.co.uk>, andrew.hawkins@audiosoft.co.uk
> (Andrew Hawkins) wrote:
> >>b) got +mp in the options file?
> >
> >Yes, tried that. I would have at least expected to see He: No We: Yes in that
> >case. It could be the compilation options. Thanks for the pointer.
> 
> Just tried that again, and now both ends are reporting MPPP support. However,
> when I force dialling of the second channel, I'm now getting an error saying
> that it can't load a module for ippp1.
> 
> It also say then that it can't find the device ippp1.
> 
> The /dev/ippp1 exists and appears to be correct, what else am I missing?

This isn't necessarily an error. From my log:

Jul 17 11:00:26 celeron kernel: isdn_net: ippp1 connected
Jul 17 11:00:26 celeron ipppd[33]: Local number: xxxxxxxxxxx, Remote
number: 08450798667, Type: outgoing
Jul 17 11:00:26 celeron ipppd[33]: PHASE_WAIT -> PHASE_ESTABLISHED,
ifunit: 1, l
inkunit: 0, fd: 8
Jul 17 11:00:26 celeron modprobe: can't locate module ippp1
Jul 17 11:00:26 celeron ipppd[33]: ioctl(SIOCSIFMTU): Operation not
supported by
 device, 7 ippp1 1500.
Jul 17 11:00:26 celeron ipppd[33]: Remote message:
Jul 17 11:00:26 celeron ipppd[33]: MPPP negotiation, He: Yes We: Yes
Jul 17 11:00:26 celeron ipppd[33]: ipppd[0]: discr: 2
Jul 17 11:00:26 celeron ipppd[33]: ipppd[0]: passed 1
Jul 17 11:00:26 celeron ipppd[33]: ipppd[0]: passed 2
Jul 17 11:00:26 celeron ipppd[33]: ipppd[0]: pap/chap-check passed
Jul 17 11:00:26 celeron ipppd[33]: ok, found a valid bundle with
linkunit 1     Jul 17 11:00:26 celeron ipppd[33]: bundle: 0  

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?

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).

Regards, Ian

Andrew Hawkins <andrew.hawkins@audiosoft.co.uk> wrote:
> Hi,

> In article <dev0l8.c21.ln@anacon.demon.co.uk>, Mark Evans 
> <mpe@anacon.demon.co.uk> wrote:

>>a) got MPPP compiled in?

> That's a very good question, I'll try re-compiling to make sure I have. 

> Ah, where is the option for that? I've done a 'make config' and all I get 
> under ipppd options is some stuff about CHAP and RADIUS. Where do I look to 
> get this option?

You need to look under the kernel sources, rather than the i4l sources.

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

In article <8kv001$9af$1@beltd.demon.co.uk>, Andrew Hawkins <andrew.hawk
ins@audiosoft.co.uk> writes
>Hi all,
>
>Can anyone give me any pointers as to how to get bonded ISDN working with 
>Demon under Linux? I understand that the Red Romp supports this.
>
>However, when we connect we get the following:
>
>MPPP negotiation, He: No We: No

I'm told that Demon tried multilink but it all went pear shaped and so
they withdrew it until they could make it work.

TB               Busby the Cat 1984 - 22.9.1999

Hi,

In article <v3v4l8.1p2.ln@anacon.demon.co.uk>, Mark Evans 
<mpe@anacon.demon.co.uk> wrote:

>You need to look under the kernel sources, rather than the i4l sources.

Thanks to all who helped out, this was the line which hit the nail on the 
head. The kernel wasn't compiled for MPPP support.

I've since re-compiled and now everything works fine.

Thanks to all who helped.

I occasionally get the odd 'skipping frame' message, are these normal?

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

In article <fxgXuUBfOxd5EwlG@btinternet.com>, Tom Bird
<hamster@nospam.demon.co.uk> writes
>I'm told that Demon tried multilink but it all went pear shaped and so
>they withdrew it until they could make it work.

Works fine from here, and it has done for quite a while now,

        Tom

In the best d.s tradition "It must be your setup."