From owner-freebsd-isdn@FreeBSD.ORG Sun Apr 6 08:04:53 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id C6E0037B401
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 08:04:53 -0700 (PDT)
Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100])
by mx1.FreeBSD.org (Postfix) with SMTP id ABD9C43F75
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 08:04:52 -0700 (PDT)
(envelope-from sm4tnp8@gmx.net)
Received: (qmail 24473 invoked by uid 0); 6 Apr 2003 15:04:51 -0000
Date: Sun, 6 Apr 2003 17:04:51 +0200 (MEST)
From: Markus Dolze <sm4tnp8@gmx.net>
To: freebsd-isdn@freebsd.org
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-Authenticated-Sender: #0000931807@gmx.net
X-Authenticated-IP: [145.254.136.178]
Message-ID: <9383.1049641491@www53.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Bugs in isdnmonitor?
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 15:04:54 -0000
Hello!
I am writing a Java-based program to monitor and control isdnd. Some work
has already be done, monitoring the connection (listing connections and bytes
in/out, event notification etc). I ran in several problems which are also
reproducable using the native isdnmonitor.
1.
In the message I4B_MON_ICTRL_CODE is the number of channels of the
controller encoded. This is always 0 (zero). I have seen this using ethereal, too.
2.
After hang up of a connection the client receives no I4B_MON_DISCONNECT_CODE
message. That means the connection data is not removed in the monitoring
client.
3.
After dialing out after a hang up, an already connected client receives no
I4B_MON_CONNECT_CODE message. That means the client get no info about the new
connection. This does not happen if the monitoring client conncts after a
establishing a dial out connection.
4.
When trying to implement the "dump rights" message i discovered the
following in isdnmonitor/monitor.h:
I4B_MON_DRINI_CODE = 2
I4B_MON_IDEV_CODE = 2
Two messages with the same event code?
Background information:
FreeBSD arwen.xxx 4.8-RELEASE FreeBSD 4.8-RELEASE #23: Thu Apr 3 00:54:17
CEST 2003 root@arwen.xxx:/usr/obj/usr/src/sys/ARWEN i386
Now my questions:
1. To whom can I talk directly to get more information about that? Who
maintains the i4b part?
2. Can someone confirm this?
3. Should I file an offical bug? Can I do this at all?
Thank you
From owner-freebsd-isdn@FreeBSD.ORG Sun Apr 6 08:32:04 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 4870D37B401
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 08:32:04 -0700 (PDT)
Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com
[194.25.134.18])
by mx1.FreeBSD.org (Postfix) with ESMTP id D897B43F3F
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 08:32:02 -0700 (PDT)
(envelope-from hm@kts.org)
Received: from fwd05.sul.t-online.de
by mailout04.sul.t-online.com with smtp
id 192C7l-0004Ru-03; Sun, 06 Apr 2003 17:32:01 +0200
Received: from ernie.kts.org (520021727764-0001@[217.227.32.86]) by
fmrl05.sul.t-online.com
with esmtp id 192C7S-1REe12C; Sun, 6 Apr 2003 17:31:42 +0200
Received: from bert.int.kts.org (bert.int.kts.org [172.31.42.2])
by ernie.kts.org (Postfix) with ESMTP
id 34A0F4CB02; Sun, 6 Apr 2003 17:31:41 +0200 (CEST)
Received: by bert.int.kts.org (Postfix, from userid 100)
id 23D3A54CB; Sun, 6 Apr 2003 17:31:41 +0200 (CEST)
In-Reply-To: <9383.1049641491@www53.gmx.net>
To: Markus Dolze <sm4tnp8@gmx.net>
Date: Sun, 6 Apr 2003 17:31:41 +0200 (CEST)
Organization: Kitchen Table Systems
X-Mailer: ELM [version 2.4ME+ PL99b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20030406153141.23D3A54CB@bert.int.kts.org>
From: hm@kts.org (Hellmuth Michaelis)
X-Sender: 520021727764-0001@t-dialin.net
cc: freebsd-isdn@freebsd.org
Subject: Re: Bugs in isdnmonitor?
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: hellmuth.michaelis@t-online.de
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 15:32:04 -0000
Markus Dolze wrote:
> Now my questions:
> 1. To whom can I talk directly to get more information about that? Who
> maintains the i4b part?
> 2. Can someone confirm this?
> 3. Should I file an offical bug? Can I do this at all?
I haven't looked at isdnmonitor for quite some time now and i'm not
astonished if someone digs out 20-30 bugs from isdnmonitor, the
part in isdnd which handles monitoring and the protocol which is
used to communicate between both.
As far as i remember, the protocol itself is suboptimal ...
To answer your questions:
1) you are possibly the one who has the most informations on the
subject; i try to maintain i4b although i have not done anything
for quite some time now - i'd like to do more but i don't find
time and patience anymore in these days.
2) see 1).
3) use send-pr to file a bug. Including a good description and a
tested patch raises the chance to get the bug fixed. If you add
_any_ new features or functionality, make diffs/patches on -current
(5.x currently) since this is the platform for _new_ stuff to add
(_new_ stuff gets added _only_ to -current and if it works it will
perhaps be merged int 4.x - since 5.0 has just been released, its
just a matter of time when 4.x will disappear [from the forhead of
the developers]; already it makes not much sense to me to develop
on 4.x anymore ..).
hellmuth
--
Hellmuth Michaelis Hamburg, Europe hm\at\kts.org www.kts.org
a duck is like a bicycle because they both have two wheels except the duck (tl)
From owner-freebsd-isdn@FreeBSD.ORG Sun Apr 6 13:48:56 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 5D72D37B401
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 13:48:56 -0700 (PDT)
Received: from mx0.gmx.net (mx0.gmx.net [213.165.64.100])
by mx1.FreeBSD.org (Postfix) with SMTP id 510D043F85
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 13:48:55 -0700 (PDT)
(envelope-from sm4tnp8@gmx.net)
Received: (qmail 9487 invoked by uid 0); 6 Apr 2003 20:48:54 -0000
Date: Sun, 6 Apr 2003 22:48:53 +0200 (MEST)
From: Markus Dolze <sm4tnp8@gmx.net>
To: freebsd-isdn@freebsd.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="========GMXBoundary60431049662133"
X-Priority: 3 (Normal)
X-Authenticated-Sender: #0000931807@gmx.net
X-Authenticated-IP: [145.254.131.117]
Message-ID: <6043.1049662133@www26.gmx.net>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Subject: Re: bugs in isdnmonitor?
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 20:48:56 -0000
This is a MIME encapsulated multipart message -
please use a MIME-compliant e-mail program to open it.
Dies ist eine mehrteilige Nachricht im MIME-Format -
bitte verwenden Sie zum Lesen ein MIME-konformes Mailprogramm.
--========GMXBoundary60431049662133
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Well, I'll see if I can manage that.
But for now, i found out these thing:
1) I must set ALL right codes in /etc/isdnd.rc i'm interrested in (the
man-page isn't clear about that). So to monitor and controll from remote I have to
set:
monitor = "192.168.1.0/24"
monitor-access = fullcmd
monitor-access = logevents
monitor-access = callout
monitor-access = callin
monitor-access = channelstate
2) There is a error in /usr/src/usr.sbin/i4b/isdnmonitor/monitor.h
original defined is
#define I4B_MON_ICTRL_SIZE
I4B_MON_EVNT_HDR+I4B_MAX_MON_STRING+8
but isdnd writes 10 Bytes after the controller string, so with
#define I4B_MON_ICTRL_SIZE
I4B_MON_EVNT_HDR+I4B_MAX_MON_STRING+10
everything works.
BTW: the number of channels per controller seems to be hard-coded to 2 (two)
channels per controller in /usr/src/usr.sbin/i4b/isdnd/monitor.c!
3) There is another error in monitor.h
#define I4B_MON_DRINI_CODE 2 /* event code */
and
#define I4B_MON_IDEV_CODE 2
have the same message code, changing results in correct message generating
For now I can do further work on my project. I'm not familiar with coding in
C. I attached my changes to monitor.h as patch. Please give me your
feedback.
Thank you
Markus Dolze
Hellmuth Michaelis wrote:
> To answer your questions:
>
>
> 3) use send-pr to file a bug. Including a good description and a
> tested patch raises the chance to get the bug fixed. If you add
> _any_ new features or functionality, make diffs/patches on -current
> (5.x currently) since this is the platform for _new_ stuff to add
> (_new_ stuff gets added _only_ to -current and if it works it will
> perhaps be merged int 4.x - since 5.0 has just been released, its
> just a matter of time when 4.x will disappear [from the forhead of
> the developers]; already it makes not much sense to me to develop
> on 4.x anymore ..).
>
> hellmuth
--========GMXBoundary60431049662133
Content-Type: application/octet-stream; name="patch"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="patch"
LS0tIG1vbml0b3IuaAlXZWQgQXVnICAxIDE5OjQ1OjA2IDIwMDEKKysrIG1vbml0b3IyLmgJU3Vu
IEFwciAgNiAyMjo0NDowOSAyMDAzCkBAIC0xMTksMTIgKzExOSwxMiBAQAogI2RlZmluZQlJNEJf
TU9OX0lEQVRBX0NMQUNDRVNTCQlJNEJfTU9OX0VWTlRfSERSKzgJLyogNCBieXRlOiBjbGllbnQg
cmlnaHRzICovCiAKIC8qIGZvbGxvd2VkIGJ5IHRoaXMgZm9yIGV2ZXJ5IGNvbnRyb2xsZXIgKi8K
LSNkZWZpbmUJSTRCX01PTl9JQ1RSTF9TSVpFCQlJNEJfTU9OX0VWTlRfSERSK0k0Ql9NQVhfTU9O
X1NUUklORys4CisjZGVmaW5lCUk0Ql9NT05fSUNUUkxfU0laRQkJSTRCX01PTl9FVk5UX0hEUitJ
NEJfTUFYX01PTl9TVFJJTkcrMTAKICNkZWZpbmUJSTRCX01PTl9JQ1RSTF9DT0RFCQkxCQkJCQkv
KiBldmVudCBjb2RlICovCiAjZGVmaW5lCUk0Ql9NT05fSUNUUkxfTkFNRQkJSTRCX01PTl9FVk5U
X0hEUiswCQkJLyogc3RyaW5nOiBuYW1lIG9mIGNvbnRyb2xsZXIgKi8KICNkZWZpbmUJSTRCX01P
Tl9JQ1RSTF9CVVNJRAkJSTRCX01PTl9FVk5UX0hEUitJNEJfTUFYX01PTl9TVFJJTkcrMAkvKiAy
IGJ5dGU6IGlzZG4gYnVzIGlkIChyZXNlcnZlcmVkKSAqLwogI2RlZmluZQlJNEJfTU9OX0lDVFJM
X0ZMQUdTCQlJNEJfTU9OX0VWTlRfSERSK0k0Ql9NQVhfTU9OX1NUUklORysyCS8qIDQgYnl0ZTog
Y29udHJvbGxlciBmbGFncyAobm90IHlldCBkZWZpbmVkKSAqLwotI2RlZmluZQlJNEJfTU9OX0lD
VFJMX05DSEFOCQlJNEJfTU9OX0VWTlRfSERSK0k0Ql9NQVhfTU9OX1NUUklORys2CS8qIDIgYnl0
ZTogbnVtYmVyIG9mIGIgY2hhbm5lbHMgb24gdGhpcyBjb250cm9sbGVyICovCisjZGVmaW5lCUk0
Ql9NT05fSUNUUkxfTkNIQU4JCUk0Ql9NT05fRVZOVF9IRFIrSTRCX01BWF9NT05fU1RSSU5HKzYJ
LyogNCBieXRlOiBudW1iZXIgb2YgYiBjaGFubmVscyBvbiB0aGlzIGNvbnRyb2xsZXIgKi8KIAog
LyogZm9sbG93ZWQgYnkgdGhpcyBmb3IgZXZlcnkgZW50cnkgKi8KICNkZWZpbmUJSTRCX01PTl9J
REVWX1NJWkUJCUk0Ql9NT05fRVZOVF9IRFIrSTRCX01BWF9NT05fU1RSSU5HKzIKQEAgLTE1MCw3
ICsxNTAsNyBAQAogICogaW4gcmVzcG9uc2UgdG8gYSBJNEJfTU9OX0RVTVBSSUdIVFNfQ09ERSBj
b21tYW5kLCB0aGUgZGFlbW9uIHNlbmRzCiAgKiB0aGlzIGV2ZW50OgogICovCi0jZGVmaW5lCUk0
Ql9NT05fRFJJTklfQ09ERQkJMgkvKiBldmVudCBjb2RlICovCisjZGVmaW5lCUk0Ql9NT05fRFJJ
TklfQ09ERQkJMTQJLyogZXZlbnQgY29kZSAqLwogI2RlZmluZQlJNEJfTU9OX0RSSU5JX1NJWkUJ
CUk0Ql9NT05fRVZOVF9IRFIrMgkvKiBzaXplIG9mIHBhY2tldCAqLwogI2RlZmluZQlJNEJfTU9O
X0RSSU5JX0NPVU5UCQlJNEJfTU9OX0VWTlRfSERSKzAJLyogMiBieXRlOiBudW1iZXIgb2YgcmVj
b3JkcyAqLwogCg==
--========GMXBoundary60431049662133--
From owner-freebsd-isdn@FreeBSD.ORG Sun Apr 6 13:51:55 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 4374837B401
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 13:51:55 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
[212.227.126.186])
by mx1.FreeBSD.org (Postfix) with ESMTP id 3CCFA43F75
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 13:51:54 -0700 (PDT)
(envelope-from martin@duskware.de)
Received: from [212.227.126.161] (helo=mrelayng.kundenserver.de)
by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
id 192H7J-0003jj-00
for freebsd-isdn@freebsd.org; Sun, 06 Apr 2003 22:51:53 +0200
Received: from [217.225.28.34] (helo=drowsy.duskware.de)
by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
id 192H7I-0007pa-00
for freebsd-isdn@freebsd.org; Sun, 06 Apr 2003 22:51:52 +0200
Received: by drowsy.duskware.de (Postfix, from userid 205)
id 082A933A83; Sun, 6 Apr 2003 22:51:49 +0200 (CEST)
Date: Sun, 6 Apr 2003 22:51:49 +0200
From: Martin Husemann <martin@duskware.de>
To: Markus Dolze <sm4tnp8@gmx.net>
Message-ID: <20030406205149.GA7714@drowsy.duskware.de>
References: <9383.1049641491@www53.gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9383.1049641491@www53.gmx.net>
User-Agent: Mutt/1.4.1i
cc: freebsd-isdn@freebsd.org
Subject: Re: Bugs in isdnmonitor?
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 20:51:55 -0000
On Sun, Apr 06, 2003 at 05:04:51PM +0200, Markus Dolze wrote:
> 4.
> When trying to implement the "dump rights" message i discovered the
> following in isdnmonitor/monitor.h:
> I4B_MON_DRINI_CODE = 2
> I4B_MON_IDEV_CODE = 2
> Two messages with the same event code?
While this is surely suboptimal, the I4B_MON_IDEV_CODE is only used in the
initial isdnd <-> client handshake, with both isdnd and monitor client in
a special state. That's why it did not bite in the in-tree implementation.
If you do "fgrep _CODE monitor.h" you will notice three ocurances of such
code overlaps in statefull protocol sections.
I don't realy care to much about changes in this area - if you think it should
be made unique, that's fine with me.
Martin
P.S.: amazing how much interest drops once your environment changes - when I
first did the monitor stuff I needed it for work - now neither work nor me
privately even use ISDN data conections any more. I have to struggle hard to
keep a working testbed connection for ocasional tests configured.
From owner-freebsd-isdn@FreeBSD.ORG Sun Apr 6 14:07:36 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 4415037B401
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 14:07:36 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de
[212.227.126.185])
by mx1.FreeBSD.org (Postfix) with ESMTP id 8196343F93
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 14:07:35 -0700 (PDT)
(envelope-from martin@duskware.de)
Received: from [212.227.126.155] (helo=mrelayng.kundenserver.de)
by moutng.kundenserver.de with esmtp (Exim 3.35 #1)
id 192HMU-0007LK-00
for freebsd-isdn@freebsd.org; Sun, 06 Apr 2003 23:07:34 +0200
Received: from [217.225.28.34] (helo=drowsy.duskware.de)
by mrelayng.kundenserver.de with asmtp (Exim 3.35 #1)
id 192HMT-0004y8-00
for freebsd-isdn@freebsd.org; Sun, 06 Apr 2003 23:07:34 +0200
Received: by drowsy.duskware.de (Postfix, from userid 205)
id B62E433A83; Sun, 6 Apr 2003 23:07:32 +0200 (CEST)
Date: Sun, 6 Apr 2003 23:07:32 +0200
From: Martin Husemann <martin@duskware.de>
To: Markus Dolze <sm4tnp8@gmx.net>
Message-ID: <20030406210732.GB7714@drowsy.duskware.de>
References: <6043.1049662133@www26.gmx.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <6043.1049662133@www26.gmx.net>
User-Agent: Mutt/1.4.1i
cc: freebsd-isdn@freebsd.org
Subject: Re: bugs in isdnmonitor?
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 21:07:36 -0000
On Sun, Apr 06, 2003 at 10:48:53PM +0200, Markus Dolze wrote:
> I4B_MON_EVNT_HDR+I4B_MAX_MON_STRING+8
> but isdnd writes 10 Bytes after the controller string, so with
> #define I4B_MON_ICTRL_SIZE
> I4B_MON_EVNT_HDR+I4B_MAX_MON_STRING+10
> everything works.
I prefer to stick to the protocol defined in monitor.h and change the
monitor.c code to: I4B_PUT_2B(ictrl, I4B_MON_ICTRL_NCHAN, 2);
I just commited this change to the NetBSD version of the code.
> BTW: the number of channels per controller seems to be hard-coded to 2 (two)
> channels per controller in /usr/src/usr.sbin/i4b/isdnd/monitor.c!
True. When this code was written there was no support for PRI adapters.
When they got added later, it was not adjusted ;-)
> 3) There is another error in monitor.h
> #define I4B_MON_DRINI_CODE 2 /* event code */
> and
> #define I4B_MON_IDEV_CODE 2
> have the same message code, changing results in correct message generating
I addressed this already in a reply to your last message - it works ok the
way it is, if the client follows closely the comments in monitor.h.
Martin
From owner-freebsd-isdn@FreeBSD.ORG Sun Apr 6 14:14:13 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id BD22637B401
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 14:14:13 -0700 (PDT)
Received: from mx12.arcor-online.net (mx12.arcor-online.net [151.189.8.88])
by mx1.FreeBSD.org (Postfix) with ESMTP id 3970043FA3
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 14:14:13 -0700 (PDT)
(envelope-from sm4tnp8@gmx.net)
Received: from gmx.net (dialin-145-254-131-117.arcor-ip.net [145.254.131.117])
by mx12.arcor-online.net (Postfix) with ESMTP id 9CE741278EE
for <freebsd-isdn@freebsd.org>; Sun, 6 Apr 2003 23:14:11 +0200 (CEST)
Message-ID: <3E9098A9.4080108@gmx.net>
Date: Sun, 06 Apr 2003 23:14:17 +0200
From: Markus Dolze <sm4tnp8@gmx.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.3) Gecko/20030312
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-isdn@freebsd.org
References: <9383.1049641491@www53.gmx.net>
In-Reply-To: <9383.1049641491@www53.gmx.net>
X-Enigmail-Version: 0.73.1.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: Bugs in isdnmonitor?
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2003 21:14:14 -0000
Thank you all for your comments on that. I will put some error handling
in my monitor and forget about the rest for now.
Bye
Markus
From owner-freebsd-isdn@FreeBSD.ORG Wed Apr 9 01:14:17 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 8421C37B401
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 01:14:17 -0700 (PDT)
Received: from peedub.jennejohn.org (p62.246.114.165.tisdip.tiscali.de
[62.246.114.165])
by mx1.FreeBSD.org (Postfix) with ESMTP id 259BA43F85
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 01:14:16 -0700 (PDT)
(envelope-from garyj@jennejohn.org)
Received: from peedub.jennejohn.org (localhost [127.0.0.1])
by peedub.jennejohn.org (8.12.9/8.11.6) with ESMTP id h398EDAF002263;
Wed, 9 Apr 2003 10:14:13 +0200 (CEST)
(envelope-from garyj@peedub.jennejohn.org)
Message-Id: <200304090814.h398EDAF002263@peedub.jennejohn.org>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3
To: Marcel Dijk <nascar24@home.nl>
In-reply-to: Your message of "Wed, 09 Apr 2003 00:15:45 +0200."
<3E934A11.3050305@home.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 09 Apr 2003 10:14:13 +0200
From: Gary Jennejohn <garyj@jennejohn.org>
cc: freebsd-isdn@freebsd.org
Subject: Re: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Gary Jennejohn <garyj@jennejohn.org>
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2003 08:14:17 -0000
[Note: I'm keeping all of this since it's new to ISDN]
Marcel Dijk writes:
> Hello all,
>
> I am trying to get ISDN4BSD to work, thusfar, no luck. I live in Europe.
> I use my ISDN adapter (Teles 16.3 ISA non-PnP) to dial in to my ISP.
> But if I start ppp and dial I get all kind of error from isdnd wich I
> cannot understand.
>
> This is my isdnd.rc:
>
> # SYSTEM section: isdnd global configuration parameters
> system
> # accounting
> acctall = on # generate info for everything
> acctfile = /var/log/isdnd.acct # name & location of accounting file
> useacctfile = yes # generate accouting info to file
> isdntime = on
> monitor-allowed = no # global switch: monitor on/off
> # User-ppp example
> entry
> name = userppp0
> usrdevicename = rbch
> usrdeviceunit = 0
> isdncontroller = 0
> isdnchannel = 1
> local-phone-incoming = 0505267744
> remote-phone-incoming = *
> local-phone-dialout = 0505267744 # This *MUST* be your local number
> remote-phone-dialout = 1234567 # ppp(8) will override this
> remdial-handling = first
> dialin-reaction = ignore
> dialout-type = normal
> b1protocol = hdlc
> idletime-incoming = 900 # Should be larger than ppp's timeout
> idletime-outgoing = 900 # Should be larger than ppp's timeout
> unitlength = 0
> unitlengthsrc = conf
> dialretries = 1
> dialrandincr = on
> recoverytime = 1 # Should be smaller than ppp's redial
> usedown = off
> downtries = 2
> downtime = 30
>
> entry
> name = userppp1
> usrdevicename = rbch
> usrdeviceunit = 1
> isdncontroller = 0
> isdnchannel = 2
> local-phone-incoming = 1234567
> remote-phone-incoming = *
> local-phone-dialout = 0505267744 # This *MUST* be your local number
> remote-phone-dialout = 1234567 # ppp(8) will override this
> remdial-handling = first
> dialin-reaction = accept
> dialout-type = normal
> b1protocol = hdlc
> idletime-incoming = 900 # Should be larger than ppp's timeout
> idletime-outgoing = 900 # Should be larger than ppp's timeout
> unitlength = 0
> unitlengthsrc = conf
> dialretries = 1
> dialrandincr = on
> recoverytime = 1 # Should be smaller than ppp's redial
> usedown = off
> downtries = 2
> downtime = 30
>
> ----
>
> I filled it in according to the example in /usr/share/examples/isdn.
>
> And here is my ppp.conf
>
> default:
> set phone ISP_NUMBER # Replace this with your ISPs phone number
> set authname MY_USERNAME # Replace these with your login name & password.
> set authkey MY_PASS # This profile assumes you're using PAP or CHAP.
> # set enddisc mac # Assuming you have a LAN (dont have a LAN on the
> ISDN PC)
> enable lqr
> set reconnect 3 5
> set redial 3 10
> set lqrperiod 45
> disable pred1 deflate mppe
> deny pred1 deflate mppe
> set timeout 60 300 # The minimum charge period is 5 minutes, so don't
> # hangup before then
> # We have no chat scripts in the ISDN world (yet)
> set dial
> set login
> set logout
> set hangup
>
> set device /dev/i4brbch0 /dev/i4brbch1 # Raw B-channel devices
> set speed sync # ISDN is synchronous
>
> enable dns # Ask the peer what to put in resolv.conf
>
> # Take a wild guess at an IP number and let the other side decide
> set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0
> add! default hisaddr
>
> # set mrru 1500 # Multilink mode please
> set mru 1504 # Room for the MP header
>
> # clone 1,2 # Two new links
> # link deflink rm # And get rid of the original one
>
> # link * set mode auto # Automatically manage the second link
> # set autoload 10 80 30 # Down @10% usage, up at 80%, 30s sample
>
> set server /var/run/ppp/ppp-isdn "" 0177 # The diagnostic port (-rw-------)
>
> ---
>
> Also filled in according to the example.
>
> I also have an alternative ppp.conf wich gives the same errors:
>
>
> default:
> set device /dev/i4brbch0 /dev/i4brbch1
> set speed sync
> set dial
> set logout
> set hangup
>
> hetnet:
> set phone ISP_NUMBER # Replace this with your ISPs phone number
> set login
> set authname THE_NAME # Replace these with your login name & password.
> set authkey THE_PASS # This profile assumes you're using PAP or CHAP.
> ifaddr 0.0.0.0
> add default HISADDR
> enable dns
>
> # set enddisc mac # Assuming you have a LAN
> # enable lqr
> # set reconnect 3 5
> # set redial 3 10
> # set lqrperiod 45
> # disable pred1 deflate mppe
> # deny pred1 deflate mppe
>
> # set timeout 60 300 # The minimum charge period is 5 minutes, so don't
> # hangup before then
>
> # enable dns # Ask the peer what to put in resolv.conf
>
> # Take a wild guess at an IP number and let the other side decide
> #set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0
> #add! default hisaddr
>
> # set mrru 1500 # Multilink mode please
> #set mru 1504 # Room for the MP header
>
> # clone 1,2 # Two new links
> # link deflink rm # And get rid of the original one
>
> # link * set mode auto # Automatically manage the second link
> # set autoload 10 80 30 # Down @10% usage, up at 80%, 30s sample
>
> # set server /var/run/ppp/ppp-isdn "" 0177 # The diagnostic port
> (-rw-------)
>
> ----------
>
> I can't give you the errors ISDND gives, I simply forgot them. It were
> unintelligable errors to me.
>
> The errors came from isdnd, not from ppp.
>
> Sorry for the mega e-mail but I thought I could best be as verbose as
> possible.
>
> Hope someone can help.
>
This should have gone to freebsd-isdn@, so I've redirected it.
The error messages from isdnd may not mean anything to you, but without them
there's no way to figure what's happening.
Please post the errors from isdnd.
---
Gary Jennejohn / garyj@jennejohn.org gj@freebsd.org gj@denx.de
From owner-freebsd-isdn@FreeBSD.ORG Wed Apr 9 05:05:16 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id AC56E37B401
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 05:05:16 -0700 (PDT)
Received: from mail5-sh.home.nl (mail5.home.nl [213.51.128.16])
by mx1.FreeBSD.org (Postfix) with ESMTP id 45E2D43F93
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 05:05:15 -0700 (PDT)
(envelope-from nascar24@home.nl)
Received: from home.nl ([217.120.167.10]) by mail5-sh.home.nl
(InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP
id <20030409120513.DTDA15277.mail5-sh.home.nl@home.nl>;
Wed, 9 Apr 2003 14:05:13 +0200
Message-ID: <3E940C7A.8010700@home.nl>
Date: Wed, 09 Apr 2003 14:05:14 +0200
From: Marcel Dijk <nascar24@home.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US;
rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Gary Jennejohn <garyj@jennejohn.org>
References: <200304090814.h398EDAF002263@peedub.jennejohn.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: freebsd-isdn@freebsd.org
Subject: Re: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2003 12:05:17 -0000
>
>
>[Note: I'm keeping all of this since it's new to ISDN]
>
>Marcel Dijk writes:
>
>
>>Hello all,
>>
>>I am trying to get ISDN4BSD to work, thusfar, no luck. I live in Europe.
>>I use my ISDN adapter (Teles 16.3 ISA non-PnP) to dial in to my ISP.
>>But if I start ppp and dial I get all kind of error from isdnd wich I
>>cannot understand.
>>
>>This is my isdnd.rc:
>>
>># SYSTEM section: isdnd global configuration parameters
>>system
>># accounting
>>acctall = on # generate info for everything
>>acctfile = /var/log/isdnd.acct # name & location of accounting file
>>useacctfile = yes # generate accouting info to file
>>isdntime = on
>>monitor-allowed = no # global switch: monitor on/off
>># User-ppp example
>>entry
>>name = userppp0
>>usrdevicename = rbch
>>usrdeviceunit = 0
>>isdncontroller = 0
>>isdnchannel = 1
>>local-phone-incoming = 0505267744
>>remote-phone-incoming = *
>>local-phone-dialout = 0505267744 # This *MUST* be your local number
>>remote-phone-dialout = 1234567 # ppp(8) will override this
>>remdial-handling = first
>>dialin-reaction = ignore
>>dialout-type = normal
>>b1protocol = hdlc
>>idletime-incoming = 900 # Should be larger than ppp's timeout
>>idletime-outgoing = 900 # Should be larger than ppp's timeout
>>unitlength = 0
>>unitlengthsrc = conf
>>dialretries = 1
>>dialrandincr = on
>>recoverytime = 1 # Should be smaller than ppp's redial
>>usedown = off
>>downtries = 2
>>downtime = 30
>>
>>entry
>>name = userppp1
>>usrdevicename = rbch
>>usrdeviceunit = 1
>>isdncontroller = 0
>>isdnchannel = 2
>>local-phone-incoming = 1234567
>>remote-phone-incoming = *
>>local-phone-dialout = 0505267744 # This *MUST* be your local number
>>remote-phone-dialout = 1234567 # ppp(8) will override this
>>remdial-handling = first
>>dialin-reaction = accept
>>dialout-type = normal
>>b1protocol = hdlc
>>idletime-incoming = 900 # Should be larger than ppp's timeout
>>idletime-outgoing = 900 # Should be larger than ppp's timeout
>>unitlength = 0
>>unitlengthsrc = conf
>>dialretries = 1
>>dialrandincr = on
>>recoverytime = 1 # Should be smaller than ppp's redial
>>usedown = off
>>downtries = 2
>>downtime = 30
>>
>>----
>>
>>I filled it in according to the example in /usr/share/examples/isdn.
>>
>>And here is my ppp.conf
>>
>>default:
>> set phone ISP_NUMBER # Replace this with your ISPs phone number
>> set authname MY_USERNAME # Replace these with your login name & password.
>> set authkey MY_PASS # This profile assumes you're using PAP or CHAP.
>># set enddisc mac # Assuming you have a LAN (dont have a LAN on the
>>ISDN PC)
>> enable lqr
>> set reconnect 3 5
>> set redial 3 10
>> set lqrperiod 45
>> disable pred1 deflate mppe
>> deny pred1 deflate mppe
>> set timeout 60 300 # The minimum charge period is 5 minutes, so don't
>> # hangup before then
>> # We have no chat scripts in the ISDN world (yet)
>> set dial
>> set login
>> set logout
>> set hangup
>>
>> set device /dev/i4brbch0 /dev/i4brbch1 # Raw B-channel devices
>> set speed sync # ISDN is synchronous
>>
>> enable dns # Ask the peer what to put in resolv.conf
>>
>> # Take a wild guess at an IP number and let the other side decide
>> set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0
>> add! default hisaddr
>>
>># set mrru 1500 # Multilink mode please
>> set mru 1504 # Room for the MP header
>>
>># clone 1,2 # Two new links
>># link deflink rm # And get rid of the original one
>>
>># link * set mode auto # Automatically manage the second link
>># set autoload 10 80 30 # Down @10% usage, up at 80%, 30s sample
>>
>> set server /var/run/ppp/ppp-isdn "" 0177 # The diagnostic port (-rw-------)
>>
>>---
>>
>>Also filled in according to the example.
>>
>>I also have an alternative ppp.conf wich gives the same errors:
>>
>>
>>default:
>> set device /dev/i4brbch0 /dev/i4brbch1
>> set speed sync
>> set dial
>> set logout
>> set hangup
>>
>>hetnet:
>> set phone ISP_NUMBER # Replace this with your ISPs phone number
>> set login
>> set authname THE_NAME # Replace these with your login name & password.
>> set authkey THE_PASS # This profile assumes you're using PAP or CHAP.
>> ifaddr 0.0.0.0
>> add default HISADDR
>> enable dns
>>
>># set enddisc mac # Assuming you have a LAN
>># enable lqr
>># set reconnect 3 5
>># set redial 3 10
>># set lqrperiod 45
>># disable pred1 deflate mppe
>># deny pred1 deflate mppe
>>
>># set timeout 60 300 # The minimum charge period is 5 minutes, so don't
>> # hangup before then
>>
>># enable dns # Ask the peer what to put in resolv.conf
>>
>> # Take a wild guess at an IP number and let the other side decide
>> #set ifaddr 172.16.0.1/0 212.0.0.0/0 0 0
>> #add! default hisaddr
>>
>># set mrru 1500 # Multilink mode please
>> #set mru 1504 # Room for the MP header
>>
>># clone 1,2 # Two new links
>># link deflink rm # And get rid of the original one
>>
>># link * set mode auto # Automatically manage the second link
>># set autoload 10 80 30 # Down @10% usage, up at 80%, 30s sample
>>
>># set server /var/run/ppp/ppp-isdn "" 0177 # The diagnostic port
>>(-rw-------)
>>
>>----------
>>
>>I can't give you the errors ISDND gives, I simply forgot them. It were
>>unintelligable errors to me.
>>
>>The errors came from isdnd, not from ppp.
>>
>>Sorry for the mega e-mail but I thought I could best be as verbose as
>>possible.
>>
>>Hope someone can help.
>>
>>
>>
>
>This should have gone to freebsd-isdn@, so I've redirected it.
>
>The error messages from isdnd may not mean anything to you, but without them
>there's no way to figure what's happening.
>
>Please post the errors from isdnd.
>
These are the errors I get after running ppp and trying to dial:
Apr 9 12:52:03 truus ppp[122]: Warning: ifaddr: Invalid command
Apr 9 12:52:03 truus ppp[122]: Warning: ifaddr: Failed 1
Apr 9 12:52:10 truus /kernel: i4b: unit 0, assigned TEI = 84 = 0x54
Apr 9 12:52:10 truus /kernel: i4b-L3 F_UEM: FSM function F_UEM
executing, state = ST_U11 - Disc Req
Apr 9 12:52:14 truus /kernel: i4b-L3 T303_timeout: SETUP not answered,
cr = 61
Apr 9 12:52:14 truus /kernel: i4b-L3 next_l3state: FSM illegal state,
state = ST_U0 - Null, event = EV_T303EXP - T303 timeout!
Greets,
Marcel.
From owner-freebsd-isdn@FreeBSD.ORG Wed Apr 9 07:57:40 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 3D53037B401
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 07:57:40 -0700 (PDT)
Received: from mail.vwsoft.com (p213.54.184.150.tisdip.tiscali.de
[213.54.184.150])
by mx1.FreeBSD.org (Postfix) with ESMTP id 9FF8643F85
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 07:57:38 -0700 (PDT)
(envelope-from Volker@VWSoft.com)
Received: from cesar2k.VWSoft.com (unknown [192.168.16.24])
by bellona.sz.vwsoft.com (Postfix) with ESMTP
id 6F01D66B2; Wed, 9 Apr 2003 16:54:40 +0200 (CEST)
Message-Id: <5.1.0.14.2.20030409163340.027afdc8@internal.net>
X-Sender: volker@internal.net (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 09 Apr 2003 16:54:22 +0200
To: Marcel Dijk <nascar24@home.nl>
From: Volker <Volker@VWSoft.com>
In-Reply-To: <3E940C7A.8010700@home.nl>
References: <200304090814.h398EDAF002263@peedub.jennejohn.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
cc: freebsd-isdn@freebsd.org
Subject: Re: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2003 14:57:40 -0000
Hi Marcel!
At 09.04.2003 14:05, Marcel Dijk wrote:
[snip]
> >>local-phone-incoming = 0505267744
> >>remote-phone-incoming = *
> >>local-phone-dialout = 0505267744 # This *MUST* be your local number
> >>remote-phone-dialout = 1234567 # ppp(8) will override this
Your local phone number looks like it contains an area code (050...).
As far as I remember, you should remove the area code from your local
numbers (I might be wrong about that - if so, would please somebody correct
me? - but depending on your telco provider your PBX might reject the
outgoing call if you're using a wrong local number).
The calling party number (local number, outgoing call) has to contain only
the MSN without any area or country code by a definition of the ITU (again,
as far as I remember).
As far as I remember means I haven't used an ISDN device on a direct telco
connection for a while. I'm using all devices behind a PABX and the
addressing is different within the local network.
> >>Sorry for the mega e-mail but I thought I could best be as verbose as
> possible.
At least when quoting, would you please cut down the quote to a reasonable
amount?
>These are the errors I get after running ppp and trying to dial:
>
>Apr 9 12:52:03 truus ppp[122]: Warning: ifaddr: Invalid command
>Apr 9 12:52:03 truus ppp[122]: Warning: ifaddr: Failed 1
>Apr 9 12:52:10 truus /kernel: i4b: unit 0, assigned TEI = 84 = 0x54
>Apr 9 12:52:10 truus /kernel: i4b-L3 F_UEM: FSM function F_UEM executing,
>state = ST_U11 - Disc Req
>Apr 9 12:52:14 truus /kernel: i4b-L3 T303_timeout: SETUP not answered, cr
>= 61
>Apr 9 12:52:14 truus /kernel: i4b-L3 next_l3state: FSM illegal state,
>state = ST_U0 - Null, event = EV_T303EXP - T303 timeout!
Helmut or Gary should have a better understanding about these error
messages but I guess the really important thing is 'SETUP not answered'
(which AFAIK should mean the remote side didn't accept the call or there's
no device listening at the remote side or the call won't be established by
the PBX. I would guess there's any phone number wrong (see my note about
the area code).
HTH,
Volker
From owner-freebsd-isdn@FreeBSD.ORG Wed Apr 9 08:17:04 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 66D4037B401
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 08:17:04 -0700 (PDT)
Received: from fragma.wildcardinternet.co.uk (fragma.wildcardinternet.co.uk
[195.82.114.65])
by mx1.FreeBSD.org (Postfix) with ESMTP id 7A35F43F75
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 08:17:03 -0700 (PDT)
(envelope-from j.a.mcguire@i-benefit.co.uk)
Received: from pam80-1-0-32.man.dial.ntli.net ([80.1.0.32]
helo=i-benefit.co.uk)
by fragma.wildcardinternet.co.uk with esmtp (Exim 3.35 #1)
id 193HJr-000I4P-00
for freebsd-isdn@freebsd.org; Wed, 09 Apr 2003 16:16:59 +0100
Message-ID: <3E943964.1020702@i-benefit.co.uk>
Date: Wed, 09 Apr 2003 16:16:52 +0100
From: James McGuire <j.a.mcguire@i-benefit.co.uk>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: freebsd-isdn@freebsd.org
References: <200304090814.h398EDAF002263@peedub.jennejohn.org>
<5.1.0.14.2.20030409163340.027afdc8@internal.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2003 15:17:04 -0000
Funny that, I used to get a similar kind of thing with an asustek
winbond (iwic) card. I would get T303's nine times out of ten when I
dialed out -- on the odd occassion it would work though, and I had the
same phone number setup, with the area code too. Anyway I'd be surprised
if it is the area code doing it, because as soon as I switched to a
Fritz card (ifpi) it worked fine. I tended to blame it on the iwic
driver because the said card worked fine under other operation systems.
James
Volker wrote:
> Hi Marcel!
>
> At 09.04.2003 14:05, Marcel Dijk wrote:
> [snip]
>
>> >>local-phone-incoming = 0505267744
>> >>remote-phone-incoming = *
>> >>local-phone-dialout = 0505267744 # This *MUST* be your local
>> number
>> >>remote-phone-dialout = 1234567 # ppp(8) will override this
>
>
> Your local phone number looks like it contains an area code (050...).
>
> As far as I remember, you should remove the area code from your local
> numbers (I might be wrong about that - if so, would please somebody
> correct me? - but depending on your telco provider your PBX might
> reject the outgoing call if you're using a wrong local number).
>
> The calling party number (local number, outgoing call) has to contain
> only the MSN without any area or country code by a definition of the
> ITU (again, as far as I remember).
>
> As far as I remember means I haven't used an ISDN device on a direct
> telco connection for a while. I'm using all devices behind a PABX and
> the addressing is different within the local network.
>
>> >>Sorry for the mega e-mail but I thought I could best be as verbose
>> as possible.
>
>
> At least when quoting, would you please cut down the quote to a
> reasonable amount?
>
>> These are the errors I get after running ppp and trying to dial:
>>
>> Apr 9 12:52:03 truus ppp[122]: Warning: ifaddr: Invalid command
>> Apr 9 12:52:03 truus ppp[122]: Warning: ifaddr: Failed 1
>> Apr 9 12:52:10 truus /kernel: i4b: unit 0, assigned TEI = 84 = 0x54
>> Apr 9 12:52:10 truus /kernel: i4b-L3 F_UEM: FSM function F_UEM
>> executing, state = ST_U11 - Disc Req
>> Apr 9 12:52:14 truus /kernel: i4b-L3 T303_timeout: SETUP not
>> answered, cr = 61
>> Apr 9 12:52:14 truus /kernel: i4b-L3 next_l3state: FSM illegal
>> state, state = ST_U0 - Null, event = EV_T303EXP - T303 timeout!
>
>
> Helmut or Gary should have a better understanding about these error
> messages but I guess the really important thing is 'SETUP not
> answered' (which AFAIK should mean the remote side didn't accept the
> call or there's no device listening at the remote side or the call
> won't be established by the PBX. I would guess there's any phone
> number wrong (see my note about the area code).
>
> HTH,
>
> Volker
>
>
> _______________________________________________
> freebsd-isdn@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isdn
> To unsubscribe, send any mail to "freebsd-isdn-unsubscribe@freebsd.org"
>
> .
>
From owner-freebsd-isdn@FreeBSD.ORG Wed Apr 9 08:27:33 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 89A0437B401
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 08:27:33 -0700 (PDT)
Received: from jhs.muc.de (pD9EB6F6D.dip.t-dialin.net [217.235.111.109])
by mx1.FreeBSD.org (Postfix) with ESMTP id B5AD743F75
for <freebsd-isdn@freebsd.org>; Wed, 9 Apr 2003 08:27:31 -0700 (PDT)
(envelope-from jhs@berklix.com)
Received: from flip.jhs.private (flip.jhs.private [192.168.91.24])
by jhs.muc.de (8.11.6/8.11.6) with ESMTP id h39FRQI64297;
Wed, 9 Apr 2003 17:27:29 +0200 (CEST)
(envelope-from jhs@berklix.com)
Received: from flip.jhs.private (localhost [127.0.0.1])
by flip.jhs.private (8.11.6/8.11.6) with ESMTP id h39FQt153578;
Wed, 9 Apr 2003 17:27:00 +0200 (CEST)
(envelope-from jhs@flip.jhs.private)
Message-Id: <200304091527.h39FQt153578@flip.jhs.private>
To: Volker <Volker@VWSoft.com>
In-Reply-To: Message from Volker <Volker@VWSoft.com>
<5.1.0.14.2.20030409163340.027afdc8@internal.net>
Date: Wed, 09 Apr 2003 17:26:55 +0200
From: "Julian H. Stacey" <jhs@berklix.com>
cc: freebsd-isdn@freebsd.org
Subject: Re: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2003 15:27:33 -0000
> Your local phone number looks like it contains an area code (050...).
>
> As far as I remember, you should remove the area code from your local
> numbers (I might be wrong about that - if so, would please somebody correct
> me? - but depending on your telco provider your PBX might reject the
> outgoing call if you're using a wrong local number).
FYI Here's what I was using in Munich via Deutsche Telekom, not using a PBX
to a Munich provider (089 = Munich, "..." to protect the innocent )
local-phone-incoming = 26023...
local-phone-dialout = 8926023...
remote-phone-incoming = 8932479...
remote-phone-dialout = 32479...
-
Julian Stacey Freelance Systems Engineer, Unix & Net Consultant, Munich.
Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren.
From owner-freebsd-isdn@FreeBSD.ORG Thu Apr 10 16:31:04 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 541B837B401
for <freebsd-isdn@freebsd.org>; Thu, 10 Apr 2003 16:31:04 -0700 (PDT)
Received: from mail6-sh.home.nl (mail6.home.nl [213.51.128.22])
by mx1.FreeBSD.org (Postfix) with ESMTP id CA6D843FBD
for <freebsd-isdn@freebsd.org>; Thu, 10 Apr 2003 16:31:02 -0700 (PDT)
(envelope-from nascar24@home.nl)
Received: from home.nl ([217.120.167.10]) by mail6-sh.home.nl
(InterMail vM.5.01.05.17 201-253-122-126-117-20021021) with ESMTP
id <20030410233101.QAMC13376.mail6-sh.home.nl@home.nl>;
Fri, 11 Apr 2003 01:31:01 +0200
Message-ID: <3E95FEB5.5080907@home.nl>
Date: Fri, 11 Apr 2003 01:31:01 +0200
From: Marcel Dijk <nascar24@home.nl>
User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US;
rv:1.0.2) Gecko/20030208 Netscape/7.02
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Julian H. Stacey" <jhs@berklix.com>
References: <200304091527.h39FQt153578@flip.jhs.private>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Volker <Volker@VWSoft.com>
cc: freebsd-isdn@freebsd.org
Subject: Re: ISDN (Europe. dial-up) POSTED to QUESTIONS and NET.
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 23:31:04 -0000
Thanks all, now it works. I had to freak around but hey, after all it is
not windows.
The transferrate is pretty high (7KB/sec) but if I use netscape or opera
it looks like browsing the web is slower compared to windows. Is that
possible? Eventhought the TX speed doesn't show this.
Thanks people you were real helpfull.
Marcel.
Julian H. Stacey wrote:
>>Your local phone number looks like it contains an area code (050...).
>>
>>As far as I remember, you should remove the area code from your local
>>numbers (I might be wrong about that - if so, would please somebody correct
>>me? - but depending on your telco provider your PBX might reject the
>>outgoing call if you're using a wrong local number).
>>
>>
>
>FYI Here's what I was using in Munich via Deutsche Telekom, not using a PBX
>to a Munich provider (089 = Munich, "..." to protect the innocent )
>
>local-phone-incoming = 26023...
>local-phone-dialout = 8926023...
>remote-phone-incoming = 8932479...
>remote-phone-dialout = 32479...
>
>-
>Julian Stacey Freelance Systems Engineer, Unix & Net Consultant, Munich.
> Ihr Rauchen => mein allergischer Kopfschmerz ! Schnupftabak probieren.
>
>
>
From owner-freebsd-isdn@FreeBSD.ORG Sat Apr 12 09:16:54 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 96C9E37B401
for <freebsd-isdn@freebsd.org>; Sat, 12 Apr 2003 09:16:54 -0700 (PDT)
Received: from ultra02.rbg.informatik.tu-darmstadt.de
(ultra02.rbg.informatik.tu-darmstadt.de [130.83.9.52])
by mx1.FreeBSD.org (Postfix) with ESMTP id D2DAC43FB1
for <freebsd-isdn@freebsd.org>; Sat, 12 Apr 2003 09:16:52 -0700 (PDT)
(envelope-from jgoebel@rbg.informatik.tu-darmstadt.de)
Received: from ultra15.rbg.informatik.tu-darmstadt.de
(ultra15.rbg.informatik.tu-darmstadt.de [130.83.129.2])
ESMTP id h3CGGph26123 for <freebsd-isdn@freebsd.org>;
Sat, 12 Apr 2003 18:16:51 +0200 (MEST)
Received: from localhost (jgoebel@localhost)ESMTP id h3CGGov06432
for <freebsd-isdn@freebsd.org>;
Sat, 12 Apr 2003 18:16:51 +0200 (MEST)
X-Authentication-Warning: ultra15.rbg.informatik.tu-darmstadt.de: jgoebel
owned process doing -bs
Date: Sat, 12 Apr 2003 18:16:50 +0200 (MEST)
From: Jan Goebel <jgoebel@rbg.informatik.tu-darmstadt.de>
To: freebsd-isdn@freebsd.org
In-Reply-To: <6043.1049662133@www26.gmx.net>
Message-ID: <Pine.SOL.4.51.0304121812580.4789@ultra15.rbg.informatik.tu-darmstadt.de>
References: <6043.1049662133@www26.gmx.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Best MTU for single-isdn
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2003 16:16:54 -0000
Hi,
I was just wondering, if the standard ethernet mtu 1500 is best for my isp
device, too. Or is it better to lower it a bit?
bye,
JAN
From owner-freebsd-isdn@FreeBSD.ORG Sat Apr 12 12:07:07 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id C541337B410
for <freebsd-isdn@freebsd.org>; Sat, 12 Apr 2003 12:07:07 -0700 (PDT)
Received: from peedub.jennejohn.org (p62.246.150.221.tisdip.tiscali.de
[62.246.150.221])
by mx1.FreeBSD.org (Postfix) with ESMTP id 3035B43F75
for <freebsd-isdn@freebsd.org>; Sat, 12 Apr 2003 12:07:06 -0700 (PDT)
(envelope-from garyj@jennejohn.org)
Received: from peedub.jennejohn.org (localhost [127.0.0.1])
by peedub.jennejohn.org (8.12.9/8.11.6) with ESMTP id h3CJ71Y9004733;
Sat, 12 Apr 2003 21:07:02 +0200 (CEST)
(envelope-from garyj@peedub.jennejohn.org)
Message-Id: <200304121907.h3CJ71Y9004733@peedub.jennejohn.org>
X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.3
To: Jan Goebel <jgoebel@rbg.informatik.tu-darmstadt.de>
In-reply-to: Your message of "Sat, 12 Apr 2003 18:16:50 +0200."
<Pine.SOL.4.51.0304121812580.4789@ultra15.rbg.informatik.tu-darmstadt.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 12 Apr 2003 21:07:01 +0200
From: Gary Jennejohn <garyj@jennejohn.org>
cc: freebsd-isdn@freebsd.org
Subject: Re: Best MTU for single-isdn
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Gary Jennejohn <garyj@jennejohn.org>
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2003 19:07:08 -0000
Jan Goebel writes:
> I was just wondering, if the standard ethernet mtu 1500 is best for my isp
> device, too. Or is it better to lower it a bit?
>
I've always used the default of 1500 with good success.
---
Gary Jennejohn / garyj@jennejohn.org gj@freebsd.org gj@denx.de
From owner-freebsd-isdn@FreeBSD.ORG Sat Apr 12 13:00:18 2003
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
Delivered-To: freebsd-isdn@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id 9431937B401
for <freebsd-isdn@freebsd.org>; Sat, 12 Apr 2003 13:00:18 -0700 (PDT)
Received: from srv1.cosmo-project.de (srv1.cosmo-project.de [213.83.6.106])
by mx1.FreeBSD.org (Postfix) with ESMTP id BAC6C43F3F
for <freebsd-isdn@freebsd.org>; Sat, 12 Apr 2003 13:00:16 -0700 (PDT)
(envelope-from andreas@klemm.apsfilter.org)
Received: from srv1.cosmo-project.de (localhost [IPv6:::1])
by srv1.cosmo-project.de (8.12.9/8.12.9) with ESMTP id h3CK0Ccx034486
(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
Sat, 12 Apr 2003 22:00:14 +0200 (CEST)
(envelope-from andreas@klemm.apsfilter.org)
Received: (from uucp@localhost)h3CK0BA6034485;
Sat, 12 Apr 2003 22:00:11 +0200 (CEST)
(envelope-from andreas@klemm.apsfilter.org)
Received: from titan.klemm.apsfilter.org (localhost.klemm.apsfilter.org
[127.0.0.1])
by klemm.apsfilter.org (8.12.9/8.12.8) with ESMTP id h3CJv129003330;
Sat, 12 Apr 2003 21:57:06 +0200 (CEST)
(envelope-from andreas@titan.klemm.apsfilter.org)
Received: (from andreas@localhost)
by titan.klemm.apsfilter.org (8.12.9/8.12.8/Submit) id h3CJutQx003328;
Sat, 12 Apr 2003 21:56:55 +0200 (CEST)
Date: Sat, 12 Apr 2003 21:56:55 +0200
From: Andreas Klemm <andreas@freebsd.org>
To: Jan Goebel <jgoebel@rbg.informatik.tu-darmstadt.de>
Message-ID: <20030412195655.GA3201@titan.klemm.apsfilter.org>
References:
<Pine.SOL.4.51.0304121812580.4789@ultra15.rbg.informatik.tu-darmstadt.de>
<200304121907.h3CJ71Y9004733@peedub.jennejohn.org>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft"
Content-Disposition: inline
In-Reply-To: <200304121907.h3CJ71Y9004733@peedub.jennejohn.org>
X-Operating-System: FreeBSD 4.8-STABLE
X-Disclaimer: A free society is one where it is safe to be unpopular
User-Agent: Mutt/1.5.3i
cc: freebsd-isdn@freebsd.org
Subject: Re: Best MTU for single-isdn
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2003 20:00:18 -0000
--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Apr 12, 2003 at 09:07:01PM +0200, Gary Jennejohn wrote:
> Jan Goebel writes:
> > I was just wondering, if the standard ethernet mtu 1500 is best for my =
isp
> > device, too. Or is it better to lower it a bit?
> >=20
>=20
> I've always used the default of 1500 with good success.
It depends on your traffic pattern.
Supposed you have often a mix of ftp / http / telnet traffic,
then ftp often tends to monopolize the link.
Cisco router have several queuing options to come around
this problem, i.e. WFQ (waited fair queueing), that has
been made for exactly this purpose, give smaller packets
a chance to come through smaller bandwidth links.
But if you download much this helps you only if your ISP
also uses WFQ, so that receiving ftp streams also don't
monopolize the link.
Using smaller mtu sizes could help you, so that many
different traffic types can make better use of the link.
The downside is, that you loose download performance and
the router has to fragment the packets which is more
CPU intensive as if he would only have to forward the
packets.
If you don't often mix ssh/telnet / ftp/hhtp traffic, then
I would say, save the work and simply use the default of 1500
which is more often desired, to get best download results of
larger files.
Andreas ///
--=20
Andreas Klemm - Powered by FreeBSD 4.8
Need a magic printfilter today ? -> http://www.apsfilter.org/
--/04w6evG8XlLl3ft
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)
iD8DBQE+mG+Hd3o+lGxvbLoRAuAxAJ929U9YCONXdXCOU643mF2JQ7ddwgCcC0nT
+Fspj0OYfWt7kbcLOjs+f6Q=
=mE9y
-----END PGP SIGNATURE-----
--/04w6evG8XlLl3ft--