Messages

1

General discussion / Install does not setup com port

« on: 2016-03-03, 18:52:37 »

I  have installed RRC Micro on a windows 10 laptop. Under PC Com Port there are no ports shown. They are not shown under Devices and Printers either. What do I need to to to install the virtual com ports?

2

General / Re: Invalid App License

« on: 2016-02-25, 22:25:35 »

Please see my post under general discussions RRC1258.

I have installed the Nano on a second Samsung S6 using G3ZVC as a call. This is operating under the trail license. With this phone Nano is working relatively well considering the problems at the Radio end. It always turns on the radio and tunes it well.

With Nano on the licensed phone (kf6c) most of the time I shows Invalid license howver it can be made to work with continued pressing of the connect button.

I am not sure how valid tests are until the Radio RCC internet connection is fixed. I will be waiting until the network link is fixed before continuing.

3

General discussion forum / Re: remote scanning of ports

« on: 2016-02-25, 21:46:34 »

It turns out there appears to be a fault on the line between my house and the service pole .  I noticed I was getting very unstable readings on the link speeds with multiple consecutive tests.  The ISP, COX , sent a service tech to check the system and he found the speed varied from 100Kbps to 198Mbps.  The checks they have done indicate there is no problem in the house or at their end.
Relating the problem to scanning of the ports appears to have been just a further  degradation of an already broken system.
For now I have to wait for COX to repair the lines.

4

General / Re: Port=713000 pop up on connect

« on: 2016-02-23, 17:55:43 »

OK but now I am back to invalid app License

Brian.

5

General / Re: Port=713000 pop up on connect

« on: 2016-02-23, 16:22:38 »

I do not understand the port issue I am not using the default port 80 so where do I enter the port. I am using the covention xxx.xxx.xxx.xxx:XXX  SIP port is 13000 audio13001 and cmd 13002

what is port 80 normally use for.

The slow internet was caused by remote scanning of the ports from Asia pacific illegal activities. This seems to have stopped for the moment. See my other posts under  RRC1258

6

General / Re: Port=713000 pop up on connect

« on: 2016-02-22, 18:42:02 »

If I delete the port number from the IP, the app comes up with invalid app License in place of the Port = 713000

I enter the wrong password with the port  number in place with the IP it reports Port = 713000

7

General / Re: Port=713000 pop up on connect

« on: 2016-02-22, 17:08:50 »

I have double checked and I am using the same numbers as  the K3O and the Setup manager agrees.

Brian KF6C.

8

General / Re: Port=713000 pop up on connect

« on: 2016-02-22, 17:06:33 »

I get the same result when I try access over the LAN. Changed IP to that of Radio LAN and phone to wireless connection.

Brian KF6C

9

General / Re: Port=713000 pop up on connect

« on: 2016-02-22, 17:01:52 »

No it comes up with time out and still does not work

Brian KF6C

10

General / Re: Port=713000 pop up on connect

« on: 2016-02-22, 16:52:54 »

I was afraid to do that, worried about license issues.

After uninstalling and reinstalling I get a time out. The K30 works but it took a while to gain connection the first time this morning. It now brings up the system in about 13 seconds.

Brian KF6C.

11

General / Re: Port=713000 pop up on connect

« on: 2016-02-22, 16:11:10 »

I mean a small window withe Port = 713000 comes up for a couple of second and then goes away. Other than that nothing happens the connect screen does not change.  The color of the connect window goes yellow while I have my finger on it.

Reentering the all the settings results in the same thing.

One change that is different for security reasons I an using a non standard port number   for the radio  xx.xxx.xxx.xxx:  xxxx

73 Brian KF6C

12

General discussion forum / Re: remote scanning of ports

« on: 2016-02-21, 17:23:22 »

Thank you for taking the time to explain the issues. The problem has gone away for now but note from anything I did, however for peace of mind I need to understand what caused it.

The scanning was coming from outside the IPs were varied as shown in the part of the  log shown here:

[LAN access from remote] from 81.214.121.40:39262 to 192.168.1.170:53413, Friday, Feb 19,2016 07:16:19
[LAN access from remote] from 68.58.52.149:29680 to 192.168.1.170:12553, Friday, Feb 19,2016 07:15:37
[LAN access from remote] from 74.105.89.93:18244 to 192.168.1.170:12553, Friday, Feb 19,2016 07:13:41
[LAN access from remote] from 159.203.12.173:1612 to 192.168.1.170:22, Friday, Feb 19,2016 07:11:29
[LAN access from remote] from 82.79.50.44:53 to 192.168.1.170:42468, Friday, Feb 19,2016 07:10:51
[LAN access from remote] from 85.25.200.110:61651 to 192.168.1.170:5038, Friday, Feb 19,2016 07:09:49
[LAN access from remote] from 208.54.4.192:48611 to 192.168.1.170:53502, Friday, Feb 19,2016 07:09:34
[LAN access from remote] from 151.236.63.50:25870 to 192.168.1.170:22, Friday, Feb 19,2016 07:08:58
[LAN access from remote] from 125.64.94.200:37093 to 192.168.1.170:8000, Friday, Feb 19,2016 07:08:15
[LAN access from remote] from 185.130.5.201:47514 to 192.168.1.170:53413, Friday, Feb 19,2016 07:04:37
[LAN access from remote] from 185.40.4.185:59222 to 192.168.1.170:8484, Friday, Feb 19,2016 07:03:59
[LAN access from remote] from 50.108.24.59:29338 to 192.168.1.170:12553, Friday, Feb 19,2016 07:03:09
[LAN access from remote] from 74.105.89.93:18244 to 192.168.1.170:12553, Friday, Feb 19,2016 07:01:20

I did have DMZ enabled. I had changed the local  network number so 170 is not used locally anymore, it does not show up on the router other than in the logs.

When I looked at the log this morning there were some records with 170 in it which appears to be an Asian pacific registered addresses one is Thailand.

[LAN access from remote] from 140.205.81.52:53 to 192.168.1.170:13221, Sunday, Feb 21,2016 06:54:20
[LAN access from remote] from 140.205.81.52:53 to 192.168.1.170:13221, Sunday, Feb 21,2016 06:39:02
[LAN access from remote] from 180.183.36.210:65348 to 192.168.1.170:53930, Sunday, Feb 21,2016 06:32:58
[LAN access from remote] from 180.183.36.210:43071 to 192.168.1.170:53930, Sunday, Feb 21,2016 06:32:57

Other than these the log is mostly composed of local references.

I have made  disconnections of the modem but the external IP has not changed. I contacted the ISP provider COX and they remotely reset the modem, but this did not change the external IP and they tell me they cannot change the external IP! 

It appears to me that because the 170 address was port forwarded some scanner picked up on this and it has been distributed by some organization.

The router I have is a relatively high end consumer device but I don think it has the ability to deal with this problem.

73 Brian KF6C.

13

General / Port=713000 pop up on connect

« on: 2016-02-21, 02:05:37 »

When I try to connect I get a pop up "Port=713000" and nothing else. The radio I working very well now under K30 control even mobile. K30 turned off before attempting access with nano.

73 Brian KF6C.

14

General discussion forum / Re: remote scanning of ports

« on: 2016-02-21, 00:07:22 »

The scanning has stopped and the link is working fine.

15

General discussion forum / Re: remote scanning of ports

« on: 2016-02-20, 23:51:07 »

The router log is showing in excess of 5 port scans per second of 192.168.1.170