I fear you about to join the "Eicon 1B Club". Its membership consists of
Eicon Diva TA owners running Linux.
I did exactly the same thing you are attempting: converted a working 56k
RH 6.0 demand-dial pppd to ISDN. I was never able to get it to
authenticate under MLPPP, and even now use only a single channel.
Do a search on http://www.deja.com for "eicon diva ~g
comp.protocols.ppp" for other tales of woe, including mine.
I would get it working in 1B mode first, to ensure everything is set up
correctly (ports, secrets, chat scripts). In 1B mode, the TA just looks
like a serial modem, so the changes are minor. I suggest you use minicom
to verify that it is dialing and connecting correctly before trying it
Keep in mind that in single link mode, pppd is talking directly to the
ISP. When you configure the Diva for MLPPP (using minicom) pppd talks to
the TA, and the TA talks to the ISP, converting PPP to MLPPP on-the-fly
(at least in theory). You do NOT need any multi-link kernel patches.
Don't be confused by all the Shiva-pap stuff; that's coming from the
Eicon, not the ISP. This makes it extremely difficult to troubleshoot,
since you can't see what is going on upstream.
Eicon tech support gave me busywork; suggesting that I move to a
previous pppd rev. I have tried each and every release from 2.3.6
through 2.3.10 with exactly the same results.
The Eicon works flawlessly in 1B mode, but I would still like to run
128k. Oh well.
If you can resolve this and post a fix, I'll nominate you for President
of the Club. For Life.
> I am going to be converting a (working) Red Hat 6.0
> server which dials an ISP using pppd and a 56K modem
> to an Eicon Diva ISDN modem.
> If anyone has experience with this, would you mind me
> mooching a copy of your /etc/ppp/options and
> /etc/sysconfig/network-scripts/chat-ppp0 files. I am
> especially interested in how you bonded (aggregated) the two
> channels together.
> Any suggestions and recommendations will also be
> greatly appreciated.
> Many thanks,