ISDN Setup: isdn_net: local hangup ippp0

G'day,

Trying to setup a Micronet ISDN PCI card to dial into
South Africa's Telkom ISP is proving to be rather painful.
It's supposed to be a multilink isdn ...

I'd appreciate any ideas, suggestions, pointers, configs
from others...

Here go's, ... the card's a HCF-PCI on irq 5 ... the USB HUB
controller was using irq 5 so I disabled it in the bios
and now only the isdn card uses irq 5. I don't have a 'lspci -vv'
listing (cause I forgot to make but the following from
/var/log/messages should kinda show what it is ...

I believe it to be a 'type 35' from
/usr/src/linux/Documentation/isdn/README.HiSax

Card types:

Type Required parameters (in addition to type and
protocol)
35 HFC 2BDS0 PCI none

Now, which protocol to chose???

However, when I setup /etc/modutils/hisax with any of the protocols,
(1,2,3) (* the US type 4 I have not tested yet ...) I get not
connection

Oct 4 15:45:01 goldex01 kernel: NETDEV WATCHDOG: ippp0: transmit
timed out
Oct 4 15:45:01 goldex01 kernel: isdn_tx_timeout dev ippp0 dialstate 0
Oct 4 15:45:01 goldex01 kernel: OPEN: 10.0.0.1 -> 10.0.0.2 ICMP
Oct 4 15:45:01 goldex01 kernel: ippp0: dialing 1 0860007249...
Oct 4 15:45:10 goldex01 kernel: isdn_net: local hangup ippp0
Oct 4 15:45:10 goldex01 kernel: ippp0: Chargesum is 0

log/messages shows:

messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Linux Driver for
passive ISDN cards
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Version 3.5
(module)
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Layer1 Revision
1.1.4.1
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Layer2 Revision
1.1.4.1
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: TeiMgr Revision
1.1.4.1
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Layer3 Revision
1.1.4.1
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: LinkLayer Revision
1.1.4.1
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Certification not
verified
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: Card 1 Protocol
EDSS1 Id=HiSax (0)
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: HFC-PCI driver Rev.
1.1.4.1
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: HFC-PCI card
manufacturer: CCD/Billion/Asuscom card name: 2BD0
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: protocol euro not
supported
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: 2 channels added
messages.0:Oct 1 17:27:01 goldex01 kernel: HiSax: MAX_WAITING_CALLS
added

Seems like the euro protocol (type 2) is not supported ...

so I tried the german one (type 1) ....

messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Linux Driver for
passive ISDN cards
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Version 3.5
(module)
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Layer1 Revision
1.1.4.1
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Layer2 Revision
1.1.4.1
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: TeiMgr Revision
1.1.4.1
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Layer3 Revision
1.1.4.1
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: LinkLayer Revision
1.1.4.1
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Certification not
verified
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: Card 1 Protocol
1TR6 Id=HiSax (0)
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: HFC-PCI driver Rev.
1.1.4.1
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: HFC-PCI card
manufacturer: CCD/Billion/Asuscom card name: 2BD0
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: protocol 1tr6 not
supported
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: 2 channels added
messages.0:Oct 1 17:35:04 goldex01 kernel: HiSax: MAX_WAITING_CALLS
added

which also appears not to be supported ...

However, protocol 3 for leased lines (no D-Channel) does not complain
....

messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Linux Driver for
passive ISDN cards
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Version 3.5
(module)
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Layer1 Revision
1.1.4.1
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Layer2 Revision
1.1.4.1
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: TeiMgr Revision
1.1.4.1
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Layer3 Revision
1.1.4.1
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: LinkLayer Revision
1.1.4.1
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Certification not
verified
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Card 1 Protocol
LEASED Id=HiSax (0)
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: HFC-PCI driver Rev.
1.1.4.1
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: HFC-PCI card
manufacturer: CCD/Billion/Asuscom card name: 2BD0
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: Leased line mode
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: 2 channels added
messages.0:Oct 1 17:44:00 goldex01 kernel: HiSax: MAX_WAITING_CALLS
added

Am I supposed to be using protocol 3 ??? (please someone kick me if
it's _definetely_ the US protocol 4 ... cause I have not tested it!

I believe to have /etc/ppp/ chap and pap secrets properly setup; both
are the same:


(E-Mail Removed) * MyPaSsWoRd

(the same way for my working modem connection, obviously different
account details)

Following is the /etc/isdn/ipppd.ippp0

## -------------------------------------------------------------------
# Options file for ipppd.
# ipppd will not read /etc/ppp/options or /etc/ppp/ioptions or any
other
# config file. Everything has to be in here.


# "peer" is the name for our syncppp partner.

# STANDARD OPTIONS

##@@ I guess (now) that I should have enabled debugging and
##@@ increased the verbose level ...
#debug # enable debugging
#kdebug X # set kernel debugging level to X

#nodetach # (no) fork to the background
#callback X # ask for callback (parameter X ?)

##@ I have tried with and without lock
lock # create a lock file for device

#domain X # add domain X to a given hostname
#pidfile X # save pid in file X
#call X # take options from privileges file (???)
#idle X # idle time limit (seconds)
#holdoff X # holdoff time limit (seconds)
#maxconnect X # set maximum connection time (in seconds ?)

##@ I have tried with and without +mp
+mp # enable multi line ppp

#+pwlog # log password (WARNING: possible security hole)
#nomagic # magic number negotiation

# ppp handshake : tuning

#silent # don't even try to initiate the connection
#passive # wait for the peer to initiate the connection
#lcp-echo-failure X # consecutive echo failures
#lcp-echo-interval X # time for lcp echo events
lcp-restart 1 # Set timeout for LCP
#lcp-max-terminate X # Set max #xmits for term-reqs
#lcp-max-configure X # Set max #xmits for conf-reqs
#lcp-max-failure X # Set max #conf-naks for LCP


# AUTHENTICATION

##name # set local name for auth XXX_

##@ replace the NNNN with the 4 digits of the real username
name (E-Mail Removed) # set local name for auth XXX_


#user X # set name for auth with peer; default is value for name
#usehostname # use hostname for auth
#remotename X # set remote name for auth


##@ I have tried with and without noauth
noauth # (dont) require peer (the other) to auth

#require-pap # allow only pap authentication (dialin only)
#require-chap # allow only chap authentication (dialin only)
#login # use system password database for pap
#papcrypt # pap passwords are encrypted

# AUTHENTICATION TUNING
#pap-restart X # Set retransmit timeout for PAP
#pap-max-authreq X # Set max #xmits for auth-reqs
#pap-timeout X # Set time limit for peer PAP auth.
#chap-restart X # Set timeout for CHAP
#chap-max-challenge X # Set max #xmits for challenge
#chap-interval X # Set interval for rechallenge

# COMPRESSION

#noaccomp # address compression on/off
#nopcomp # protocol field compression on/off
#novj # van jacobsen compression on/off
#novjccomp # van jacobsen connection-ID compression on/off
#vj-max-slots X # tune maximum vj header slots
#nobsdcomp # bsd compression on/off
#nodeflate # deflate compression on/off
#nopredictor1 # predictor1 compression in/off
##@@ this I left as is ...
noccp # compression negotation on/off
nolzs # LZS compression off (not yet supported fully)


# IP NETWORKING

#noip # (do not) disable ip transfer
#X:Y # (do not) set local ip to X, remote ip to Y
noipdefault # do not use name for default ip addr
#useifip # (do) use ip addresses from interface
#usefirstip # (do) use first ip from auth file for remote
netmask 255.255.255.255 # do set netmask, 255.255.255.255 for
pointopoint

##@ I have tried with and without defaultroute
defaultroute # (do not) set default route

#nohostroute # do not set host route
#proxyarp # (do not) set an proxy arp entry
#mru X # (do not) set maximum size of receive units to X
#default-mru # (do not) enable mru negotation
##@@ this I left as is ...
mtu 1500 # do set max size of transmit units (1500 is OK)
#useifmtu # (do not) use mtu from interface
#ipparam X # (do not) set ip parameters in script X
#ms-dns X # (do not) set dns addr for the peers use (dialin only)
#ms-wins X # (do not) wins address for the peers use (dialin only)
##@@ this I left as is ...
ms-get-dns # (do not) accept peers suggestion of dns addr (dialout)
#set_userip # (do not) define valid ip addrs in /etc/ppp/useriptab


#ipcp-restart X # Set timeout for IPCP
#ipcp-max-terminate X # Set max #xmits for term-reqs
#ipcp-max-configure X # Set max #xmits for conf-reqs
#ipcp-max-failure X # Set max #conf-naks for IPCP

##@@ these two were always there ...
ipcp-accept-local # Accept peer's address for us
ipcp-accept-remote # Accept peer's address for it

# IPX NETWORKING

#noipx # en/disable ipx
#ipx-network X # IPX network number
#ipxcp-accept-network # Accept peer netowrk
#ipx-node X # IPX node number
#ipxcp-accept-local # Accept our address
#ipxcp-accept-remote # Accept peer's address
#ipx-routing X # IPX routing proto number
#ipx-router-name X # IPX router name
#ipxcp-restart X # Set timeout for IPXCP
#ipxcp-max-terminate X # max #xmits for term-reqs
#ipxcp-max-configure X # max #xmits for conf-reqs
#ipxcp-max-failure X # max #conf-naks for IPXCP
## -------------------------------------------------------------------


Following is /etc/isdn/device.ippp0


#!/bin/sh
# Instructions: read the comments for each command, and if necessary,
edit
# the command (e.g. replace EAZ with your real EAZ or MSN). Look for
lines
# marked with XXX_, which is probably all you need to change.
# If the command is commented out, remove the leading '#' to enable it
if
# the command is needed.
#
# After you have configured this file, remove the "Warning!" line
above to
# enable this file.

# If using dynamic IP addresses:
# Check out the /etc/ppp/ip-up.d/isdnutils and
/etc/ppp/ip-down.d/isdnutils
# scripts, to ensure that any routing is done correctly there (the
# ip-up.d/isdnutils script is run after a syncPPP link is established,
and the
# ip-down.d/isdnutils script is run after the link goes down).
# You need to have the ppp package installed for those scripts to
work.

set -e # exit on _any_ error

# Get the device name
device=`basename $0`; device=${device#*.}
# this used to be simple, but POSIX is a bit more limited
# ippp0+8 -> devtype=ippp
devtype=${device%%[0-9]*}
# ippp0+8 -> devnums=0+8
devnums=${device##$devtype}
# ippp0+8 -> device=ippp8
device=$devtype${devnums#[0-9]*+}
dowhat="$1"
masterslave="$2"
case "x$masterslave" in
xmaster) master=true; slave=false;;
xslave) master=false; slave=true; masterdevice="$3";;
x) master=false; slave=false;;
*) echo "Error, $0 called with unknown 2nd arg '$masterslave',
aborting!"
exit 1;;
esac


# The (dummy) IP addresses
#
# Use 10.0.0.1 for LOCALIP and 10.0.0.2 for REMOTEIP if you have
# dynamic IP addresses; with static address fill in the real values!


##@ TELKOM is supposed to work with dynamic IPs ... so we leave this
##@ as is ... I guess?

LOCALIP=10.0.0.1 # XXX_
REMOTEIP=10.0.0.2 # XXX_

# Phone numbers (without the leading zero)
#
# REMOTEMSN may be a list of numbers to dial, separated by a space.
# If you do that, DO put quotes around the whole value! Like:
# REMOTEMSN='221345788 221345789'
#
# The REMOTEMSN must be the areacode (without the leading zero) +
phonenumber!
#
# Example: areacode: 0221 phonenumber: 345789
# => REMOTEMSN='221345789'
#
# EXPLANATION:
# A zero is added below when it is used as the outgoing number;
# when it it used as the incoming number, it must be without a leading
zero
# (which is why you must leave that leading zero out below).
# The local number must also be given without the leading zero!
#
# EXCEPTION:
# In countries where there are NO areacodes, this leading zero must
NOT be
# added. In that case, change the value of LEADINGZERO below to ''
# LEADINGZERO could conceivably need to be something else in certian
# situations, so it is configurable.

LOCALMSN='0NNNNNNNNN' # XXX_ ##@ replaced with N's for anonymity

#REMOTEMSN='manual' # XXX_
REMOTEMSN='0860007249' # XXX_

##@@ I have tried with and without the leading zero ... makes no diff,
##@@ I still get the cursed "isdn_net: local hangup ippp0"


# DIALMODE:
# New with kernel 2.0.36 is the `dialmode' setting.
# dialmode=auto is compatible with the old behaviour (dial-on-demand
enabled).
# Read the isdnctrl manpage for more info.
# Change the value below if you want a different setting when the
interface is
# started.
# For slave devices (channel bundling) dialmode _must_ be auto,
# so for slave devices this setting is ignored.

