Re: isdn4linux with Kernel 3.2

Hallo Peter,

On 06/20/2013 05:31 PM, Peter Koch wrote:
> Dear isdn experts,
> 
> I'm using isdn4linux for almost 20 years now. About 8 years ago I
> installed a couple of linux boxes with isdn4linux and these machines are
> interchanging data via ISDN with abolutely no problems. For security
> reasons these machines are not connected with the internet. Whenever one
> machine wants to talk to another one (which happens approximately once
> per day) it calls the other machine and the other machine will do a
> callback.
> 
> Now I would like to contact these machines from our central intranet
> server. Should be easy: plug in a fritzcard, add isdn4linux to the
> kernel, compile isdn4k-util, configure the callback numbers - that's it.
> 
> Today I realized that the isdn-stuff has completely changed during the
> last 5-8 years.

No the old stuff is still here and not changed so much, so everything
should work with the original configs. I did not test it by myself for
about 2 years, but nothing was changed, if something doesn't work,
it could be a side effect of some other changes in the network layer -
but I'm not aware of anything.

The new stuff is independent and gives new functions, not needed for
simple data communications.

> 
> Our isdn-machines are running Linux 2.4.29 with isdn4k-util v3.2p1.
> The intranet server runs Linux 3.2 and the admins are planning to
> upgrade to 3.4.
> isdn4linux has been replaced by mISDN and CAPI-stuff. No one seems to
> use ISDN for data connections any more
> 

Also CAPI can make data connections - via pppdcapiplugin and pppd, but
for you the old stuff should be easier.


> So here's my simple question: Is it possible to connect our Linux 3.2
> server with the old 2.4 machines. Or must I create a separate
> Ethernet-to-ISDN gateway based on a 2.x kernel?
> 

Best regards

Karsten