7610 not link in remote

Usage Questions
1

Good afternoon. I think I have read about everything on the forum to connect the 7610… but it doesn’t link.

On a local network it works great… but not in remote. It seems as if it has a port conversor.

In the log I see that it converts a random port to 50001…

2023-02-22 16:59:35.342 INF system: Cannot prepare WF view without rigCaps. Waiting on this.
2023-02-22 16:59:35.350 INF rig: creating instance of rigCommander()
2023-02-22 16:59:35.350 INF udp: Starting udpHandler user: “ea3aji” rx latency: 150 tx latency: 150 rx sample rate: 48000 rx codec: 4 tx sample rate: 48000 tx codec: 4
2023-02-22 16:59:35.350 INF cluster: starting dxClusterClient()
2023-02-22 16:59:35.388 INF udp: UDP Stream bound to local port: 55074 remote port: 50001
2023-02-22 16:59:35.450 INF system: Received CommReady!!
2023-02-22 16:59:35.450 INF default: Setting rig state for wfmain

I have changed ports… disconnected CI-V… and everything I could think of. No result.

Any ideas?

73s
Pere, EA3AJI

2

port conversor… can you elaborate?

also can you check if the udp ports are really open from the outsid workd and not being blocked by your ISP for instance?

3

Good afternoon.

In this line of the log you can see how it converts port 55074 to 50001.

2023-02-22 16:59:35.388 INF udp: UDP Stream bound to local port: 55074 remote port: 50001

I don’t know if this is relevant…

I have the ports opened as I can access to my router. I have also spoken with my ISP and they have verified it.

4

what you mean is PAT, I think.

And: my router/firewall at home maps the udp ports 1:1 so if your router does that too, it’s outside of your network.

this is an example of how it shuld look like, src/dest ports in your router/firewall

--------------------------------------------------------------------
  UDP     1350                  (192.168.1.110)         1350    
  UDP     4472                  (192.168.1.110)         4472    
  UDP     50001-50003           (192.168.1.151)         50001-50003
  UDP     50011-50013           (192.168.1.110)         50011-50013
  UDP     50021-50023           (192.168.1.97)          50021-50023
  UDP     50031                 (192.168.1.110)         50031
  UDP     50041                 (192.168.1.110)         50041
  UDP     50053                 (192.168.1.110)         50053
  UDP     50061-50063           (192.168.1.75)          50061-50063```
5

Port 55074 is the local (source) port and has no relevance here, the important port is 50001 which is the destination port.

73 Phil M0VSE

6

Good afternoon.

Now I have seen that although I have the ports open as UDP in the router… physically they are not like that because when I run a port test it shows them as TCP.

I am going to talk with my ISP

7

You could try using different port numbers from the standard (50001, 50002, 50003).

I have a friend where a lot of his connections were blocked, but he changed to using these UDP ports, which are also used by Zoom, and the problem went away: 8801, 8802, 8803.

Make sure to change the ports in all three places – on the radio, on the router’s port forwarding page, and on your client.

There’s no guarantee this will work, but it might.

–E
de W6EL

8

Good afternoon.

I did it before: I put 50011, 50012 and 50013. And it didn’t work anyway.

It’s unusual that you can’t set the port manually on the 7610 and you have to keep pressing + or -. :roll_eyes:

9

Oh gosh, I forgot about that annoying thing. That’s a lot of button pressing. Maybe try some ports just below 50000.

–E
de W6EL

10

Yes… I have seen it… I don’t know how ICOM did not foresee this… :nauseated_face:

11

You can also use the VFO knob to increase/decrease the port number!

12

Nice tip!

In spite of this and changing ports… I still don’t have a connection. Let’s see what the ISP says

13

is the client you use (where wfview runs) the same inside and outside of your local network?

14

Yes… but I have also tested it from the outside and it does not connect anyway.

It’s like I don’t have the ports open… but I have it

This is weird stuff.

15

via internal works, outside not. network issue. sure you use udp ports open?

16

GM

Yes… sure… I have checked several times.

17

if you install nmap on the host,

what do you see if you nmap -sU -p outside of your internal network?

Like:

nmap -sU your.address -p50001-50003

ORT STATE SERVICE
50001/udp open|filtered unknown
50002/udp open|filtered unknown
50003/udp open|filtered unknown

or do you see “closed” or “filtered” ?

18

This is a really good suggestion. nmap is such an excellent tool.

Here’s how my network looks, scanning from 50001-500012 (I have a few radios available remotely):

PORT      STATE         SERVICE
50001/udp open|filtered unknown
50002/udp open|filtered unknown
50003/udp open|filtered unknown
50004/udp open|filtered unknown
50005/udp open|filtered unknown
50006/udp open|filtered unknown
50007/udp open|filtered unknown
50008/udp open|filtered unknown
50009/udp open|filtered unknown
50010/udp closed        unknown
50011/udp closed        unknown
50012/udp closed        unknown

–E
de W6EL

19

Pere,

did you find anything? I assume that you are also using the external IP address to get into your network.
If you need a test-scan and the ISP does not “do things” I can di that for you too.
In that case share your external IP address (preferrably not here on the forum).

20

Good afternoon.

Yes… I have tried it before… I get the same result.

Host is up (0.0010s latency).

PORT STATE SERVICE
50001/udp open|filtered unknown
50002/udp open|filtered unknown
50003/udp open|filtered unknown