Re: [Linux-decnet-user] [Kernel 2.4.0] ioctl:invalid argument

[Raimund H. <ra...@ba...>]

Thanks Steve and Ed,

Now I know more about the single steps, but I'm afraid of not
understanding the whole thing :-) 


On Tue, Aug 08, 2000 at 08:52:31PM +0100, Steve Whitehouse wrote:
> 
> with the 2.4.0 versions of DECnet you don't want to use the startnet
> script. You can set the files in /proc/sys/net/decnet/ using
> the echo command from the command line. The recommended way of
> setting the DECnet address is at boot on the LILO command line
> or at module load time (depending upon which method you use).

OK, I have also read about this in Documentation, but I was not shure
about the right time in the boot init. Now I modified the script
/etc/init.d/dnprogs (which comes with Debian package dnprogs). I
deleted the line with "startnet" and added two lines with the
echo command:
echo -n "1.177" > /proc/sys/net/decnet/node_address
echo -n "eth0" > /proc/sys/net/decnet/default_device

Now a "cat /proc/net/decnet_device show me the loopback and the
eth0 device. In the other place (/proc/sys/net/...) I can see the 
node address (1.177) but the node name is not there (only shown:???). 

When I try "sethost vax" ("vax" is node 1.1) then appears:
"no route to host".

> It is not recommended to load the module more than once (i.e. once
> loaded, don't unload it) as it will very likely cause a memory leak
> if you do.

I use DECnet support in 2.4.0 not as module.

In 2.2.14 I use Eduardos patch. I set the MAC address AA:00:04:00:B1:04
in the network scripts, when pcmcia is coming up and ifconfig -a shows
me also this hardware address.

Sorry for my stupid questions, but I'm a little bit confused of the
changes to 2.4.0. Is /etc/decnet.conf still valid or is it now obsolete?
Where to I set the other node (1.1) I want to contact to?

Thanks,
Raimund