[nodes] stanza seemingly ignored

was coherced into deploying a science project repeater I have been messing with
and added the nodes stanza to rpt.conf
but the thing is still looking outside for the local nodes
example
repeaterCLI> rpt lookup 558933
Node: 558933 Data: radio@127.0.0.1:4567/558933,NONE
repeater
CLI> rpt lookup 558932
Node: 558933 Data: radio@97.90.235.102:4574/558932,97.90.235.102

it should look similar to what our other nodes do

rpt lookup 558932
Node: 558932, Method: DNS, Actual: LOCAL, Data: radio@127.0.0.1/558932,NONE
Node: 1999, Method: DNS, Actual: LOCAL, Data: radio@127.0.0.1/558932,NONE
cvarcuhf*CLI> rpt lookup 558933
Node: 558932, Method: DNS, Actual: LOCAL, Data: radio@192.168.10.101:4567/558933,NONE
Node: 1999, Method: DNS, Actual: LOCAL, Data: radio@192.168.10.101:4567/558933,NONE

the new node is ASL 2.0 b6 on a Pi3
the others are hamvoip

is as if it doesnt know to use the node stanza
this gives me a clue
Method: DNS, Actual: LOCAL that I missed somthing

what did i miss

de k9wkj

ASL lookup works a little different than HamVoIP. Here’s a sample from my ASL 2.0-beta6:

rambo4*CLI> rpt lookup 2530
Node: 2520       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2530       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2501       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2503       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2505       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2521       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2522       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2523       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2525       Data: radio@127.0.0.1:4569/2530,NONE
Node: 2526       Data: radio@127.0.0.1:4569/2530,NONE
Node: 41936      Data: radio@127.0.0.1:4569/2530,NONE
Node: 42720      Data: radio@127.0.0.1:4569/2530,NONE
Node: 25333      Data: radio@127.0.0.1:4569/2530,NONE
rambo4*CLI> rpt lookup 2000
Node: 2520       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2530       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2501       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2503       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2505       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2521       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2522       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2523       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2525       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 2526       Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 41936      Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 42720      Data: radio@162.248.93.134:4569/2000,162.248.93.134
Node: 25333      Data: radio@162.248.93.134:4569/2000,162.248.93.134
rambo4*CLI>

hey Tim
here is the nodes stanza
[nodes]
558933 = radio@127.0.0.1/558933,NONE
558932 = radio@192.168.10.101:4574/558932,NONE
43353 = radio@192.168.10.100:4569/43353,NONE
46397 = radio@192.168.10.102:4570/46397,NONE
;43351 = radio@192.168.10.104:4567/43351,NONE
43352 = radio@192.168.10.103:4568/43352,NONE
43350 = radio@192.168.10.105:4572/43350,NONE
42923 = radio@192.168.10.28:4573/42923,NONE
45517 = radio@192.168.10.236:4571/45517,NONE

and here are the lookup results

repeaterCLI> rpt lookup 558933
Node: 558933 Data: radio@127.0.0.1:4567/558933,NONE
repeater
CLI> rpt lookup 558932
Node: 558933 Data: radio@97.90.235.102:4574/558932,97.90.235.102
repeaterCLI> rpt lookup 43353
Node: 558933 Data: radio@97.90.235.102:4569/43353,97.90.235.102
repeater
CLI> rpt lookup 46397
Node: 558933 Data: radio@97.90.235.102:4570/46397,97.90.235.102
repeaterCLI> rpt lookup 43352
Node: 558933 Data: radio@97.90.235.102:4568/43352,97.90.235.102
repeater
CLI> rpt lookup 43350
Node: 558933 Data: radio@97.90.235.102:4572/43350,97.90.235.102,y
repeaterCLI> rpt lookup 42923
repeater
CLI> rpt lookup 45517

558933 will connect to 558932
but 558932 will not connect to 558933
some connections work, but others dont

note it does not return anything for the last 2 even though they are in the stanza
those nodes were off line when i queried

these are all on the same network
but ASL looks outside at the public IP
my eyes are blurring looking at 5 different node stanzas with mostly the same numbers in them

any thoughts?

de k9wkj

So which box is the nodes stanza from ?

By looking at it, I would say this nodes stanza belongs to 558933

SO, show us 558932 nodes stanza as I’m guessing you are missing or have a malformed entry on it since it does not connect outbound to a node inside your nat.

the 1st posted is 558933
here is 558932

558932 = radio@127.0.0.1/558932,NONE
;1999 = radio@127.0.0.1/1999,NONE
46397 = radio@192.168.10.102:4570/46397,NONE
;558932 = radio@192.168.10.101:4574/558932,NONE
558933 = radio@192.168.10.104:4567/558933,NONE
43353 = radio@192.168.10.100:4569/43353,NONE
;43351 = radio@192.168.10.104:4567/43351,NONE
43352 = radio@192.168.10.103:4568/43352,NONE
43350 = radio@192.168.10.105:4572/43350,NONE
42923 = radio@192.168.10.28:4573/42923,NONE
45517 = radio@192.168.10.236:4571/45517,NONE

still dont grok why it is looking at the public IP
the purpose of the nodes stanza is to have it look on its own subnet
for the listed IP addys

de k9wkj

[quote=“k9wkj, post:3, topic:19501”][/quote]

*33stanza
558932 = radio@192.168.10.101:4574/558932,NONE -using port 4574 ?

*32stanza
558933 = radio@192.168.10.104:4567/558933,NONE or port 4567?
558932 = radio@127.0.0.1/558932,NONE -NO PORT DECLARED

You should verify your port usage in each box with that in iax.conf
Any changes will require a restart.

Any connection inside your NAT requires a ‘correct’ path to the desired connection from each you want to be able to connect. IP and PORT

External connections are handled through the registration system and managed in the file
/var/lib/asterisk/rpt_extnodes

Anything else must be declared correctly in the nodes stanza.

While I can’t tell you where the exact error is, look and you shall find it.

You do not have to declare a local port for internal nodes, but you should put it in there to help you rationalize what you are doing when looking at it. Especially with so many nodes inside same NAT on different IP’s.

For me, I can’t tell from looking at it if even the IP’s are correct. Take your time to verify it all. Create a cheat sheet as you may find yourself doing this again when you make changes.

afternoon Mike
yes, looking at it for to long makes your head woozy
but I think your missing my real question
whether or not the 2 nodes will connect is most assuredly me typing poorly
but that does not explain why it is looking at the public IP for every node
if I had typed at least one of them properly it should show that IP addy when I query it
i suppose I will have to disconnect everything and try them all 1 by 1
its was brought to my attention that there may be extraneous characters in the file that dont show in the editor, yet another thing to ponder

de k9wkj

It’s looking for a public address since it does not see one described locally.
It does not know where it is, but it will search available paths of registration.