Hey all,
I saw CM-631 and the clock-api.txt document, but that appears to be
referring to the dbus api. Is there something I can put in main.conf
(or elsewhere?) that will disable the ntp syncing behaviour?
Thanks,
Mike
___
connman mailing list
That did the trick, thanks!
On Jan 13, 2015 11:22 PM, David Lechner da...@lechnology.com wrote:
On 01/13/2015 06:53 PM, Mike Purvis wrote:
When I set up connman 1.27 to connect to an AP and then restart my
machine,
it seems to reconnect okay on startup (most of the time).
However, when I
When I set up connman 1.27 to connect to an AP and then restart my machine,
it seems to reconnect okay on startup (most of the time).
However, when I set it to create an AP (tether) and restart my machine, it
comes up with the wifi idle.
Is there a way to have it resume the tethering activity on
Works great, thanks for the quick fix! The connman 1.27 package on my PPA
has now been updated to include this patch; it may be of use to anyone else
running connman on Ubuntu Trusty systems:
https://launchpad.net/~mikepurvis/+archive/ubuntu/network
On 12 January 2015 at 09:29, Mike O'Driscoll
BATMAN is interesting because it operates at Layer 2 rather than Layer 3,
unlike most IP-based mesh networking schemes. There is some explanation
here, including the rationale for its implementation as a kernel module the
batctl CLI:
http://www.open-mesh.org/projects/batman-adv/wiki/Doc-overview
.c#n1687
I'm happy to provide a full debug log if needed.
--
Mike O'Driscoll
On Mon, Jan 5, 2015 at 12:16 PM, Mike Purvis
mpur...@clearpathrobotics.com wrote:
We're presently experiencing 100% CPU in connmand when tethering is
enabled, using version 1.27 (PPA
https://launchpad.net
We're presently experiencing 100% CPU in connmand when tethering is
enabled, using version 1.27 (PPA
https://launchpad.net/~mikepurvis/+archive/ubuntu/network) on Ubuntu
Trusty, with kernel 3.16. The problem appears in virtualbox connected to a
USB dongle as well as on a physical J1900 motherboard
messages from rtnl.c; seems to be several of them
every few seconds.
On 5 September 2014 06:07, Patrik Flykt patrik.fl...@linux.intel.com
wrote:
Hi,
On Thu, 2014-09-04 at 17:02 -0400, Mike Purvis wrote:
- When I connect to my wifi, it no longer creates a directory for it
under
/var
September 2014 09:29, Mike Purvis mpur...@clearpathrobotics.com
wrote:
Hmm. My exact command sequence from startup is:
$ connmanctl
connmanctl agent on
Agent registered
connmanctl enable wifi
Error wifi: Already enabled
connmanctl scan wifi
Scan completed for wifi
connmanctl connect
I just upgraded my Ubuntu 14.04 system to 1.25, and I'm getting two
oddities:
First, what's up with the change to make the agent only work in interactive
mode? Having to do the whole agent/scan/connect dance inside the connmanctl
prompt, and away from my bash history, is a pretty big pain.
2014 15:07, Mike Purvis mpur...@clearpathrobotics.com
wrote:
I just upgraded my Ubuntu 14.04 system to 1.25, and I'm getting two
oddities:
First, what's up with the change to make the agent only work in
interactive mode? Having to do the whole agent/scan/connect dance inside
the connmanctl
Hey all,
I'm looking for a specific behaviour, and I'm wondering if there's a
straightforward way for connman to provide it. The behaviour is:
- Attempt to find known AP.
- Attempt to connect to known AP.
- After timeout, fall back on hosting on AP (tethering in connman
parlance).
I have never seen this error. Did this work earlier and you have not
upgraded your dbus or rest of the system? Anyway, this does not look
like a connman issue.
Yes, it worked previously. No updates have been applied to the system; the
only changes have been fiddling this the various config
policy blocked the reply, the
reply timeout expired, or the network connection was broken.
This is Linux 3.13, with a Centrino Advanced-N 6235 wifi module, on a
modern Intel Q87 chipset motherboard.
Mike
On 14 July 2014 10:27, Mike Purvis mpur...@clearpathrobotics.com wrote:
I have never seen
You should never need to run connmanctl as a root, it is just something
that is not needed if dbus is configured correctly.
It was adding the parameter to ignore p5p1 which triggered the problem. I
reversed that change and now connmanctl works as before without sudo. The
other problems
output; I've captured it in a file here:
https://gist.github.com/mikepurvis/bfd728f76a660223bbe4
Thoughts?
On 8 July 2014 08:42, Jukka Rissanen jukka.rissa...@linux.intel.com wrote:
Hi Mike,
On ti, 2014-07-08 at 08:33 -0400, Mike Purvis wrote:
I also tried moving my service
I also tried moving my service definition
to /var/lib/connman/example.config, but this registered no response
either.
So you are saying that even with this file, the system does not set the
IP address of the ethernet interface when you plug in the ethernet
cable? Note that ethernet
,
Mike
On 7 July 2014 03:58, Jukka Rissanen jukka.rissa...@linux.intel.com wrote:
Hi Mike,
On pe, 2014-07-04 at 13:45 -0400, Mike Purvis wrote:
Hey all,
I have a platform where I'd like an ethernet port to come up with a
static
IP, much as it does with /etc/network/interfaces
Rissanen jukka.rissa...@linux.intel.com wrote:
Hi Mike,
On ma, 2014-07-07 at 07:41 -0400, Mike Purvis wrote:
Hi Jukka,
Very helpful, thanks— not sure why it didn't occur to me to look in
the source repo itself for docs. For others following along, the
config file documentation
Hey all,
I have a platform where I'd like an ethernet port to come up with a static
IP, much as it does with /etc/network/interfaces containing:
auto p5p1
iface p5p1 inet static
address 192.168.54.1
netmask 255.255.255.0
This is essential so that a user can set a static IP on their laptop,
20 matches
Mail list logo
