![]() And it’s the same case here, so go ahead and: The good old “ have you tried turning it off and back on again?” is a good remedy against different technical hiccups. So make sure that Air Link is actually enabled before trying to launch the connection! This might and has caused confusion among a large number of VR users (including myself). In addition to that, the Air Link functionality turns off automatically after 24 hours, in which case you also have to manually re-enable it again. It’s such an obvious step, but the thing that has confused me and many others is that you have to manually enable Air Link each time you launch Oculus Software. I tested restarting my computer and Air Link was able to detect my PC even when Oculus software was not running. Update (November 2021): Starting from Oculus software v34, you don’t need to manually enable the Air Link toggle in Oculus software anymore. The first thing to check when Air Link is unable to find your PC is that you have actually enabled the Air Link functionality in the Oculus Software (Settings → Beta). To help you out, I have created this list of potential steps you can take to solve your problem and get your PC detected and connected! So let does not waste any more of your time and get started!ġ) Make Sure Air Link is Enabled in Oculus Software But what to do if you try launching Air Link connection from your headset, but it is simply unable to find your PC? Internet - ISP Router (NAT) - 192.168.49.0/24 - Opnsense Router - 192.168.38.Oculus Air Link is often praised for how easy it is to set up. I have an ISP router that runs NAT, behind that is the OpnSense router behind which is my test client What am I doing wrong? I have tried two different servers I would expect that the gateway should be up, even if I cannot route any packets across it at this point □ The two yellow addresses are 10.xx.yy.(zz-1) followed by 10.xx.yy.zz I will stop here - cos at this point the gateway isn't coming up (with 100% packet loss). Moving on Step 6 - Create a Gateway with the interface I created earlier and the 10.xx.yy.(zz-1) address I used earlier from the Interface section of the config file Gateway is Online Still no connection that I can see on AirVPN's Dashboard So Question 1: Am I correct - should I be showing a connection on "Your VPN Sessions" on AirVPN's dashboard or have I not reached that stage yet? However there is no sign of any tunnel on the AirVPN Sessions which has my 3 OpenVPN Sessions from other firewalls active and their is no handshake - but I am not sure what should be appearing there. Step 4: Assign an Interface No real config here - but again, followed the instructions.Īt this point I feel the tunnel should be up - unless I am misunderstanding things. Step 2: Configure Local Peer A Public key has appeared as has a private key Tunnel Address is as per the file 10.xx.yy.zz/10 Listen Port is randomly selected Gateway is 10.xx.yy.(zz-1) as per instructions I have set the endpoint and port as in the file and set the keepalive to the number in the file as well. I have tried with / without the PreShared Key in the appropriate EndPoint field So Step 1: Configure Endpoint I have used the public key BBBBBBBBBBBBBBBBBBBB. PublicKey = BBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBBB PresharedKey = CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC Endpoint = 146.70.94.2:1637 AllowedIPs = 0.0.0.0/0, ::/0 PersistentKeepalive = 15 I am following the guide: I have downloaded a config file with some parts masked out: Address = 10.xx.yy.zz/10, ipv6 address PrivateKey = AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA DNS = 10.128.0.1, fd7d:76ee:e68f:a993::1 HI, Hopefully by writing something here I can see what I am doing wrong.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |