Bernie,
All I can report is what Arachne did, or did not, do. And what other
programs reported about Arachne.
_______________________________________________
> It is included in Arachne. Let me quote.
> First from wattcp\src\readme.2nd:
> "The bootp code now supports dhcp."
-----------------------------------------------
First BOOTP doesn't support DHCP; DHCP supports BOOTP ... protocol says
it has to be backwards compatible with BOOTP. The change(s) made must
have been to bring BOOTP up to last standards before everything switched
to DHCP. Independent programs report that BOOTP was being used [not
DHCP].
______________________________________________________________________
> From changes.txt (1.60b1):
> Notes: 1.50 stable release was skipped due to release of new
> version of WATTCP library.
> Improvements: Arachne 1.60 beta is based on WATTCP release "9911"
> which should be faster, more stable, and it which supports DHCP.
>
> Finally from Arachne.Cfg:
> ;IP_Address BOOTP ... WatTcp attempts to use BOOTP protocol
----------------------------------------------------------------------
Second, using the Install wizard for EtherNet, the Arachne.cfg file was
set up as:
==================begin config file=========================
;This is ARACHNE.CFG for Arachne version 1.4+
;If you want to use Arachne on PC with CPU 486+ you should start here.
;(tested on AMD K5/133)
;This configuration file can be completely controled from Arachne setup.
;Run "setup" if you are not sure what to change in configuration file.
[profile]
Profile CABLE.ACF
Connection READY
Hangup NUL
;Connection @cmd ... command cmd will estabilish connection
;Connection READY ... connection is permanent, packet driver in AUTOEXEC...
;Connection NUL ... do not start TCP/IP (run "arachne -c" to force this)
[tcp/ip]
IP_Address BOOTP
IP_Grab IP address set to
NameServer 0.0.0.0
AltNameServer 0.0.0.0
Gateway 0.0.0.0
AltGateway 0.0.0.0
Netmask 0.0.0.0
;IP_Address n.n.n.n ... fixed IP address
;IP_Address PPP ... for PPP.EXE and PPPD.EXE (get address from
PPP.LOG)
;IP_Address BOOTP ... WatTcp attepmts to use BOOTP protocol
;IP_Address %enviro% ... Minuet style (enviroment variable, like %MYIP%)
;IP_Address WATTCP ... use ONLY values from TCPconfig (variable "my_ip")
;IP_Grab string ... prefix of IP address in PPP.LOG ("IP address set
to")
;TCPconfig filename ... name of WatTcp configuration file (often
WATTCP.CFG)
==== end of applicable cfg =====
Notice that there is no line in actual configuration for "TCPconfig
filename"; regardless of what the docs may say [they may not have been
updated], this configuration worked without ever attempting to access
WATTCP.CFG
More:
This is WATTCP.CFG as is currently sets on my HDD, as extracted from
Arachne 1.61
--------begin WATTCP.CFG
#
# To be used with Klos PPP - PPPWAT.EXE will modify this:
# Nameservers can be defined in ARACHNE.CFG
#
my_ip = 0.0.0.0
netmask = 255.255.255.0
gateway = 0.0.0.0
#
sockdelay=40
hostname=arachne
mss=512
-----------end WATTCP.CFG
Note that it file itself says it is for use with Klos PPP. BOOTP is
*not* Klos PPP. The values in the file have not been modifed, and if
the file had been accessed everything would have crashed. Why? Wrong
netmask, wrong gateway, and if packet size were limited to 512 [mss=512]
I wouldn't have gotten the speeds I have.
______________________________________________________________________
> Conclusion, you (as are we all) are using WatTCP (which is short for
> Waterloo TCP).
----------------------------------------------------------------------
Sorry, but the documentation you quote doesn't match the system
setup by Wizard.
It doesn't match for BOOTP [which I initially used because I knew
ISP was using DHCP], and it doesn't even apply to static IP.
If we are using Waterloo TCP, it's either invisible [not part of
the installation package] or has been included in its entirety
within Core.exe
_______________________________________________________________
> Please check what your TCPconfig line says (I'm on PPP here -
> PPPTCP.CFG is mine called)
> ;TCPconfig filename ... name of WatTcp configuration file
> (often WATTCP.CFG)
---------------------------------------------------------------
My current static IP configuration [also done via Ethernet Wizard] is:
===========begin applicable portion configuration file==================
[profile]
Profile CABLE3.ACF
Connection READY
Hangup NUL
;Connection @cmd ... command cmd will estabilish connection
;Connection READY ... connection is permanent, packet driver in
AUTOEXEC...
;Connection NUL ... do not start TCP/IP (run "arachne -c" to force
this)
[tcp/ip]
IP_Address 10.5.16.15
IP_Grab IP address set to
NameServer 207.40.122.15
AltNameServer 207.40.122.20
Gateway 10.5.1.1
AltGateway 0.0.0.0
Netmask 0.0.0.0
mss=4096
;IP_Address n.n.n.n ... fixed IP address
;IP_Address PPP ... for PPP.EXE and PPPD.EXE (get address from PPP.LOG)
;IP_Address BOOTP ... WatTcp attepmts to use BOOTP protocol
;IP_Address %enviro% ... Minuet style (enviroment variable, like %MYIP%)
;IP_Address WATTCP ... use ONLY values from TCPconfig (variable "my_ip")
;IP_Grab string ... prefix of IP address in PPP.LOG ("IP address set to")
;TCPconfig filename ... name of WatTcp configuration file (often WATTCP.CFG)
<snip to bottom line>
TCPconfig LANTCP.CFG
=============end applicable portion configuration file==========
This is LANTCP.CFG Regardless of the the Arachne.cfg says, nothing in
Arachne is using lantcp.cfg. Why? Read what the file says -- it's all
defaults and you can't use the defaults.
=========================begin lantcp.cfg================
#
# The following are options specific to Arachne Waterloo TCP for LAN.
#
# DO NOT USE THE DEFAULT VALUES OF THESE OPTIONS.
# Never guess IP numbers. If you are unsure, contact you local network
# administrator.
#
#############################################################################
## Don't write IP address to this file, if you are using Arachne - WWW browser
## for DOS. Write it to ARACHNE.CFG.
# netmask mandatory option, unless BOOTP
#
# netmask is simply your [sub]network mask. This value should never
# be 255.255.255.255
# Ask your local network administrator for the correct network mask if
# you do not know.
# If you use BOOTP as my_ip, you will not have to use netmask. Comment
# out the following line if you desire; if you do not comment
# the line out, use the correct netmask!
# If you use PPP dialer, the netmask is 0.0.0.0.
#netmask=?.?.?.?
# gateway mandatory option, unless BOOTP
#
# gateway is your local gateway. This value should be a valid IP number
# of another networked computer that your local network
# administrator calls your gateway.
# Ask your local network administrator for the correct gateway IP if
# you do not know.
# If you use BOOTP as my_ip, you will not have to use gateway. Comment
# out the following line if you desire; if you do not comment
# the line out, use the correct gateway IP!
# The esoteric use of gateway allows you to configure a routing table
# with up to 12 separate entries. Each entry must specify a
# gateway, an optional destination subnet, and then an optional
# subnet mask:
# gateway=0.0.0.0[, 0.0.0.0[, 0.0.0.0]]
# You may use the same gateway IP in each entry if need be.
#gateway=?.?.?.?
# nameserver mandatory option, unless BOOTP
#
# nameserver is a networked computer that can tell your computer an IP
# number of yet another networked computer. You can have up to
# 9 different nameserver entries, each assigned a different IP
# number. Waterloo TCP will go through the list of provided
# nameservers in order of appearance until a valid IP number
# is determined.
# Ask your local network administrator for the correct nameserver IPs if
# you do not know.
# If you use BOOTP as my_ip, you will not have to use nameserver.
# Comment out the following lines if you desire; if you do not
# comment the lines out, use correct nameserver IPs!
#nameserver=?.?.?.?
# domainslist mandatory option
#
# domainslist tells Waterloo TCP your domain. Afterwards, any computers
# specified without a full domain name will have the domainslist
# value appended to them.
# For best results, enclose the value of the domainslist entry within
# double quotes.
# Ask your local network administrator for the correct domain if you do
# not know.
#domainslist="arachne.cz"
# include optional
#
# include will simply insert another file's contents as if it were
# inside this configuration file at the line which the include
# directive resides.
# Only Waterloo TCP keywords will be recognized in the included file.
#include=c:\your_own.cfg
# bootp optional, esoteric
#
# bootp will use a specific bootp server by specifying the server's IP.
# If you are not using bootp or have no need to specify the exact bootp
# server then there will be no need to use to bootp keyword.
# Ask your local network administrator for the correct bootp server IP
# if you do not know.
#bootp=0.0.0.0
# bootpto optional
#
# bootpto specifies the amount of time that Waterloo TCP will wait for
# your bootp server to respond with your network information.
# The default timeout value is 30 seconds.
#bootpto=30
# ethip optional, esoteric
#
# ethip is used to allow use of multiple IP numbers within the same
# configuration file with each one being tied to a particular
# ethernet address.
# This is mainly for use of one big configuration file residing on a
# network that every user can use.
#ethip=00:00:00:00:00:00, 0.0.0.0
# hostname optional, unless BOOTP
#
# hostname allows you to give your computer a name while Waterloo TCP is
# active. Remote computers will recognize you by the hostname.
# Do not use another computer's name as your hostname.
# Do not append the domain to the hostname, it will be done for you
# by appending the entry in domainslist.
# BOOTP will provide a host name for you if used.
hostname=arachne
# sockdelay optional
#
# sockdelay allows you to specify a specific amount of seconds that
# Waterloo TCP will attempt to connect to a remote computer,
# wait for data from a remote computer, and wait to accomplish
# other miscellaneous networking tasks.
# The default is 30 seconds, but may be set longer if you have an
# especially slow connection.
sockdelay=40
# mss optional
#
# mss is the maximum segment size that Waterloo TCP can receive.
# The default value is believed to be at 1024.
# The maximum value should not exceed 4096.
mss=1024
=================end lantcp.cfg file======================
_______________________________________________
> RTFM (*.cfg) ;-)
-----------------------------------------------
Thank heavens the EtherNet Wizard made RTFM unnecessary [Well, that and
the help I got here.] If I'd actually had to READ [and follow what was
written] the funny manual, I *still* wouldn't be up and running on cable.
>> If I can't sent this or can't download, it may be because I went ahead
>> and put mss=4096 in the tcp/ip section of Arachne.cfg
________________________________________________________________________
> If you want to try something like that set mss=0 in arachne.cfg instead.
> //Bernie
------------------------------------------------------
You tryin' to get rid of me? Just for that I will, to see what happens!
l.d.
