IsdnHowto

Differences between revisions 3 and 6 (spanning 3 versions)
⇤ ← Revision 3 as of 2005-08-19 07:56:16 →
Size: 3216
Editor: S0106000d88b9f3db
Comment: added contents of IsdnHowtoHoary - needs more cleanup still
← Revision 6 as of 2006-05-24 05:29:59 → ⇥
Size: 1433
Editor: S0106000fb085cc63
Comment: remove reference to warty
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
== ISDN in Warty Warthog (Ubuntu 4.10) == == ISDN in Hoary (Ubuntu 5.04) and Breezy (Ubuntu 5.10) ==
To make isdn work in Hoary/Breezy you need to:
Line 3: Line 4:
isdn4linux (hisax) is deprecated in the upstream Linux 2.6 kernel. The following steps will install help you installing mISDN, the new isdn driver.

To get working isdn support with a AVM Fritz PCI card, do the the following:

1. Install from the Warty-CD (sudo apt-get install ...):

   isdnutils-base

and manually download and install (sudo dpkg -i ...) the following packages for capi support

  [http://archive.ubuntu.com/ubuntu/pool/universe/i/isdnutils/pppdcapiplugin_3.3.0.20040728-2_i386.deb pppdcapiplugin]
 [http://archive.ubuntu.com/ubuntu/pool/universe/i/isdnutils/libcapi20-3_3.3.0.20040728-2_i386.deb libcapi20]

2. Put the following modules in /etc/modules (sudo nano /etc/modules) to have them loaded at boot-time:
{{{
     ppp_generic
     ppp_synctty
     capi
     mISDN_core
     mISDN_l1
     mISDN_l2
     l3udss1
     mISDN_capi
     mISDN_isac
     avmfritz protocol=2
}}}
3. Disable the hisax-modules by adding the following ones to /etc/hotplug/blacklist (sudo nano /etc/hotplug/blacklist):
{{{
     hisax_fcpcipnp
     hisax
     hisax_isac
     hisax_st5481
}}}
4. Configure the dial-up account for my provider /etc/ppp/peers/isdn-provider (sudo nano /etc/ppp/peers/isdn-provider):
{{{
     sync
     noauth
     user <username>
     plugin userpass.so
     password <password>
     defaultroute
     plugin capiplugin.so
     number <dial-in number>
     protocol hdlc
     ipcp-accept-local
     ipcp-accept-remote
     /dev/null
}}}
5. Add a nameserver to /etc/resolv.conf
{{{
sudo nano /etc/resolv.conf

i.e. add this line to the file:
nameserver 195.82.119.192

press ctrl-x to exit nano
}}}
6. Add my user to the group "dip" and re-logon.
{{{
sudo adduser $USER dip
}}}

7. dial by executing "pon isdn-provider" and hangup using "poff isdn-provider"

You might add gpppon - A gnome applet that is a wrapper around pon and poff.

== ISDN in Hoary (Ubuntu 5.04) ==
To make isdn work in Hoary you need to:

1. install linux-restricted-modules-$ARCH (to get the binary avm drivers) and avm-fritz-firmware-2.6.10-3 (to get the firmware)		 1. install linux-restricted-modules-$ARCH (to get the binary avm drivers), avm-fritz-firmware-2.6.10-3 (to get the firmware) and pppdcapiplugin. The first of those is installed automatically on Breezer during OS installation.
Line 124: Line 56:
 * what about non-AVM hardware? Where does configuration differ?

ISDN in Hoary (Ubuntu 5.04) and Breezy (Ubuntu 5.10)

To make isdn work in Hoary/Breezy you need to:

1. install linux-restricted-modules-$ARCH (to get the binary avm drivers), avm-fritz-firmware-2.6.10-3 (to get the firmware) and pppdcapiplugin. The first of those is installed automatically on Breezer during OS installation.

2. add capi to /etc/modules

PCI

1. create /etc/hotplug/backlist.d/isdn with:

  • hisax
  • hisax_fcpcipnp

2. reboot so that the avm/capi modules get loaded

3. Create the connection with "Desktop/Adminstration/Networking"

4. pon ppp0; poff should work now

(sucessfully tested with AVM fritz card A1 (2.0))

PCMCIA

1. Remove the "avma1_cs" lines from /etc/pcmcia/config

2. add 

 device "fcpcmcia_cs"
   class "avma1" module "fcpcmcia_cs"

 card "AVM S0/PC ISDN"
   version "AVM", "ISDN A"
   bind "fcpcmcia_cs"

(sucessfully tested with Fritz!Card PCMCIA2.0)

USB Fritzcard DSL USB

1. edit /etc/isdn/capi.conf and add as last line: 

fcdslusb        fdsubase.frm    DSS1    -       -       -       -

(sucessfully tested with Fritz!Card DSL USB)

ToDo

Things not yet working in hoary:

  • network-admin can't activate the connection directly yet
  • modem-applet can connect too
  • what about non-AVM hardware? Where does configuration differ?

CategoryDocumentation CategoryCleanup

IsdnHowto (last edited 2008-08-06 16:39:51 by localhost)