https://redmine.graphics-muse.org/https://redmine.graphics-muse.org/favicon.ico?16278048512013-02-17T23:52:19ZGraphics Muse Issue TrackerPiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5222013-02-17T23:52:19ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>10</i></li></ul>Connman links:
<ul>
<li><a href="http://connman.net/" class="external">web site</a></li>
<li><a href="https://wiki.archlinux.org/index.php/Connman" class="external">ArchLinux Wiki</a></li>
<li><a href="http://www.gigamegablog.com/2012/02/06/beaglebone-linux-101-assigning-a-static-ip-address-with-connman/" class="external">Beaglebone Linux 101: Assigning a Static IP Address with Connman</a></li>
<li><a href="http://wiki.buglabs.net/index.php/Networking" class="external">BugLabs</a> - which uses Connman under the hood</li>
<li><a href="https://wiki.ubuntu.com/ConnMan" class="external">Ubuntu Wiki</a></li>
<li><a href="http://arstechnica.com/information-technology/2009/06/intels-linux-connman-examining-the-pros-and-conns/" class="external">The pros and cons of Intel's ConnMan for Linux</a></li>
<li><a href="http://learn.adafruit.com/beaglebone/wifi" class="external">Adafruit tutorial</a></li>
<li><a href="http://forum.meego.com/showthread.php?t=4306" class="external">Meego discussion</a></li>
<li><a href="http://lwn.net/Articles/456967/" class="external">Mobile network management with ConnMan</a></li>
<li><a href="http://wiki.meego.com/D-Bus/ConnMan" class="external">D-Bus/ConnMan</a></li>
</ul>
<p>I need to see if connman can be convinced to bring up the network only if the interface is configured. If so, I can drop S50network and let connman handle it instead.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5332013-02-23T23:07:06ZHammelmjhammel@graphics-muse.org
<ul><li><strong>% Done</strong> changed from <i>10</i> to <i>20</i></li></ul><p>Based on <a href="https://wiki.archlinux.org/index.php/Connman" class="external">ArchLinux Wiki</a>, the following updates need to be made.</p>
<ol>
<li>Add dbus-python under Hardware Handling for Buildroot</li>
<li>Add --enable-test in the connman package. This requires a patch for connman in Buildroot. Ideally, it should be a patch that adds the test scripts as a configurable option (and submit to Buildroot if its not there now) or, at a minimum, a patch that copies <src>/test/test-connman to <target>/usr/bin</li>
</ol>
<p>The former is required before I can even test the ArchLinux instructions. The latter can be copied by hand to perform that test.</p>
<p>It's not clear how this interacts with wpa_supplicant and whether /etc/wpa_supplicant.conf needs to be updated by connman or not. We'll just have to try it and see.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5352013-02-24T20:04:10ZHammelmjhammel@graphics-muse.org
<ul><li><strong>% Done</strong> changed from <i>20</i> to <i>50</i></li></ul><p>I've enabled python support for dbus and added a patch for enabling the test option. These build fine in my sandbox. I need to do a full rootfs build while I test the rootfs on the Pi board before checking these changes in.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5392013-02-25T16:12:09ZHammelmjhammel@graphics-muse.org
<ul><li><strong>% Done</strong> changed from <i>50</i> to <i>60</i></li></ul>Verified build completes correctly with the following updates:
<ol>
<li>Bump connman to 1.11</li>
<li>Add connman-tests configuration to get test-connman script.</li>
<li>Disabled avahi. Not needed by anything that I know of.</li>
<li>Enabled python-dbus for connman. </li>
<li>Disable ext2 image creataion.</li>
</ol>
<p>Initial use of <a href="https://wiki.archlinux.org/index.php/Connman" class="external">test-connman</a> does not generate a list of services as displayed on the ArchLinux wiki, though the mods to /etc/dbus-1/system.d/connman.conf has not yet been applied. It's unclear if I have additional configuration to do or not.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5402013-03-02T04:37:57ZHammelmjhammel@graphics-muse.org
<ul></ul><p>Connman wants wpa_supplication 0.8 or 1.0. Buildroot 201205 provides 0.7.3. The configuration settings specified for wpa_supplication to work with connman can't be set with 0.7.3.</p>
<p>I'll need to rev wpa_supplication before continuing with connman integration.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5422013-03-03T23:22:15ZHammelmjhammel@graphics-muse.org
<ul></ul><p>Rev'd Buildroot to 2013.02 to pick up latest wpa_supplicant and everything else I might need. Seems to work so far, but the rootfs needs to be sanitized on a 32bit build system first.</p>
<p>Once that's done, I can return to trying to get connman running.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5452013-03-09T22:33:37ZHammelmjhammel@graphics-muse.org
<ul></ul>Buildroot is rev'd to 2013.02.<br />That gives me connman 1.10 and wpa_supplicant 2.0.<br />The build boots on the Pi board okay (minor tweaks to buildroot build required, but those are checked in now).<br />Testing using these instructions:
<ol>
<li><a href="https://wiki.archlinux.org/index.php/Connman" class="external">ArchLinux wiki</a></li>
<li><a href="http://www.gigamegablog.com/2012/02/06/beaglebone-linux-101-assigning-a-static-ip-address-with-connman/" class="external">Beaglebone Linux 101: Assigning a Static IP Address with Connman</a></li>
</ol>
<p>Neither works. I get no output at all.</p>
<p>Trying connmanctl, I can list technologies which only shows the wired port. No wifi port even though the wifi drive is loaded and manually configuring wpa_supplicant will get it to work.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5462013-03-09T22:50:15ZHammelmjhammel@graphics-muse.org
<ul></ul><p>Forget connman. Too much trouble to get working. Instead, just config the wifi with wpa_supplication manually.</p>
<p>As for eth0 trying to come up, the S40network script can be modified to look in /etc/network/interfaces for interfaces marked as "auto". These are the ones that should be configured with dhcp. Only two such interfaces will be supported: eth0 (wired) and wlan0 (wifi).</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5532013-03-10T18:08:30ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Priority</strong> changed from <i>Urgent</i> to <i>Immediate</i></li></ul> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5692013-04-08T15:33:25ZHammelmjhammel@graphics-muse.org
<ul></ul><p>I've started writing <a href="http://redmine.graphics-muse.org/projects/bui-network-config" class="external">bui-network-config</a> for editign /etc/network/interfaces and /etc/wpa_supplicant.conf. This is extremely simple-minded but it should suffice for a project like PiBox or BeagleBox. This configuration utility is C/GTK+ based and will be available from the BUI panel.</p>
<p>Once configuration of the /etc/network/interfaces file is handled, S40network can be modified to use ifup to bring up only configured interfaces.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5802013-04-14T23:09:49ZHammelmjhammel@graphics-muse.org
<ul></ul><p>bui-network-config has been written and tested on my desktop.</p>
I now need to do the following:
<ol>
<li>integrate it into the PiBox build</li>
<li>Revert S40network to the Busybox/Buildroot version</li>
<li>Add bui-network-config to default BUI configuration</li>
<li>Test bui-network-config on the target</li>
</ol>
<p>Getting close to decent network support.....</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5832013-04-25T15:11:09ZHammelmjhammel@graphics-muse.org
<ul></ul><p>First test of bui-network-config on target failed with a crash. This may be due to a bug fix that's been applied to bui-network-config (see <a href="http://redmine.graphics-muse.org/projects/bui-network-config/repository/revisions/80b7974fa925d37ac614fc8384621973335be51f" class="external">revision #80b7974f</a>). This may not be currently included in the version I tested on the target.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5862013-04-29T15:07:27ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Severity</strong> changed from <i>03 - Medium</i> to <i>01 - Critical</i></li></ul> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=5922013-05-01T14:59:47ZHammelmjhammel@graphics-muse.org
<ul></ul><p>Rebuild bui-network-config on target and it still crashed. This was even after removing the cached local archive.</p>
<p>I've created a bug against the bui-network-config project (See <a class="issue tracker-1 status-5 priority-7 priority-highest closed" title="Bug: Crashes on Pibox target hardware (Closed)" href="https://redmine.graphics-muse.org/issues/189">#189</a>). I'll need to generate the xcc-debug opkg to debug on the target.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=6002013-07-07T23:07:21ZHammelmjhammel@graphics-muse.org
<ul></ul><p>bui-network-config is fixed, though new issues (see <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Interfaces need "Enable/Disable" buttons (Closed)" href="https://redmine.graphics-muse.org/issues/190">#190</a>) are being opened on it to provide new features.</p>
<p>Now S40network needs to be rewritten to parse /etc/network/interfaces.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=6032013-07-08T15:12:18ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Severity</strong> changed from <i>01 - Critical</i> to <i>03 - Medium</i></li></ul> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=6342013-07-19T00:16:04ZHammelmjhammel@graphics-muse.org
<ul><li><strong>% Done</strong> changed from <i>60</i> to <i>70</i></li></ul><p>After fixing bui-network-config to properly update the interfaces file, I tried running ifdown/ifup to bring up the wlan and not the wired port. Works as expected.</p>
<p>This should simplify the structure of S40network dramatically, but I need to actually test that to be certain it works.</p>
What I need to do:
<ol>
<li>change S40network start to be ifup -a</li>
<li>change S40network stop to be ifdown -a</li>
<li>Run multiple tests, changing the configuration between eth0, wlan0 and both and make sure the script does as expected.</li>
<li>Verify reboots bring the network up as expected.</li>
</ol>
<p>If this works, save the modified S40network to the skeleton in the pibox source tree.</p> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=6502013-07-29T20:20:42ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Severity</strong> changed from <i>03 - Medium</i> to <i>01 - Critical</i></li></ul> PiBox - Bug #164: eth0 comes up even if nothing is connectedhttps://redmine.graphics-muse.org/issues/164?journal_id=6562013-07-30T03:08:26ZHammelmjhammel@graphics-muse.org
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Closed</i></li><li><strong>% Done</strong> changed from <i>70</i> to <i>100</i></li></ul><p>Done. S40network now uses just ifup/ifdown but must manually start/stop wpa_supplicant. Tried various configs with eth0 and wlan0 enabled or disabled with dhcp. Seems to work well, even on reboots.</p>
<p>Code pushed upstream.</p>
<p>Closing issue.</p>