[App_rpt-users] Problem with a Two Node Configuration.
buddy at brannan.name
Fri Nov 23 09:37:00 EST 2012
OK, so both nodes are on the same machine. Are they both on separate URI's or other USB interfaces, or is one used for something else?
A couple things spring to mind:
First, in your rpt.conf file, do you have lines in both to report status?
Second, you're going to need both nodes defined locally as 127.0-.0.1. Mine looks like this, so just replace your node numbers:
2331 = radio at 127.0.0.1/2331,NONE
28529 = radio at 127.0.0.1/28529,NONE
Betcha a cold cheeseburger that only one of these is defined, i.e. the one you can connect to.
Buddy Brannan, KB5ELV - Erie, PA
Phone: (814) 860-3194 or 888-75-BUDDY
On Nov 23, 2012, at 9:11 AM, Keith Goobie <keith at goobie.org> wrote:
> Hi All
> A colleague – VA3SD – built a standalone node on an Acid based platform, the node he was assigned is 27211. The associated callsign is VE3UOR.
> WE needed to add a second node, so I subscribed and was given node number 29133. The repeater callsign is VE3LSR and my profile is established as VA3YC.
> I followed the guidance from the internet regarding the creation of two nodes on the same ACID platform.
> The resulting configuration more or less works. Here are the issues I am seeing:
>> • Both nodes show up on the nodelist page. You can do a successful drill down on detail for the VE3LSR/29133 node, but it is not possible on the VE3UOR/27211 node.
>> • You can successfully connect from the VE3UOR node to the VE3LSR node but not vice versa.
> Thoughts or guidance will be much appreciated.
> keith at goobie.org
> Keith Goobie
> Richmond Hill, ON, CANADA
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
More information about the App_rpt-users