Looking for help with getting RM to work with a access point. I read thru some of the threads regarding RM for APX but couldn't find the answer im looking for. I have the RM installed on my Panasonic FZ-55 and confirmed it works (read/write) via the mobile hotspot option. I have a GL.iNet GL-SFT1200 portable router which is connected to the ethernet port of my laptop and to WAN on the router, set it to access point mode in admin page and set the SSID name to whats on the radio under data>wifi. The radio sees the SSID and connects to it (confirmed it by the wifi icon on the display and wifi menu option), but no luck with read/write. Looking at the settings under RM, job processor, etc they are all set to localhost, im wondering if thats where the issue is and if it needs to be changed to something else or if im missing something else. Any help is appreciated.
-
To anyone looking to acquire commercial radio programming software:
Please do not make requests for copies of radio programming software which is sold (or was sold) by the manufacturer for any monetary value. All requests will be deleted and a forum infraction issued. Making a request such as this is attempting to engage in software piracy and this forum cannot be involved or associated with this activity. The same goes for any private transaction via Private Message. Even if you attempt to engage in this activity in PM's we will still enforce the forum rules. Your PM's are not private and the administration has the right to read them if there's a hint to criminal activity.
If you are having trouble legally obtaining software please state so. We do not want any hurt feelings when your vague post is mistaken for a free request. It is YOUR responsibility to properly word your request.
To obtain Motorola software see the Sticky in the Motorola forum.
The various other vendors often permit their dealers to sell the software online (i.e., Kenwood). Please use Google or some other search engine to find a dealer that sells the software. Typically each series or individual radio requires its own software package. Often the Kenwood software is less than $100 so don't be a cheapskate; just purchase it.
For M/A Com/Harris/GE, etc: there are two software packages that program all current and past radios. One package is for conventional programming and the other for trunked programming. The trunked package is in upwards of $2,500. The conventional package is more reasonable though is still several hundred dollars. The benefit is you do not need multiple versions for each radio (unlike Motorola).
This is a large and very visible forum. We cannot jeopardize the ability to provide the RadioReference services by allowing this activity to occur. Please respect this.
dickie757
Wired
I'd say hook laptop into LAN, not WAN. They way you have it now would make the laptop the "service provider." If you have a SIM in the laptop, then that may work, but the sub is most likely looking for a port on the local network into RM, not the internet, unless your instance of RM is at the shop.
Thank you for your reply. I'll try that.
Correct. RM wont work on routed network. You need to be on the same LAN as the server.
So I’m just getting started with RM and its setup, bear with me. The RM is just installed on the laptop. No actual server in use.
docholliday666
Newbie
- Joined
- Apr 26, 2026
- Messages
- 3
- Reaction score
- 0
WAN configuration won't make a difference - the router handles that. Be sure that the WLAN is on the same native network as the LAN port on the router and that the IP address block the radio gets is the same as the laptop. Assign a STATIC IP to the laptop LAN port.
Then, TURN OFF the useless software Windows Firewall on the laptop as it causes issues. Be sure the connection type is Private, not Public on the computer. Or, be sure that UDP 5353 is allowed inbound on the laptop.
Install DDNS and MNIS on the laptop (not always necessary, but install it now just to be sure). If everything (RM Server, Job processor, device monitor, SQLExpress) is on the same computer, localhost is perfectly fine.
Go into the radio codeplug (use CPS2 if necessary over USB) and set the Wi-Fi Network -> General -> DNS-SD interval to 90s, DNS-SD Listening Port to 5353 -> Device Discovery Server Name to the (static) IP of the laptop.
Go to the RM Server Configuration, be sure that Machine Authorization is enabled and the laptop (by name) has "Device Programmer" and "Job Processor" checked. Also, be sure User Authorization has a Non-Domain user added for both RM Administrator and RM Client User (make a new Non-Domain account by hitting the + and keep it simple for now - user "moto", password "password".
Go into Job Processor and Device Monitor. Click the Test Connection button. If it doesn't connect, choose "One-Time Password" and use the account you created. It'll switch to Certificate after a successful validation.
In Device Monitor, also be sure the DNS-SD Listening port is 5353, the communication method is "USB" AND "Wireless (LAN)". Don't check OTA or IP.
Be sure that the radio is on the new(er)(est) firmware - ideally at the same level as the RM install. If the FW is too old, it can do really stupid things.
Restart computer, wait about 2 minutes, and it should program.
Then, TURN OFF the useless software Windows Firewall on the laptop as it causes issues. Be sure the connection type is Private, not Public on the computer. Or, be sure that UDP 5353 is allowed inbound on the laptop.
Install DDNS and MNIS on the laptop (not always necessary, but install it now just to be sure). If everything (RM Server, Job processor, device monitor, SQLExpress) is on the same computer, localhost is perfectly fine.
Go into the radio codeplug (use CPS2 if necessary over USB) and set the Wi-Fi Network -> General -> DNS-SD interval to 90s, DNS-SD Listening Port to 5353 -> Device Discovery Server Name to the (static) IP of the laptop.
Go to the RM Server Configuration, be sure that Machine Authorization is enabled and the laptop (by name) has "Device Programmer" and "Job Processor" checked. Also, be sure User Authorization has a Non-Domain user added for both RM Administrator and RM Client User (make a new Non-Domain account by hitting the + and keep it simple for now - user "moto", password "password".
Go into Job Processor and Device Monitor. Click the Test Connection button. If it doesn't connect, choose "One-Time Password" and use the account you created. It'll switch to Certificate after a successful validation.
In Device Monitor, also be sure the DNS-SD Listening port is 5353, the communication method is "USB" AND "Wireless (LAN)". Don't check OTA or IP.
Be sure that the radio is on the new(er)(est) firmware - ideally at the same level as the RM install. If the FW is too old, it can do really stupid things.
Restart computer, wait about 2 minutes, and it should program.
Last edited:
docholliday666
Newbie
- Joined
- Apr 26, 2026
- Messages
- 3
- Reaction score
- 0
Sorry...completely missed that it was APX and not TRBO. But we took it to PM and got some ideas to try, general concepts of RM should be pretty similar.
TampaTyron
Beep Boop, Beep Boop
Not sure if APX is the same or not, but get rid of 5353, we use 5454 and it works MUCH MUCH better. 5353 is shared by so many Windows softwares that it is a pain to get working. The overall process is radios call out to the Device Discovery Server (RM Device Programmer that can see the wifi traffic) on 5454, then the DP replies on 8002, then back and forth for wifi programming. Make sure the DP (RM server in this instance) has Windows firewall set to allow/allow (in/out) all traffic, then disable windows firewall. If you just disable windows firewall without allow/allow, windows often blocks your traffic.
TT
TT
docholliday666
Newbie
- Joined
- Apr 26, 2026
- Messages
- 3
- Reaction score
- 0
No, it doesn't. It blocks if you disable the *service*. If you disable the firewall from inside, there's no filtering or blocking. It just stops listening and affecting traffic.
Project25_MASTR
TX-COMU
First step is make sure the Device Programmer, can talk with the Server. If your server is co-located on the same machine as the DP, that should be a couple of automatic firewall rules created by the installers. Make sure that the server connection is active in the DP settings. For what it's worth, the DP to RM Server function can work over any Layer 4 boundary as long as ports are appropriately forwarded to the RM Server. I commonly would create a ZeroTier network for DPs (programming laptops) and the RM server and point the DPs at the ZeroTier address for the server…just works.
Second step is to make sure the DP and radios are in the same Layer 2 segment (same VLAN). This works fine over WiFi on both ends with DHCP (Automatic) IP addresses assigned by the router (give me a bit and I can actually post a video of this working). It should work across Layer 2 segments if mDNS repeating is present as well but this I've never tried, too much work outside of my control. You also need to make sure client isolation isn't enabled on the AP if your DP is on the same wireless network and AP. If you are on a larger network, make sure Port Isolation (isolating ports between each other within the same VLAN) is also turned off on your switch. I've never tried haripinning at the router using mDNS repeating with port isolation on, again too much work for too little reward.
After that, it should...just work but it can take some time to find devices on the network. I recommend using shorter DHCP leases (like 600 seconds or 300 seconds) as the radios will multicast announce via mDNS every time they make the attempt to renew (half way through the lease for the first lease).
When it works, you can program up to 10 radios simultaneously (of course your jobs can be hundreds of radios). Personally, I setup a Mikrotik hAP Lite with the Motorola M-RadioConfig SSID (and leave it in the radios) so I can zero-touch provision out of the box or program in an evironment where fixed WiFi isn't available. Also, if you are dealing with BN APXs, keep in mind they only support 2.4 GHz APs. CN's and N series support 2.4 GHz and 5 GHz.
Second step is to make sure the DP and radios are in the same Layer 2 segment (same VLAN). This works fine over WiFi on both ends with DHCP (Automatic) IP addresses assigned by the router (give me a bit and I can actually post a video of this working). It should work across Layer 2 segments if mDNS repeating is present as well but this I've never tried, too much work outside of my control. You also need to make sure client isolation isn't enabled on the AP if your DP is on the same wireless network and AP. If you are on a larger network, make sure Port Isolation (isolating ports between each other within the same VLAN) is also turned off on your switch. I've never tried haripinning at the router using mDNS repeating with port isolation on, again too much work for too little reward.
After that, it should...just work but it can take some time to find devices on the network. I recommend using shorter DHCP leases (like 600 seconds or 300 seconds) as the radios will multicast announce via mDNS every time they make the attempt to renew (half way through the lease for the first lease).
When it works, you can program up to 10 radios simultaneously (of course your jobs can be hundreds of radios). Personally, I setup a Mikrotik hAP Lite with the Motorola M-RadioConfig SSID (and leave it in the radios) so I can zero-touch provision out of the box or program in an evironment where fixed WiFi isn't available. Also, if you are dealing with BN APXs, keep in mind they only support 2.4 GHz APs. CN's and N series support 2.4 GHz and 5 GHz.
