| |
KG6BAJ > SYSOP 11.03.14 01:05l 36 Lines 1231 Bytes #999 (0) @ WW
BID : 16751_KG6BAJ
Read: GUEST
Subj: JNOS to BPQ32 link - SOLVED
Path: IZ3LSV<IV3SCP<IW0QNL<JH4XSY<JS1FVG<JH9YMQ<JE7YGF<7M3TJZ<CX2SA<N6RME<
KG6BAJ
Sent: 140310/2349z @:KG6BAJ.#NCA.CA.USA.NOAM [Grass Valley] #:16753 $:16751_KG6
Thanks to all of you who responded willing to be a test
link for me.
I have discovered the link issue between my JNOS station and a
link partner who uses BPQ32. I have made a temporary work-around
for the issue.
For any of you who are linking from JNOS 2.0j (linux) to
BPQ32 (version 6.0.5.1) and your link is not stable and you
only seem to be able to connect from your jnos station to
your BPQ32 link parter via AX25, yet connecting via netrom fails,
the issue I found in my JNOS configuration was that I established
the link using 'name-based' routing and not 'ip-based' routing.
As soon as I changed from name-based to ip-based, the link became
stable and netrom connections were perfect.
As a footnote..... 'Yes', I do have the built-in timer to allow
for JNOS to become fully active before starting any of the
name-based links, so that JNOS's resolver is fully active.
Anyway, if you're having this issue, this could be your problem.
I have forwared this to Maiko for investigation.
I do *NOT* have John Wisemans contact info. But, hopefully this
bulletin will also find it
it's way to his box as well, so he may investigate BPQ32 as well.
Hope this helps any of you struggling with this issue.
73
Bill
KG6BAJ
Read previous mail | Read next mail
| |
