I'm just wondering, after you installed VirtualBox, did you happen to restart your computer? There's a couple of kernel modules that are added via DKMS when you install VirtualBox, mostly having to do with networking.
I suspect that NAT may work without these kernel modules, kind of like how KVM user-mode networking works, but I'm certain those drivers would be needed for bridged networking as it effectively bypasses Linux's network stack to make like a virtual network adapter.
So, if you've been doing all this without rebooting, reboot and try again to see if that helps.
I find this behavior odd. If I install Linux on a laptop or desktop
Linux's config is what matters. And that is what I was expecting from
VirtualBox. VirtualBox does things that actually interfere. I'm sure
it has all these features for a reason. I was expecting to Install
Linux and be on with my life. I might have spent 20 hours on this
project. And I expect to spend more time on it. Hopefully I will be
done with it by tonight.
I want to try another flavor of Linux on my desktop (another old
laptop), probably Mint... I know it is also Debian... any suggestions on
a distro to try for my desktop for testing VirtualBox only? Id another
distro works than it might be something within Kubuntu.
On 2022-11-15 23:54, Steve Litt via PLUG-discuss wrote:
> Bob Elzer via PLUG-discuss said on Tue, 15 Nov 2022 21:30:14 -0700
>
>
>> If you're local IP address was 192, where did the 10 address come
>> from?
>
> If VirtualBox is anything like Qemu, the 10 is because the default
> behavior is to NAT the VM guest to 10.whatever. In Qemu this behavior
> can be changed, as documented at
> you can do the same thing with VirtualBox.
>
> SteveT
>
> Steve Litt
> Autumn 2022 featured book: Thriving in Tough Times
> ---------------------------------------------------
> To subscribe, unsubscribe, or to change your mail settings:
---------------------------------------------------
To subscribe, unsubscribe, or to change your mail settings: