Perhaps I've come across a new regression in the network stack or some such, and perhaps you'llnever encounter this problem. But if you do, I did manage to find a semi-reasonable workaround, whichcould perhaps help you until your particular bridged networking issues, whatever they be on whicheverbuild of VirtualBox, are resolved. And I'm saying yours, because otherwise, you wouldn't be reading this article.