Subject: Re: DHCP, Cable Modem and all that jazzzzz...help
To: Ken Nakata <kenn@synap.ne.jp>
From: None <mcmahill@mtl.mit.edu>
List: port-mac68k
Date: 02/28/1999 23:16:33
On Mon, 1 Mar 1999, Ken Nakata wrote:

> On Sun, 28 Feb 1999 17:09:10 -0500 (EST), mcmahill@mtl.mit.edu wrote:
> > oh.  hmmmm.  Is the 28.8 outgoing phone line modem built into the cable
> > modem?  How does it know where to dial to on the MacOS side?  Are you also
> > running FreePPP or something similar?
> 
> Unnecessary.  Those parameters (phone #, login, and password) can be
> and should be stored in the cable modem itself.  That's exactly how my
> ISDN dial-up router works when it dials out.  Remember, your box and
> cable modem aren't connected via point-to-point serial link.
I just wasn't sure if the cable modem or the OS handled the phone line.
But I now understand it to be the former.


> > this means your computer asked for configuration and didn't get a reply.
> > However, if it didn't dial, than clearly the server never got the request.
> 
> No, no.  It shouldn't dial out at all.  The cable modem *IS* the DHCP
> server on your LAN.
Really?  I'm suprised at this.  I guess I thought that the "real" DHCP
server was at the cable company and that the cable modem just provided the
physical interface and that a 2-way link was required for this initial
exchange.

> 
> > > Trying recorded lease <null address>
> > > /etc/dhclient-script: 175: Syntax error: end of file unexpected 
> > > (expecting "fi")
> 
> > I vaguely seem to recall seeing this once.  Sounds like a bug to me.
> > In fact looking at my dhclient-script I seem to have added a fi , 18 lines
> > up from the end (just before
> > 
> > ifconfig $interface inet -alias $new_ip_address $medium
> 
> Um, if it was broken, did you file a PR about it?

doh!  It was on my list of things to do, right after checking a newer
version of dhclient-script to make sure it hadn't already been fixed (I'm 
still running 1.3 on this particular machine).   Anyway, you've prompted
me to get with it and look in to it.  The version of
/etc/dhclient-script that came with NetBSD/mac68k-1.3 had this bug.  The
version I just grabbed from 

ftp://ftp.netbsd.org/pub/NetBSD/NetBSD-current/src/usr.sbin/dhcp/client/scripts/netbsd
# $NetBSD: netbsd,v 1.4 1999/02/03 00:19:00 tron Exp $

appears to have exactly the additional 'fi' I mentioned.  I guess this
means I shouldn't send-pr since it seems to be fixed in -current.

-Dan