[lug] pump.conf config, AT&T

keyser soze droid_1138 at yahoo.com
Sun Aug 11 13:58:42 MDT 2002


AT&T has some sort of SAS server that your have to
authenticate with
before you can get anywhere.  After several attempts,
I ended up booting
back to an ancient copy of win98 I had left on this
drive and using
their install cd.  Once you authenticate your modem
with their server
everything will work like a normal dhcp setup.  

supposedly you can specify sas.r4.attbi.com as your
proxy server in your
browser and then actually go to that address with your
browser and enter
your info.  This would eliminate the need to use their
software,
however, I never got this to work.

Hope that helps

James

Quoting "D. Stimits" <stimits at idcomm.com>:

> Mark Horning wrote:
> > D. Stimits wrote:
> > 
> >> The cable modem guy is outside working right now,
I'm wondering if
> 
> >> anyone has advice on pump.conf dhcp client setup
for AT&T? I'm
> telling 
> >> it basically what the sample script is, which is
pretty much
> nothing 
> >> but nodns to stop it from writing resolv.conf. If
anyone has 
> >> suggestions or comments for AT&T (I can do this
before he finishes
> the 
> >> actual cable), let me know.
> >>
> >> D. Stimits, stimits AT idcomm.com
> >>
> >> _______________________________________________
> >> Web Page:  http://lug.boulder.co.us
> >> Mailing List:
http://lists.lug.boulder.co.us/mailman/listinfo/lug
> >> Join us on IRC: lug.boulder.co.us port=6667
channel=#colug
> > 
> > 
> > I have the same problem....fixed it by copying in
my own
> resolv.conf out 
> > of rc.local
> > Not really a fix, just a really bad (lazy)
workaround ;-)
> > 
> > I don't use an /etc/pump.conf file, the nodns
option never seemed
> to 
> > work right.
> > I just let it come up by itself and it appears to
do the right
> thing. I 
> > seem to recall
> > having to play with networking a bit at first but
I can't recall
> what if 
> > anything
> > I did with it. Here's what I have now.
> > 
> > A pump -s shows:
> > [root at 12-254-25-xxx /root]# pump -s
> > Device eth0
> >        IP: 12.254.25.xxx
> >        Netmask: 255.255.252.0
> >        Broadcast: 255.255.255.255
> >        Network: 12.254.24.0
> >        Boot server 12.242.19.34
> >        Gateway: 12.254.24.1
> >        Hostname: trigger-for-attbi
> >        Domain: attbi.com
> >        Nameservers: 216.148.227.68 204.127.202.4
> >        Renewal time: Sun Aug 11 14:41:52 2002
> >        Expiration time: Mon Aug 12 02:41:52 2002
> 
> On the above, was the netmask and boot server
assigned by the DHCP?
> Did 
> you ask for a specific hostname, such as "trigger",
or was that 
> completely determined by the DHCP?
> 
> D. Stimits, stimits at idcomm.com
> 
> > 
> > [root at 12-254-25-xxx /root]# hostname
> > 12-254-25-xxx.client.attbi.com
> > 
> > My system is a RH 6.1/6.2 combo :-) The networking
was set as:
> > [root at 12-254-25-xxx sysconfig]# pwd
> > /etc/sysconfig
> > 
> > [root at 12-254-25-xxx sysconfig]# cat network
> > NETWORKING=yes
> > # FORWARD_IPV4 removed; see /etc/sysctl.conf
> > HOSTNAME=12-254-25-xxx.client.attbi.com
> > GATEWAY=12.254.24.1
> > NETMASK=255.255.252.0
> > GATEWAYDEV=eth0
> > 
> > [root at 12-254-25-xxx network-scripts]# pwd
> > /etc/sysconfig/network-scripts
> > 
> > [root at 12-254-25-xxx network-scripts]# cat
ifcfg-eth0
> > DEVICE=eth0
> > BOOTPROTO=dhcp
> > IPADDR=0.0.0.0
> > NETMASK=255.255.252.0
> > MACADDR=00:80:C8:4B:xx:xx
> > 
> > 
> > Hope that helps.
> > Mark
> > 
> > 
> 
> 
> 
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List:
http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667
channel=#colug
> 


__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com



More information about the LUG mailing list