Remote IP Programming issues

[FMROB]

Hello all. I got the EID key for the remote IP programming. Loaded onto the programming software all is running well. I can connect to my repeaters, however when I go to read any repeater I am getting an error message 8499. Anyone have any luck with the IP programming yet or know what this error code is.

Thanks, Rob

 

[escomm]

Have you enabled the station to permit IP programming and have you loaded the key into the station to permit IP programming?

 

[FMROB]

Have you enabled the station to permit IP programming and have you loaded the key into the station to permit IP programming?

Yes, on the repeaters that support it. I haven't changed out to all 8400's yet and/or upgraded all f/w to current versions.

It is just the one IP programming enable check box under network, yes?

 

[escomm]

Authentication Key (IP Repeater Programming)







Description



Sets an authentication key for Peer to Peer Protocol (P2P) messages in IP Repeater Programming. If Peer packet authentication is enabled, all P2P messages sent and received by the application will be authenticated. This key is 20 bytes in length and is a shared authentication key that must be the same in all radios/peers including the PC belonging to the same system. The default value is 0.



For security reasons, once the authentication key is saved, its value is shown as Ø.




Range

Maximum
FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF (Hex)

Minimum
0000000000000000000000000000000000000000 (Hex)

Increment
1 (Hex)




Note

Authentication of P2P messages is disabled if this feature value is set to 0 or a string of 0s.

This feature is disabled if the selected system is currently connected or the IP System Alias list is empty.

Multiple selection is not supported. This feature is disabled if multiple items are selected in the IP System Alias list.

 

[escomm]

I guess maybe the key isn't a requirement? I thought it was..

 

[FMROB]

I am using the Auth key on all the repeaters, and have entered same on the programming software under ip config.

 

[com501]

Did you specify a UDP port for programming? IT cannot be the same as any repeater on the network. The IP address of the computer being used for programming cannot be the same as any repeater, all radios and computers must be in the same subnet, and no repeater or other device and can have a duplicate UDP or IP address. Also, IP programming is not supported before a certain FW level, did you check in RDAC to make sure your level is high enough, and can you actually see your repeater in RDAC?

"The IP Repeater Programming feature allows a system operator to configure the networked repeaters from a physical location which is different than where the repeater resides. A networked repeater is a repeater that is connected to a backend IP network. The system operator is allowed to perform four different operations through a networked CPS:

Read: Allows the operator to view codeplug parameters currently configured in the repeater.

Write: Allows the operator to write updated codeplug parameters back to the repeater.

Update: Allows the operator to update the firmware and codeplug parameters to a newer version. All existing codeplug and tuning parameters are preserved during the update.

Purchase Radio Features: Allows the operator to remotely enable a chargeable feature within the repeater.



Start with configuring the IP Repeater Programming settings for CPS and the Link Establishment parameters for each of the Repeater which will support IP Repeater Programming feature. Currently the IP Repeater Programming feature is supported in Capacity Plus, IP Site Connect, and Single Site Conventional modes. In order for the Single Site Conventional repeater to support IP Repeater Programming, it is required that the Repeater is configured to be a Master.



The CPS/Repeater connection utilizes a TCP/IP connection which is inbound to CPS. If the CPS resides behind a firewall, then the system administrator must ensure the inbound TCP port is routed to the correct CPS instance. For more details, please refer to the system planner.



When programming the Repeaters within an IP Site Connect or Capacity Plus system, where there exist multiple Peers, it is recommended to start with the Peers followed by the Master last, since all requests for programming are routed through the Master. The user can then proceed with the following IP Repeater Programming operations:

Reading from a Connected Device

Writing to a Connected Device

Updating a Connected Device



For added security, a codeplug password can be configured into each Repeater. If configured, the user will have to enter in the codeplug password for all IP Repeater Programming operations.



Note

The CPS and RDAC (Repeater Diagnostics and Control) applications can both be connected to the same system but the applications ID and UDP Port number must be different from each other.

The IP Repeater Programming feature can only connect to one system at a time.

The IP Repeater Programming feature is supported only on Repeaters which have the higher memory (i.e. 32MB Repeaters). Please refer to the MOTOTRBO Repeater Basic Service Manual for the Repeater model specification."

 

[com501]

Here is the major gotcha:

Are you running ANY kind of antivirus? Disable it temporarily. Disable your builtin firewall.

If everything suddenly works, your AV or firewall is blocking the inbound program (mototrbocps.exe) from executing on the inbound request. Norton, AVG and Avast! blocked inbound by default. We had to set up an exception in UAC to handle that.

 

[sm0tsc]

Also look here

http://cwh050.blogspot.se/2013/08/ip-repeater-programming-repeaters.html

//Johan

 

[Astro Spectra]

To make this work you must allow an incoming connection from the Internet to your PC on the port you set for remote programming.

To recap how this works. Your PC sends a one way UDP message to the master. Just like any other peer your CPS needs a DMR ID, don't use 1. This message needs to have the same auth key as any peer would to contact the master and the CPS needs to know what that key is and what port the master is listening to.

Now for the cunning bit, when the master gets your CPS UDP message it tries to establish an independent outgoing TCP connection to your PC.

These arrangements are clever because you don't have to open any special ports on the infrastructure between the internet and the master as the CPS message to the master uses the same mechanism as any other peer and because the master opens its own TCP connection back to your PC the normal infrastructure NAT process works.

Now you do have to allow the incoming connection from the master to reach your PC and get thru your PC's firewall to CPS from the internet. You will need to open an incoming port on your router and point it at your PC to do. This inevitably involves having the PC on a fixed internal IP so the router knows where to direct the incoming traffic. You don't need to open everything just the port you selected for remote programming.

Once you establish a CPS connection to the master, CPS will tell you which peers you can then program. All comms goes via the master.

I support a network of '8400 machines and this works very well. You can even do firmware updates remotely. It's a life saver.

 

[MattSR]

I support a network of 8400 machines and this works very well.

I thought at first that you had a network of 8,400 repeaters...

 

[Astro Spectra]

Feels like it sometimes when things go wrong ...

 

[va3xft]

Hey all!

I'm able to program my master with IP programming, however I cannot access the peer, even though it appears in the list of available repeaters for IP programming. Is there a set-by-step guide to configuring and troubleshooting this feature of the CPS?

Thanks!

Don
VA3XFT