From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935299AbcCJKyD (ORCPT ); Thu, 10 Mar 2016 05:54:03 -0500 Received: from mout.kundenserver.de ([212.227.126.135]:55278 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753141AbcCJKx4 (ORCPT ); Thu, 10 Mar 2016 05:53:56 -0500 Subject: Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging To: Tilman Schmidt , Paul Bolle , Arnd Bergmann References: <1456945629-1793533-1-git-send-email-arnd@arndb.de> <1456945629-1793533-2-git-send-email-arnd@arndb.de> <56D7F62E.6050502@linux-pingi.de> <1659125.tHp8H942OG@wuerfel> <1457108303.2651.112.camel@tiscali.nl> <56DADA57.9010200@imap.cc> <1457340486.2737.19.camel@tiscali.nl> <56E09F4A.8010202@imap.cc> Cc: Christoph Biedl , linux-arm-kernel@lists.infradead.org, Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-doc@vger.kernel.org, netdev@vger.kernel.org, Jonathan Corbet , linux-kernel@vger.kernel.org, "David S. Miller" From: isdn@linux-pingi.de Message-ID: <56E15211.7080206@linux-pingi.de> Date: Thu, 10 Mar 2016 11:53:05 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <56E09F4A.8010202@imap.cc> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:kOLoMXCd8dh7I1FMUUUD2UJmg8TMNderjkZP8Hdmp+8UaUeRBIe ApLsBHk13BDfeDKxCy8sXgRE8fHsi8if7Cg5z2VOnxjeYtRreA2560Q36mNC2B6Pss9Oen0 Iu+SFdf1YJ2yPpElbCFpx4F93c2ExCY/5lYiUcmAETdVUDeqRcWd4aloq1KyCnKRSKhIJZ6 QSg0/k0/TBG43Ue30rBOA== X-UI-Out-Filterresults: notjunk:1;V01:K0:T2G3k650GYk=:54tMr/fBDRZ0vWW6/CuXtf higcPoYXSPp1AwADFcIq7nPBXDe70G2qrVSEqgqWCPETeI353exr9exgxw6+CUkZyXeFNpZNC QBnOTLpucyNvmXrLqz7Z7iZcuhboc0FenA6sOyrSO7+//Q+oRC6Fw4x74xVFqM/1QpQ3YHCD8 0faoZE1yQAdgHBliSNFJd3KzKTIPOBjhdBKuETAerTcJMysioRKmbOPHbmYjk0Apm57leT2oH IEiGZ8eS5ss+/L2m+raUo0ODrnD+7kdsFKSsOvK/r02WEXBc2sRDkBzEQxLMw8WmJdEJy5iog +xP7Fz7JpmDHemKfx461qNznkumBdc2EqntFwrJX0C4WV5A6RgBAHRZbQFpcR97JGxXIwGHw5 wlhdba9ipK9YPV8ysEr1gcpaIMHJObYW5nWe4gzStmLnZ4jJ2nGFiNiHJFq5IjUH3USsw9QKp VWA/49sMmAq+XmSFOrTch+Vl9WdhbpnBUU7wZL/mgt/xyIk6vh4KzX4Co+Zg8QdB9dQj5eb4K 2q12MiGZt9OetABV85RahZCV6K1hZuesRK7LQ2QESaoeQnRdrp4FnTwDpUmnrmYeYfB9uo83g SHgfWou6h9yUlIdOPN5zetZrv07nbP7l/dkqmBk5qEw+CYQMLeklkgi/cPkJ7Mefll3vHLonZ bkNiUgnu/z+8alVx9XUlq+nlxxhtSu3rUfiWlagkLDjiXJV7meah3yE5Z4/Rg6StXxbP1PTyC yJv5be/h5y6+vUIZ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 09.03.2016 um 23:10 schrieb Tilman Schmidt: > Am 07.03.2016 um 09:48 schrieb Paul Bolle: >> On za, 2016-03-05 at 14:08 +0100, Tilman Schmidt wrote: >>> As a consequence, owners of HiSAX type adapters are in fact stuck with >>> the old hisax driver if they want to continue using i4l userspace >>> tools. >> >> Do you know whether or not mISDN tools offer functionality comparable to >> i4l tools? > > AFAICS they don't. mISDN seems very much geared towards voice use, for > example with Asterisk. The entire topic of ISDN data connections appears > to be missing. I don't see how someone currently using i4l for Internet > dial-in (either client or server side) could migrate to mISDN. > Not true. mISDN with CAPI support works just fine with pppd and pppdcapiplugin and the CAPI works for all mISDN HW. Following I4L services are not supported: - RAW IP dialin/dialout - termnal connections via X75 (e.g. dialin via minicom on a remote machine). - isdndivert RAW IP was very popular in the nineties because of easy to setup and low protocol overhead, but very insecure, since only authorization was done by the phone numbers. This was not a such big issue in the nineties, since it was hard to get a public line with the allowance to send any numbers. Today this is no problem to get the allowance (if you can get a new ISDN line at all - which is more a problem today). Terminal connection where only used seldom, more as last resort or for debuging. isdndivert was used to manage call redirections, it could be easely replaced by an mISDN or CAPI application, but here were not so much requests for it. Since Telekom offers callredirection in their Web customer center here is no much need anyways. Karsten From mboxrd@z Thu Jan 1 00:00:00 1970 From: isdn@linux-pingi.de Subject: Re: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging Date: Thu, 10 Mar 2016 11:53:05 +0100 Message-ID: <56E15211.7080206@linux-pingi.de> References: <1456945629-1793533-1-git-send-email-arnd@arndb.de> <1456945629-1793533-2-git-send-email-arnd@arndb.de> <56D7F62E.6050502@linux-pingi.de> <1659125.tHp8H942OG@wuerfel> <1457108303.2651.112.camel@tiscali.nl> <56DADA57.9010200@imap.cc> <1457340486.2737.19.camel@tiscali.nl> <56E09F4A.8010202@imap.cc> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: devel@driverdev.osuosl.org, linux-doc@vger.kernel.org, Greg Kroah-Hartman , Jonathan Corbet , linux-kernel@vger.kernel.org, netdev@vger.kernel.org, Christoph Biedl , "David S. Miller" , linux-arm-kernel@lists.infradead.org To: Tilman Schmidt , Paul Bolle , Arnd Bergmann Return-path: In-Reply-To: <56E09F4A.8010202@imap.cc> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: driverdev-devel-bounces@linuxdriverproject.org Sender: "devel" List-Id: netdev.vger.kernel.org Am 09.03.2016 um 23:10 schrieb Tilman Schmidt: > Am 07.03.2016 um 09:48 schrieb Paul Bolle: >> On za, 2016-03-05 at 14:08 +0100, Tilman Schmidt wrote: >>> As a consequence, owners of HiSAX type adapters are in fact stuck with >>> the old hisax driver if they want to continue using i4l userspace >>> tools. >> >> Do you know whether or not mISDN tools offer functionality comparable to >> i4l tools? > > AFAICS they don't. mISDN seems very much geared towards voice use, for > example with Asterisk. The entire topic of ISDN data connections appears > to be missing. I don't see how someone currently using i4l for Internet > dial-in (either client or server side) could migrate to mISDN. > Not true. mISDN with CAPI support works just fine with pppd and pppdcapiplugin and the CAPI works for all mISDN HW. Following I4L services are not supported: - RAW IP dialin/dialout - termnal connections via X75 (e.g. dialin via minicom on a remote machine). - isdndivert RAW IP was very popular in the nineties because of easy to setup and low protocol overhead, but very insecure, since only authorization was done by the phone numbers. This was not a such big issue in the nineties, since it was hard to get a public line with the allowance to send any numbers. Today this is no problem to get the allowance (if you can get a new ISDN line at all - which is more a problem today). Terminal connection where only used seldom, more as last resort or for debuging. isdndivert was used to manage call redirections, it could be easely replaced by an mISDN or CAPI application, but here were not so much requests for it. Since Telekom offers callredirection in their Web customer center here is no much need anyways. Karsten From mboxrd@z Thu Jan 1 00:00:00 1970 From: isdn@linux-pingi.de (isdn at linux-pingi.de) Date: Thu, 10 Mar 2016 11:53:05 +0100 Subject: [PATCH 2/2] isdn: i4l: move active-isdn drivers to staging In-Reply-To: <56E09F4A.8010202@imap.cc> References: <1456945629-1793533-1-git-send-email-arnd@arndb.de> <1456945629-1793533-2-git-send-email-arnd@arndb.de> <56D7F62E.6050502@linux-pingi.de> <1659125.tHp8H942OG@wuerfel> <1457108303.2651.112.camel@tiscali.nl> <56DADA57.9010200@imap.cc> <1457340486.2737.19.camel@tiscali.nl> <56E09F4A.8010202@imap.cc> Message-ID: <56E15211.7080206@linux-pingi.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Am 09.03.2016 um 23:10 schrieb Tilman Schmidt: > Am 07.03.2016 um 09:48 schrieb Paul Bolle: >> On za, 2016-03-05 at 14:08 +0100, Tilman Schmidt wrote: >>> As a consequence, owners of HiSAX type adapters are in fact stuck with >>> the old hisax driver if they want to continue using i4l userspace >>> tools. >> >> Do you know whether or not mISDN tools offer functionality comparable to >> i4l tools? > > AFAICS they don't. mISDN seems very much geared towards voice use, for > example with Asterisk. The entire topic of ISDN data connections appears > to be missing. I don't see how someone currently using i4l for Internet > dial-in (either client or server side) could migrate to mISDN. > Not true. mISDN with CAPI support works just fine with pppd and pppdcapiplugin and the CAPI works for all mISDN HW. Following I4L services are not supported: - RAW IP dialin/dialout - termnal connections via X75 (e.g. dialin via minicom on a remote machine). - isdndivert RAW IP was very popular in the nineties because of easy to setup and low protocol overhead, but very insecure, since only authorization was done by the phone numbers. This was not a such big issue in the nineties, since it was hard to get a public line with the allowance to send any numbers. Today this is no problem to get the allowance (if you can get a new ISDN line at all - which is more a problem today). Terminal connection where only used seldom, more as last resort or for debuging. isdndivert was used to manage call redirections, it could be easely replaced by an mISDN or CAPI application, but here were not so much requests for it. Since Telekom offers callredirection in their Web customer center here is no much need anyways. Karsten