Leaderboard

Hi there, I am the main developer of the OpenVPN DCO kernel module and I am really happy to hear that you guys have been testing it out! The larger the user base, the faster we can find and squash bugs! Regarding compiling DCO, we normally strive to have it always compile on the latest kernel. However, in the past few weeks we were focused on implementing some big and important changes, therefore we had to shift our effort a bit and could not work on compatibility with 6.1/6.2. However, I think master compiles on 6.2 since a month at least. I just tested in this very moment whether it compiles on the latest netdev tree and it does. So it should all be good for 6.3 as well! Regarding issues: if you have experienced anything that could be reported, please do so on GH in the issue page. It's *vital* that users experiencing problems do report them upstream and provide reproducible steps (if possible). At the moment we still have a few "quite hard to reproduce" issues open and it'd be nice to receive any kind of input regarding them if you are experiencing the same.

@sebi Hello! You need to uncheck "Use Hummingbird if available" in the "Preferences" > "Advanced" window. Eddie will then look for OpenVPN in your command path (OpenVPN must be installed in your Linux box). If you have some OpenVPN binary you want to use outside the path, then you need to tell Eddie where to find that OpenVPN binary. Note that Eddie will run with root privileges only binaries owned by root. Beta versions exist exactly because unexpected problems may (and usually will) come out. Eddie stable releases are always packaged with a tested Hummingbird version. About the Suite, we are almost ready to launch a version linked against our openvpn-airvpn fork fixing the new bugs and regressions unfortunately inherited from the main branch which we did not find with our tests (our fault, hands down). If you want to use Eddie with a working version of Hummingbird you can rely on Eddie 2.21.8, which is the latest stable release and is packaged with Hummingbird 1.2.0. This is an excellent question, and currently Eddie can not renounce to those directives for a complex reason. In a few words, with the risk of oversimplifying, it's because of how our servers are configured in order to maintain backward compatibility with OpenVPN 2.3 and 2.4. Sooner or later we will break compatibility at least with OpenVPN 2.3. From that moment on, Eddie can be re-designed with more freedom in mind and some behavior which may appear "strange" when compared with ordinary OpenVPN configuration files (as it is in this case, with the directives you mention) can be simplified or canceled. Also note that some other behavior is dictated by the fact (and this is perfectly logic as well) that Eddie adds some important features on top of OpenVPN features (routes inside and outside the tunnel, DNS management, Network Lock...). Thank you, this sounds like a bug and it's great that bugs are found during beta testing (or anyway before a stable version is out). We will forward your message to Eddie's developer. Furthermore, please feel free to report this on GitHub and on Eddie's thread in "News", if you wish so. Kind regards

Maybe we already built DCO including the TCP rework (on our dedicated server)? Can you tell when the rework and simplification have been committed? To use that change you need openvpn 2.6.2 in userspace, which was released just yesterday. So the tests you performed were still using the old ovpn-dco version. You can easily check dmesg and see what version you have loaded. If the DCO version starts with v0.1 it means it's the "old" one. If it starts with v0.2, then you have the newest version including the change I am talking about. Just remember that you must use openvpn-2.6.2 to be able to use DCO v0.2. Should you guys have a chance to run DCO v0.2 and encounter any issue, do not hesitate to let us know! Thanks a lot

Longtime AirVPN user, since 2012, and I would choose no other VPN! Very, very pleased over the years! Thank you team! Meanwhile, for some reason my phone has just recently gotten around to updating to Eddie 3.0, however, now Eddie only stays connected to a server for a few minutes at a time! It is constantly disconnecting. There is no problem connecting to a server, however, it will only stay connected for a few minutes. Has anyone else had this issue, and is there a known solution? Thank you for your time!

None of my business, really, but as a member of the community who has used AirVPN daily for years and who has family and friends who have as well, and who is an engineer with decades of experience solving technical problems, I'm just going to interject that I am also offended by the OP's attitude that if something is wrong, surely it must be because someone is trying to cheat him. Super poor vpn performance across many of a providers' servers is actually not indicative of a "bad vpn" (go stand in the corner!), but the technical settings in the software that will work for your situation can depend on many things, even the particulars of your ISP's service. Set the MTU too high for a particular ISP's network, for example, and you can bring any VPN system to its knees, not because the VPN server is slow — it isn't — but because the network between you and that server is not getting packets to the server efficiently. In that situation it's like it can't run or even walk because it's tripping over its own feet with every step. Is that the fault of the destination? Networks are complicated. It's the reality and a lot of crazy things can bog them down. Air has a really fast VPN system, and they have the best technical support I have ever seen. Work with them on sorting out what's going wrong in your particular situation and killing most of your speed, and do it without the insults. This is almost certainly something that can be cured with an easy adjustment at your end, once the problem is identified.