109 lines
6.1 KiB
HTML
109 lines
6.1 KiB
HTML
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
|
|
<HTML>
|
|
<HEAD>
|
|
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
|
|
<TITLE>Linux IPX-HOWTO: Some Frequently Asked Questions</TITLE>
|
|
<LINK HREF="IPX-HOWTO-18.html" REL=next>
|
|
<LINK HREF="IPX-HOWTO-16.html" REL=previous>
|
|
<LINK HREF="IPX-HOWTO.html#toc17" REL=contents>
|
|
</HEAD>
|
|
<BODY>
|
|
<A HREF="IPX-HOWTO-18.html">Next</A>
|
|
<A HREF="IPX-HOWTO-16.html">Previous</A>
|
|
<A HREF="IPX-HOWTO.html#toc17">Contents</A>
|
|
<HR>
|
|
<H2><A NAME="s17">17. Some Frequently Asked Questions</A></H2>
|
|
|
|
<P>
|
|
<DL>
|
|
<DT><B>Where can I find commercially supported IPX software for Linux ?</B><DD><P>The Caldera Corporation offers a fully licensed and fully supported
|
|
Netware 3.x and 4.x client. You can obtain information about it from the
|
|
<A HREF="http://www.caldera.com/">Caldera Inc Web Server</A>.
|
|
<P>
|
|
<DT><B>Does the IPX software work with Arcnet/Token Ring/etc. ?</B><DD><P>The Linux IPX software does work with ArcNet and Token Ring interfaces.
|
|
I haven't heard of anyone trying it with AX.25 yet. Configuration is the same
|
|
as for configuring for ethernet except you will have to substitute appropriate
|
|
device names in place of 'eth0' and appopriate hardware addresses where
|
|
necessary.
|
|
<P>
|
|
<DT><B>How do I configure more than one IPX interface ?</B><DD><P>If you have more than one interface in your machine you should use the
|
|
<EM>ipx_interface</EM> command to manually configure each one, you should not
|
|
use the `plug n play' configuration.
|
|
<P>
|
|
<DT><B>How do I choose IPX addresses ?</B><DD><P>IPX networking is similar, but not identical to, IP networking. A major
|
|
difference is the way that addresses are used. IPX does not use the concept
|
|
of subnetworking and so the sort of associations that you have between network
|
|
addresses and networks is different. The rules are fairly simple:
|
|
<UL>
|
|
<LI>Every IPX network address must be unique on a wide area network. This
|
|
includes Internal Network Addresses. Many organisations using IPX over a wide
|
|
area network will have some sort of addressing standard that you should follow.</LI>
|
|
<LI>Every Host address on an individual network must be unique. This means
|
|
that every host on each IPX network must have a uniquely assigned address. In
|
|
the case of ethernet network this isn't difficult as the cards each have a
|
|
unique address. In the case of IPX/PPP this means you must ensure that you
|
|
allocate unique addresses to all hosts on the network, irrespective of which
|
|
end of the link(s) they are connected. Host address do not need to be unique
|
|
across a wide area network as the network address is used in combination with
|
|
the host address to uniquely identify a host.</LI>
|
|
</UL>
|
|
<P>
|
|
<DT><B>What are frame types, which should I use ?</B><DD><P>There are a variety of frame types in use over which you can run IPX.
|
|
The most common of these are described in the 'common terms' section of this
|
|
document (under the `<CODE>Frame Type</CODE> entry').
|
|
<P>If you are installing your machine on an existing network then you must use
|
|
whatever is already in use to allow you to interwork with the other hosts on
|
|
the network, but if the installation is a brand new network you can use any
|
|
of a range of protocols to carry your IPX traffic. My recommendation if you
|
|
are configuring a brand new network and you need to carry both IPX and IP
|
|
traffic is to use the <CODE>Ethernet_II</CODE> frame type.
|
|
<P>
|
|
<DT><B>My Windows95 machines mess up my frame type autodetection ?</B><DD><P>Apparently they can, yeah. I could make nasty comments, but instead
|
|
I'll just suggest that you use the manual frame type configuration instead
|
|
of the automatic one. It is probably the better way anyway.
|
|
<P>
|
|
<DT><B>Why do I get the message `invalid argument' when I configure IPX ?</B><DD><P>You are probably not running a kernel that supports IPX, either recompile
|
|
your kernel so it does, or double check that you have actually used lilo to
|
|
install and run the new kernel.
|
|
<P>
|
|
<DT><B>Why do I get the message `package not installed' when I configure IPX ?</B><DD><P>You are probably not running a kernel that supports IPX, either recompile
|
|
your kernel so it does, or double check that you have actually used lilo to
|
|
install and run the new kernel.
|
|
<P>
|
|
<DT><B>Why do I get the message `IPX support not in kernel' from <EM>pppd</EM> ?</B><DD><P>You've probably compiled IPX as a module and not ensured that it was
|
|
loaded before started <EM>pppd</EM>.
|
|
<P>
|
|
<DT><B>How do I NFS export a mounted NCP filesystem ?</B><DD><P>To use NFS to export an NCP filesystem you must mount it using the
|
|
<EM>ncpmount</EM> <CODE>-V</CODE> option. This option allows you to mount only
|
|
one volume of a fileserver instead of the usual mounting of all of them.
|
|
When you do this your NFS daemon will allow you to export that filesystem in
|
|
the usual way.
|
|
<P>
|
|
<DT><B>Why doesn't slist work when I have an internel network with mars_nwe ?</B><DD><P>You must have the get nearest server enabled. That is, entry 401 in
|
|
/etc/nwserv.conf should be 0 unless you have a reason for not responding
|
|
to get nearest servers. If you just want slist to work and not respond to
|
|
every get nearest server request, include your internal network and node
|
|
number in /etc/nwserv.stations and set entry 401 in /etc/nwserv.conf to 2.
|
|
<P>
|
|
<DT><B>Does ncpfs package work with mars_nwe ?</B><DD><P>Martin and Volker's code is slowly beginning to converge. Recent versions
|
|
of <EM>mars_nwe</EM> have an option to enable it to work with <EM>ncpfs</EM>.
|
|
You must enable the <CODE>WITH_NAME_SPACE_CALLS</CODE> in the <EM>mars_nwe</EM>
|
|
<CODE>config.h</CODE> file.
|
|
<P>
|
|
<DT><B>Is there any free DOS software to work with mars_nwe ?</B><DD><P>A contrived question deserves a contrived answer. I'm glad you asked,
|
|
Martin has a package that he distributes alongside his <EM>mars_nwe</EM>
|
|
package that offers free DOS client support for the <EM>mars_nwe</EM> server.
|
|
You can find it at the same sites as the server, and it will be called
|
|
<CODE>mars_dosutils-0.01.tgz</CODE>. It includes C source code for programs such
|
|
as <EM>slist.exe</EM>, <EM>login.exe</EM>, <EM>map.exe</EM> etc. The source
|
|
is compilable with Borland(tm) C.
|
|
<P>
|
|
</DL>
|
|
<P>
|
|
<HR>
|
|
<A HREF="IPX-HOWTO-18.html">Next</A>
|
|
<A HREF="IPX-HOWTO-16.html">Previous</A>
|
|
<A HREF="IPX-HOWTO.html#toc17">Contents</A>
|
|
</BODY>
|
|
</HTML>
|