[NTLUG:Discuss] Linux, DSL, and Qwest?

[Richard Cobbe]

Lo, on Tuesday, March 6, Steve Egbert did write:

> 
> If the Ethertype is 0800, then you're probably using a 

?

I think part of this sentence got lost somewhere.

> > Originally, I'd thought Qwest used PPPoE, so I downloaded rp-pppoe,
> > installed it, and configured it for their network.  It was never able
> > to establish the connection to the ISP---timed out waiting for a PPP
> > initialization message.  (I don't have the logs in front of me, so I
> > don't remember the exact problem.)
> > 
> > However, when I tried it with the Win95 box, I didn't need to set up
> > PPPoE.  It was just plug it in, turn on DHCP, and go.

In retrospect, I'm not completely certain this actually worked, although
I'm fairly sure it did.

> It would help to know if you are using a DSL-bridge modem or DSL-router
> modem.
> 
> Based on your email, sounds like a DSL bridge modem but I cannot be sure.

Well, it would appear to be a DSL-router, based on
http://www.cisco.com/warp/public/cc/pd/rt/600rt/prodlit/678so_ds.htm, but
I'm not entirely certain.

> Only in RedHat 6.2, there is a severe problem with "pump".  I recommend
> going back to the ISC's dhcpcd instead or do a RedHat upgrade.

I've gotten that suggestion from a couple of other folks, so I'll give it a
shot.  (The machine is downtown, and I'm in Plano, so I'll have to wait
until Saturday to try these things out.)

> > Destination     Gateway         Netmask             Interface
> > 192.168.0.1     *               255.255.255.255     eth0
> > 192.168.0.0     *               255.255.255.0       eth0
> > 10.0.0.0        *               255.0.0.0           eth1
> > 127.0.0.0       *               255.0.0.0           lo
> > default         10.0.0.1        0.0.0.0             eth1
> > 
> > (The gateway IP was supplied by Qwest's tech support, for what that's
> > worth.)

> Looks like you are now using a DSL router which already performed NAT.  You
> will need to turn on RIP or assign static routes so that packets can reach
> the subnet 10 from the DSL router.

This would appear to be consistent with the URL referenced above.  When you
say turning on RIP or assigning a static route, do you mean on the Linux
machine or on the router itself?  If it's the latter, this could be
difficult.  The techs set the administrative password on the modem when
they installed it, and I don't happen to know what the password is....

> 
> > I tried to ping 10.0.0.1, by IP address, and it printed the 
> > error message
> > 
> > >From 10.0.0.2: Destination Host Unreachable
> > 
> > I control-C'd out of ping and went to try some other things, when the
> > kernel started dumping errors to the console:
> > 
> > eth1: 21140 transmit timed out, status fe67c057, SIA 00000000 00000200
> > 00000000 c40ffec8, resetting...
> 
> There is a cabling fault (possibly a crossover instead of a straight-thru or
> vice-versa).

I'm quite ready to believe that the cable is dead, but I'm fairly sure that
I got the crossover-vs-straight-thru part right: I'm using the cable
included with the DSL modem for this express purpose.  (Assuming, of
course, that Cisco got it right....)  Also, it was the same cable I used
for the Win95 test earlier.

Richard