By Xander Koote 984334
#537092 Hello guys,

since forever I have been having issues logging in to vPilot when the are a lot of people connected. Basically when flying in tje weekend out of EGLL it is offline because I constantly get error 10060. So I read up a bit and it seems setting up port forwarding and Static IP address seems like a possible fix. As of now I have vPilot as an allowed app in Win 10 x64 on both private and public networks. But delving deeper into network settings was my last option since even though I am tech savvy, networking seems like freaking black magic to me. So my question is;

In my UAE Etisalat router I have an option to forward ports. However it asks me for the IP address. I run vPilot over a network. So which IP address do I put. The host PC or the remote PC?

Also just as an FYI I don’t have any issues of getting disconnected if I don’t transmit for a while. It is just that when I try to connect, you see vPilot trying to populate traffic and ATC, however after about 30 seconds if it has not managed to get all data, I get disconnected from the network.

Cheers,

Xander
By Nick Botica 999991
#537206 Seems strange.
I wouldn’t have thought Pitt forwarding would help though. If your computer establishes the connection then your router knows which computer it came from, and, when it gets a reply passes the message back.

What is the model of your router? Maybe check the bottom for a label. Perhaps there’s a firewall built in to the router which is stopping the connection after seeing a lot of traffic on a non normal port.

You IP address shouldn’t be changing that often. But you could try settling a static IP address on your computer. Eg 192.168.1.10 (depending on your subnet and DHCP).
By Xander Koote 984334
#537225 Hi,

I have been having this issue for quite a while on and off. vPilot just bugs out (disconnects) if there’s too much traffic. I live in Dubai and I know they are notorious for monitoring the internet through their ISP’s.
I have just finished flying and have set static IP’s for my host and remote PC’s as well as the previously mentioned port forwarding. That, together with the Windows 10 allow an app settings and fingers crossed it’ll be better next time.
The router is a DIR-850L. There is no mention of firewall on its info sticker. The firewall setting in setup only refers to filtering choices which are off, VLAN and DMZ which are also off and the port forwarding page where I forwarded ports 3290-3291 to my host PC (now) static IP.
Over here however, that router is plugged into a dedicated ISP box before disappearing into the wall. An Etisalat branded Huawei HG8240H.

Xander
By Xander Koote 984334
#538473 So I still have the same problems whenever the airspace is busy with controllers and ATC. I get bumped off no matter what server I try. I have attached my debug if it helps. Error 10060 is the recurring error. Is there anything I can try? I have read somewhere about certain routers or ISP's timing out connections if no data is received after a certain time? Forgot to mention that this happens in both a networked and local setup. Any help would be appreciated. Steps already performed are:

1. vPilot allowed in Windows Security on both PC's (server and client)
2. Opened ports 3290/3291 on the host PC IP in the router

