You are not logged in.
Tigran,
After checking the doc linked by brebs i agree with calling Vbox networking insane .
So far so great.
Thank you for your opinion, too
But the insanities of VBox networking hadn't had been any matter. Instead, the generic issue was some kind of insanity or call it whatever of Arch networking in VBox guest environment, cause it's been the single OS (accompanied by W7 and WS2008 and Fedora latest) which couldn't reach the network from under VBox host.
Thank you all for lots of questions concerning the matters I have described many times before. Thank you for your opinions that were not relevant to the generic question at all. For advises that couldn't be useful in the circumstances I have.
So I have lost a week answering many times the same questions and elementary doubts that could be answered by attentive reading of the initial posting.
I recognize that nobody here owes me anything, and I have tried to call for help at my own risk. So thank you, everybody, and don't waste your time anymore.
Last edited by Tigran (2017-08-08 16:21:09)
Offline
As for wasting time : this is an interesting problem and I don't feel trying to help was a waste of time.
I do realise the change you'll read this is slim, but continuing to try to help is not a waste of time for me.
So I have lost a week answering many times the same questions and elementary doubts that could be answered by attentive reading of the initial posting.
I disagree, this thread contains much more info then your initial post.
For advises that couldn't be useful in the circumstances I have.
I don't know enough about your circumstances to determine which advise would be useful for you, so gave the best advise i could think of.
Your reaction makes clear you need a solution that will work in your current setup.
With bridged networking, VirtualBox uses a device driver on your host system that filters data from your physical network adapter. This driver is therefore called a "net filter" driver. This allows VirtualBox to intercept data from the physical network and inject data into it, effectively creating a new network interface in software. When a guest is using such a new software interface, it looks to the host system as though the guest were physically connected to the interface using a network cable:
That makes clear an archlinux VBox Host handles networking differently then a normal archlinux system.
However 3 guests do work with this AL host, so the problem may be on the client side.
A possible differrence is which version of VBox guest additions was used and where it came from .
Archlinux has it's own VBox guest support, but can also be used with upstream guest additions.
I have some recommendations for you :
- verify if using AL guest support or upstream guest additions makes a difference.
- get help from a VBox networking specialist.
- In the future, stick to VBox supported hosts & guests
Edited for typos
Last edited by Lone_Wolf (2017-08-08 18:52:07)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I have some recommendations for you :
- verify if using AL guest support or upstream guest additions makes a difference.
- get help from a VBox networking specialist.
- In the future, stick to VBox supported hosts & guests
Well, there have been no difference with or without virtualbox-guest-dkms installed. All the modules are loaded correctly but nothing changes.
I disagree, this thread contains much more info then your initial post.
Point me at least one sentence that contains something not present in the initial post))
Whatever, thanks again to everybody. I'll just switch to routing using two different NICs on the host system, that would probably work as the Arch guest successfully gets and sends packets within the host box.
Offline
[Point me at least one sentence that contains something not present in the initial post))
The network on host and Arch guest are both controlled by systemd-networkd.
It allowed me to eliminate two thrones in my side -- netctl and NetworkManager
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Online
Paravirtualized network adapter (virtio-net)
The "Paravirtualized network adapter (virtio-net)" is special. If you select this, then VirtualBox does not virtualize common networking hardware (that is supported by common guest operating systems out of the box). Instead, VirtualBox then expects a special software interface for virtualized environments to be provided by the guest, thus avoiding the complexity of emulating networking hardware and improving network performance.
Providing Arch is the single of the guest systems that failed to network correctly, I am not sure if the virtualisation of NIC by the Arch guest will do any good.
Anyway, the main target of my post wasn't to find a workaround, there are a number of ways to overcome the trouble, but to define and - who knows - to correct the defect of Arch that places the favorite distro into such a negative light compared even to windozes, not to mention Fedora.
Offline
Run tcpdump (or e.g. wireshark) on the host, and compare the traffic, looking for differences between the Arch & Fedora guests.
Offline
Run tcpdump (or e.g. wireshark) on the host, and compare the traffic, looking for differences between the Arch & Fedora guests.
Thank you! I have tried this, both on host system and remote router nics, but failed to find anything my skills in analyzing network packets could accept as useful)
Offline