Hacking the Actiontec 56k Modem/Gateway
william_lorenz writes "The Actiontec Dual 56k External Modem is an inexpensive device with a built-in 56k modem and two Ethernet ports that can be used as an Internet gateway of sorts. What's great about it is that it runs some form of uClinux, it's easily hackable, and Greg Boehnlein of the Linux Users Group of Cleveland and NOOSS fame recently contributed a detailed report on his findings! Pictures of the board are also available here, here, and here. Lots of specific details are included in Greg's article, and there's been some further discussions about this on the LUGC mailing lists."
Looks like a nice machine with default software that is a bit lame. But since that is now easily fixable, I can think of a few folks in dialup hell that I'll probably be crossing off my Xmas list. :)
Democrat delenda est
Jeez...
Slashdotted already.. this article's gonna set the record for redundant posts.
Yes, we KNOW his server MUST be behind that 56k modem.
Right, now that we've got that out of the way...
Personally, I'm more intrigued by the company's anti-kidnapping technology. I'll sleep easier once that's out of the way.
~ Whence do you come, slayer of men, or where are you going, conqueror of space?
Two ethernet ports + linux + easily hackable = who cares about the modem jack?
"it's easily hackable"
If only we could hack it into a 256k modem...
Would it be possible to hack an adsl/cable router to be used as a simple webserver? For a low traffic and static site it would be perfect for my business website hosting needs. 10watts consumption...fanless operation...and small footprint it sounds like a dream! I could even imagine other hacks like interfacing a larger amount of flash storage or running a real low end db &scripting engine to have behaviour like mysql/php3 together.
We played dungeons and dragons for 3 hours.....then i was slain by an elf
What next? RAID-5 using a stack of 8 inch floppies?
Too late
56k is better then nothing. Keep in mind also the fact that primarly text information gets compressed unlike in broadband technologies. Keep in mind that many a small business or small remote office doesn't nessicarly need lots and lots of bandwidth just to get e-mail.
Hackability? Well I'm somewhat curious what they can do with such a device. The first thing that comes to mind is a standby gateway that goes online when the primary gateway fails. This would be MOST handy.
There is no sanctuary. There is no sanctuary. SHUT UP! There is no shut up. There is no shut up.
Hmm .. perhaps in your country. In South Africa, this is basically the standard .. sure you have ISDN / ADSL ..
..
BUT
ISDN - very expensive to start with (+- R2000-00 initial startup @ R 7.50 / $1) then you still pay for the call charges. If the config goes haywire you can end up with a bill of R 4000-00/month.
ADSL is only available in certain areas - but there is a 3gig monthly cap. some guys can go through that in a day if they wanted to, and the service is being oversubscribed so quickly that the transfer rates are becoming dysmal. The only advantage is the 24x7 online connectivity (although they say that this is not guaranteed)
So most subscribers pay for 56k access (and we do pay for every local call made)
Maybe once the monopoly is broken (ie: SNO) there will be some sort of relief for the south african public
A NATted LAN is certainly better than nothing when you're sharing a house with multiple machines. Yes, it's slow if two people are using it at once, but it also means you don't need a modem in each box, don't need to risk someone else trying to dial out with another machine while you're already connected, someone can sneak in a quick Google or mail-read around your activity (or, in my case, I could stay on IRC while others browsed to their hearts' content)... ...But most importantly, it's a dramatic convenience when working with *NIX machines, and other software/projects that assume use in a LAN environment. Yes, you *can* net-install OpenBSD overnight on a 56k link - but you'll need to be ethernetted to do it, since they didn't fit ppp on the install floppy.
Now, I can see some vague utility for this hardware in the SOHO market, though I can't tell if it's configured for same by default (the marketing and 'modem' branding suggests not):
A lot of small businesses rely on DSL or Cable shared through a simple Linksys, but should there be an outage, their LANs are dead in the water. With a modem *in* the dinky embedded router, they'd have the option of falling back to dialup rather than closing up shop or waiting for their MCSE to get to dealing with it. With the appropriate firmware load, one of these things could provide fully automatic failover - and "failback" when it detects the DSL or cable has returned.
Many businesses I've met have been confused into paying for a full unused phone line/number 'beneath' their DSL anyway, so this would improve their uptime without adding to their costs. True, the same could be done with a dedicated *NIX machine, or even Windows ICS, but not everyone has technical staff on hand, and it'd be cheaper to have a contractor drop in $100 of 'foolproof' hardware once than stay on-call for care-and-feeding of a less "embedded" solution.
The "dual modem" mention in the article header made me think for a moment this product allowed multiple users to share a composite link. (See my earlier post on this topic). Rather this product allows 2 users to share *one* link.
A composite link to two *different* ISP could be implemented quite simply by say, using a proxy server to multiplex outbound HTTP requests among multiple interfaces (each interface corresponding to one phone connection).
This approach is more coarse-grained and inefficient than TCP/IP-level channel bonding. However, it would still be useful for places out in the boondocks where you can get two telephone lines, but no broadband. Also, its efficiency could be improved by using HTTP functionality that allows specific byte-ranges to be downloaded for a particular resource.
1. Two posts only? That is not very useful at all. You probably need a hub as well.
2. uClinux is not readily hackable, at least until you drift of it, and also know how to recover when this thing freezes. You can not just dive into it as if it was a linux PC.
3. The modem is probably the *best* part, but that has been done for many, many years. Nothing special.
If this thing had more than 2 eth ports, it could be useful; but, I would rather have it wirelss.
The only downside of your setup is that the 56k modem drops to 33k6 when you use it to dial in...
56k only works if the isp can tap into the digital phone exchange...
Jeroen
Secure messaging: http://quickmsg.vreeken.net/
this is not a modem sharing thingy! this is a cheap single board computer that runs linux, has two ethernet ports and a modem, probably some other digital/serial io. (boxed, with psu, etc) that runs linux!!! perfect candidate for a web thermometer, ethernet garage door opener, robot brain, home weather station controller, etc.
Sounds like this might be usable for anyone wanting to set up a server for a satellite connection that has the downlink via the dish/usb modem and the uplink via ISP/phone modem like DirecPC does. The only linux project so far is at Sourceforge: http://sourceforge.net/projects/direcpc
Incidentally, this isn't even a thing of the past. It turns out 56K Frame Relay links live on. I know of a _massive_ corporation that links most of its stores to the central mainframe via 56K FR links. Why? Because It Works.
While I'm sure you are aware of it, I doubt many others are: 56k frame and 56k analog dialup are fantastically different in actual performance. A 56k FR has very low latency, which makes interactive apps (like telnet and SNA crap, the bulk of the traffic I see still going over these links) very much usable. Try that with a modem and the latency makes it very difficult to tolerate with multiple users.
Do not fold, spindle or mutilate.
Laugh if you want, but necessity dictates that I can only get a 56k internet connection, and there's two computers in the house. I'm currently using XP's internet connection sharing thingie but I'd kill for a hardware-based solution right about now, at least one that doesn't cost an arm and a leg. I thought Stratitec's (discontinued) "Easy Internet Router," which had a serial port for connecting an external modem as well as ethernet ports, would be The Answer, except that the router seriously slowed down when routing a dial-up connection (tech support's excuse was "Well, we only intended it to be a back-up and the router really isn't designed to do that...")
Now I hear about this, which to me sounds like a Holy Grail, and I can't seem to find it anywhere. The only place I can find it is one of those shady dealers operating on Amazon. There has to be somebody slightly more reputable with some for sale, or at the very least something else to let me compare prices!
They listed the device as compatible with:
Operating System Compatibility Windows 98 / 98SE / ME / 2000 / XP/ MAC OS 7.1 and higher/ Linux / Unix
But then for Minimum System Requirements they ask for:
Windows 98, 98SE, Windows Me, Windows 2000, or Windows XP
Is it necessary to have an ms Windows pc in order to configure the thing? What if all you have is Macintosh or, like me, Linux? Or are they saying that Windows is the bare minimum and, of course, anything else more than meets the requirements?
The limitation you refer to has very little to do with managing crosstalk. What actually happened is that the phone company was maximizing the number of channels they could fit on a single wire by using a technology called Frequency Division Multiplexing (FDM).
Since an average voice conversation has a bandwidth of about 2KHz, they built in a low-pass filter with a cutoff somewhere in the vicinity of 3KHz. This means they can heterodyne the channels, each (roughly)3KHz wide, onto a single wire.
Now, this means that the data rate (in terms of zero crossings per second (the original meaning of baud) is limited to about 2400. The "high speed" modems, all the way up to 56K, have a baud rate of 2400. This is a hard limit due to the phone company hardware.
What changed is the number of bits per baud. A 56K modem might use as many as 24 bits per baud, assuming the line is clear enough. The number of bits per baud is capped by the noise floor of the signal, which is also why you won't always connect at 56K (noisier lines can't handle the resolution).
In the move to digital networks, the same total channel datarate was designed into the switching systems. I'm not entirely sure the sampling rate and quantization parameters of these systems, though.
Hardware, software, and blinking lights!