Bug 2940 - connman forgets default gateway when the cable is unplugged
Summary: connman forgets default gateway when the cable is unplugged
Status: VERIFIED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: connectivity (show other bugs)
Version: 1.3
Hardware: E-Menlow Multiple
: Medium+ normal
Target Milestone: 1.3 M5
Assignee: Alexandru Damian
QA Contact:
URL:
Whiteboard:
Depends on: 3149
Blocks:
  Show dependency tree
 
Reported: 2012-08-13 14:23 UTC by Alexandru Georgescu
Modified: 2012-10-09 11:03 UTC (History)
5 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandru Georgescu 2012-08-13 14:23:59 UTC 
In Connman UI, set manual IP (IP, netmask and default gateway). 
Unplug the network cable from the board then plug it in back again. Check the default gateway settings displayed in Connnman.

EXPECTED RESULT:
default gateway remains set.

ACTUAL RESULT:
The default gateway is reset (blank).


OTHER:
Happens in e-Menlow and other BSPs as well.
Comment 1 Saul Wold 2012-08-16 15:00:50 UTC 
Check latest version, Andrei might be updating it currently.
Comment 2 Jessica 2012-09-14 14:12:30 UTC 
Please check latest upstream version, it maybe fixed there
Comment 3 Andrei Dinu 2012-09-17 08:11:05 UTC 
I've tried testing with the latest versions on : 

http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/

and i couldn't boot into the images on e-menlow machine.

it seems like all the hddimg are broken. 

The last image that i tried booting is : 

http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20120914-1/machines/emenlow/core-image-lsb-sdk-emenlow-20120914115130.hddimg  with the same results.

Can someone please point a link to a stable new release in order to test/reproduce the bug?

Thanks.
Comment 4 Alexandru Damian 2012-09-24 09:24:42 UTC 
could not repro on 8f1f81bea80c6e780101bb1edd5f28ff9666a056
Comment 5 Alexandru Georgescu 2012-10-09 11:03:41 UTC 
Couldn't reproduce on 86c9aa8081f107420cd3763d0566d779daddc2b1