Instancing works with VPN, not without.

Hi there,
I am located in Australia and frequently wish to wing up with a buddy in Utah. This has proven to be nearly impossible since wings was first released. We might have achieved it less than half a dozen times.
When I enable a VNP, it works without fail.

Can anyone shed some light on why this might be?
Surely I shouldn't have to subscribe to a VPN just to be able to use what is essentially a core feature of the game.
 
No clue. A Virtual Private Network is inherently a slower connection than not, and these types of VPN's, really little more than proxies, should not have this effect - unless something along your route between you and your friend is somehow interfering with traffic and you're managing to bypass that route some how.

It would be interesting to see some tracert reports between your IP and your friend, both on and off the VPN.
 
I have no idea how to do any of that.

Although I just did a latency check and my latency isn't any worse than what it was without the VPN, 269ms to a New York server.
 
Last edited:
I have no idea how to do any of that.

Although I just did a latency check and my latency isn't any worse than what it was without the VPN, 269ms to a New York server.

Look at that speed test, it should show you the IP of the server you're testing again.
From a DOS prompt, enter tracert www.xxx.yyy.zzz (the IP of the server you tested against).
Not all that interested in hop 1, but 2-30 are of interest.
 
OK, I worked it out.

Tracing route to cpe-68-203-225-97.gt.res.rr.com [68.203.225.97]
over a maximum of 30 hops:

1 197 ms 199 ms 198 ms 10.110.230.1
2 199 ms 199 ms 198 ms v134.ce02.sfo-12.us.leaseweb.net [209.58.135.125]
3 202 ms 206 ms 200 ms be-2.br02.sfo-12.us.leaseweb.net [209.58.135.200]
4 204 ms 201 ms 200 ms te-0-2-0-4.bb02.sfo-11.leaseweb.net [31.31.39.2]
5 199 ms 201 ms 199 ms sjo-b21-link.telia.net [213.248.88.209]
6 206 ms 205 ms 207 ms las-b21-link.telia.net [62.115.116.41]
7 244 ms 243 ms 278 ms timewarner-ic-305702-las-b21.c.telia.net [62.115.36.58]
8 * 252 ms 254 ms bu-ether27.tustca4200w-bcr00.tbone.rr.com [107.14.19.57]
9 246 ms 246 ms 247 ms bu-ether16.dllstx976iw-bcr00.tbone.rr.com [66.109.6.1]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * ^C


NO VPN

Tracing route to cpe-68-203-225-97.gt.res.rr.com [68.203.225.97]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Budii.iiNet [10.1.1.1]
2 5 ms 6 ms 7 ms lo0.bng1.mel4.on.ii.net [150.101.32.44]
3 5 ms 6 ms 6 ms ae4.cr1.mel4.on.ii.net [150.101.33.106]
4 25 ms 17 ms 17 ms ae2.br1.syd7.on.ii.net [150.101.33.28]
5 173 ms 173 ms 172 ms te0-1-1-3.br2.sjc2.on.ii.net [150.101.33.149]
6 * * * Request timed out.
7 222 ms 219 ms 219 ms bu-ether15.snjucacl67w-bcr00.tbone.rr.com [66.109.6.142]
8 221 ms 222 ms 223 ms bu-ether13.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.7]
9 225 ms 226 ms 220 ms bu-ether11.tustca4200w-bcr00.tbone.rr.com [66.109.6.5]
10 220 ms 222 ms 222 ms bu-ether16.dllstx976iw-bcr00.tbone.rr.com [66.109.6.1]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
 
OK, I worked it out.

Tracing route to cpe-68-203-225-97.gt.res.rr.com [68.203.225.97]
over a maximum of 30 hops:

