Hi Yogib33r,
I'm going to quote you in a different order in the hope it make things more clear for you.
excuse me it is new to me, i'm use to make vms on qemu but as new linux ones and sometimes win$
You can forget everything related to running AROS in qemu as the procedure for running AROS hosted is different.
Having said that, running AROS hosted on Windows or Linux is pretty much the same except for the fact that running AROS hosted on Windows is currently missing a few features (such as windows hosted does not support audio and networking).
So then i used the script of the iso when choicing eth0, /home directory with folders and didn't touched to the network even if i tried the dhcp one.
I am not familiar with the Icaros Desktop hosted installation script so i can not really comment on that.
What i can do for you is make some generic remarks that will hopefully be able to make things more clear for you. If not then please feel free to comment/ask.
Running AROS hosted (either on Linux or Windows) let you run AROS as a normal windows/Linux process as you would run any other program on these OS-es.
The only difference with a normal program is that AROS is actually a complete operating system (that in itself wil be able to run AROS programs).
In order to accomplish that, it is required that you copy all files from the .iso to a specific directory from where you wish to run AROS (hosted).
I am assuming that the Icaros Desktop script is doing that automatically for you. In my case (becuase i do things in a custom way) i copied all necessary AROS files to a directory of my choice.
When all necessary files are in place you can then start AROS hosted by invoking the AROSbootstrap executable. For example on my raspberry pi I do that by typing the command "/home/apps/AROS/AROS-20190318-linux-armhf-system/Arch/linux/AROSBootstrap -m 200". Note that the actual location of the AROSBootstrap executable may vary and might be at a different location on your AROS hosted installation.
If you know where exactly your AROSbootstrap executable is located you can then incorporate that into your network startup script.
Again please note that i am using the script as is shown
here on the wikibook.
That script contains two network routes: one for wired (eth0) and one for wirelesws (wan0) and i only wanted to use the wired one (so i removed the wan0 routing). Whn the hosting part of the network is setup correctly i wanted the script to start AROS, so that my script looks like:
#!/bin/sh
# store current directory
CWD="$(pwd)"
NETON=`ifconfig | grep aros0`
if [ "$NETON" = "" ]; then
echo "Installing bridge network... (sudo access required)"
sudo tunctl -b -u "$USER" -t aros0
sudo ifconfig aros0 192.168.166.1
sudo iptables -t nat -A POSTROUTING -o eth0 -s 192.168.166.0/2 -j MASQUERADE
sudo sh -c "echo 1 > /proc/sys/net/ipv4/ip_forward"
fi
echo "Set your AROS config to:"
echo " device : tap.device"
echo " IP : 192.168.166.2"
echo " Mask : 255.255.255.0"
echo " Gateway : 192.168.166.1"
echo " Primary DNS : 8.8.4.4"
echo " Secondary DNS : 208.67.222.222"
# change directory to AROS' SYS:
cd /home/apps/AROS/AROS-20190318-linux-armhf-system
# invoke AROS bootstrap
./Arch/linux/AROSBootstrap
# return to starting directory
cd $CWD
Then i have the following response to your remark:
.... even if i tried the dhcp one.
You should not use dhcp but use hard coded IP addresses in your AROS hosted setup.
The network addresses used in AROS hosted do not have anything to do with your local network or any other machines in your network.The tap.device creates something that you could compare to a virtual internal network that is only used by AROS. If you have the routing setup correctly then all AROS network traffic is routed to your host machine and as such AROS uses you existing network infrastructure. You can access AROS by using the aros0 network interface (but that is only of concern when you are diving deep into the internals, e.g. as a normal user you usually do no use that directly and simply use existing network software).
So, when i use my script the network settings for AROS are actually echoe'd to the shell but because the script also directly invoke AROSBootstrap executable these lines might not be visible long enough for you to read.
Bottom line is that the network settings and IP values that you should use in your AROS hosted network settings can be determined pretty easy from the script.
device : tap.device"
IP : 192.168.166.2"
Mask : 255.255.255.0"
Gateway : 192.168.166.1"
Primary DNS : 8.8.4.4"
Secondary DNS : 208.67.222.222"
And thus those are the settings you should use in AROS network settings when using the script as shown.
As said before, Paolone's script uses a more sophisticated approach and Paolone statements let me believe that when you install Icaros Desktop hosted that all the network settings are configured automatically for you.
If that is not the case then you must change the settings manually and Paolone's script would then use other IP/Mask/gateway settings that do not correspond to what i have posted here (just now).
In the hope it helps and good luck !