DIALMODE=auto # XXX_ other values can be 'on' and 'off'


[snip off the rest of the file cause I have not changed anything ...]
## -------------------------------------------------------------------


An ifconfig (which I do not have at hand unfortunately) shows the
ippp0 interface, and appears healthy with an mtu of 1500


here's a good chunk of log/messages trying to unsuccedfully dial out
....

Oct 4 16:43:57 goldex01 kernel: NETDEV WATCHDOG: ippp0: transmit
timed out
Oct 4 16:43:57 goldex01 kernel: isdn_tx_timeout dev ippp0 dialstate 0
Oct 4 16:43:57 goldex01 kernel: OPEN: 10.0.0.1 -> 10.0.0.2 ICMP
Oct 4 16:43:57 goldex01 kernel: ippp0: dialing 1 0860007249...
Oct 4 16:44:05 goldex01 kernel: isdn_net: local hangup ippp0
Oct 4 16:44:05 goldex01 kernel: ippp0: Chargesum is 0
Oct 4 16:44:37 goldex01 kernel: NETDEV WATCHDOG: ippp0: transmit
timed out
Oct 4 16:44:37 goldex01 kernel: isdn_tx_timeout dev ippp0 dialstate 0
Oct 4 16:44:37 goldex01 kernel: OPEN: 10.0.0.1 -> 10.0.0.2 ICMP
Oct 4 16:44:37 goldex01 kernel: ippp0: dialing 1 0860007249...
Oct 4 16:44:45 goldex01 kernel: isdn_net: local hangup ippp0
Oct 4 16:44:45 goldex01 kernel: ippp0: Chargesum is 0

