<p>Will maybe look into one of those. Trying to get AT&T to just replace the stupid thing now.</p>
<p>I may look at, in the longer term, getting an internal adsl modem. First, though, I need to learn how they go about getting the multiple static IPs delivered. It is something to do with RIP, that's all I have discovered thus far.</p>
<p>--<br>
Sent from my HTC Dream---Running Froyo!<br>
Thanks, @cyanogen!</p>
<p>On Jul 14, 2010 12:12 PM, "Greg Clifton" <<a href="mailto:gccfof5@gmail.com">gccfof5@gmail.com</a>> wrote:<br type="attribution">> Mike,<br>> <br>> If you just need to power cycle the DSL modem, there a number of<br>
> manufacturers that offer remotely controller PDU devices (APC, Tripp Lite,<br>> etc.). Many of these are IP addressable now, but I seem to recall that<br>> serial versions are/were available in times past and perhaps even devices<br>
> with a modem built in. I take it that you couldn't use an IP addressable<br>> device, since you loose the connection until you cycle the DSL modem? If you<br>> had a managed PDU device with a dial up modem, you could power the DSL modem<br>
> down remotely, but no doubt this solution would cost more than a simple<br>> internal modem in the box.<br>> <br>> GC<br>> <br>> On Wed, Jul 14, 2010 at 10:59 AM, Michael B. Trausch <<a href="mailto:mike@trausch.us">mike@trausch.us</a>>wrote:<br>
> <br>>> On Wed, 2010-07-14 at 08:35 -0400, James Sumners wrote:<br>>> > I understood your situation to be that you have two external<br>>> > connections coming into the firewall 24/7. That is, DSL on eth0 and T1<br>
>> > on eth1 (or whatever, I've never dealt with a T1).<br>>><br>>> That would be correct.<br>>><br>>> > I thought the "manual" part was all done at a keyboard. Now I<br>>> > understand that you have to unplug the DSL connection from the<br>
>> > firewall and plug in the T1? If that's the case, well, I don't know<br>>> > what to suggest in regard to the two networks.<br>>> ><br>>> This is also correct. I'm just not sure that I understand what bridging<br>
>> the two interfaces together would accomplish. Basically, I have the DSL<br>>> attached to eth0, the LAN attached to eth1, and the T1 line attached to<br>>> eth2. When packets stop going across eth0 (which I can adequately<br>
>> determine by using "ping -c4 <default gateway> > /dev/null" and checking<br>>> the status code), I need to trigger a failover to the eth2 device. Of<br>>> course, I only had the light-bulb moment about checking the default<br>
>> gateway late last night... the DSL modem provides the default gateway.<br>>><br>>> > I assume you're just power cycling the AT&T modem? I'm fairly positive<br>>> > that you will not be able to power cycle that thing remotely. I'd be<br>
>> > shocked if AT&T offers anything that useful. You might look into a PCI<br>>> > modem[1]. Then you can remotely take the interface down and bring it<br>>> > back up via your dial-up connection.<br>
>><br>>> To make things more complicated, this is something of a nonstandard<br>>> setup. I think that if I print out the whole configuration listing on<br>>> the advanced configuration page, I can probably mirror the<br>
>> configuration. What I *don't* know about DSL is if you have to register<br>>> the device on the network before being able to use it. I know that at<br>>> least with cable modems, you have to have the network provider whitelist<br>
>> the hardware address of the modem so that they will talk to it. Perhaps<br>>> since DSL authentication is done using PPPoE, that is different? I<br>>> don't know.<br>>><br>>> I will check into the PCI modem, though, because that would very likely<br>
>> solve all of the issues that I have. I'll just need to figure out<br>>> exactly how they are tunneling the static IP addresses to me; the modem<br>>> picks up a dynamic address over PPPoE and then uses that to gateway the<br>
>> static IP addresses. If everything works out perfectly with this, I<br>>> would be able to use all 6 addresses in the /29 that is allocated to us,<br>>> instead of giving up one for the modem... that would be nice.<br>
>><br>>> Is it too much to expect of any service provider to just work and to<br>>> provide hardware that just works? I'm beginning to think that it is<br>>> indeed too much of an expectation.<br>
>><br>>> --- Mike<br>>><br>>> _______________________________________________<br>>> Ale mailing list<br>>> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>>> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>
>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>>> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>>><br></p>