|
From: Steven W. <st...@gw...> - 2001-11-07 15:43:52
|
Hi,
>
>
> 1 i am download new redhat 7.2 distribution with kernel 2.4
> 2. i am install on new system with asus maiboard, ATA100, Vanta, 2 x
> D-link 220 ethernet cards with AUI, BNC, UTP support, also i have HUB with
> AUI, BNC, UTP
>
> 3. with original kernel everything is ok both card work fine
> 4. PCT/IP network is ok
> 5. I am bulid new kernel from manuals from sourceforge
>
> - make xconfig
> - DECnet support (m)
> - DECnet SIOCGIFCONF (y)
^ Are you 100% sure of this ? I suspect that you want
to say n here, but I don't think this is the cause
of the problem that you report.
> - SYSCTL support (y)
> - /proc file system support
>
[some more config commands snipped...]
The rest of your config looks fine.
>
> on booting only one card is live eth0 no eth1
>
> after changing in /etc/grub.conf
>
> kernel /boot/bzImage etc ether=3,0x300,eth0 ether=4,0x320,eth1
> it is look like ok both of cards are one TCP/IP network live
>
> what about DECnet ?
> file
>
> /etc/decnet.conf - properly configured
>
> after that i am download dnprogs-2.16 with a lot of troubles
> i thin i am install this package if i try rpm or tar.gz there are some
> errors on compile missed some files or what. what ever i am install
> dnprogs with rpm package on other linux 2.2.14 computer and manualy copy
> bin files on 2.4 linux
>
> well it's look as ok
>
The dnprogs package uses the kernel source for a header file. You need to
check that you compiled it on the same version of the kernel (2.2 vs. 2.4)
as you are using it on.
> script /etc/rc.d/init.d/decnet work properly
>
> in scripts
> /etc/sysconfig/network-scripts/ifcfg-eth0 and ifcfg-eth1
> i am put on the end of files lines
>
> MACADDR=00:80:C8:2C:E4:C4 (eth0)
> MACADDR=00:80:C8:2C:e4:A2 (eth1)
^^^^^^^^^^^^^^^^^ These don't conform to the DECnet standard for MAC
addresses, which is why your ethernet card is not
automatically recognised. The howto explains how
these should be set I think (its a while since I
looked at it :-)
>
> configuration of /etc/decnet.conf is as folow:
>
> executor 1.1 name veseli line eth0
>
> now on end ow /etc/rc.d/init.d/decnet script i was added
>
> echo "1.10" > /proc/sys/net/decnet/node_address
> echo "eth0" > /proc/sys/net/decnet/default_device
>
> i am put this two line on several startup scripts with hope an\bout
> working :)
>
> after rebooting of computer i have situation as folow
>
> in /proc/sys/net
>
> node_name:
> ???
This is fine. Its just a place for userland to lookup and read the nodename,
so it can be set by you if you want to use it.
> default_device:
> (nothing)
This ought to be set to the ethernet card which you want to use in the case that
there are no known routes in your neighbour cache to a particular destination.
The DECnet specification which covers routing will explain this in more detail,
but it will only be looked at as a fall back.
> node_address:
> 1.10
This looks fine. Your node address has been set correctly.
> debug:
> 0
> di_count, dr_count:
> 3
>
> dn_count:
> 1
> dst_gc_interval
> 2
> time_wait:30
>
All these are fine too.
>
> /config
>
> forwarding:
> (nothing)
> priority:
> 0
> t2:
> 1
> t3:
> 10
>
These are fine as well.
> /proc/net
> decnet_dev:
>
> Name Flags T1 Timer1 T3 Timer3 Blksize Pri State
> lo B 0000 0000 0002 0010 1498 000 00
> DevType Router Peer
> loopback
>
decnet_dev would have eth0 and/or eth1 in it had those cards been recognised
(see above comment about the MAC address). You won't be able to specify any
device as the default device unless it is listed in this table. The lo
device, just like TCP/IP is used for communication via DECnet within the
node itself.
> decnet_neigh:
> Addr Flags State Use Blksize Dev
> 1.10 --- 40 01 0001498 lo
>
This entry means that the node is able to see packets being sent over loopback.
On a real DECnet network, you should see entries for every host which is
directly attached to your physical network.
> decnet_cach:
> (nothing)
>
> decnet:
> local Remote
> 0.0/2014 0001:001 0000:0000 2 29 0.0/0000 0000:0000 0000:0000 2 0
> OPEN IMM ED
> 0.0 /2012 0001:0001 0000:0000 2 29 0.0/0000 0000:0000 0000:0000 2 0
> open imm ed etc.
>
This shows that your DECnet network daemons have started up ok.
> i am modify file /etc/rc.d/inet.d/decnet
>
> interfaces="eth0"
> startnet = "$prefix/sbin/startnet -hw $interfaces"
>
> and i have started phonetd
>
> when i try dnping veseli
> no route to host
>
> it is loo like is not in function
>
This is caused by the lack of a default route I think (as above).
> i am scare to go on real DECnet network and put my linux box, and DECnet
> is not in function
>
> How i can resolve my problems ? Mybe i am do something wrong ? I don't
> know ?
>
Well I'd be rather surprised if you could cause any problems with adding
a Linux DECnet box to a network unless you have configured it with a
duplicate address of another box on the network. You are pretty close
to having it working correctly though,
Steve
|