.... it just repeats until I stop pinging ...

I hope someone can help me out with this.
More than willing to send over any config file you may deem necessary.
Sorry for the long posting.

Simply put, I'm beat ... any ideas are greatly appreciated.
If you like, please post-reply and cc me as well

TIA,

Cheers, Sabio

On Tue, 05 Oct 2004 12:32:35 -0700, Sabio62 wrote:

> G'day,
>
> Trying to setup a Micronet ISDN PCI card to dial into
> South Africa's Telkom ISP is proving to be rather painful.
> It's supposed to be a multilink isdn ...
>
<snip>

http://www.one.btinternet.co.uk/isdnfaq/isdnfaq.htm
lots of Hisax isdn options here...for UK though...

In article <(E-Mail Removed) >, Sabio62 wrote:
> Oct 4 15:45:01 goldex01 kernel: ippp0: dialing 1 0860007249...
> Oct 4 15:45:10 goldex01 kernel: isdn_net: local hangup ippp0

I ditched ISDN a year ago, but I remember fighting with local hangup
problems with RedHat 7.1 to 8.0 systems. Somehow isdnctrl didn't set up
huptimeout automatically from the config files, so I had to use a my
own scripts with 'isdnctrl huptimeout ippp0 0 && isdnctrl
huptimeout ippp1 0', and then the actual network interface had to be
named ippp0 not isdn0.

Also, you might want to try out setting the ISDN parameters with
isdnctrl manually for one channel and dial with it too. That way you
might find the faulty parameter(s). This nice page shows howto do that
with finnish/european ISDN protocols (in finnish, but the commands are
universal):
http://ping-viini.org/jinux/ohjeet/isdn-ohje.html

Good luck,
-Mikko