John J. Bauerly wrote:
>
> Hello All;
>
> It was brought to my attention that the node was not accessable directly
> but only thru another netrom node. I am running ax25 utilities -42a, kernel
> 2.0.36 under 5.1 RedHat. My set-up is questionable. The netrom node is
> KSOLA:NW0I-6 this works. An ax25 connect to the node is NW0I-7. This works.
> But is it possible for both netrom or ax25 connects under the netrom alias?
Hi John.
I'll have a go at this (and probably be erroneous in the process).
After poking and prodding Net/ROM and its derivitives for both the TNC
and PC for several years, I've come to some conclusions as to its
behavior.
1. The node alias is intended to be used for AX.25 uplinks to a given
node and to aid the user in referencing a distant network node.
2. Level 3 connections take place bewteen nodes using their assigned
calls. i.e. NW0I-6 > N0NB-10.
Of course, I don't know that these are hard and fast rules, but seem to
be a general assumption of their behavoir. I do remember an
inexperienced BBS op a number of years back who locked a nodes table
entry and used the distant node's alias in place of the callsign. Each
time his BBS node would connect to the distant node, it would connect to
that distant node's alias, like an AX.25 user. As the Net/ROM (or
TheNet, I don't remember which) wasn't expecting Level 3 packets
directed to its alias, all kinds of weird and entertaining responses
were seen from that poor distant node. Add in the fact that Net/ROM and
its derivitives allow an uplinking user to connect to the node multiple
times using the alias + an SSID, we have a real mess.
Thus I think the fix for sysops of the Linux node is similar to what
I've tried here. This seems to work, although it hasn't been
extensively tested. I'd like feedback on how it works. In ax25d.conf I
have the following:
[7A0031-0 VIA 1]
parameters * 14 5 * * 900
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
[7A0031-1 VIA 1]
parameters * 14 5 * * 900
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
[7A0031-2 VIA 1]
parameters * 14 5 * * 900
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
. (repetition deleted)
.
.
[7A0031-15 VIA 1]
parameters * 14 5 * * 900
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
# NET/ROM Ports begin with a '<'.
#
<netrom>
parameters * 14 5 * * 900
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
As you can see, I have repeated the alias to my node for each possible
SSID, from 0 - 15 to allow for the multiple connect feature. I have
also disallowed AX.25 uplink connects to my node's N0NB-10 callsign.
This isn't consistent with Net/ROM behavior, but most users are used to
using the alias rather than the callsing anyway in these parts.
The N0NB-10 callsign is used by local nodes for Level 3 connections and
this Linux node issues Level 3 connections using the N0NB-10 callsign.
So far, no major complaints. Again, my setup is based on my assumptions
of Net/ROM operation and bear in mind the Linux node can be configured
radically different.
73, de Nate >>
--
Packet | N0NB @ WF0A.#SCKS.KS.USA.NOAM | "FAILURE IS NOT
Internet | [EMAIL PROTECTED] | AN OPTION!
Location | Valley Center, Kansas USA EM17hs | It's bundled
Visit my Linux + Ham Radio pages | with the soft-
http://homepage.netspaceonline.com/~ka0rny/ | ware..."
