9 Mar
2017
9 Mar
'17
6:27 a.m.
Hi All,
Since compiling JNOS2.0 some years ago, I have always had problems with
Netrom transmits killing it back to the directory prompt.
I have been using JNOS1 version ? in its place for a long time because of
the same problem.
But today I downloaded and compiled the latest JNOS2.0k and have the very
same problem.
It all compiles ok on my Fedora (latest updates) it starts and runs
perfectly until it does a node transmit and dies immediately.
I can poke it with all the netrom commands until I do "netrom bcnodes port"
and it crashes.
It receives nodes ok and populates the list ok. It also does normal "Connect
XX VK1KW-5" ok.
So to try another idea, I removed all my netrom options from autoexec.nos
and used the defaults. (except interface /call/node name). Same problem and
crashed.
I notice also in this version, you need to type the whole word eg "connect"
vice "con" or "ifconfig" vice "ifc".
Maybe something in Fedora is not compiled in or is missing or I haven't read
enough yet.
There may be a conflict in my config.h but it's pretty much the same as
original.
So I am open to ideas.
Thanks in advance
Regards
Rob
Vk1kw
9 Mar
9 Mar
7:18 a.m.
Hello Rob.
From what you described, to me it looks like
there could be something messed up in your system.
For a VERY long time I had almost exactly
the same problem, even with JNOS-2.0j7.
Then it appeared I have same issue with JNOS-2.0k.
Searching for possible troublemaker I ended up
with compiling both versions on different machine.
Then I tested both binaries on my main desktop PC.
Both were performing just fine, amazingly!!!
I may send you binary file for i386
and/or amd64 architectures.
Just let me know which one you need.
Best regards.
--
Tom - SP2L
------------------------------------
It is nice to be important.
But it is more important to be nice!
On 09/03/17 12:27, vk1kw wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Hi All,
Since compiling JNOS2.0 some years ago, I have always had problems with
Netrom transmits killing it back to the directory prompt.
I have been using JNOS1 version ? in its place for a long time because of
the same problem.
But today I downloaded and compiled the latest JNOS2.0k and have the very
same problem.
It all compiles ok on my Fedora (latest updates) it starts and runs
perfectly until it does a node transmit and dies immediately.
I can poke it with all the netrom commands until I do "netrom bcnodes port"
and it crashes.
It receives nodes ok and populates the list ok. It also does normal "Connect
XX VK1KW-5" ok.
So to try another idea, I removed all my netrom options from autoexec.nos
and used the defaults. (except interface /call/node name). Same problem and
crashed.
I notice also in this version, you need to type the whole word eg "connect"
vice "con" or "ifconfig" vice "ifc".
Maybe something in Fedora is not compiled in or is missing or I haven't read
enough yet.
There may be a conflict in my config.h but it's pretty much the same as
original.
So I am open to ideas.
Thanks in advance
Regards
Rob
Vk1kw
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
8:05 a.m.
Hello Tom,
While it seems to jnos2.0k seems to compile ok it has one consistent syntax
warning several times but does make the jnos file ok it seems. But you may
be right and Fedora has its fingers in there somewhere.
There was no log file produced. I tried the debug procedure but gdb debug
only said "detaching after fork from child" and hung.
Please send me the i386 file if possible?
Vk1kw(a)netspace.net.au
Most appreciated Tom.
Thanks and Regards
Rob
-----Original Message-----
From: 44Net [mailto:44net-bounces+vk1kw=netspace.net.au@hamradio.ucsd.edu]
On Behalf Of SP2L
Sent: Thursday, March 09, 2017 11:18 PM
To: AMPRNet working group
Subject: Re: [44net] JNOS2.0K and Netrom problem
(Please trim inclusions from previous messages)
_______________________________________________
Hello Rob.
From what you described, to me it looks like there could be something
messed up in your system.
For a VERY long time I had almost exactly the same problem, even with
JNOS-2.0j7.
Then it appeared I have same issue with JNOS-2.0k.
Searching for possible troublemaker I ended up with compiling both versions
on different machine.
Then I tested both binaries on my main desktop PC.
Both were performing just fine, amazingly!!!
I may send you binary file for i386
and/or amd64 architectures.
Just let me know which one you need.
Best regards.
--
Tom - SP2L
------------------------------------
It is nice to be important.
But it is more important to be nice!
8:19 a.m.
Rob.
Already been sent to you directly.
Best regards.
--
Tom - SP2L
------------------------------------
It is nice to be important.
But it is more important to be nice!
7:41 a.m.
Hi Rob,
It receives nodes ok and populates the list ok. It
also does normal "Connect
XX VK1KW-5" ok.
from here:
?,A,B,C,CONV,D,E,F,H,I,IH,IP,J,K,L,M,N,NR,O,P,PI,R,S,T,U,V,W,X,Z >
n vk1kw-5
no such node
n i0ojj-3
Node Neighbour Port Qual Obs Usage Hops
(I)rtt
RMGATE:I0OJJ-3 QC105:VE2HAR-7 har 201 6/B 0 0 0
PKTNOD:VE2PKT-13 pkt 114 3/B 0 0 0
?,A,B,C,CONV,D,E,F,H,I,IH,IP,J,K,L,M,N,NR,O,P,PI,R,S,T,U,V,W,X,Z >
c i0ojj-3
Trying... The escape character is: CTRL-T
*** connected to RMGATE:I0OJJ-3
An advanced SICD ampr.org router/server
in Rome Italy - JN61LR @ i0ojj.ampr.org
Type H(elp) to access the server commands
13:38:12 09.03.17 I0OJJ de I0OJJ-3 =>
--
73, gus i0ojj
A proud member of linux team
3044
days inactive
3044
days old
5 comments
3 participants
participants (3)
-
Gustavo Ponza -
SP2L -
vk1kw