Network unreachable in virtualbox

[Member woodlark]

I installed antix 19.2 in virtualbox. My host computer is connected to my network by wired ethernet, and my network is 192.168.1.x. If I tell antix to use DHCP to connect, it sets the ip address to 10.0.2.15. I tried to set a static address of 192.168.1.40, and according to ifconfig, that works. However antix still cannot see my network. I have installed other distros in virtualbox (MX, Manjaro, solydx, linux lite), and none of them have any problem connecting to my network. Is there something special about antix that I am missing?

[Member Xecure]

Helpful

Up

0

::

woodlark wrote:

installed antix 19.2 in virtualbox

Which one? Net, core, base or full?

woodlark wrote:

If I tell antix to use DHCP to connect, it sets the ip address to 10.0.2.15. I tried to set a static address of 192.168.1.40, and according to ifconfig, that works.

What program do you use to setup the network?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member woodlark]

Helpful

Up

0

::

I tried both ceni and directly using ifconfig.

[Member Xecure]

Helpful

Up

0

::

Xecure wrote:

woodlark wrote:

installed antix 19.2 in virtualbox

Which one? Net, core, base or full?

I will repeat myself.
antiX 19.2 net, 19.2 core, 19.2.1 base or 19.2 full?

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member woodlark]

Helpful

Up

0

::

antix-19.2_x64-full.iso.

after my previous post, I tried Conman. No better luck.

[Member Xecure]

Helpful

Up

0

::

After setting up ethernet with ceni, connman will become “dumb” and cannot connect. If your preference is ceni, you can remove connman and reassign resolv.conf:

anticapitalista wrote:

1. Remove connman and cmst

sudo apt-get remove --purge connman cmst connman-bluetooth-firmware-antix

2. Delete the resolv.conf sym link in /etc/
3. Create a new symlink in etc like this (in a terminal)

sudo ln -s /etc/resolvconf/run/resolv.conf /etc/resolv.conf

4. Try ceni again

This should fix your problem. I am almost sure you can ping 8.8.8.8 but not google.com when using ceni. If that is so, that means that it cannot resolv the DNS properly and need resolv.conf to be “fixed”.

Sorry for the inconvenience. I was a bit insistant about antiX version because the procedure is different for each one.

antiX Live system enthusiast.
General Live Boot Parameters for antiX.

[Member woodlark]

Helpful

Up

0

::

Xecure,

Thank you for your help. It turns out that my problem was not with Antix, but with my Virtualbox settings. I needed to change the network settings “Attached To: ” from the default of “NAT” to “Bridged Adapter”.

[Member olsztyn]

Helpful

Up

0

::

woodlark wrote:

It turns out that my problem was not with Antix, but with my Virtualbox settings. I needed to change the network settings “Attached To: ” from the default of “NAT” to “Bridged Adapter”.

It may not be an antiX problem but any system in VM should still be able to see your network when config is NAT, as default. The way I understand setting it as ‘bridged’ is not necessary for that.
However I defer such determination to experts in this forum…

Live antiX Boot Options (Previously posted by Xecure):
https://antixlinuxfan.miraheze.org/wiki/Table_of_antiX_Boot_Parameters

[Author]

Posts