Novell pro obyc.drate
Petr Rehor
REHO at decros.cz
Thu Jun 16 08:37:59 CEST 1994
> > > Pokial mate vsetko NOVELL v3.11, tak sa da pouzit IP-TUNNELing. Je
> > > v standardnej dodavke, jeho popis je v TCP/IP Transport Guide. Je
> >
> > V standartni dodavce NW 3.11 neni funkcni IP tunel. Funkcni se da
> > ziskat z NetWire, CD-ROM Novell Support Encyklopedia nebo z
>
> S tymto tvrdenim nemozem suhlasit. IP TUNNEL sme instalovali na
> 5 ethernet segmentoch z originalnych diskiet dodanych v standardnom
> baliku a ziadnu chybu sme nezisitli. Z aktualizovanych programov
> pouzivame len najnovsiu verziu ODI driverov, inac sme nic nemenili.
> Tiez sme nainstalovali IP TUNNEL z LAN WorkPlace for DOS na remote
> workstation a vsetko O.K.
> Ake chyby Vam to vlastne robi?
Asi jsem trochu prehnal, tvrzeni, ze IPTUNNEL neni funkcni. Je v nem
toliko jedna "drobna" chyba, ktera abenduje server pri fragmentaci
IP paketu. Prikladam original popis od Novellu pro novou verzi.
------
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: Update for TCPIP.NLM and IPTUNNEL.LAN
DOCUMENT ID: TID000396
DOCUMENT REVISION: A
DATE: 01JUL93
ALERT STATUS: Yellow
README FOR: TCP101.EXE
NOVELL PRODUCT AND VERSION:
TCP/IP 1.x
ABSTRACT:
This file contains the following fixes: (1) Fixes problem in
IPtunnel when IP packets were fragmented in the tunnel (2) Fixes a
bug in TPI that caused the server to crash when TCP received and
urgent update (3) Checks for proper specification of subnet mask
during the "BIND IP" command line and prints out warning messages
(4) The READ.ME file includes some warnings and document notes that
apply to TCP/IP v1.01.
_________________________________________________________________
DISCLAIMER:
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL. NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS
INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS
FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR IMPLIED
CLAIMS TO THE VALIDITY OF THIS INFORMATION.
Self-Extracting File Name: TCP101.EXE
Files Included Size Date Time
TCP101.TXT (This File)
IPCONFIG.NLM 6670 1-06-92 7:49p
IPTUNNEL.LAN 6061 1-06-92 8:01p
IPTUNNEL.TXT 1874 1-06-92 8:01p
TCPIP.NLM 173286 1-06-92 8:01p
TCPIP.TXT 1807 1-06-92 8:01p
PROTO.NLM 40241 1-06-92 7:49p
SNMP.NLM 13124 1-06-92 7:49p
SNMPLOG.NLM 8947 1-06-92 7:49p
TCPCON.NLM 160408 1-06-92 7:49p
Warnings and Documentation Notes in NetWare v3.11 TCP/IP Transport
Version 1.01 as of October 4th, 1991.
1. IPTunnel v1.0 had a bug which could crash the server if IP packets
were fragmented in the tunnel. This bug has been fixed in version
1.02 of IPTunnel.Lan.
2. TCPIP v1.01 now Checks for proper specification of the subnet mask
on the "IP bind" command line. As result, TCPIP may print one of the
following messages when subnet mask is improperly specified. These
messages are in addition to those listed in Appendix C of TCP/IP
Transport Supervisor's Guide.
"Warning: Subnetwork mask disagrees with mask used with <IP address>"
The subnet mask that you just specified is different from the mask
that was specified for the interface <IP address> that are attached
to the same IP network. Make sure that you are configuring subnets of
different sizes within an IP network. If the subnet masks are
different by mistake, you should unbind the interface with wrong
subnet mask and bind it again with correct value. Refer to section 2
for further recommendation.
"Fatal Error: Cannot support <IP address> with mask <subnet mask>
because it conflicts with <IP address 2> with mask <subnet mask 2>,
an address IP is already supporting on another interface. (Refer to
'Netware TCP/IP supervisor Guide' for information about conflicts
between subnets with different subnet masks"
This means that the subnet mask that you just specified is illegal.
Refer to section 2 for the recommendation. You should review your
subnet configurations and rebind the interfaces involved with correct
subnet masks.
"Fatal Error: This interface, <IP address>, is connected to the same
network as the network as the interface using address <IP address 2>.
TCPIP.NLM cannot support two interfaces to the same network"
TCPIP prints this message if the network (or subnet if subnetted)
number that is being assigned to the interface <IP address> is
already assigned to the interface <IP address 2>. You should
assign different network (subnet) number to each interface. the
network/subnet number is <IP address> bits masked with subnet mask of
the interface <IP address>.
"Fatal Error: <IP address> is a loopback network address"
The IP address that you just specified is reserved for the loopback
address. Obtain a legal IP address from the network administrator and
use it for the interface.
"Fatal Error: There are no network bits set in "<IP address>"
zero network number cannot be assigned to an IP network. get a valid
IP address with valid network and host number from the network
administrator.
"Fatal Error: <IP address> is illegal: host field is zero or all one"
Zero or all ones in a host part of the IP address is reserved and
cannot be assigned to an interface. Obtain a valid IP address with
with valid host number from the network adminstrator.
"Fatal Error: <IP address> is illegal: subnet field is zero or all
one"
Zero or all ones in the subnet number part of the IP address is
reserved and cannot be assigned to an interface. Obtain a valid IP
address with valid subnet number from the network administrator.
3. TCPIP allows subnets of the same network to have different subnet
masks, although there are several restrictions on what combinations
of masks can be used. TCPIP issues a warning when it detects such a
configuration to insure that that masks are intentionally different.
Novell does not recommend this type of configuration, as it requires
a great deal of IP expertise to set up the environment so that
packets can be successfully routed through the IP internet.
Furthermore, the RIP routing protocol cannot handle mixed subnet
masks, so NetWare cannot express the topology accurately to the rest
of the internet. (In such setups, manual configuration is required
for the participating nodes' routing databases).
--------
Warnings and Documentation Notes From Version 1.0 That Still Apply to
Version 1.01
4. Appendix A of "NetWare v3.11 TCP/IP Transport Supervisor's Guide"
refers to a compatible IP Tunnel product by Schneider & Koch which
uses UDP port 59139. The appendix recommends specifying port 59139
when loading a NetWare IP Tunnel to allow it to talk to the S&K
product. Beginning with version 1.3 of the S&K drivers, the S&K
product now uses the same UDP port as NetWare's IP Tunnel, port 213.
If you are using version 1.3 or later of the S&K drivers, you will
not need to specify the UDP port to the NetWare IP Tunnel; the IP
Tunnel's default port will be correct.
5. Appendix A also contains a sample NET.CFG file for setting up a
DOS IP Tunnel. The following two lines were omitted from that sample
file and should be added at the end of it:
Protocol IPX
Bind IPTunnel
6. The system will fail if the TCPIP.NLM is unloaded while any
application is actively using the AT&T Streams interface for TCP,
UDP, or IP communications. Currently, no Novell products use streams
to access TCP/IP, so you will not encounter this problem unless you
have installed add-on TCP/IP products on your system. If any such
application is present, TCP/IP will issue the following warning:
Warning: Some utilities have streams open to the TCP/IP protocols.
TCP/IP service to those utilities will be terminated, and SYSTEM
INTEGRITY MAY BE COMPROMISED. Unload module anyway? n
We strongly discourage you from unloading TCP/IP until you have found
the utilities using the streams interface and have unloaded them.
7. Under some conditions, a message something like the following
will appear when the TCPCON.NLM is unloaded:
2/1/91 12:05pm: 1.1.14 Module did not release 304 resources Module:
TCP/IP Console v1.00 (910215) Resource: Small memory allocations
Description: Alloc Short Term Memory (Bytes)
This message does not indicate a problem. It can be ignored.
--------------
Petr Rehor (rehor at decros.cz)
---------------------------------------------------------------------
DECROS Ltd. Tel/Fax: +42-38-33380
Skuherskeho 14 Tel: +42-38-34636
370 01 Ceske Budejovice Tel: +42-38-26690
Czech Republic Fax: +42-38-27872
ÿ
More information about the net
mailing list