<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">No, I'd just run<div class="">port echo rdepends:vde2</div><div class="">and noticed virtualbox and a couple of related sub-ports in the output.</div><div class=""><br class=""></div><div class="">Still, I gather one could also use vde2 with some builds of QEMU, for example. So it presumably still has its uses, esp. since it can apparently optionally apply degrees of network impairment, perhaps useful for testing network stack or network server or client application robustness without expensive test hardware.<br class=""><div><br class=""></div><div>I'm not sure why I have vde2 installed, actually. I might have been thinking of building something that required it (not necessarily something in MacPorts), but I don't recall what that might be. I recall having some interest in getting hercules with bridged networking to work (both with the host and out to the internet) even if only WiFi and not Ethernet was in use (ISTR that local to the host didn't work with only WiFi and their implementation of bridging, but I could be misremembering); but hercules doesn't seem to have any need or option for vde2, so that probably wasn't it.</div><div><br class=""></div><div><br class=""></div><div><blockquote type="cite" class=""><div class="">On Oct 5, 2019, at 14:39, Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><div class="">Oh, gosh -- our virtualbox port is so old and out of date I wouldn't even consider using it.</div><div class=""><br class=""></div><div class="">it should probably be removed, I guess. </div><div class=""><br class=""></div><div class="">Do you actually have it installed? I am startled if so !</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Ken</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><br class=""><div class=""><div class="">On 2019-10-05, at 11:08 AM, Richard L. Hamilton wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite" class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Thank you! From the tickets you filed, it certainly looks like you did a thorough job of investigating and reporting the issues. Hopefully they'll get to it reasonably soon, although clearly that's beyond your control.<div class=""><br class=""></div><div class="">Given that virtualbox depends on it (at least if the vde2 variant is enabled), I was surprised that it has such issues left unresolved. But in</div><div class=""><a href="https://www.virtualbox.org/manual/ch06.html#network_vde" class="">https://www.virtualbox.org/manual/ch06.html#network_vde</a></div><div class="">I see "At the moment this option requires compilation of Oracle VM VirtualBox from sources, as the Oracle packages do not include it." So I guess the folks with commercial resources also just avoided that.</div><div class=""><br class=""></div><div class="">Would it be a good idea, until vde2 is working again (not that it would help anyone with the virtualbox port already installed), to have it not be a default variant for the virtualbox port? (that's how I read [+]vde2 in the output of port info virtualbox)</div><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On Oct 5, 2019, at 09:21, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" class="">ryandesign@macports.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><br class="">On Oct 4, 2019, at 21:41, Richard L. Hamilton wrote:<br class=""><br class=""><blockquote type="cite" class="">I see that kdelibs4 and xmms2 are ok now; thanks to whoever did that (esp. kdelibs4, which is probably nasty to maintain).<br class=""><br class="">The one I have left that means I can't just "port upgrade outdated" on my system with the most packages installed, running the current (Mojave) OS, is vde2; a look at the log file makes it appear quite likely that's also an openssl changeover related problem.<br class=""></blockquote><br class="">I looked into vde2 a few days ago.<br class=""><br class="">It is not compatible with openssl 1.1, as you found.<br class=""><br class="">There is a newer version than the one we have in the port available, but it is years old and is also still not openssl 1.1 compatible.<br class=""><br class="">This has been reported to the developers. Their response was to change their code so that it uses wolfssl instead of openssl. They have not yet released a new version containing this change.<br class=""><br class="">I tried to update the port to the latest released version and backport the wolfssl change. Just getting that patch to apply required me to backport a number of other changes as well, and I don't think I ended up with a successful build after that either.<br class=""><br class="">In the process, I noticed a half dozen other problems with their code. I reported these to the developers. I was intending to wait for them to acknowledge and hopefully fix those issues and release a new stable version so that I could then update the port to that version but so far they have not responded to those reports.<br class=""><br class=""><a href="https://github.com/virtualsquare/vde-2/issues" class="">https://github.com/virtualsquare/vde-2/issues</a><br class=""><br class=""><br class=""><br class=""></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div></body></html>