1 197 ms 199 ms 198 ms 10.110.230.1
2 199 ms 199 ms 198 ms v134.ce02.sfo-12.us.leaseweb.net [209.58.135.125]
3 202 ms 206 ms 200 ms be-2.br02.sfo-12.us.leaseweb.net [209.58.135.200]
4 204 ms 201 ms 200 ms te-0-2-0-4.bb02.sfo-11.leaseweb.net [31.31.39.2]
5 199 ms 201 ms 199 ms sjo-b21-link.telia.net [213.248.88.209]
6 206 ms 205 ms 207 ms las-b21-link.telia.net [62.115.116.41]
7 244 ms 243 ms 278 ms timewarner-ic-305702-las-b21.c.telia.net [62.115.36.58]
8 * 252 ms 254 ms bu-ether27.tustca4200w-bcr00.tbone.rr.com [107.14.19.57]
9 246 ms 246 ms 247 ms bu-ether16.dllstx976iw-bcr00.tbone.rr.com [66.109.6.1]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * ^C


NO VPN

Tracing route to cpe-68-203-225-97.gt.res.rr.com [68.203.225.97]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Budii.iiNet [10.1.1.1]
2 5 ms 6 ms 7 ms lo0.bng1.mel4.on.ii.net [150.101.32.44]
3 5 ms 6 ms 6 ms ae4.cr1.mel4.on.ii.net [150.101.33.106]
4 25 ms 17 ms 17 ms ae2.br1.syd7.on.ii.net [150.101.33.28]
5 173 ms 173 ms 172 ms te0-1-1-3.br2.sjc2.on.ii.net [150.101.33.149]
6 * * * Request timed out.
7 222 ms 219 ms 219 ms bu-ether15.snjucacl67w-bcr00.tbone.rr.com [66.109.6.142]
8 221 ms 222 ms 223 ms bu-ether13.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.7]
9 225 ms 226 ms 220 ms bu-ether11.tustca4200w-bcr00.tbone.rr.com [66.109.6.5]
10 220 ms 222 ms 222 ms bu-ether16.dllstx976iw-bcr00.tbone.rr.com [66.109.6.1]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.

Mine, as a comparison:
2 9 ms 8 ms 8 ms 142.254.150.161
3 468 ms 21 ms 19 ms 24.164.99.57
4 17 ms 15 ms 14 ms be23.pltsohae01r.midwest.rr.com [24.33.103.70]
5 29 ms 16 ms 14 ms be25.clmkohpe01r.midwest.rr.com [65.29.1.28]
6 27 ms 24 ms 30 ms bu-ether15.chctilwc00w-bcr00.tbone.rr.com [66.109.6.68]
7 51 ms 55 ms 55 ms bu-ether13.dllstx976iw-bcr00.tbone.rr.com [66.109.6.22]
8 * * * Request timed out.
Time outs through hop 30. We've hit a number of the same routers along the way though.
Now to be fair, I am in the US, so I'm not going quite as far as you are, but I suspect there may be some sort of either traffic control on your side, as your 2nd and 3rd hops are already in the US, on VPN, and still in the Melbourne area off of it. If that's the case, then that may explain why you don't have instancing issues using it and roughly the same RTT.
 
So basically getting info out of Aus is the hard part? Surprises me not.

I wonder if it's possible for Frontier to implement some form of a workaround?
 
Last edited:
Is it only you who gets on the VPN or both of you?

Does it matter which area you connect to?

Have you tried it with more than 2 people?
 
Only I am using the VPN, to appear as though I am on the west coast of the USA. I am getting populated instances all of the time now and my buddy is always in them. As opposed to empty instances 90% of the time and never being able to wing up with my buddy.
 
Don't worry about the timeouts lots of webservers just don't send you back a response as it's something they are not obligated to do, it doesn't mean it's not working properly.

I think the problem you may be having is simply a case of you being in diffirent areas of the world, I believe the netcode is suppose to match you up with others from your area to help with lagg etc etc.

Can't help but wonder if this doesn't affect when people from vastly different areas of the world try to team up, would explain some of the spotty problems people encounter when trying to play in wing.


I wouldn't be surprised at all if you guys "switched", as in you just play with no vpn and he uses on and makes it look like he in australia that would work too.
 
