Michael Tokarev <m...@tls.msk.ru> wrote:
switch away from the user-mode networking since it is really incomplete and not everything works with it. It is good for quick testing but definitely not for anything serious.
I only use this particular guest to test changes to a program. I always test first on the host, because the host is already configured for the most common way I use the program. Then I test in the guest, because there are some other configurations that are easier for me to have set up in a VM, instead of reconfiguring the host. To do this, I need to copy the new program from host to guest (about 4 megabytes), run the tests, and then copy the test results back from guest to host (maybe 60-120 megabytes or so). I do this about two or three times a year. For that level of usage, combined with the ease of setup, I find the user-mode networking to be perfectly acceptable.
It might be easier to switch to either oldstable (with its own load of bugs including security ones!) or to current stable than to backport stuff to old-old-stable.
This one is on me. I just haven't upgraded this host off of oldoldstable (9) yet. I have other hosts that have been running oldstable (10) for a while now with no problems. (I didn't discover 11 was out until I was researching package version numbers for this bug report.) I reported it anyway because it seemed to be caused by the recent patch, and I thought it might affect other releases as well. In your next email, you noted
btw, email from our mailserver is incorrectly blocked by your provider:
I didn't know this was happening. I will contact the email address provided in the bounce message, but I don't know how much effect it will have. I don't work at AT&T or have control over AT&T's mail servers. I know email from bugs.debian.org to me was working as recently as November 2020, because I got a message about another bug at that time. I haven't filed any new bugs since then. I *did* get the automatic "marked as closed" email from ow...@bugs.debian.org about this bug when Markus closed it, and another one from that same address a few minutes ago after I submitted my "it's working" report, so not everything seems to be blocked. Matt Roberds
