SpellCaster DataCommute/BRI ISDN Adapter
Manufacturer: SpellCaster Telecommunications Inc.
Platforms: Linux 2.x, Windows NT 4.0, Windows 3.51 and 95
Price: $359 US
Reviewer: Jay Painter
For the last 4 months, I have used two SpellCaster DataCommute/BRI ISDN cards to connect SSC's satellite office to the main office. Previously, we had used high speed modems, and after that, a set of 3Com ISDN modems. The DataCommute/BRI has given us the fastest and most reliable connection. This ISDN adapter was designed specifically for Linux, and the ISDN4Linux driver is shipped with the Linux 2.1.x development kernel. See sidebar for hardware features.
The DataCommute/BRI is a 16bit ISA card. It is easy to install because there are no jumpers to set. The board's IRQ and shared memory are all set within the software driver.
SpellCaster has written an ISDN4Linux compliant driver for their ISDN cards. It is available for download from SpellCaster's ftp site: ftp.spellcast.com /pub/drivers/isdn4linux/scisa-2.00.tar.gz. This package compiles the kernel module, sc.o, and a configuration program, scctrl. The scctrl utility is used to set the ISDN switch type and SPID numbers, and to check the connection status, along with numerous other options. I had no problems compiling the driver and the scctrl utility. The kernel module takes several command line arguments to set the IRQ, memory base and io base. I recommend the use of the sc.o driver option do_reset=1 when using insmod to install the driver module into the kernel. If the reset option is not used, the kernel module will fail to install after a soft reboot unless you remove the module before the reboot.
The SpellCaster/BRI must first be configured to communicate with the phone company's ISDN switch. This action includes setting the SPID numbers of your two ISDN channels, setting the phone number (the ISDN board needs to know its phone numbers), the ISDN switch type and the speed of each channel. These hardware settings are set using the scctrl utility which is provided by SpellCaster and comes with the kernel driver. After hardware configuration is complete, the connection configuration is handled by the generic ISDN4Linux utilities. These utilities require “ISDN Subsystem” support compiled into the kernel. ISDN4Linux supports single channel and dual (128K) PPP connections, as well as HDLC connections. IPX can also be transmitted by using ISDN4Linux's emulated ethernet encapsulation.
It is important to use the 2.0.27 kernel with the SpellCaster boards. There have been problems reported with the ISDN subsystem in later kernels, and it hasn't been fixed as of 2.0.30. It is essential that the SpellCaster/BRI's firmware is at least version 1.51. If you have a card with an earlier firmware revision, multilink PPP connections will have less throughput than a single-channel connection due to a bug that causes packet dropping.
I found the SpellCaster's performance to be its greatest asset. Ping times between the two SpellCasters average 47ms, and long haul FTP transfers average 15KB/sec (122Kbps) with a multilink PPP connection. The CPU utilization is so low that at maximum transfer speed, the process of receiving from the ISDN and routing to Ethernet only used 1% of the processor time on a 486-33. The stability of the connection is also impressive. Our two ISDN routers have maintained a connection now for over a month with no intervention, despite periodic outages caused by unreliable ISDN service from our phone company. Reconnecting after an outage is handled by the ISDN4Linux subsystem automatically.
The hardware and the software of the SpellCaster/BRI both work well and are easy to use. The ISDN4Linux subsystem is more difficult to configure, and I recommend getting the FAQ at http://www.lrz-muenchen.de/~ui161ab/www/isdn/ before spending a lot of time attempting to decipher the cryptic acronyms.
Jay Painter is the systems administrator for SSC. He can be reached via e-mail at firstname.lastname@example.org.
|Dynamic DNS—an Object Lesson in Problem Solving||May 21, 2013|
|Using Salt Stack and Vagrant for Drupal Development||May 20, 2013|
|Making Linux and Android Get Along (It's Not as Hard as It Sounds)||May 16, 2013|
|Drupal Is a Framework: Why Everyone Needs to Understand This||May 15, 2013|
|Home, My Backup Data Center||May 13, 2013|
|Non-Linux FOSS: Seashore||May 10, 2013|
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- Dynamic DNS—an Object Lesson in Problem Solving
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- Tech Tip: Really Simple HTTP Server with Python
- Keeping track of IP address
45 min 4 sec ago
- Roll your own dynamic dns
5 hours 58 min ago
- Please correct the URL for Salt Stack's web site
9 hours 9 min ago
- Android is Linux -- why no better inter-operation
11 hours 25 min ago
- Connecting Android device to desktop Linux via USB
11 hours 53 min ago
- Find new cell phone and tablet pc
12 hours 51 min ago
14 hours 20 min ago
- Automatically updating Guest Additions
15 hours 29 min ago
- I like your topic on android
16 hours 15 min ago
- This is the easiest tutorial
22 hours 51 min ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi
It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?