[15:58:31.313] vPilot version 2.4.0
[15:58:39.863] Event received from remote: CommandSubmitted
[15:58:39.864] Command submitted: ConnectToNetworkCommand
[15:58:39.865] Connecting to network...
[15:58:39.946] Connected to network.
[15:58:40.358] Received capabilities request from AAL001 - sending CAPS
[15:58:40.358] Received capabilities request from unknown callsign: AAL001
[15:58:40.638] Received capabilities request from DLH1340 - sending CAPS
[15:58:40.639] Received capabilities request from BAW9697 - sending CAPS
[15:58:40.639] Received capabilities request from EDGG_T_CTR - sending CAPS
[15:58:40.639] Aircraft discovered: UAE44 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:40.640] Received capabilities request from unknown callsign: DLH1340
[15:58:40.640] Received capabilities request from unknown callsign: BAW9697
[15:58:40.640] Received capabilities list from: BAW9697 - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:40.643] Requesting full ACCONFIG packet from BAW9697
[15:58:40.644] Received capabilities request from unknown callsign: EDGG_T_CTR
[15:58:40.992] Received capabilities request from RYR11NW - sending CAPS
[15:58:40.993] Received capabilities request from UKV44Y - sending CAPS
[15:58:40.994] Received capabilities request from BAW2672 - sending CAPS
[15:58:40.995] Received capabilities request from LFUP_CTR - sending CAPS
[15:58:40.996] Received capabilities request from SAS300 - sending CAPS
[15:58:40.997] Received capabilities list from: DLH1340 - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:40.998] Requesting full ACCONFIG packet from DLH1340
[15:58:40.998] Received capabilities request from unknown callsign: RYR11NW
[15:58:40.999] Received capabilities request from unknown callsign: UKV44Y
[15:58:41.000] Received capabilities list from: RYR11NW - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:41.001] Requesting full ACCONFIG packet from RYR11NW
[15:58:41.002] Received capabilities request from unknown callsign: BAW2672
[15:58:41.003] Received capabilities list from: UKV44Y - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:41.003] Requesting full ACCONFIG packet from UKV44Y
[15:58:41.004] Received capabilities request from unknown callsign: LFUP_CTR
[15:58:41.005] Received capabilities list from: BAW2672 - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:41.006] Requesting full ACCONFIG packet from BAW2672
[15:58:41.006] Received capabilities request from unknown callsign: SAS300
[15:58:41.310] Received capabilities request from UAE44 - sending CAPS
[15:58:41.311] Aircraft discovered: AAL001 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:41.312] Received capabilities request from UAE44 - requesting aircraft info
[15:58:49.752] Received capabilities request from MSR986 - sending CAPS
[15:58:49.753] Aircraft discovered: DLH1340 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.754] Received aircraft configuration info from UAE44: {"config":{"spoilers_out":true}}
[15:58:49.755] Received capabilities list from: UAE44 - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:49.755] Requesting full ACCONFIG packet from UAE44
[15:58:49.759] Received capabilities request from unknown callsign: MSR986
[15:58:49.760] Aircraft discovered: UKV44Y - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.760] Aircraft discovered: SAS300 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.761] Received capabilities list from: MSR986 - VERSION=1:ATCINFO=1:MODELDESC=1:ACCONFIG=1
[15:58:49.762] Requesting full ACCONFIG packet from MSR986
[15:58:49.763] Aircraft discovered: BAW9697 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.764] Aircraft discovered: MSR986 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.765] Aircraft discovered: BAW2672 - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.766] Aircraft discovered: RYR11NW - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:49.769] Received aircraft configuration info from UAE44: {"config":{"spoilers_out":false}}
[15:58:49.827] Received aircraft configuration info from BAW2672: {"config":{"lights":{"strobe_on":true}}}
[15:58:52.239] Still no type code received for UAE44 after position update #3 - requesting aircraft info
[15:58:52.241] Received aircraft configuration info from BAW2672: {"config":{"lights":{"strobe_on":false}}}
[15:58:52.241] Still no type code received for DLH1340 after position update #3 - requesting aircraft info
[15:58:52.243] Still no type code received for AAL001 after position update #3 - requesting aircraft info
[15:58:52.244] Still no type code received for UKV44Y after position update #3 - requesting aircraft info
[15:58:52.245] Still no type code received for SAS300 after position update #3 - requesting aircraft info
[15:58:52.245] Still no type code received for BAW9697 after position update #3 - requesting aircraft info
[15:58:52.878] Discovered controller: EDGG_T_CTR
[15:58:53.444] Still no type code received for MSR986 after position update #3 - requesting aircraft info
[15:58:53.826] Discovered controller: LFUP_CTR
[15:58:54.150] Still no type code received for BAW2672 after position update #3 - requesting aircraft info
[15:58:54.755] Still no type code received for RYR11NW after position update #3 - requesting aircraft info
[15:58:55.494] Still no type code received for UAE44 after position update #4 - requesting aircraft info
[15:58:56.252] Still no type code received for AAL001 after position update #4 - requesting aircraft info
[15:58:56.369] Still no type code received for DLH1340 after position update #4 - requesting aircraft info
[15:58:56.507] Received aircraft configuration info from BAW2672: {"config":{"lights":{"strobe_on":true}}}
[15:58:56.969] Still no type code received for UKV44Y after position update #4 - requesting aircraft info
[15:58:56.970] Still no type code received for SAS300 after position update #4 - requesting aircraft info
[15:58:57.163] Still no type code received for BAW9697 after position update #4 - requesting aircraft info
[15:58:58.262] Still no type code received for MSR986 after position update #4 - requesting aircraft info
[15:58:58.446] Aircraft discovered: RYR5MU - requesting CAPS, sending CAPS, requesting aircraft info
[15:58:59.156] Still no type code received for BAW2672 after position update #4 - requesting aircraft info
[15:58:59.564] Network error: EndReceive failed: (10060) A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
[15:58:59.581] Disconnected from network.
[15:58:59.582] Deleting all controllers
[15:58:59.583] Aircraft deleted - Callsign: UAE44 - Reason: Disconnect
[15:58:59.584] Aircraft deleted - Callsign: AAL001 - Reason: Disconnect
[15:58:59.585] Aircraft deleted - Callsign: DLH1340 - Reason: Disconnect
[15:58:59.586] Aircraft deleted - Callsign: UKV44Y - Reason: Disconnect
[15:58:59.587] Aircraft deleted - Callsign: SAS300 - Reason: Disconnect
[15:58:59.588] Aircraft deleted - Callsign: BAW9697 - Reason: Disconnect
[15:58:59.588] Aircraft deleted - Callsign: MSR986 - Reason: Disconnect
[15:58:59.589] Aircraft deleted - Callsign: BAW2672 - Reason: Disconnect
[15:58:59.590] Aircraft deleted - Callsign: RYR11NW - Reason: Disconnect
[15:58:59.591] Aircraft deleted - Callsign: RYR5MU - Reason: Disconnect
By Nick Botica 999991
#538501 There are logs on your router you could look at. Clear the logs then recreate the problem. Once the error occurs stop logging, or export them to have the least logs possible.

Another thing to try would be to bypass the router temporary if you could go rule it out. Connect the cable from the modem to your router to you computer instead. It most likely won’t connect without some config.
First check how your router connect to your modem eg dynamic ip, username and password, static ip...then mimic that on your computer.