| 8d0c31bb481b712a3b2e6612390679e29053c620 |
|
13-Oct-2015 |
Alex Vakulenko <avakulenko@google.com> |
apmanager: Rename "chromeos" -> "brillo" in include paths and namespaces
libchromeos is transitioning to libbrillo and chromeos namespaces
and include directory is changing to brillo.
Bug: 24872993
TEST=built for aosp and brillo, all unit tests pass on dragonboard
Change-Id: I4c6efbc5bbf80d251e5d91bc3db49f02bc0e4732
/system/connectivity/apmanager/main.cc
|
| 56e03e7819eab800e077513451cb4fce68ec6066 |
|
28-Sep-2015 |
Peter Qiu <zqiu@google.com> |
Do not run apmanager in minijail for now
When starting apmanager through Android's init system, the daemon
will be started under "system" user, and that's currently targeted
user for running apmanager. So there is no need to use minijail to
drop the user privileges to "system" user" again.
So skip this for now until we create a new user/group to run apmanager
under.
Bug: 22828115
TEST=Manual test on dragonboard
Change-Id: Ib37553126f9a9a4024a16f68d91d240ca855f55c
/system/connectivity/apmanager/main.cc
|
| 771952dc58b6e5eef5fcfe97a1ba2ac7881b2bfe |
|
28-Sep-2015 |
Peter Qiu <zqiu@google.com> |
Do not run logger on Android
Logger utility doesn't exist on Android, so do not run it on Android.
Bug: 24451556
TEST=Manual test on dragonboard
TEST=Test AP setup on Chrome OS device
Change-Id: I4014f5ca3ab91b348a98169cb355c6841d6530fd
/system/connectivity/apmanager/main.cc
|
| 9b1df04c163524658b482602c2070aacddbe7374 |
|
28-Sep-2015 |
Peter Qiu <zqiu@google.com> |
Do not daemonize (fork) the daemon process
When starting the daemon using an init system, the environment setup
is already being handled by the init system, so there is no need
to daemonize the daemon process create such setup.
By daemonizing the daemon process, it spawns off a new process to
run the daemon and terminates the current process. This causes
a problem with the init system, where it thinks that the daemon
failed to start. We were able to work around it on Chrome OS's
upstart script by adding the forking expectation in the init
scritp ("expect fork"), but there is not such workaround on
Android's init system.
Fix it by removing the daemonize call (daemon()) and remove the
the forking expectation on Chrome OS's init script.
Bug: 24412675
TEST=Manual test on dragonboard
TEST=start/stop apmanager on Chrome OS device
Change-Id: I4dff678946801310982c3af366ab6182f5864a81
/system/connectivity/apmanager/main.cc
|
| 326b6cfba5ab73c9e41a7585d1bc95871631122a |
|
02-Sep-2015 |
Peter Qiu <zqiu@google.com> |
Re-license apmanager to Apache2
This patch automatically replaced the license on all text files from
Chromium OS (BSD style) to AOSP (Apache2), keeping the original year as
a reference.
The license header was added to .gyp, the NOTICE was replaced with a copy
of the Apache2 license and MODULE_LICENSE_* file was updated.
BUG=23619937
TEST=grep 'Chromium OS Authors' doesn't find anything.
Change-Id: I4ade0a15ff18ab159d4a2f99525b62c780b13c89
/system/connectivity/apmanager/main.cc
|
| 7f267ab51daeda0fb685587953bd494de0226303 |
|
02-Apr-2015 |
Alex Vakulenko <avakulenko@chromium.org> |
platform2: Explicitly use base:: namespace with CommandLine
The current revision of libchrome is removing CommandLine class
from global namespace and only retain the one in base::.
Sweep the code to use the correct namespace in anticpation of
libchrome revision roll.
BUG=None
TEST=./build_packages
Change-Id: Ib7ca448dac1204c1e36ab053e775a5a5214997ac
Reviewed-on: https://chromium-review.googlesource.com/263785
Trybot-Ready: Alex Vakulenko <avakulenko@chromium.org>
Tested-by: Alex Vakulenko <avakulenko@chromium.org>
Reviewed-by: Alex Deymo <deymo@chromium.org>
Commit-Queue: Alex Vakulenko <avakulenko@chromium.org>
/system/connectivity/apmanager/main.cc
|
| 58676b65cea23a831d032639e5cbfd350d58ff6a |
|
17-Dec-2014 |
Peter Qiu <zqiu@chromium.org> |
apmanager: run daemon inside minijail
Run apmanager inside a minijail with limited privileges and system calls
through seccomp filter.
BUG=chromium:442186
TEST=Verify AP services with client connectiviy on arm (peach_pit),
x86 (x86-alex), and amd64 (stumpy) platforms.
CQ-DEPEND=CL:236097
Change-Id: I10b2b0c6943cad134028894505d54e2ca4993a26
Reviewed-on: https://chromium-review.googlesource.com/236098
Tested-by: Zeping Qiu <zqiu@chromium.org>
Reviewed-by: Jorge Lucangeli Obes <jorgelo@chromium.org>
Commit-Queue: Zeping Qiu <zqiu@chromium.org>
Trybot-Ready: Zeping Qiu <zqiu@chromium.org>
/system/connectivity/apmanager/main.cc
|
| bf8e36cde93c8714b5e1482d205d2e3e424d1290 |
|
04-Dec-2014 |
Peter Qiu <zqiu@chromium.org> |
apmanager: DHCP server support
Start a DHCP server for an AP service when it is configured in server
mode. The server address is configure as "192.168.x.254" where
x is the least significant byte of the service identifier. The DHCP
range is from 192.168.x.1 to 192.168.x.128.
BUG=chromium:438836
TEST=unittests and manual test
Manual test:
Start an AP service using apmanager and verify a DUT can connect
to it with an IP address
CQ-DEPEND=CL:233032,CL:233493
Change-Id: I16a0d03c8eac7f02722c8c8f5185ca75a1edebcb
Reviewed-on: https://chromium-review.googlesource.com/233047
Reviewed-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Peter Qiu <zqiu@chromium.org>
Tested-by: Peter Qiu <zqiu@chromium.org>
/system/connectivity/apmanager/main.cc
|
| 8e785b9645b8d6f32f3e2cae8d7e2a7ec3c71e76 |
|
24-Nov-2014 |
Peter Qiu <zqiu@chromium.org> |
apmanager: add support for HT capability
Parse wiphy's HT capability and add it to the AP service's configuration
file to correctly support AP in 80211n mode.
BUG=chromium:431763
TEST=unittests and manual test by using python to invoke dbus calls
to start AP service in 802.11n mode.
Change-Id: I6c902136832eea6b38b806f733231d6cbe14e3f6
Reviewed-on: https://chromium-review.googlesource.com/231681
Reviewed-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Peter Qiu <zqiu@chromium.org>
Tested-by: Peter Qiu <zqiu@chromium.org>
/system/connectivity/apmanager/main.cc
|
| 5dd242dfe5acf25696f877999320ac4164785a5b |
|
14-Oct-2014 |
Peter Qiu <zqiu@chromium.org> |
apmanager: initial skeleton files.
BUG=chromium:423407
TEST=FEATURES=test emerge-$BOARD apmanager
USE='clang asan' FEATURES=test emerge-$BOARD apmanager
CQ-DEPEND=CL:223258, CL:223302
Change-Id: Ib42bd1eef4a9d6b0f30e085a64e9454c5b618d28
Reviewed-on: https://chromium-review.googlesource.com/223322
Reviewed-by: Peter Qiu <zqiu@chromium.org>
Commit-Queue: Peter Qiu <zqiu@chromium.org>
Tested-by: Peter Qiu <zqiu@chromium.org>
/system/connectivity/apmanager/main.cc
|