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: ConnMan 1.31 (Patrik Flykt)
   2. Re: Extend DHCP request to query timezone (Patrik Flykt)
   3. [PATCH] dhcp: Timeserver issue on IP address renewal after
      lease expiry (Patrik Flykt)
   4. Re: incorrect iptable rule deletion for session fwmarks
      (Daniel Wagner)


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

Message: 1
Date: Mon, 11 Jan 2016 10:02:00 +0200
From: Patrik Flykt <[email protected]>
To: connman <[email protected]>
Subject: Re: ConnMan 1.31
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"


        Hi,

For Debian one can also pick up "upstream" .deb packages and build
ConnMan using https://github.com/pfl/connman-deb as well as oFono using
https://github.com/pfl/ofono-deb

If there are any active Debian (Ubuntu) developers that are familiar
with official distro procedures and want to keep ConnMan and oFono
packages up to date for both distros, this is your chance! This in order
to reduce duplication of work between current Debian, latest Ubuntu by
Mike and the latest "upstream" packaging above.

Besides these, there are GNOME UIs https://github.com/jgke/connman-gtk
https://github.com/jgke/gnome-extension-connman , system tray UIs
https://github.com/tbursztyka/connman-ui , and  pacrunner
http://git.kernel.org/cgit/network/connman/pacrunner.git/ than are up
for some packaging polish.

Cheers,

        Patrik

On Thu, 2015-12-31 at 14:49 -0500, Mike Purvis wrote:
> For interested parties, my PPA has been updated for current Ubuntu
> releases:
> 
> 
> https://launchpad.net/~mikepurvis/+archive/ubuntu/network







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

Message: 2
Date: Mon, 11 Jan 2016 10:11:40 +0200
From: Patrik Flykt <[email protected]>
To: Bertrand Jacquin <[email protected]>
Cc: [email protected]
Subject: Re: Extend DHCP request to query timezone
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"

On Sat, 2016-01-02 at 15:06 +0000, Bertrand Jacquin wrote:
> Hi all,
> 
> I've been looking on how to extend DHCP request to query additional
> fields like option 101 (Timezone) via the config file, but it looks to
> be somewhat hardcoded in the source code. In there any opportunies to
> extend this ? I'm traveling quiet a bit in regions with different
> timezone and as a lazy man I would like to avoid manually changing my
> timezone.

It's indeed hardcoded at the moment. This sounds like a useful option
would someone like to implement it.

To me it looks like handling the timezone option in src/dhcp.c with
dhcp_initialize() and lease_available_cb(), and then using
src/timezone.c, __connman_timezone_change(), to set it. Perhaps not
everybody wants a timezone change, so an main.conf option is needed for
this. But this after only 2 mins of inspecting, please take it with a
grain of salt.

Cheers,

        Patrik



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

Message: 3
Date: Mon, 11 Jan 2016 11:05:01 +0200
From: Patrik Flykt <[email protected]>
To: [email protected]
Subject: [PATCH] dhcp: Timeserver issue on IP address renewal after
        lease expiry
Message-ID:
        <[email protected]>

Similar to nameservers, timeservers are also checked against previous
values when added. When there is no change in timeservers when the DHCP
lease is lost and reacquired, the service will not be notified if the
timeservers have changed. With timeservers removed on lease lost,
timeservers are not properly updated once reacquired.

Fix this by removing timeservers from the dhcp struct when lease is lost.
---
 src/dhcp.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/dhcp.c b/src/dhcp.c
index 159fecb..4040ad1 100644
--- a/src/dhcp.c
+++ b/src/dhcp.c
@@ -108,6 +108,8 @@ static bool apply_dhcp_invalidate_on_network(struct 
connman_dhcp *dhcp)
                        __connman_service_timeserver_remove(service,
                                                        dhcp->timeservers[i]);
                }
+               g_strfreev(dhcp->timeservers);
+               dhcp->timeservers = NULL;
        }
        if (dhcp->nameservers) {
                for (i = 0; dhcp->nameservers[i]; i++) {
-- 
2.1.4



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

Message: 4
Date: Mon, 11 Jan 2016 13:25:03 +0100
From: Daniel Wagner <[email protected]>
To: Dragos Tatulea <[email protected]>
Cc: [email protected]
Subject: Re: incorrect iptable rule deletion for session fwmarks
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

Hi Dragos,

On 01/08/2016 05:25 PM, Dragos Tatulea wrote:
> I'm playing around with connman 1.31 and sessions with user policies. I have
> observed a case when deletion of iptable fwmark rules doesn't work as
> expected. The wrong rule gets deleted.
> 
> With connman running, I create the following sessions:
> 
> #> ./connman/test/test-session create /foo session0
> #> ./connman/test/test-session create /foo session1
> #> iptables -t mangle -L
> ...
> Chain connman-OUTPUT (1 references)
> target     prot opt source               destination         
> MARK       all  --  anywhere             anywhere             owner UID match 
> vagrant MARK set 0x100
> MARK       all  --  anywhere             anywhere             owner UID match 
> vagrant MARK set 0x101
> ...
> 
> #> ./connman/test/test-session destroy /foo session1
> ...
> Chain connman-OUTPUT (1 references)
> target     prot opt source               destination         
> MARK       all  --  anywhere             anywhere             owner UID match 
> vagrant MARK set 0x101
> ...
> 
> I would expect that rule with mark 0x100 would be deleted. 

Me too.

> The commands
> are being run as user vagrant. The policy file looks like this:
> #> cat /usr/local/var/lib/connman/session_policy_local/vagrant.policy
> [policy_vagrant]
> uid = vagrant
> ConnectionType = any
> AllowedBearers = ethernet
> 
> As noticed from the path, I'm running connman in maintainer mode.
> 
> So, is this expected behavior? This might be harmless in general. I'm
> working on having per session multipath routes installed. In that case,
> getting the fwmark right is important.

Note you need for each session its own unique uid in order to match
correctly. But that is something for later.

First we need to get the destroy working correctly. Could you post
(maybe pastebin) the ConnMan debug log output (connman -n -d)? I am not
completely convinced that the test script works as expected.

thanks,
daniel


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

Subject: Digest Footer

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


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

End of connman Digest, Vol 3, Issue 6
*************************************

Reply via email to