Network issue

[Christian Helmuth]

Hello Dima,

welcome to the Genode mailing list.

>From your issue description below I suspect your network configuration
is more complex non-standard than our NIC router component currently
supports. For example, we had issues in the past (and this is still a
TODO item) with DHCP offers that contained multiple DNS servers (e.g.,
site-local and internet name resolution).

Beyond my suspicion, we fixed several issues (see below) in the 20.05
release of Genode. You may cherry-pick the commits to try if your
issue is fixed already.

I hope Martin Stein (the author of the NIC router) has some hints too
and jumps in to help you as I'm on vacation next week.

[1] https://github.com/genodelabs/genode/issues/3716
[2] https://github.com/genodelabs/genode/issues/3717
[3] https://github.com/genodelabs/genode/issues/3686
[4] https://github.com/genodelabs/genode/issues/3681

Regards
-- 
Christian Helmuth
Genode Labs

https://www.genode-labs.com/ · https://genode.org/
https://twitter.com/GenodeLabs · /ˈdʒiː.nəʊd/

Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden
Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

On Thu, Aug 13, 2020 at 11:00:36 CEST, Dima Sokolov wrote:
> Hello. I am experiencing a network issue in Sculpt OS. Wired connection is
> established, and the computer gets an IP address assigned dynamically (e.g.
> 192.168.1.6), RAM FS is activated and in use, but I cannot download anything
> from the depot (using any source). Fetchurl keeps trying, and these messages
> can be seen in the log:
> Libc RNG not configured
> Fetchurl got stuck, respawning (it’s shown multiple times)
> Packet operation = 0 failed (finally, I get this one)
>  
> I’m testing on bare metal. I have tried various network card combinations
> (Intel / Realtek) as well as various different motherboard / CPU configurations
> – the result is still the same. I tried Sculpt 20.02 and compiled 20.03 from
> the sources – again, the result is the same. Also, I tried disconnecting and
> reconnecting – still the same.
>  
> I have these network cards, that should be compatible as stated in the manual
> (E1000), but they yield the same results: Intel PRO/1000 MT (PCI)
> Intel PRO/1000 GT DESKTOP (PCI)
>  
> Motherboard / CPU combinations:
> Asus P5W64 WS Pro (classic BIOS, AHCI, VT-x) + Intel Xeon X5460
> Asus Sabertooth X58 (classic BIOS, AHCI, VT-x, VT-d) + Intel Xeon X5650
> Asus M5A97 LE R2.0 (UEFI BIOS, AHCI, IOMMU) + AMD Phenom II X6 1055T
>  
> What should I do to fix the problem? Is there anything I missed in
> configuration?
>  
> On a side note, if I use bridged networking inside Virtualbox on Ubuntu (trying
> to rule out motherboard incompatibility), the results are exactly the same. I
> downloaded Arora using NAT networking and hard drive FS depot, and then tried
> bridge networking to see if the culprit is in fetchurl, but Arora also cannot
> access websites. Since I want to test Virtualbox and Seoul on Sculpt OS, and
> nested virtualization results in a black screen for either of them, I need to
> go bare metal.
>  
> Best regards,
> Dima Sokolov