v86
v86 copied to clipboard
Networking on KolibriOS?
Hi all!
I'm having a issue where the relay docker images that I'm using for my v86 emulator, is not working when connected from the same server hosted with both my main website and v86 site..
I usually test the networking on kolibriOS to see if it did anything, but it somehow didn't want to connect to the internet or use the assigned ip address with the docker image at all!
I assume it was a configuration problem with my nginx server doing a proxy thing to reverse, or even a port number that was supposed to be in the command..
Can someone explain what I did wrong? Thanks a lot! 😉
I think v86 networking doesn't work with KolibriOS because it doesn't say "Include network support" in copy.sh/v86 page
This is likely a bug in v86's ne2k implementation.
That's strange..
I thought the OS had some sort of tool that should "release" or "renew" ip command, but I guess not..
Anyway, I should change the title for a bit more understanding..
I know that other OSes on v86 require you to run a command like modprobe ...
or dhcpcd
on buildroot/debian /arch.
See here
Probably something like that exusts for your OS.
Edit: nvm if copy himself labelled it as bug, it's probably that 😅
@tennox As far as I understand, KolibriOS starts DHCP configuration via zeroconf
(http://wiki.kolibrios.org/wiki/Networking_for_dummies) automatically at booting time.
By the way, I noticed that in the Debug Log, when trying to make an HTTP request, an error appears about failed contacting DNS-server (all IP settings were set automatically).
UPD: somehow it turned out to load the page with DNS turned off in settings/network.ini
I mean, networking works in Virtualbox for some reason.
I have no idea why it did not run or did dhcp thing on start up.
I even did it with the proxy provided from relay.widgetry.org
anyway, but nothing.
@tennox As far as I understand, KolibriOS starts DHCP configuration via
zeroconf
(http://wiki.kolibrios.org/wiki/Networking_for_dummies) automatically at booting time.By the way, I noticed that in the Debug Log, when trying to make an HTTP request, an error appears about failed contacting DNS-server (all IP settings were set automatically).
UPD: somehow it turned out to load the page with DNS turned off in
settings/network.ini
Hmm..
I did try this, but I'm not sure if the DNS line is supposed to be off or deleted..
Also checked node-relay (more precisely fork BelleNottelling/node-relay) the result is the almost same.
I've noticed a few things so far:
- DNS is not working, what was mentioned earlier
- not all packets are received, for example, in the screenshots below only 4/7 successful packets on
8.8.8.8
are received, other reachedTimeout.
on both relays. - on default relay, in Debug board I catched a message:
RTL8029: Error on receive
on node-relay I had this:
TCP_send: IP error
IPv4_output: ARP error=FFFFFFFF
IPv4_output: ip=0xF80DE340
node-relay
default relay (websockproxy)
This seems to be working now. Not sure if it was a change in v86 or kolibrios.