21 Aug
2018
21 Aug
'18
10:57 a.m.
Hello All,
Have you noticed if you do a "C port Call" connect via a com port from Linux
JNOS window with your own (JNOS) call sign to BPQ, BPQ32 or XROUTER that the
connection is established but there is no further response in the connection
and seems to not respond any more.
However if you use another call sign via say Telnet or TNC via JNOS com
port, all works fine and the connection across the com port is established
and proceeds normally.
It makes it hard to test the configuration and have not gotten to the bottom
of it yet.
This has happened thru several versions of JNOS, but I am using similar
autoexec, etc files.
Any Ideas please?
Secondly, why does McAfee keep quarantining my WIN10 BPQ32.EXE file and also
the contents of downloaded BPQ32 EXE ZIP file from the official web site?
Thanks
Rob
Vk1kw
21 Aug
21 Aug
12:58 p.m.
Have you tried testing using a different ssid with your callsign
making the your callsign-ssid unique at each end.
de Paul
1:22 p.m.
Hi Paul,
It all works ok if I connect from the BPQ32 switch call sign vk1kw-5 to JNOS
vk1kw across the com port but not back the other way from the JNOS window as
vk1kw.
So on my JNOS I have only the entry window, the BBS/connect window and the
monitor window via F9. But nowhere can I change the JNOS ssid I am using
unless I actually change the JNOS gateway ssid.
It almost sounds like a permissions problem but if so it should never
connect.
Rob
-----Original Message-----
From: 44Net [mailto:44net-bounces+vk1kw=netspace.net.au@mailman.ampr.org] On
Behalf Of Paul
Sent: Tuesday, August 21, 2018 3:58 PM
To: 44net(a)mailman.ampr.org
Subject: Re: [44net] Strange Connect problem across Com ports to BPQ32 and
XROUTER
Have you tried testing using a different ssid with your callsign
making the your callsign-ssid unique at each end.
de Paul
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
2:04 p.m.
Hi Rob
As a test with my DOS (under WinXP pro JNOS111E, yep >18 years old
Kenwood THD7e in kiss mode on 70cms
ax25 mycall gb7cip
connect tnc0 gb7cip-7 (node)
Connected and looking on the node GB7CIP-7
and 70cm interface
Current users:
Uplink <GB7CIP on interface u432b> >idle etc
This is my experimental systems proving that
the Kenwood THD7E TS2000e TASCO modems (and other flavours of Kenwoods
can be made to work in it's limitations.
PS i'm a native linux person
I was given a challange to set-up dos jnos system for testing
a couple of months ago to assist with DOS JNOS support!!! hihi
as last used in 1993/94
The above may not be useful, as I have not tried it, accepted the challange
as had only used IP routing over the 70cm link.
Paul g4apl
4:48 p.m.
Hello All,
Thanks everyone for their help.
I have solved the problem! Yeeeh!
It turns out that after connecting from JNOS "mycall=vk1kw" via a com port to
BPQ32/XROUTER "call=vk1kw-5" further traffic seems to be ignored.
I changed JNOS mycall=vk1kw-1 did not fix.
I changed JNOS mycall=(my old call sign) did not fix - in fact the connection still used
vk1kw call sign to connect.
I changed AX25 BBSCALL from vk1kw to vk1kw-1 and fixed the problem. (Of course!)
So, JNOS ax25 bbscall cannot be the same as mycall.
This may also apply to ttycall and others.
It does not seem to affect TNC's.
Thanks again.
Rob
2316
days inactive
2316
days old
4 comments
2 participants
participants (2)
-
Paul -
vk1kw