(FWD)linux, cable modem, and RCN

[Michael Dinsmore]

Seeing how I was the one asking this not too long ago, I figured I better
reply.  It ended up being pretty simple in the end -- but I have not tried
it since they came and changed my modem -- RCN no longer uses hybrid modems
like they used to, but now use digital modems.   They changed mine around a
couple of weeks ago and the installer mentioned that anyone with a hybrid
modem wouldn't be work once thye finished switching it around.  I promise to
rebot my  Linux box (too much time at work lately to turn my computer on at
home) and verify that its still simple to get going (after getting all the
expert advice on this mailing list, that is).
Regards,
Michael


----- Original Message -----
From: "Derek Atkins" <warlord at MIT.EDU>
To: "John Chambers" <jc at trillian.mit.edu>
Cc: <discuss at Blu.Org>
Sent: Tuesday, February 06, 2001 1:25 PM
Subject: Re: (FWD)linux, cable modem, and RCN


> As I said, pump _just worked_ for me with RCN.  The installers come,
> plug everything in, and then they turn the stuff on.  They wait a
> couple minutes for everything to sync up.  They may call back to the
> home office to make sure stuff is turned on.  Then you plug-in, "turn
> on your machine" (e.g.  run pump), and you should be on the net.  Just
> do this part yourself and ask them what they want to test.  Generally
> you can prove you're on the net by going to some web page (or pinging
> something).
>
> Also, pump logs to daemon.* so you probably want to put this in
> syslog.conf:
>
> daemon.debug /var/log/debug.log
>
> -derek
>
> John Chambers <jc at trillian.mit.edu> writes:
>
> > | VA uses Red Hat -- you should have 'pump' installed.  And Pump works
> > | fine for me on my RCN cablemodem.
> >
> > Hey, thanks for the clue! I hadn't noticed pump, and its name doesn't
> > exactly attract they eye when looking for dhcp stuff.
> >
> > Now on to the next question.   To  try  to  get  at  least  minimally
> > prepared, I noticed the comment in "man pump" that it writes a lot of
> > stuff to syslog at the debug level.  Ok, I thoug;  I'll  just  add  a
> > couple of lines to /etc/syslog.conf:
> >
> > # DHCP client [jc]
> > dhcp,pump.debug                     /var/log/dhcp.log
> >
> > I then did the obvious
> > : touch /var/log/dhcp.log
> > : /etc/rc.d/init.d/syslog restart
> > : pump -i eth0
> >
> > It failed as I'd expect, since  eth0  is  there  and  alive  but  not
> > physically connected to anything but a dust bunny. Absolutely nothing
> > got written to /var/log/dhcp.log, though you'd expect at least a line
> > about the failure. The /var/log/messages file did grow, but only with
> > syslog and kernel messages, as you'd expect.  Nothing from pump.
> >
> > What am I doing wrong here?  (I note that "man syslogd.conf"  is  not
> > very  informative  as  to  just what goes before the dot in the first
> > field.   I  thought  that  "dhcp"  and  "pump"   oughta   cover   the
> > possibilities in this case, but apparently not. When I need to use it
> > for real, it might be nice if I can get a lot of info about why  it's
> > failing (which is of course the expected behavior).
> >
> > Is there a way to verify this sort of thing beforehand?  Or will I be
> > stuck  with  just  sending  out  a  "Help!"  message  after  the  RCN
> > installers are long gone?
> >
>
> --
>        Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
>        Member, MIT Student Information Processing Board  (SIPB)
>        URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
>        warlord at MIT.EDU                        PGP key available
> -
> Subcription/unsubscription/info requests: send e-mail with
> "subscribe", "unsubscribe", or "info" on the first line of the
> message body to discuss-request at blu.org (Subject line is ignored).
>
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).