Pi77Bull 0 Posted ... Hi everyone. I have a couple of issues. For your information: I'm using Fedora 43 (KDE Spin) on a Laptop with WiFi and the AirVPN Suite 2.0.0. My bluetit.rc file looks like (I stripped bootstrap servers and RSA parameters): airconnectatboot quick networklockpersist on airusername <redacted> airpassword <redacted> airkey Laptop forbidquickhomecountry on country us tunpersist on networkcheck off allowprivatenetwork on allowping off ignorednspush off allowtrafficsplitting on trafficsplitfirewall on and my goldcrest.rc only specifies air-user, air-password and air-key. When 'networkcheck' was 'on' (the default value), the bluetit.service got stuck waiting for the network ('systemctl status bluetit' printed something along the lines of "waiting for network" over and over again) Now that it's set to 'off' everything works as expected. Traffic splitting doesn't work. I suspect this has to do with Fedora restricting user namespaces (or something like that). I'm not very familiar with that. When I run 'cuckoo -r bash' I get this output: ERROR setnamespace: Cannot open directory '/etc/netns/aircuckoo': No such file or directory Or maybe it's something completely different, I really don't know. When disconnecting the connection via 'goldcrest --disconnect' and after that reconnecting via 'goldcrest --reconnect', I get the following error: ERROR: Cannot start WireGuard connection. Client name and user name (system login name) not provided. When reconnecting while the connection is still active, everything works. If anybody can help with with 2. and 3. I'd be very happy. If you need more info, please ask. Quote Share this post Link to post
Staff 10477 Posted ... @Pi77Bull Hello! 1. This is a bug experienced on different distributions by a few users but not reproducible on our systems at the moment. A comprehensive inquiry to understand and fix the issue is slated for the near future. In the meantime, can you please also test this: networkcheck airvpn and verify what happens? Remember to re-start Bluetit each time you edit its configuration file, of course. Can you also tell us whether the Docker daemon dockerd is running in your system? According to another report, when this daemon runs (even if no containers are created) the problem you experience appears, and when the daemon is stopped networkcheck works fine but only in airvpn mode and not in gateway mode. 2. This is unexpected. Can you please send us a complete Bluetit log taken after the problem has occurred? sudo journalctl | grep bluetit > bluetit.log 3. This is expected as the reconnect option is intended solely for the re-establishment of an extant session. A more contextually apposite, tailored to your specific circumstance, error message will be duly considered. Kind regards Quote Share this post Link to post
Pi77Bull 0 Posted ... 1. With networkcheck airvpn the connection was successfull, but between resuming from sleep and establishing the connection I was able to check my public IP and saw my real one. With networkcheck off this doesn't happen. I've attached two logs - one with networkcheck on and one with networkcheck airvpn . Regarding Docker, I have never installed Docker on this machine. I have Podman, though I don't use it and its services are all stopped and disabled. 2. I've attached the log from right after running cuckoo -r bash . It says "Cannot find a free IPv4 in 's network". Seems like it can't find the network or something. 3. OK, good to know. networkcheck_airvpn_bluetit.log networkcheck_on_bluetit.log trafficsplit_bluetit.log Quote Share this post Link to post
Staff 10477 Posted ... @Pi77Bull Hello! Thanks for all the logs. They will help us address the waiting for network loop problem which is under investigation. The traffic splitting configuration is "dirty" for unknown reasons. You might resolve this specific problem by deleting the /etc/netns/aircuckoo directory content while Bluetit is not running. Please let us know whether this operation solves the problem or not. Kind regards Quote Share this post Link to post