Last edited:
Don't worry about the timeouts lots of webservers just don't send you back a response as it's something they are not obligated to do, it doesn't mean it's not working properly.

I think the problem you may be having is simply a case of you being in diffirent areas of the world, I believe the netcode is suppose to match you up with others from your area to help with lagg etc etc.

Can't help but wonder if this doesn't affect when people from vastly different areas of the world try to team up, would explain some of the spotty problems people encounter when trying to play in wing.

I've long suspected that, which is why I tried out the VPN. The fact the VPN works some what confirms this theory.
Now my question is, can Frontier give us the option to circumvent this "feature" so we can play with friends and player group allies around the world?
 
Last edited:
I've long suspected that, which is why I tried out the VPN. The fact the VPN works some what confirms this theory.
Now my question is, can Frontier give us the option to circumvent this "feature" so we can play with friends and player group allies around the world?

Dunno maybe but it would require changing the netcode they use since we don't use a traditional server like most mmo do.
 
Last edited:
Elite is the only game that seems to have this problem on such a consistent basis. Surely there is something the can do.

Oh I am pretty sure they could do something, finding the motivation to on the other hand..dunno they chose a p2p netcode and knew going in the pitfalls this has compared to having everyone connect to a main server like most games do.
 
I live in Guam and I use a VPN to get better instancing.

My theory is that the VPN fools the game into thinking you are in a different location (I use a server in Los Angeles fairly frequently), so it instances based on the ping time to the LA server rather than the ping time to my actual PC out here in the middle of the Pacific Ocean.

The downside to the VPN method is that it leads to more syncing issues. Anytime I can get good instancing naturally, without my VPN, is preferred.
 
Last edited:
A lot really depends on the ISP's involved, how they view VPN traffic, and their peerage deals.

FD themselves, and their P2P model, are pretty blameless in this.

Blame thieving infrasturcture companies, Hollywood demands, and cheap ISP's who sling absolutely everything they can over awful backhauls.

There is nothing wrong with using VPN, and if it helps your instancing then that is great - but it's really not helping actual instances or your traffic flow. The speed of light isn't changing any time soon.
 
Last edited:
A lot really depends on the ISP's involved, how they view VPN traffic, and their peerage deals.

FD themselves, and their P2P model, are pretty blameless in this.

Blame thieving infrasturcture companies, Hollywood demands, and cheap ISP's who sling absolutely everything they can over awful backhauls.

There is nothing wrong with using VPN, and if it helps your instancing then that is great - but it's really not helping actual instances or your traffic flow. The speed of light isn't changing any time soon.



EH no. it's not about speeds it about FD making a p2p code that wants you to play with people near your area and not with those too far away...it about people that are trying to get into an instance needing to connect to each other machine rather than them connecting to a server run by FD.

Like the post above said the vpn is working cause it fooling the netcode into thinking the guy from down under is in usa like the other guy is.

At least that what I think is happening, I could be wrong. One thing for sure though if they had done a proper server instead like most games do now no one would be having these problems.
 
Last edited:
EH no. it's not about speeds it about FD making a p2p code that wants you to play with people near your area and not with those too far away...it about people that are trying to get into an instance needing to connect to each other machine rather than them connecting to a server run by FD.

Like the post above said the vpn is working cause it fooling the netcode into thinking the guy from down under is in usa like the other guy is.

That still does not change the speed of light. In fact is makes everything worse.

Between wiretime, transition time, routing time, more wiretime, and finally VPN decoding time - your "shoot lasers" packet can arrive before "deploy hardpoints"

Guess what happens then?
 
That still does not change the speed of light. In fact is makes everything worse.

Between wiretime, transition time, routing time, more wiretime, and finally VPN decoding time - your "shoot lasers" packet can arrive before "deploy hardpoints"

Guess what happens then?

That's not relevant to topic though which is them being unable to connect to each other...
 
Back
Top Bottom