FlyawayRavage 0 Posted ... (edited) Hello, When attempting a "quick" connection either with goldcrest (or the at boot connection with bluetit) with a server whitelist specified under airwhiteserverlist in /etc/bluetit.rc, the client attempts to connect to what I assume is the "best" server regardless of the whitelist only to fail with "ERROR: AirVPN Server is not allowed by Bluetit policy". I can connect to whitelist servers just fine if I manually specify one of them. I would have assumed that "quick" connection would select the "best" server within the whitelist. Have I just misconfigured something? Thanks! Edit: It seems disabling the airwhitecountrylist option fixes this. I'm not seeing anything in the readme that suggests there's this sort of interaction between the country and server whitelist options. I assumed it would just select from the intersection set of the two restrictions. Admittedly I can't think of much of a use case for using both options, but it might be useful to document how the "quick" connection option works with respect to the whitelists. I may have also missed this in the readme or just misunderstood what these settings are described to do. Here's my bluetit.rc config for reference: # # bluetit runcontrol file # # AirVPN bootstrap servers bootserver http://63.33.78.166 bootserver http://52.48.66.85 bootserver http://54.93.175.114 bootserver http://63.33.116.50 bootserver http://[2a03:b0c0:0:1010::9b:c001] # RSA Parameters rsaexponent AQAB rsamodulus wuQXz7eZeEBwaaRsVK8iEHpueXoKyQzW8sr8qMUkZIcKtKv5iseXMrTbcGYGpRXdiqXp7FqrSjPSMDuRGaHfjWgjbnW4PwecmgJSfhkWt4xY8OnIwKkuI2Eo0MAa9lduPOQRKSfa9I1PBogIyEUrf7kSjcoJQgeY66D429m1BDWY3f65c+8HrCQ8qPg1GY+pSxuwp6+2dV7fd1tiK> # bootserver <ip|url> # rsaexponent <value> # rsamodulus <value> airconnectatboot quick networklockpersist nftables airusername XXX airpassword XXX airkey Labserver # airserver aircountry us airproto tcp # airport <port> # aircipher <cipher_name> # airipv6 <yes|no> # air6to4 <yes|no> # manifestupdateinterval <minutes> airwhiteserverlist Saclateni # airblackserverlist <server list> # airwhitecountrylist us # airblackcountrylist <country list> forbidquickhomecountry no country us # remote <ip|url list> # proto <udp|tcp> # port <port> # tunpersist <yes|no> # cipher <cipher_names> # maxconnretries <number> # tcpqueuelimit <value> # ncpdisable <yes|no> networklock nftables # ignorednspush <yes|no> # timeout <seconds> Edited ... by FlyawayRavage Quote Share this post Link to post
Staff 9972 Posted ... 15 hours ago, FlyawayRavage said: Edit: It seems disabling the airwhitecountrylist option fixes this. I'm not seeing anything in the readme that suggests there's this sort of interaction between the country and server whitelist options. I assumed it would just select from the intersection set of the two restrictions. Admittedly I can't think of much of a use case for using both options, but it might be useful to document how the "quick" connection option works with respect to the whitelists. I may have also missed this in the readme or just misunderstood what these settings are described to do. Hello! We will look into the issue together with the developer. Your case is peculiar as you enforce a white list of a single server, so it is equivalent to specify the connection to a single server directly and not to a country and not in quick mode. You can be right, the manual may document more thoroughly the interaction and/or the program could manage the situation differently. Something under this respect was planned anyway, please feel free to test next releases of the Suite 2 preview: Kind regards Quote Share this post Link to post