[lug] ATT at Home setup
sanders at b-squared.net
Mon Oct 16 10:05:05 MDT 2000
I may not have any answers for you, but I use @home too and use RH6.2 as my
firewall/masq. The installer (subcontractor) set up my windows box as the main
system using the connection. Had to inform him that I was not using it on a network
or using Linux. He seemed to be a sticler. Didn't even want to install on a dual boot!
But as I have it booting by default into windows he didn't notice the boot loader (non-lilo
at the time). I digress...
He set up DHCP and using a proxy (cacheing server) and had to divert around the proxy
as it goes down all the time as in my case it was down. After he left I undid the DHCP and
set up my Linux box. All is well 6 months later still. I was informed a week or two ago
about an upgrade to the service for the upstream pipe.
"AT&T at Home will be deploying 128 kbps upstream rate management in your market
by the end of November."
Not sure but maybe this was going on in your area as well, (I'm in Montana). Also I have
not noticed any outages but email. I pop my email from work not on the @home network.
Also I use two NICs on the gateway one for my local network and one to the @home net.
I chose this for best firewalling, but do believe you can alias one NIC as well.
> This is my first time posting to a group, but since you are a local
> Colorado group, I thought someone might have had some experience with
> the local flavour of ATT at HOME.
> I have completed installing ATT at Home (Aurora system) cable modem om my
> Red Hat 6.0 system. So far, they seem to be down about 2 hours a night,
> beginning at 6 pm. Is this S.O.P. or a bad run of it?.
> Any how, the real question....I am using the Linux box as a gateway to
> my home network, sharing the cable modem and local network using one nic
> connected through a small hub. However, I had to use hard-coded static
> TCP/IP address for the modem connection, getting the address by first
> connecting with windows, and then transferring the settings to the Linux
> machine. It worked, but I'm nervous when they may reboot something on
> their end and leave me having to do the whole thing again. This set up
> is a messy couple of hours and I don't want to repeat it all that often.
> I was never able to get dhcp to work, although I tried all the stuff
> that I found on the national lists, and various FAQ's etc. involving
> hardcoding the MACADDR, installing DCHPCP rather than PUMP, etc. I
> wonder If anyone has made this work, especially could you share NIC as
> eth0 and eth0:0 when one is static address and the other is dynamic, and
> what parameters did you use for the DCHPCP call.
> Thanks for any help.
> Web Page: http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Warren Sanders (I'm my kid's Dad)
Ãdea's photo album: http://adea.b-squared.net
More information about the LUG