🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: demon.tech.unix
Article #246

Re: Bonded ISDN with Linux

#246
From: Ian Northeast
Date: Wed, 19 Jul 2000 00:00
54 lines
3104 bytes
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
Technical Details
Message-ID: <3975F656.CDF67418@house-from-hell.demon.co.uk>
Path: arc1-ca.pugleaf.net!unknown!not-for-mail
References: <8kv001$9af$1@beltd.demon.co.uk> <dev0l8.c21.ln@anacon.demon.co.uk> <8l3p94$2jo$1@beltd.demon.co.uk> <8l4kt1$k7h$1@beltd.demon.co.uk>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fac57,75e4812e2558b8b2
X-Google-Attributes: gidfac57,public
From: Ian Northeast <ian@house-from-hell.demon.co.uk>
Subject: Re: Bonded ISDN with Linux
Date: 2000/07/19
Message-ID: <3975F656.CDF67418@house-from-hell.demon.co.uk>
X-Deja-AN: 648302170
Content-Transfer-Encoding: 7bit
X-NNTP-Posting-Host: house-from-hell.demon.co.uk:212.228.30.193
References: <8kv001$9af$1@beltd.demon.co.uk> <dev0l8.c21.ln@anacon.demon.co.uk> <8l3p94$2jo$1@beltd.demon.co.uk> <8l4kt1$k7h$1@beltd.demon.co.uk>
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: abuse@demon.net
X-Trace: news.demon.co.uk 964032091 nnrp-14:23336 NO-IDENT house-from-hell.demon.co.uk:212.228.30.193
MIME-Version: 1.0
Newsgroups: demon.tech.unix