[NTLUG:Discuss] AT&T@Home redux

[Richard Geoffrion]

Michael,

Is THIS the option to which you are referring?

man dhcpcd | grep hostname
       -h hostname
              specifies a string used for the hostname option field when
dhcpcd sends DHCP messages. Some DHCP servers
              require the hostname option field containing a specific string
in the DHCP messages from clients.

so a dhcpcd -h c12345-a  _should_ work?

I need to take a Linux box over to my m-in-law's and try this out. I
wondered how that AT&T required that name.

----- Original Message -----
From: "Michael Patrick" <michael at techiesplace.com>
To: <discuss at ntlug.org>
Sent: Wednesday, March 07, 2001 8:27 AM
Subject: Re: [NTLUG:Discuss] AT&T at Home redux


> Ian,
>
> I think you will find the issue is a little known DHCP client hostname
> field in the DHCP Request.  Try using the fully qualified domain name (or
> maybe even just hostname) they gave you.
>
> Michael
>
> At 20:46 2001-03-06 +0600, you wrote:
> >High speed Internet access has finally come to the technological back-
> >water of Valley Ranch.  Unfortunately it has come in the form of AT&T
> >@Home, so it looks like I now live in a Windows-only zone.
> >
> >I just schlepped my laptop over to the house of a friend who has the
> >service installed, and I verified that it is impossible to get an IP
> >address without the supplied NETBIOS name.  A quick test with Samba was
> >unsuccessful.
> >
> >Before I retreat to a cave in the mountains out of complete disgust, has
> >anyone been able to get this new variant of @Home working with Linux?
> >
> >Thanks!
> >--
> >========================================================================
> >Ian Pilcher                                       pilcher at concentric.net
> >========================================================================
> >_______________________________________________
> >http://ntlug.org/mailman/listinfo/discuss
>
> _______________________________________________
> http://ntlug.org/mailman/listinfo/discuss
>