[lug] Very odd, not really linux question -- WATT 32, AT&T at home

[Zichary O`Tea]

I tried posting this on the wttcp list, but I didn't get much of a
response..  Well..  actually, I didn't get a response.  So, if any of you
can help me out, that would be great. 

BTW watt 32 is a TCP/IP package for dos.  I'm trying to set up a
unix-like box using some of the Tools in watt 32, Boa, Seal 2, and FreeDOS

Watt-32: http://www.bgnett.no/~giva/
BOA: http://www.geocities.com/SiliconValley/Network/8907/boa_dos.html
Seal 2: http://sealsystem.sourceforge.net/
FreeDOS: http://www.freedos.org

-------------------------------------------------------------------------

Date: Wed, 14 Nov 2001 05:48:34 -0700 (MST)
To: watt-32 at yahoogroups.com
Subject: TCPINFO and AT&T at Home

Hey watt-32,

I'm trying to use Watt 32 with the AT&T at home network.  AT&T at home has a
funny way of identifying its members.  It requires each computer to use a
host name generated by them to identify themselves to the network.
Windows users only need to change their computer's name, to the host name
they've generated.  Unix users can use pump or dhcpcd with the -h option,
(i.e. dhcpcd -h "c1234567-a").

Although I can set my hostname in wattcp.cfg, it appears that when my host
name is sent durning the DHCP DISCOVER process, it appears as a "fully
qualified" host name, i.e. c1234567-a.your.domain.name. Because of this,
it seems that the AT&T at home sever won't respond.

Has anyone else sucessfully used watt 32 with at&t at home?  Is there away to
stop the DHCP client from reporting a fully qualified host name?