Re: [Linux-decnet-user] 2.4.0 kernel

[Patrick C. <pa...@pa...>]

On Tue, Aug 22, 2000 at 06:53:20AM -0700, ecc wrote:
> 
> I am experiencing a problem with the 2.4.0 kernel (sorry don't know the
> release)
> It appears that I can use Decnet out of my linux box, but not into it.
> 
> I thought it was my changes and have tried to find the cause, but I
> reinstalled the original dnprogs-2.05 with the same result.
> 
> Tcpdump shows the connection attempts with no response from Linux, but
> from Linux I can sethost to vax.
> 
> Is there something I may have missed in setting up the new kernel?
> I am running decnet as a module ( never did before), but cat
> /proc/modules shows "decnet  59016 0" (the zero worries me).
> 
> Insmod decnet, replies module already exists.
> Per Steve we do not need to "startnet", and it did not make any
> difference when I did.(Steve: I thought maybe I needed it for module
> decnet)
> 
> I will try to recompile in the kernel. My prerelease built itself like
> this, so if it really is an issue others will have the same experience.

That is odd, my 2.4 kernels have all been fine since test3 and I've just tried
test7 and that's OK too.

I know you don't want to hear me say this but which compiler are you using to
compile 2.4.0? I had problems with 2.7.2 so switched to 2.95.2 and that seems
better. Mind you, the kernel doesn't compile at all with 2.7.2 so you'd probably
notice that!

The zero on the end of the modules line should only worry you if you have a
DECnet server running. in which case it hasn't opened the socket correctly. Try
stracing the server and see what it says - there may also be a failure message
in syslog.

Finally (and you knew I was going to say this) make sure your dnprogs are
compiled against the right kernel...

patrick