[lug] Qwest ADSL

[Larry D. Ashton]

----- Original Message -----
From: "ljp" <ljp at llornkcor.com>
To: <lug at lug.boulder.co.us>
Sent: Sunday, February 18, 2001 10:23 PM
Subject: Re: [lug] Qwest ADSL


>
> >
> >Well, at least it is nice to know it can work.
> >Tell me more about how you set it up.  Is it set up to come up at boot
time
> >or do you manually configure it?  Is the cisco hooked to eth1 or eth0?
What
> >ethernet cards are you using?  I'm using 3COM 3C509B cards and loading
> >separate instances of the module for each card.  Which version of DHCP
are
> >you using?  What version and distribution of linux are you using?  I've
got
> >RedHat linux 6.1, but also have the 7.0 disks but didn't want to tackle
an
> >upgrade yet.  For the last year and a half, I've had this machine as an
ip
> >masquerading, firewall, gateway router for 5 boxes on the inside network
> >connected to eth0 and has been my internet server though dialup - DSL
just
> >came to town and I am trying to switch over to DSL.
> >
> >thanks for the info,
> >Larry
>
> Setup is in the dark, cold, basement dungeon. Where, in the summer, lots
of
> spiders lurk about all over.
> 675 is using DHCP. Although it always addresses eth0 at 10.0.0.1, or is it
> 10.0.0.0
> If I recall, I did have to set some thing up in there, but I forget what,
or
> maybe I tried static IPs in it, and switched to DHCP on it for when it
goes
> down..
> DHCP and NAT are both enabled in the 675
>
> minicom in to cisco:
>
> cbos>show route
> [TARGET]         [MASK]           [GATEWAY]       [M] [TYPE]    [IF]
[AGE]
> 0.0.0.0          0.0.0.0          0.0.0.0          1  SA        WAN0-0   0
> 10.0.0.0         255.255.255.0    0.0.0.0          1  LA        ETH0     0
> x.x.x.x   255.255.255.0    0.0.0.0          1  A         WAN0-0   0
> x.x.x.x   255.255.255.255  0.0.0.0          1  AH        WAN0-0   0
>
> eth0 leads to firebox's eth1.
> firebox eth0 is connected to the switch and inner depths of my network.
> geez the more  look at this, the more confused I am . good thing it all
works.
> :)
>
> [root at fire /root]# /sbin/route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
> 10.0.0.2        0.0.0.0         255.255.255.255 UH    0      0        0
eth1
> 192.168.0.3     0.0.0.0         255.255.255.255 UH    0      0        0
eth0
> 10.0.0.0        10.0.0.1        255.255.255.0   UG    0      0        0
eth1
> 10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0
eth1
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0
eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         10.0.0.1        0.0.0.0         UG    0      0        0
eth1
>
>
> alias eth0 tulip - which is linksys v 4.1 (and a pain in the ass to get up
> and running)
> alias eth1 e100 - which is Intel Pro 100 (came with the cisco unit.)
>
> Comes up at boot, or did the last time I booted- I think
> [root at fire /root]# uptime
>    9:27pm  up 83 days,  1:47,  2 users,  load average: 0.00, 0.00, 0.00
>
> heh- not much going on there...
> The linux box(es) use static IP's all around.
> Firewall is basically redhat 6.1 w/ services shutdown.
> kernel version 2.2.17
> The cisco does a good job of keeping everything out. I think. I hope.
>
> I dunno if this is even how its supposed to be, seems to work fine.


Thanks for getting back to me.  Now I'll know what my routing table will
look like on both the linux box and the 675 when it's working.  I'll try
playing with the 675's lan side and see what happens.

thanks again,
Larry