# Node number limitation? **URL:** \ **Category:** AllStarLink\ **Created:** [November 11, 2024, 8:39pm UTC](https://community.allstarlink.org/t/node-number-limitation/22239 "2024-11-11T20:39:06Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![TK5EP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/tk5ep/32/2382_2.png) [@TK5EP](https://community.allstarlink.org/u/TK5EP)\ **Post date:** [November 11, 2024, 8:39pm UTC](https://community.allstarlink.org/t/node-number-limitation/22239/1 "2024-11-11T20:39:06Z")
Hi all, We’ve a few nodes still running under v 2. All are working just fine. I’m actually trying to move one on these nodes under v3 without changing anything on the hardware. We are on a private network and the server is node #1, the node I want to change is #100. I have now way to make it work by changing the different config files to use #100. When I set them to # 1111 , everything works as expected. Is there a limitation in the node number in ASL3 ? Thanks and 73, Patrick. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [November 11, 2024, 8:51pm UTC](https://community.allstarlink.org/t/node-number-limitation/22239/2 "2024-11-11T20:51:03Z")
The `asl-menu` (and `node-setup`) expects node #'s to be 4 digits (1000+) with private node numbers between 1000-1999. We had a discussion a while back (many months ago) about what range to allow for private nodes but, offhand, I don’t recall why we set the lower end to be 1000. ---
**Author:** ![Mike](https://community.allstarlink.org/user_avatar/community.allstarlink.org/mike/32/1569_2.png) [@Mike](https://community.allstarlink.org/u/Mike)\ **Post date:** [November 11, 2024, 9:09pm UTC](https://community.allstarlink.org/t/node-number-limitation/22239/3 "2024-11-11T21:09:03Z")
It has always been advised to use private node number between 1000 and 1999 And I might add if anyone starts using asterisk functions on their sip devices via industry standard, you will have a 3 digit conflict almost assuredly. I think some of the older versions left those enabled default. 3 digits are left for internal dialplan I believe. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [November 11, 2024, 11:04pm UTC](https://community.allstarlink.org/t/node-number-limitation/22239/4 "2024-11-11T23:04:58Z")
By spec, the ASL node numbers are 4-6 digits starting with 2, 4, 5, or 6 with 4 digit numbers starting 1 are reserved as “private” nodes. Three digit numbers are not supported and have quirky problems. Especially with the updated codebase where they were never contemplated, I wouldn’t expect them to work at all. I’d suggest just adding 1 to everything. ---
**Author:** ![TK5EP](https://community.allstarlink.org/user_avatar/community.allstarlink.org/tk5ep/32/2382_2.png) [@TK5EP](https://community.allstarlink.org/u/TK5EP)\ **Post date:** [November 12, 2024, 6:15am UTC](https://community.allstarlink.org/t/node-number-limitation/22239/5 "2024-11-12T06:15:37Z")
Thanks, I’ve asked our sysop to create a new node with a 4 digit number and we will probably have to change all our node numbers. 73, Patrick