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. [PATCH 2/2] doc: Update IPv4 method values for services
      ([email protected])
   2. Re: Iptables error with rule creation (Jeff Gray)


----------------------------------------------------------------------

Message: 1
Date: Tue, 30 May 2017 10:14:13 +0000
From: [email protected]
To: [email protected]
Subject: [PATCH 2/2] doc: Update IPv4 method values for services
Message-ID:
        
<1496139253-13988-2-git-send-email-jose.blanquicet-melen...@magnetimarelli.com>
        

From: Jose Blanquicet <[email protected]>

---
 doc/service-api.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/service-api.txt b/doc/service-api.txt
index 712627a..1b2b488 100644
--- a/doc/service-api.txt
+++ b/doc/service-api.txt
@@ -311,6 +311,12 @@ Properties string State [readonly]
                                Possible values are "dhcp", "manual"
                                and "off".
 
+                               It could be "auto" in case address was got
+                               through IPv4LL after DHCP failed. In this
+                               case also IPv4.Configuration will become
+                               "auto" to allow user to ask for a DHCP
+                               address at any time.
+
                                The value "fixed" indicates an IP address
                                that can not be modified. For example
                                cellular networks return fixed information.
-- 
1.9.1



------------------------------

Message: 2
Date: Tue, 30 May 2017 20:34:10 +1000
From: Jeff Gray <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: Iptables error with rule creation
Message-ID:
        <cahb0ztk7955-1ybzt6rmnf9qn7a11_acouys6_mwbhkxfm0...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi Daniel,

On 30 May 2017 at 06:10, Daniel Wagner <[email protected]> wrote:
>
> Old is for sure not the right term, it is from a different millennium! :)
>

Yes, it is one from the vaults... I wish I was in a position to replace it.

The iptables code in ConnMan is known to be not 100% correct on how it
> creates the iptables. It seems to okay for modern kernels but that is just
> luck. One way around this problem could be to replace the ConnMan code
> which creates the iptables with calling iptables shell command.
>
> Obviously there would be some forks involved but that would be the
> simplest solution in your situation I suppose. I wouldn't recommend to
> spend time figuring out what ConnMan is doing and what the kernel expects.
> I spend far too many hours myself on this topic. That's why I recommend to
> use the nftable implementation usally but that is probably not going to fly
> with 2.6.
>

Thanks for the helpful suggestion. Has anyone else ever tried to do this?

Would you be able to point me in the right direction in terms of what
functional layer to insert iptables shell commands?
I can see that at __connman_iptables_insert() for example, I have a fairly
complete iptables parameter list already.
Should I just ifdef out the existing iptables API calls? The code is fairly
daunting to understand completely, so any help appreciated.

I got wifi working today, so I'm pretty pleased that side was so easy. It's
just the gadget interface that will take a bit more work.

Regards,
Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.01.org/pipermail/connman/attachments/20170530/27d340c4/attachment-0001.html>

------------------------------

Subject: Digest Footer

_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman


------------------------------

End of connman Digest, Vol 19, Issue 17
***************************************

Reply via email to