[nodes] stanza seemingly ignored

App_rpt-users
1

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
repeaterCLI> 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

2

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>
3

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
repeaterCLI> 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
repeaterCLI> 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
repeaterCLI> rpt lookup 43350
Node: 558933 Data: radio@97.90.235.102:4572/43350,97.90.235.102,y
repeaterCLI> rpt lookup 42923
repeaterCLI> 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

4

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.

5

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

6

[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.

7

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

8

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.

9

good day!
revisiting this a year later, as the issue is still a stumbling block
I had typed up a LONG post with all of the current info from config and the errors, which I saved for quick access
and it occurred to me to have a gander at what Asterisk was actually doing

here is what its going by (note the embolden ports)

558933
repeater*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
34.105.111.212:4569 Y 558933 47.32.40.151:4569 179 Registered

558936
6meter*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
162.248.92.131:4569 Y 558936 47.32.40.151:4569 179 Registered

46397
W9CVA-46397*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
34.105.111.212:4569 Y 46397 47.32.40.151:4570 180 Registered

558932
cvarcuhf*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
162.248.92.131:4569 Y 558932 47.32.40.151:4574 180 Registered

iax.conf on both machines has the correct port
register=558936:xxxxxxxxxxxx@register.allstarlink.org
bindport = 4576

register=558933:xxxxxxxxxxxx@register.allstarlink.org
bindport = 4567

both show the proper port in Supermon
558936 shows [ AstP: 4576 ]
558933 shows [ AstP: 4567 ]

I also checked the portal to make sure the ports were proper
and they match

this smells to be the root of problem
but I dont know where to look to see why/how the registration is pooched

here is a excpert from the node stanzas
[nodes]
558933 = radio@127.0.0.1:4567/558933,NONE
558936 = radio@192.168.10.114:4576/558936,NONE

[nodes]
558936 = radio@127.0.0.1:4576/558936,NONE
558933 = radio@192.168.10.104:4567/558933,NONE

our node 43353 uses :4569 which explains the connect attempt and then disconnect

where else could the wrong port be called ?

thanks for suffering long post

de k9wkj

10

Ohh forget to mention
both of these suspect systems take external incoming connections just fine

de k9wkj

11

Could you post a copy of your rpt.conf ?

12

Hey Mike
which machine? both?
looking at your post, it prodded my brain to look at them
more specifically the node definition part at the top
and on one of them I found the default :4569 that should have been :4576
I restarted both of them with a cheery smile that finally the typo (lack of typing) has been found
nope, they still exhibit the same behavior and the registration query still shows :4569 on both of them
6meterCLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
162.248.92.131:4569 Y 558936 47.32.40.151:4569 179 Registered
6meterCLI>

repeaterCLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
162.248.92.131:4569 Y 558933 47.32.40.151:4569 179 Registered
repeaterCLI>

I would be happy to send you both rpt.conf
thats alot of fill here in the forum
would email be better and I would also feel better security wise

13

Mike,
I messaged you both rpt.conf
had to be 2 messages as they were to big for 1

14

This is what is showing in the registration file

558933=radio@47.32.40.151:4567/558933,47.32.40.151
558936=radio@47.32.40.151:4576/558936,47.32.40.151

look that over while I look at your config’s

15

can you tell me more about the connection attempt.
Are the nodes connected to anything else ?

And would I be correct if I say that
they can connect any other node but not each other in either direction ?

Did you look at your whilelist/blacklist ?

16

A quick check for you to preform…

In each server, Look at /var/lib/asterisk/rpt_extnodes file to see if they are up to date
(look at date/time creation)
and look in the contents to see the description for each node. Make sure they both exist in the file in each server.

If all looks good and you are still stumped…
‘CUT’ your nodes section from the top of the file and paste it where I show below…

[events]

<----------------put [nodes] list here. Not at the top of your file.

#includeifexists custom/rpt.conf

do on each and save/restart each server.

17

After re-reading your posts several times, I think I just had a case like yours a week ago from newb that stumbled on my node last week.

I may need to get back with you as I put some wheels in motion.

Let me know how the above turns out if anything.

18

image
image

fresh as a daisy, and the nodes in question are there with the proper info
image
image

i keep seeing this stuff pop up in the ast log of both of the machines

[Oct 11 17:09:51] WARNING[11072] app_rpt.c: Node 46397 IP 47.32.40.151 does not match link IP 192.168.10.102!!
[Oct 11 17:10:13] WARNING[11089] app_rpt.c: Node 558936 IP 47.32.40.151 does not match link IP 192.168.10.1!! (but 192.168.10.1 is not 558936 its the router)

oddly 46397 is also a node that these 2 dont play well with (192.168.10.102 is its addy)
but I was always sure that was really just a typo
they can both connect to 46397
but 46397 can not connect to either of them

19

I dont know why the rpt.conf has that definition at the top
I was going to mount up a fresh image and see if thats how it ships
I would not have done that, as I know where the nodes list goes
unless some very late night copy/paste bit me

20

didnt know I had any