821084 - Disabling wifi closes nsIServerSocket listening on 0.0.0.0

Status: RESOLVED DUPLICATE of bug 820617

(Firefox OS Graveyard :: Wifi, defect, P1)

Description

[Jonathan Griffin (:jgriffin)]

Marionette currently opens a listening socket on 0.0.0.0:2828, so we can connect to it remotely for panda testing.  See bug 800138.

Unfortunately, when wifi is disabled, this socket gets closed, even if the socket was opened before wifi was first enabled.  This breaks gaia smoke tests on unagis, which toggle the wifi status often during tests.

This problem doesn't occur if Marionette listens only for local connections (on 127.0.0.1:2828).

Comment 1

[Jonathan Griffin (:jgriffin)]

Noming for bb+ because this prevents us from running gaia smoke tests on unagis, which is the only platform on which we can run certain kinds of tests, like telephony and SMS.

Comment 2

[JP Rosevear [:jpr]]

I'm looking at http://dxr.mozilla.org/mozilla-central/dom/system/gonk/nsINetworkManager.idl.html and http://dxr.mozilla.org/mozilla-central/dom/system/gonk/NetworkManager.js.html

I don't see an ethernet type for connection, just wifi and various mobile type connections.  NETWORK_TYPE_WIFI = 0 in the idl, so I will take a wild guess and say that the ethernet connection is typed as wifi, causing this issue

Comment 3

[Andrew Overholt [:overholt]]

Philipp said he could take this.

Comment 4

[Philipp von Weitershausen [:philikon]]

Yup, we don't recognize the Ethernet connection. Please see bug 820617 comment 21.

Comment 5

[Philipp von Weitershausen [:philikon]]

For some reason I can't get my Panda to connect to my home wifi. I shall try again the office later this week. If somebody wants to beat me to it, the patch in bug 820617 *should* fix this problem.

Comment 6

[Jonathan Griffin (:jgriffin)]

(In reply to Philipp von Weitershausen [:philikon] from comment #5)
> For some reason I can't get my Panda to connect to my home wifi. I shall try
> again the office later this week. If somebody wants to beat me to it, the
> patch in bug 820617 *should* fix this problem.

I've verified the patch from bug 820617 does fix this problem.