[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Novell och APT-källeval



...
> 1. Kan någon peka på bra dokumentation om hur man integrerar en GNU/Linux-burk 
> i ett Novell-nätverk? Nyare Novell-mjukvara verkar bygga på LDAP, men om så 
> inte är fallet? Finns det mjukvara som möjliggör det hela gratis?
...
> */ Christoffer Sawicki <qerub@home.se>

Har bara erfarenhet med Novell och ipx:

 fyra paket plus konfig i kärnan (ipx, ncpfs):
ipx - Utilities to configure the kernel ipx interface.
ipxripd - IPX RIP/SAP daemon
libncp - Shared library used by programs that use NetWare Core Protocol
ncpfs - Utilities to use resources from NetWare servers.

 $ dpkg -L ipx | grep /usr/sbin/
 /usr/sbin/ipx_configure
 /usr/sbin/ipx_interface
 /usr/sbin/ipx_internal_net
 /usr/sbin/ipx_route
 /usr/sbin/ipx_cmd

Se även bifogad ipx.conf.

ipxripd är praktisk att anvdända om du ska routa ipxtrafik mellan flera
nätverk.

 $ dpkg -L ncpfs | grep /usr/bin/ | pr -3 -t          
 /usr/bin/nwsfind        /usr/bin/nwbocreate     /usr/bin/nwauth
 /usr/bin/ncpmount       /usr/bin/nwborm         /usr/bin/nwfstime
 /usr/bin/ncpumount      /usr/bin/nwboprops      /usr/bin/nwvolinfo
 /usr/bin/ncplogin       /usr/bin/pqstat         /usr/bin/nwtrustee
 /usr/bin/ncpmap         /usr/bin/pqrm           /usr/bin/nwdir
 /usr/bin/slist          /usr/bin/nwbpcreate     /usr/bin/nwfsctrl
 /usr/bin/pqlist         /usr/bin/nwbprm         /usr/bin/ncopy
 /usr/bin/nwfsinfo       /usr/bin/nwbpvalues     /usr/bin/nwtrustee2
 /usr/bin/pserver        /usr/bin/nwbpadd        /usr/bin/nwpurge
 /usr/bin/nprint         /usr/bin/nwbpset        /usr/bin/nwrights
 /usr/bin/nsend          /usr/bin/nwgrant        /usr/bin/nwdpvalues
 /usr/bin/nwpasswd       /usr/bin/nwrevoke       /usr/bin/ncplogout
 /usr/bin/nwbols         /usr/bin/nwuserlist

Exempelvis:
 slist - Lists available NetWare Servers
 nwsfind - Find a NetWare Server
 ncpmount, mount.ncp - mount volume(s) from a specified NetWare fileserver.
   ncpmounts mansida nämner även tcp

Bindery:
 nwbols - List NetWare Bindery Objects
 nwbpset - Create a bindery property or set its value

NDS:
 nwgrant - Add Trustee Rights to a directory
 nwtrustee - List an object's trustee directory assignments

Om du vill ha en novellserver på din linuxburk, kan du prova marsnwe:
http://systemhaus.gkdmedien.de/mars_nwe/
Senast jag provade emulerade den en 3.11 server.

Hälsningar,
/Karl

-----------------------------------------------------------------------
Karl Hammar                    Aspö Data           karl@kalle.csb.ki.se
Lilla Aspö 2340                                                 Nätverk
S-742 94 Östhammar            0173 140 57            Datorer/Utrustning
Sweden                       070 511 97 84        Linux/Unix konsulting
-----------------------------------------------------------------------

#!/bin/sh
# Choose one:

case "$1" in
list)
  # see the result
  echo
  for i in /proc/net/ipx*
  do
    echo "**** $i:"
    cat $i
    echo
  done
  ;;
stop)
  ipx_configure --auto_primary=off --auto_interface=off
  ipx_interface delall
  ;;
start)
  #IPX_AUTO=yes	# autodetect everything
		# for a client and/or a server without a internal net
		# if there are multiple frame types running on your cable
		# you might see collisions due to that in your logs
		# stick to one frame type on your Novell servers if possible

  IPX_AUTO=no	# set up all things yourself
		# like a std. Novell server or for an ipx router


#-----------------------------------------------------------

  if [ "$IPX_AUTO" == "yes" ]
  then

    ipx_configure --auto_primary=on --auto_interface=on

  else

    ipx_internal_net add  ffff0002  1

    ipx_interface    add  eth0  EtherII  1
    #ipx_interface    add  eth1  802.2    2

  fi
fi
  ;;
esac
exit 0

###############################################################################

  How to config


Set up the optional internal network

   ipx_internal_net add  a  b

arg a: your internal net number
arg b: your node number on that internal net, use 1

Set up real networks

   ipx_interface add      a  b  c
   ipx_interface add  -p  a  b  c

arg a: networkt device, eth0, eth1, ppp0, ...
arg b: frame type, either 802.2, 802.3 or EtherII
arg c: a uniq net number

-p: make this interface the primary interface
    don't use this if you have set up the internal net,
    it has the primary interface
    you must have one and only one primary interface

Auto config, an alternative to ipx_interface

   ipx_configure --auto_primary=a --auto_interface=b

arg a: on or off, assign automatically the primary interface if not set, use on
arg b: on or off, listen on every NIC and do automatically the ipx_interface
       stuff when new kind of ipx traffic is seen

Set up routing manually (why not install ipxripd instead)

   ipx_route add  a  b  c

arg a: target_network
arg b: router_network
arg c: router_node


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

  The possible things used during configure are:

net  number: a  8 digit hex (4 bytes) integer, 0 to ffffffff
node number: a 12 digit hex (6 bytes) integer, 0 to ffffffffffff
frame type:  either 802.2, 802.3, SNAP, 802.2TR or EtherII
device:      e.g. eth0, eth1, ppp0
do you want to use a internal net or not

  Node numbers are easy, they are the same as the ethernet address of your NIC,
except for the internal net which don't have any NIC's.
Use node number 1 (or whatever you like, except 0 and ffffffffffff
which are reserved) for the internal net.

  Net numbers are trickier, and each net must have a uniqe number (for your
collection of nets). There are internal nets and external nets.

External nets have two qualities,
  1, which network (which cables, hubs, etc.) your NIC is connected to
  2, which frame type used on that cable
That means you can have e.g. two ipx nets on the same cable, using different
frame types.

All machines accessing the same network using the same frame type
must use the same net number

All machines not using the same network or not using the same frame type
must use different net numbers, otherwise they will confuse other machines.

Internal nets are used by Novell servers and ipx routers.
Such an machine have one single internal net. When you do slist, it will show
you the internal net number of the Novell servers.

  Frame type, if possible stick to one frame type for all your ipx nets.
802.2 is the current default for Novell products, Tcp/Ip uses EtherII.
Avoid 802.3, SNAP and 802.2TR.

  Device is as reported by 'ifconfig' or 'cat /proc/net/dev'

  Do you want to use an internal net?
For an ipx router:     yes
For an ipx fileserver: yes
For an ipx client:     no

The internal net is there to simplify routing, see IPX-HOWTO for more details.
If you want to use an internal net, you must enable it in the kernel by
adding CONFIG_IPX_INTERN=y to /usr{/local,}/src/kernel-source-x.x.x/.config
(2.0.x make *config scripts don't give you the choise) and recompile.

Reply to: