Send connman mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.01.org/mailman/listinfo/connman
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of connman digest..."
Today's Topics:
1. Re: Documentation change request (Patrik Flykt)
2. Adding Ad-hoc(ibss) support to connman (COLIN Tangi)
----------------------------------------------------------------------
Message: 1
Date: Mon, 03 Jul 2017 11:13:18 +0300
From: Patrik Flykt <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: Pierre Couderc <[email protected]>, [email protected]
Subject: Re: Documentation change request
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Hi,
On Fri, 2017-06-30 at 10:13 +0200, Daniel Wagner wrote:
> Hi Patrik,
>
> On 06/16/2017 09:46 AM, Pierre Couderc wrote:
> > Please find here my feeling from a newcomer to connman.
> >
> >
> > First, it works. I have used it during months without having the
> > idea to
> > try to read its doc. So, thank you for it !
Thanks for the comments!
> > But as I have IPV6 problems, so I try to find doc. My first try was
> > to
> > find the README in jessie. This README is empty, so there is a
> > problem
> > for the debian maintainer.
That's a bit bad, and in addition the version has been lagging behind
from time to time. As ConnMan receives bug fixes with every rolling
release, using previous versions are never a good idea.
> > Next, google makes me go to https://01.org/connman/documentation
> > which
> > sends me to
> >
> > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/doc
> > that
> > I do not know how to read nor what it is speaking about.
> >
> > and to
> > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/src
> > /main.conf
> > which is not usefull
> >
> >
> > I suggest the following small points which would have saved me
> > hours :
> > in fact the main introduction is in
> >
> > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/REA
> > DME
> >
> > I suggest that :
> >
> > 1- a link to
> > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/REA
> > DME
> > is added in https://01.org/connman/documentation
Updated the first section of that page to contain links to the useful
resources in the following order: README, main.conf (for tuning),
config-format.txt (for pre-configured networks), vpn-config-format.txt
(for pre-configured VPNs) and the documentation directory on the git
server as the last option.
> > 2- a README file containing a single line to link to
> > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/REA
> > DME
> >
> > is?????added in
> > https://git.kernel.org/pub/scm/network/connman/connman.git/tree/doc
> >
All documentation except the 01.org page are found in the git sources
and the source code tar balls. So they should be covered.
> Since I don't have access to 01.org can you adapt the website? I
> really
> appreciate that Pierre takes the time to points out where we could
> improve :)
Done.
> > (Not all users are specialist git.kernel.org site or of git itself)
> >
> > There is too a problem for debian maintainer : particularly where
> > are
> > configuration file(s) ? I hope to find that in README.debian
> >
> > I have tried to declare this as a documentation bug in
> > > https://01.org/jira/browse/CM|
> >
> > But I am not allowed to connect.
Interesting, it worked today, wonder if it had a temporary or more
permanent glitch?
> Again, I think Patrik might know how to get an account on this Jira.
Good question. Anyone in the absence of JIRA downtime is/should be able
to see all bugs. Does this part work or what are the symptoms? After
that all I get is "Your JIRA administrator has not yet configured this
contact form.", so even I have to go for a bit of JIRA bug submission
contact hunting. But bugs are also welcomed on the mailing list.
HTH,
Patrik
------------------------------
Message: 2
Date: Mon, 3 Jul 2017 15:14:35 +0000
From: COLIN Tangi <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Adding Ad-hoc(ibss) support to connman
Message-ID:
<am4pr08mb2914ec2b2dc1d48bbe719bf5c4...@am4pr08mb2914.eurprd08.prod.outlook.com>
Content-Type: text/plain; charset="iso-8859-1"
Hello everybody,
I need to have ad-hoc support into connman. I have a project that will use
B.A.T.M.A.N mesh protocol so i need ad-hoc mode for using it. By doing a small
look into source code of connman and its git history i see that ad-hoc network
are discard from connman. For example you can look the commit
cd9d9e6b485cf730275680d8a4260003b206a1ae Ignore WiFI networks with IBSS (adhoc
mode)
Do it have some particular reason to discard ad-hoc support from connman ?
(Does it conflict with other feature supported by connman for example). And if
i start a work to add ad-hoc mode to connman does it have a change to be
mainlined ?
Every glues to add this support in a proper way are welcome.
Best regards,
Tangi COLIN
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20170703/79b80f3d/attachment-0001.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 21, Issue 1
**************************************
