Ok ... more information ... the problem is still with me. After looking 
at it more closely I can see exactly *what* is happening but not *why*.

What's happening is that as soon as I start my kissattach command, it 
*removes* all of the other directories under /proc/sys/net ... except 
for ax25! 

Just after a reboot .... before starting ax25 services ...

# cd /proc/sys/net
# ls -l 
total 0
dr-xr-xr-x   9 root     root            0 Aug  3 21:57 ./
dr-xr-xr-x   5 root     root            0 Aug  3 21:57 ../
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 802/
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 ax25/
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 core/
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 ethernet/
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 ipv4/
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 netrom/
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 unix/

The netrom directory is there as it should be ...

# ls -l netrom
total 0
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 ./
dr-xr-xr-x   9 root     root            0 Aug  3 21:57 ../
-rw-r--r--   1 root     root            0 Aug  3 21:57 default_path_quality
-rw-r--r--   1 root     root            0 Aug  3 21:57 link_fails_count
-rw-r--r--   1 root     root            0 Aug  3 21:57 network_ttl_initialiser
-rw-r--r--   1 root     root            0 Aug  3 21:57
obsolescence_count_initialiser
-rw-r--r--   1 root     root            0 Aug  3 21:57 routing_control
-rw-r--r--   1 root     root            0 Aug  3 21:57
transport_acknowledge_delay
-rw-r--r--   1 root     root            0 Aug  3 21:57 transport_busy_delay
-rw-r--r--   1 root     root            0 Aug  3 21:57 transport_maximum_tries
-rw-r--r--   1 root     root            0 Aug  3 21:57
transport_requested_window_size
-rw-r--r--   1 root     root            0 Aug  3 21:57 transport_timeout

Then just after I start the ax25 services ... *all* the other directories
go away except for ax25!

# ls -l
total 0
dr-xr-xr-x   3 root     root            0 Aug  3 21:57 ./
dr-xr-xr-x   5 root     root            0 Aug  3 21:57 ../
dr-xr-xr-x   2 root     root            0 Aug  3 21:57 ax25/

Here's what is in my ax startup file. I ran it line by line ... it's 
definately the kissattach command that is the culprit. 

#!/bin/sh

case $1 in
        start)
                ifconfig nr0 down
                echo "Attaching ax25 devices ..."
                /usr/sbin/kissattach -i 44.124.6.16 -m 512 /dev/ttyS1 ax0
                ifconfig ax0 netmask 255.0.0.0 broadcast 44.255.255.255 mtu 256
                route add -host 44.124.6.254 ax0
                route add -net 44.124.0.0 netmask 255.255.0.0 gw 44.124.6.254
# These seem to be working well with the Azden PCS4000 
                /usr/sbin/kissparms -p ax0 -f n -t 170 -s 10 -r 64 -l 50

                echo "Attaching netrom devices ..."
                /usr/sbin/nrattach -i 44.124.6.16 netrom
                ifconfig nr0 netmask 255.0.0.0 broadcast 44.255.255.255

                echo "Starting listening daemons ..."
                /usr/sbin/netromd -i -l
                /usr/sbin/ax25d -l
                /usr/sbin/ax25rtd
                /usr/sbin/mheardd -f
                ;;
        stop)
                kill `ps x | grep kissattach | cut -c1-5`
                kill `ps x | grep mheardd | cut -c1-5`
                kill `ps x | grep ax25d | cut -c1-5`
                kill `ps x | grep ax25rtd | cut -c1-5`
                kill `ps x | grep netromd | cut -c1-5`
                ifconfig nr0 down
                ;;
esac

Ok, now, anyone have a clue what's happening here? Thanks.

At 09:23 PM 8/3/99 -0700, you wrote:
>I just recently got ax25-utils-2.1.42a goiing on my Redhat 2.0.33
>kernel. Everything seems to be working great ... ax25, tcp/ip, and 
>netrom, except for one thing!
>
>netromd hears the broadcast routes that other stations are putting out,
>by they are not being saved. Apparently this is because of the following
>error that is logged (syslog) whenever one *is* heard ...
>
>netromr: cannot open /proc/sys/net/netrom/obsolescence_count_initialiser
>
>... and yes, I can see that the netrom hierarchy does not exist under 
>/proc/sys/net (but the ax25 one does).
>
>I'm stumped. nrattach work fine. netrom connections work fine. So does 
>node. The nrparms command works but puts it's entries into /proc/net/nr_neigh,
>when I thought they were supposed to go into nr_nodes?
>WHy in the world would netromd not be able to create the proper /proc/sys
>entries when ax25d (which is very similar in src code) can?
>
>Any ideas would be appreciated.
>
>I do have plans to go to RH 6.0 soon, but I wanted to get familiar with 
>all this stuff on what I already know runs well. 
>
>TIA
>--
>-= Brad Fisher =-  (PPSEL)                 I'm just   
>internet: [EMAIL PROTECTED]                 a       
>  packet: n7xss.amp.org (soon!)             wanna be   
>    http://www.scinetinc.com/~bradf/       UNIX guru!
>
>
--
-= Brad Fisher =-  (PPSEL)                 I'm just   
internet: [EMAIL PROTECTED]                 a       
  packet: n7xss.amp.org (soon!)             wanna be   
    http://www.scinetinc.com/~bradf/       UNIX guru!

Reply via email to