<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I'm beating my head against this -- and Maiko is also noodling on
it -- but I am getting nowhere.</p>
<p>The quick version of my question is "Does anyone know why return
addresses are sometimes ABC%DEF.bbs@GHI and have that ".bbs" in
the middle rather than being ABC%DEF@GHI. Responding to such a
message (with the ".bbs") does not work if it's going to a remote
JNOS station -- the message is silently dropped with no reason
given ("FS -" response) and the sender is not notified.
(Responding to ABC%DEF@GHI does work.)<br>
</p>
<p>- - - - - - -<br>
</p>
<p>A friend and I have two JNOS BBS's operating here in San
Francisco (AA6AX and KJ6PTX) and want to pass messages back and
forth.</p>
<p>When he addresses a message to me aa6ax@AA6AX his JNOS sends it
out to my JNOS on the radio (he has a rewrite rule and forward.bbs
that take care of that), but then when I open it, the return
address is kj6ptx%kj6ptx.bbs@AA6AX.</p>
<p>All well and good, <u>except</u> for that ".bbs" in the middle,
and we have no idea where that came from. We believe it <u>should</u>
be kj6ptx%kj6ptx@AA6AX instead. The JNOS log itself shows the
correct return address <u>without the .bbs</u> in it. However,
that's just the log. Inside my JNOS "area" (aa6ax.ind) the message
is from kj6ptx%kj6ptx.bbs@AA6AX instead.<br>
</p>
<p>I also have rewrite and forward.bbs rules in place. My rewrite
is:</p>
<pre>*%*.bbs@AA6AX $1@$2 r</pre>
<p>My understanding is that this rule (REGEX) looks for
anything-percent-anything-dotBBS@AA6AX and then rewrites it <u>without
any .bbs in the rewritten string</u>.</p>
<p>If I check within JNOS, the rewrite seems to correctly analyze.<br>
</p>
<pre>jnos> rewrite kj6ptx%kj6ptx@AA6AX
to: kj6ptx_bbs
</pre>
<p>Note that this is <u>correct</u>. My rewrite and forward.bbs
rules say that messages to %KJ6PTX are to be queued in kj6ptx_bbs
(underscore, not dot) until sent.</p>
<p>When JNOS goes to send this message, however, it snags. JNOS at
AA6AX connects to JNOS at KJ6PTX and proposes a transfer, but the
destination address is KJ6PTX.BBS, and the JNOS at KJ6PTX rejects
this ("FS -") for reasons we don't understand, but anyway it is
rejected. So that's the issue...<br>
</p>
<pre>Wed Jul 8 12:04:26 2020 - vhf sent:
KISS: Port 0 Data
AX25: AA6AX-1->KJ6PTX-1 I NR=1 NS=0 pid=Text
<font color="red">0000 00 96 94 6c a0 a8 b0 e2 82 82 6c 82 b0 40 63 20 ...l (0b..l.0@c
0010 f0 5b 4a 4e 4f 53 2d 32 2e 30 6d 2d 42 31 46 48 p[JNOS-2.0m-B1FH
0020 49 4d 24 5d 0d 46 41 20 50 20 41 41 36 41 58 20 IM$].FA P AA6AX
0030 4b 4a 36 50 54 58 2e 42 42 53 20 4b 4a 36 50 54 KJ6PTX.BBS KJ6PT
0040 58 20 31 35 39 33 5f 41 41 36 41 58 20 34 30 35 X 1593_AA6AX 405
0050 0d 46 3e 0d .F>.</font></pre>
<pre>Wed Jul 8 12:04:30 2020 - vhf recv:
KISS: Port 0 Data
AX25: KJ6PTX-1->AA6AX-1 I NR=1 NS=1 pid=Text
<font color="blue">0000 00 82 82 6c 82 b0 40 e2 96 94 6c a0 a8 b0 63 22 ...l.0@b..l (0c"
0010 f0 46 53 20 2d 0d pFS -.</font></pre>
<p>First of all, am I understanding this correctly? Should I be able
to just "reply" to kj6ptx%kj6ptx.bbs@AA6AX and have the rewrite
rule route it correctly? Obviously it handles the overall message
using my rewrite and forward.bbs rules, but does nothing to the
"To:" inside the message, which retains the .bbs in it, which
presumably is why it won't transfer properly.</p>
<p>Second, is it possible that the JNOS on the receiving end should
be smarter and understand that "KJ6PTX.BBS" is in fact its own
name?</p>
<p>For the record, I have tried modifying these settings:<br>
</p>
<pre>bulletin return on|OFF
bulletin check on|OFF
</pre>
<p>which supposedly tells JNOS whether to pay attention to "R:"
information in bulletin routing, yet it makes no difference in how
these incoming messages are being handled. I still get the "%"
format and the ".bbs" in the return address.<br>
</p>
<p>This does not happen to return addresses to non-JNOS stations.
They are as expected and do not have this "%" nonsense in them.
This is JNOS being fussy with other JNOS systems. Or JNOS being
fussy with "R:" headers?<br>
</p>
<p>—Sky<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"Sky" (Jim Schuyler)
—Amateur Radio AA6AX
<a class="moz-txt-link-freetext" href="http://aa6ax.us/">http://aa6ax.us/</a></pre>
<div class="moz-cite-prefix">On 7/16/20 7:23 PM, Sky wrote:<br>
</div>
<blockquote type="cite"
cite="mid:05301c31-7346-08bb-46c3-c5c79328e988@aa6ax.us">
<pre class="moz-quote-pre" wrap="">Answers inline. If this isn't appropriate for this list, let me know.
—Sky/aa6ax
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
"Sky" (Jim Schuyler)
—Amateur Radio AA6AX
<a class="moz-txt-link-freetext" href="http://aa6ax.us/">http://aa6ax.us/</a>
On 7/16/20 5:11 PM, Bill Vodall wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">)
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">On Wed, Jul 15, 2020 at 11:31 AM Sky <a class="moz-txt-link-rfc2396E" href="mailto:sky@aa6ax.us"><sky@aa6ax.us></a> wrote:
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Hello Sky and the NOSBBS world...
Mesh continues to bring back the fun of packet - I know - the tunnel's
are cheating a bit but hey - with NPR and LORA coming soon we'll have
new tech that fills that missing 1 to 10 mile coverage at a useable
speed.
Yesterday as a zero pi day big time. I went from zero to three in a
couple hours. Having prepurchased the essentials worked out well.
The USB-Micro to 3 regular USB ports (and one with Ethernet) made it
easy to hook up the keyboard and mouse to get running.
The middle pi zero was a bit of an impediment. Worked on getting it
associated with the local WIFI for a hour before I noticed the missing
W (as in Wifi Wireless) on the circuit board. Plugged in the hub with
Ethernet and it came right up.
The associate at the end of the tunnel set up another PI for me this
morning. Since then I've compiled JNOS and delivered it over the
tunnel so it's running at the remote site. Thus leaving only the
minor task of configuring JNOS. If only I had a nickel for every
config change...
Lot's of history with JNOS and many historical config files but since
I'm starting fresh I'll take the packaged jnos installer for a test
ride.
(Hey Maiko - there's still a couple references to the jnosinstaller in
the Makefile...)
There isn't much happening on the MESH world - that's about to change
when JNOS gets running. Specially the web pages and even MRTG stats.
LINBPQ has more web interaction - but it's even harder to get going
than JNOS. I'll take it for a mesh test drive soon.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Hey, Bill ——
Compile was 100% easy.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Yes - copied the config.h.default - removed a couple defines not
needed for a pure IP environement and removed the two jnosinstalls.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">My JNOS appears at 192.168.2.2 on the Pi via the tunnel set up in autoexec.nos. So I can access any services there that are listening. Is this what you're asking?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">I'm expecting these jnos instances will use another 10. address on the
mesh. Kinda like the old 44 net days. That was my original
question. With 'real' linux the TUN interface allows connecting JNOS
(like a virtual machine) to the hosting Linux. Is that how you set
up your 192.168.2.2 interface.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">My 192.168.2.2 is configured in the autoexec.nos file. That's all I
know. –Sky
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I use home-built Python add-ons to knit my JNOS into other capabilities like email. I use regular email app (Claws Mail) to send and receive thru JNOS (like using Outpost PMM, but without the need to run Windows). There are a few glitches that are getting worked out, but basically this works really, really smoothly.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">That's where I hope this leads. It'll provide a locally hosted email
system I can access with Thunderbird or alpine - I think Alpine is the
client these days. I left ELM at the y2k and still miss it. NNTP
newsgroups, CONVER chat and the whole works - handled on a relatively
safe relatively quiet VPN'ish 10. net.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Precisely. This stuff should be easy enough for regular folk to use it.
I'm tired of going into an emergency simulation and taking 2 hours to
fiddle with parameters before the packet station can be up and running. —Sky
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">See <a class="moz-txt-link-freetext" href="https://SFWEM.NET/">https://SFWEM.NET/</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Are you hooked on the big AREDN test tunnel with around 600 stations?
Right now I want both - the big tunnel worldwide and a nice quiet
local net with friends. I picked up a Mikrotiq hAP (
<a class="moz-txt-link-freetext" href="https://amzn.to/3h80O1P">https://amzn.to/3h80O1P</a> ) for a full time tunnel server. I may get a
second one so I can be on both networks.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">SFWEM.NET is local with about 60 nodes. Tunnels are a problem as they
add too many nodes. —Sky
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">—Sky
—Amateur Radio AA6AX
<a class="moz-txt-link-freetext" href="http://aa6ax.us/">http://aa6ax.us/</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
</blockquote>
</body>
</html>