The installation menu provides a prototype network number made from the
logical AND of your IP address and your netmask. If the user types in the
wrong netmask or overrides the prototype network number (which I think is
what happened here), they can get an incorrect value. I'll have to look at
this
> : NETWORK=129.186.31.38
>
> IPADDR as the same as the NETWORK address?? Strange, isn't it?
err, forgot about this in the message i just sent.
On these machines, i found that i had to use their own address as teh
network address, rather than the .0 address; otherwise they wouldn't
talk to anyt
> The reason the last "route add -net ${NETWORK}" is not working is that it
> is expecting a network address (ending in .0) and it is getting a host
> address instead. In the above example, change the "NETWORK=129.186.31.38"
> line to "NETWORK=129.186.31.0" and things should work. If this is i
On Wed, 12 Jun 1996, Rick Hawkins wrote:
> Under the beta releases with 1.3.9x, the following file is created:
>
> #! /bin/sh
> ifconfig lo 127.0.0.1
> route add 127.0.0.1
> IPADDR=129.186.31.38
> NETMASK=255.255.255.0
> NETWORK=129.186.31.38
> BROADCAST=129.186.31.255
> GATEWAY=129.186.31.
4 matches
Mail list logo
