<div dir="ltr"><div><div><div><div>Hi Guys,<br><br></div>I just faced a similar issue and figured out that in the VBox network settings for the VM that the 'Cable Connected' checkbox for each adapter was unticked after a clean install.<br><br></div>Checking those boxes fixed the issue<br><br></div>Regards,<br><br></div>Lewis Rockliffe<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Jul 21, 2016 at 8:24 AM, Marcin Mielniczuk <span dir="ltr"><<a href="mailto:marmistrzmar@gmail.com" target="_blank">marmistrzmar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Hi,</p>
<p>I tried zyppering the package, but <br>
</p>
<p><tt>Error code: connection failed</tt><tt><br>
</tt><tt>Error message: Couldn't resolve host:
'<a href="http://releases.jolla.com" target="_blank">releases.jolla.com</a>'</tt></p>
<p><tt>$ ping 8.8.8.8</tt><tt><br>
</tt><tt>connect: Network is unreachable</tt></p>
<p>So I have no networking inside the VM.</p>
<p>Last upgrade was a couple of days ago, next will be today. I did
reboot ;)</p>
<p>The port is open: <br>
</p>
<p><tt>State Recv-Q
Send-Q Local
Address:Port
Peer Address:Port </tt><tt><br>
</tt><tt>LISTEN 0
10
<a href="http://127.0.0.1:2222" target="_blank">127.0.0.1:2222</a>
*:* users:(("VirtualBox",pid=31842,fd=47))</tt><br>
</p>
<p>I'm the member of the following groups: adm, bumblebee, lp, sudo,
vboxusers, wheel<br>
</p><div><div class="h5">
<div>On 21.07.2016 07:50, Martin Kampas
wrote:<br>
</div>
<blockquote type="cite">
<div style="direction:ltr;font-family:Tahoma;color:#000000;font-size:10pt">Hi Marcin,<br>
<br>
failed.log, statefs.log: both failing statefs and tmpfiles are
known issues and shouldn't be related to this.<br>
<br>
sshd.log: according to the log you mistyped "sshd" as "ssh", but
anyway "sshd.service" is not used, instead you should check the
status of "sshd.socket". Also note that the config is
"/etc/ssh/sshd_config_engine".<br>
<br>
If the output of `journalctl _COMM=sshd -b` was empty after
trying to log in via SSH even with verbosity increased, then my
suspicion falls on host/virtualbox.<br>
<br>
You could also verify with tcpdump that it did not reach the
guest (install with `zypper in tcpdump`, run as `tcpdump -n port
ssh` inside the MerSDK VM). And on host you can check that the
ports are really occupied by virtualbox with `sudo ss -tpln
|grep ':222[23]\>'`.<br>
<br>
I am also using Arch Linux as you (last full system upgrade on
2016-06-28) and it works well. Did you try reboot? :)<br>
<br>
BR,<br>
Martin<br>
<br>
</div>
</blockquote>
<br>
</div></div><span class="HOEnZb"><font color="#888888"><pre cols="72">--
Marcin</pre>
</font></span></div>
<br>_______________________________________________<br>
SailfishOS.org Devel mailing list<br>
To unsubscribe, please send a mail to <a href="mailto:devel-unsubscribe@lists.sailfishos.org">devel-unsubscribe@lists.sailfishos.org</a><br></blockquote></div><br></div>