[NCLUG] Cable @home questions

[Mark Smith]

Bill, 
I'm not exactly wure what's goin on, but my guess is that you've got the
modem workin in windows, but not linux.  Is that right?  Anyway, if it is,
something that might snag you is that @home requires you to already have a
hostname when requesting an ip via dhcp.  I don't think the name ever
changes (at least mine hasn't in 2 1/2 months), so what you can do if this
is the case is set up the hostname they have given you as the host of the
computer you're using.  It should be somethin like this:
<hostname>.ftclns1.co.home.com.
Also, I'm not sure how you're calling dhcp, but this is what I use:
/bin/dhcpcd eth0 -h <hostname>
The default line that came w/ the system I installed didn't work too well
w/ @home and I cut/pasted this from one (coyote linux) that did.
Hope that helps.  If not, let me know and maybe I can still answer any
qyestions you got :)

Mark



"Every revolution was first              "Kill the wabbit"
a thought in one man's mind." 
                     -R.W. Emerson	                   -E. Fudd
*---------------------------------------------------------------------------*
Mark c. Smith				 Markcs at CS.ColoState.EDU
Dept. Computer Science                   http://WWW.CS.ColoState.EDU/~markcs
Colorado State University		 (970)491-3505 (work)
*---------------------------------------------------------------------------*

On Wed, 11 Oct 2000, Bill Thorson wrote:

> 
> nclugers,
> 
> I got @home installed (my wife wanted it) and cannot seem to get it
> working.  It came with the Surfboard 3100 modem.  Since I live and work in a
> Microsoft free zone so their software doesn't help me at all.
> 
> Here are my symptoms after power on:
> 
>    1) Power light flashes and then turns green.
> 
>    2) Receive light flashes and then turns green.
> 
>    3) Send light flashes and then turns green.
> 
>    4) Online light flashes, flashes, flashes, ...
> 
> If I understand things correct the modem is trying to acquire it's
> IP address from the upstream DHCP server and cannot.  It this correct?
> If yes then it isn't my problem, right?
> 
> I've let the modem set up my nic card via DHCP and surfed to it's
> built-in web pages at http://192.168.100.1/.  All the status info
> I get it this:
> 
> 	Acquire Downstream Channel			Done
> 	Obtain Upstream Parameters			Done
> 	Establish IP Connectivity using DHCP		In Progress
> 
> And the logs say things like this:
> 
> 	5-Warning	D520.2		DHCP Attempt# 1 BkOff: 4s Tot DSC:1
> 					OFF:0 REQ:0 ACK:0
> 
> Then I though for awhile. "Dang, does the Winders software provide DHCP
> service to the modem?"  I've spend the last hour or so proving to myself
> that it doesn't because, using tcpdump,  I never saw a bootp packet head
> to my machine from the modem.  I did see the other direction from the
> dhcpcd I was running.
> 
> What am I doing wrong?  
> 
> Bill
> 
> _______________________________________________
> NCLUG mailing list
> NCLUG at nclug.org
> http://www.nclug.org/mailman/listinfo/nclug
>