Nothing in AX.25 Nodes List

[Carl N4MNC]

I'm having the same problem that Dave Perkins posted about in August.  
We have no AX.25 nodes in our area, and our club is looking to stand up a few.  
At this point I'm just testing with two nodes at my house. I can't get the Node list to populate on either digipi, even though beacons are received by both.   Thanks in advance for any help with this. 
AX.25 mode enable on two digipi units running 1.9-4
/etc/ax25/uronode.conf modified to read: NrPort          netrom
Restarted both nodes
Both Radios are on 145.050
Packet Logs on each show beacons received from the other node
AXCall "Connect to your node", then entering command NODES show only the local                      node. both nodes are behaving this way.
Shell "netstat -A netrom -rn" showing no nodes.  Same on both nodes.
I can make an AXCall connection via RF to the other node by entering CallSign-4

ke4mh uronode config fix:

n4mnc uronode config fix:

ke4mh packet log:

n4mnc packet log:

ke4mh shell node list:

n4mnc shell node list:

n4mnc AXCall connected to ke4mh-4, then did NODES:

ke4mh AXCall connected to n4mnc-4, then did NODES:

[Craig]

Thanks for the detailed info Carl!

Please edit these files and change #DIGI or DIGI to a short unique node name (five characters?)

/etc/ax25/nrports:    netrom KM6LYW-4 #DIGI 255     145.730 Linux Node
/etc/ax25/uronode.conf:    NodeId        DIGI:KM6LYW-4

#DIGI is an "invalid" place-holder node name so people don't flip on node
and trash the regional routing tables.

This is really not obvious.

if it helps,
-craig
KM6LYW

--
You received this message because you are subscribed to the Google Groups "DigiPi" group.
To unsubscribe from this group and stop receiving emails from it, send an email to digipi+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/digipi/4bfbb0c6-d7c8-4427-ae9a-a83088d872ban%40googlegroups.com.

[David Rose]

In Carl's example he was setting his radio to 145.050

In Craig's reply the nrports file indicated  145.730

I have been confused by what frequency we should set our radio to when in production. I have searched my area and only find Winlink nodes and nothing that appears to be related to BBS and the Winlink that is close and I can hear a beacon is on 145.010.

I assume we don't use the same frequency as the Winlink node. Correct?

Should we be using 145.730 since that is what is in the config file? Is there a 'most' common frequency for BBS nodes? And should whatever we set our radio to (in the band plan) also be the same as the nrports file we edit?

David

K2LJL

[Craig]

It depends on your regional band plan.  I poked in 145.730 as a suggestion since that's
a legit non-phone/non-repeater frequency in America.

In California, we have a more refined plan which includes quite a few stations for data,

https://ncpa.n0ary.org/bandplan/digital_db.php

if it helps,
-craig
KM6LYW

To view this discussion visit https://groups.google.com/d/msgid/digipi/a1acb9f0-0d7e-4f88-819a-b9ae0c030e00n%40googlegroups.com.

[Dave Perkins]

Carl,

I've been reading up a lot on Uronode and Netrom and found that you do not want your netrom ssid to be the same as your AX25 id. Something about how it causes loop backs. This was taken from the dude who built Uronode:

  Note: you CAN NOT use your NetRom SSID! If you do, your node will also try to establish a connect as a user as well as encapsulate NetRom to the remote end. By NOT configuring your NetRom SSID here you can prevent this from occurring and also prevent unwanted loop traffic as your node will continue to spawn itself to the remote end. This is where many MANY people make an error! Don't let this happen to you!

What he's talking about is in ax25d.conf, your "AX25 node" is configured as N4NMC-4 to handle inbound call connections. Your Netrom ssid is also N4NMC-4 in nrports.  I changed mine to a random SSID that isn't being used by anything else in ax25d.conf. See below:

 

I also had an issue where people couldn't connect to my alias LCITY. It just wouldn't work for them. So I made an entry in ax25d.conf to handle that.

I could be wrong, but I am hoping this works. Havent been able to test it out yet but I am pretty sure this will fix the problem.

Just wanted to pass this along.

Take it easy,

Dave