[NCLUG] Cable @home questions

[Matt Pujol]

Bill,

I have @home working well with Linux.  I didn't use DHCP, I went static IP.
Your static IP and the DNS info are listed on the install paperwork the
@home_guys had (I'm assuming) your wife sign.  The problem with their system is
it sometimes takes hours for the @home system to get all the routing info
propagated down the system for your new modem, and sometimes I think it never
happens.  The @home_guys always leave even if the modem doesn't come up
immediately.  They probably told your wife it would be up in an hour or so.
When they first installed my modem, it never worked on the network until I
called the 800 number and told the service person to "push my modem".  Then it
worked.  The operative phrase is "push the modem".  Apparently, it's a command
they initiate from the head end that forces all the downstream equipment to
recognize your modem.  If you get a service person who doesn't understand that
term, call back until you get one that does.

Regards,

Matt


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

--
/***********************
Matt Pujol
Product Marketing Manager
1394 and USB CoreWare Technologies

LSI Logic
2001 Danfield Court
Fort Collins, Co 80525
970-206-5816
matt.pujol at lsil.com
***********************/