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: [PATCH] plugins: Build dynamically loadable VPN plugins
(Daniel Wagner)
2. Re: [PATCH] vpn: Rename openconnect-script to vpn-script.
(Daniel Wagner)
3. Re: [PATCH] plugins: Build dynamically loadable VPN plugins
(Jussi Laakkonen)
4. Re: Why can't connman automatically enable and connect to
cellular network interface? (JH)
5. Re: duplicate entries in /etc/resolv.conf (Doron Behar)
6. Re: IPv6 privacy extensions with connman (Christian)
7. Re: Re: VLAN configuration support (Langlois, Maxime)
----------------------------------------------------------------------
Message: 1
Date: Tue, 30 Apr 2019 09:05:40 +0200
From: Daniel Wagner <[email protected]>
To: Jussi Laakkonen <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] plugins: Build dynamically loadable VPN plugins
Message-ID: <20190430070539.hzixutbed7dv5zmj@beryllium>
Content-Type: text/plain; charset=us-ascii
Hi Jussi,
On Mon, Apr 29, 2019 at 05:31:08PM +0300, Jussi Laakkonen wrote:
> This commit fixes the issue of loading external (library) VPN plugins
> using dlopen(). The vpn/plugins/vpn.c source should not be built with
> external VPN plugins as vpn/plugins/vpn.c is regarded as a plugin. This
> will cause undefined symbol erros when opening the .so using dlopen(),
> since vpn.c uses functions defined only for local (builtin) use and are
> cannot be accessed by plugins.
>
> The vpn/plugins/vpn.c source must be included in vpn build sources if
> there is a single VPN plugin to be built. Both builtin and external
> VPN plugins require this. Otherwise, when there are no builtin VPN
> plugins included in build, loading of the external plugins will fail as
> the vpn/plugins/vpn.c would have never included in connman-vpnd.
Patch applied.
I hope you are offended by this: I modified the commit message
slightly. Starting the commit message with 'This patch' or 'This
commit' is redundant. Instead just write in imparative what you do.
Thanks,
Daniel
------------------------------
Message: 2
Date: Tue, 30 Apr 2019 09:07:41 +0200
From: Daniel Wagner <[email protected]>
To: Jussi Laakkonen <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] vpn: Rename openconnect-script to vpn-script.
Message-ID: <20190430070740.ahqzaw25nhznksko@beryllium>
Content-Type: text/plain; charset=us-ascii
Hi Jussi,
On Mon, Apr 29, 2019 at 05:32:50PM +0300, Jussi Laakkonen wrote:
> The scripts/openconnect-script.c has nothing OpenConnect specific and is
> also used by VPNC. Thus, renaming it to generic vpn-script.c clarifies
> the purpose of the script.
>
> Changed OpenConnect and VPNC plugins to use vpn-script. Modified
> Makefile.plugins also to use the vpn-script..
Patch applied.
Thanks,
Daniel
------------------------------
Message: 3
Date: Tue, 30 Apr 2019 10:18:13 +0300
From: Jussi Laakkonen <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] plugins: Build dynamically loadable VPN plugins
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi Daniel,
(Sorry, last one did not reach list)
On 4/30/19 10:05 AM, Daniel Wagner wrote:
> Hi Jussi,
>
> On Mon, Apr 29, 2019 at 05:31:08PM +0300, Jussi Laakkonen wrote:
>> This commit fixes the issue of loading external (library) VPN plugins
>> using dlopen(). The vpn/plugins/vpn.c source should not be built with
>> external VPN plugins as vpn/plugins/vpn.c is regarded as a plugin. This
>> will cause undefined symbol erros when opening the .so using dlopen(),
>> since vpn.c uses functions defined only for local (builtin) use and are
>> cannot be accessed by plugins.
>>
>> The vpn/plugins/vpn.c source must be included in vpn build sources if
>> there is a single VPN plugin to be built. Both builtin and external
>> VPN plugins require this. Otherwise, when there are no builtin VPN
>> plugins included in build, loading of the external plugins will fail as
>> the vpn/plugins/vpn.c would have never included in connman-vpnd.
>
> Patch applied.
>
> I hope you are offended by this: I modified the commit message
> slightly. Starting the commit message with 'This patch' or 'This
> commit' is redundant. Instead just write in imparative what you do.
>
No worries, that is fine. I'll keep that in mind in the next ones. Thanks!
> Thanks,
> Daniel
>
Cheers,
Jussi
------------------------------
Message: 4
Date: Tue, 30 Apr 2019 18:39:22 +1000
From: JH <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: Why can't connman automatically enable and connect to
cellular network interface?
Message-ID:
<CAA=hcwsvfkdkus5e5tae9jkyhp2vbsoh-3byaa9tui-dvks...@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Hi Daniel,
> Type is missing. See examples in config-format.txt
OK, fixed all errors, both wifi and cellular services are added, but
the WiFi and cellular are still not shown in network interface at
follows:
# connmand -n -d src/config.c
connmand[360]: Connection Manager version 1.35
connmand[360]: Adding configuration wifi
connmand[360]: Adding service configuration wifi
connmand[360]: Adding configuration cellular
connmand[360]: Adding service configuration cellular
connmand[360]: Checking loopback interface settings
connmand[360]: lo {newlink} index 1 address 00:00:00:00:00:00 mtu 65536
connmand[360]: lo {newlink} index 1 operstate 0 <UNKNOWN>
<DOWN>
connmand[360]: Adding interface eth0 [ ethernet ]
[ 1318.264479] Micrel KSZ8081 or KSZ8091 20b4000.ethernet-1:02:
attached PHY driver [Micrel KSZ8081 or KSZ8091]
(mii_bus:phy_addr=20b4000.ethernet-1:02, irq=POLL)
connmand[360]: Adding interface eth1 [ ethernet ]
connmand[360]: sit0 {newlink} index 4 address 00:00:00:00:08:00 mtu 1480
connmand[360]: sit0 {newlink} index 4 operstate 2 <DOWN>
connmand[360]: wwan0 {create} index 5 type 1 <ETHER>
connmand[360]: wwan0 {update} flags 4098 <DOWN>
connmand[360]: wwan0 {newlink} index 5 address AE:9E:88:64:6F:1B mtu 1500
connmand[360]: wwan0 {newlink} index 5 operstate 2 <DOWN>
connmand[360]: Adding interface wwan0 [ cellular ]
connmand[360]: mlan0 {create} index 8 type 1 <ETHER>
connmand[360]: mlan0 {update} flags 36866 <DOWN>
connmand[360]: mlan0 {newlink} index 8 address D4:CA:6E:60:D7:F9 mtu 1500
connmand[360]: mlan0 {newlink} index 8 operstate 2 <DOWN>
connmand[360]: Adding interface mlan0 [ wifi ]
I removed Ethernet cable just in case, no wifi and cellular:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:04:9F:05:0F:C0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:235 errors:0 dropped:0 overruns:0 frame:0
TX packets:343 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31217 (30.4 KiB) TX bytes:43427 (42.4 KiB)
eth1 Link encap:Ethernet HWaddr 00:04:9F:05:0F:BF
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:8392 (8.1 KiB) TX bytes:8392 (8.1 KiB)
Anything I could still be missing here?
Thank you.
- jupiter
------------------------------
Message: 5
Date: Tue, 30 Apr 2019 16:25:57 +0300
From: Doron Behar <[email protected]>
To: Daniel Wagner <[email protected]>
Cc: [email protected]
Subject: Re: duplicate entries in /etc/resolv.conf
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
I've patched these against the 1.37 tag and everything seems fine.
I've tried to delete the file (/var/run/connman/resolv.conf) and restart
connmand and I didn't see any duplicate entries like before.
I've also inspected the file during disconnections and connections and
everything seems fine.
Thanks a lot! I'll ask the Arch Linux package maintainers to include
thes patches.
Doron.
On Mon, Apr 29, 2019 at 11:13:12AM +0200, Daniel Wagner wrote:
> HI Doron,
>
> On 28.04.19 18:12, Doron Behar wrote:
> > Would it be possible if perhaps you'll kindly post the commit ids that
> > fixed this when those will be ready? I'd love to build connman with
> > those patches because this is kind of crucial for me.
>
> Could you test these patches:
>
> [PATCH 0/2] Don't export duplicate entries in resolv.conf
>
> Thanks,
> Daniel
------------------------------
Message: 6
Date: Tue, 30 Apr 2019 16:42:14 +0200
From: Christian <[email protected]>
To: [email protected], [email protected]
Subject: Re: IPv6 privacy extensions with connman
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Hi Daniel,
ok, good to know. A bit complicated on some systems, maybe the
connmanctl could print it as well when called with help?Right now I
have 1.37 and still same behaviour.
Were you able to investigate why a "scope global secondary dynamic"
address is created instead of a "scope global temporary dynamic".
Kind regards Christian
Am Mittwoch, den 24.04.2019, 08:53 +0200 schrieb Daniel Wagner:
> Hi Christian,
> On 4/16/19 11:43 AM, Christian wrote:
> I just updated to newer version of libreelec (RPi2.arm-devel-
> 20190413210320-#0413-g977b2aa) and this runs connman 1.37. If you
> want to try it yourself, you find it here:
> https://forum.kodi.tv/showthread.php?tid=298461However I only saw the
> version 1.37 in the update notes. Is there a way to check the version
> via connmanctl? I did not see an option.
> On startup ConnMan will print the version number. I suppose you will
> find in the log files.
> When asking my question, the version must have been at least 1.36
> (also only derived from libreelec update notes).
> Regarding the spelling of preferred, I think any wrong spelling
> should be purged. I know that it is well meant to be fault tolerant,
> but it is massively confusing.
> The wrong spelling is not mentioned except for
> - IPv6.Privacy: IPv6 privacy option. Value can be either
> "disabled", "enabled" or "preferred" (or the misspelled
> "prefered"). Seeuse_tempaddr variable description in Linux kernel
> Documentation/networking/ip-sysctl.txt file.
> and the code just excepts 'prefered' as alternative. Whenever we do a
> major update we can also drop that part.
> Thanks,Daniel
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20190430/8bdffc91/attachment-0001.html>
------------------------------
Message: 7
Date: Tue, 30 Apr 2019 17:41:59 +0000
From: "Langlois, Maxime" <[email protected]>
To: "[email protected]" <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: Re: VLAN configuration support
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"
On Mon, 2019-04-29 at 21:30 +0200, Daniel Wagner wrote:
> Just posted a patch which adds support to match on device name. Please
> if possible give them a spin and report back.
Hi Daniel,
sure I can give it a go as soon as I have a chance! Will keep you posted...
Thanks!
- Maxime
**********************************************************************
DISCLAIMER:
Privileged and/or Confidential information may be contained in this message. If
you are not the addressee of this message, you may not copy, use or deliver
this message to anyone. In such event, you should destroy the message and
kindly notify the sender by reply e-mail. It is understood that opinions or
conclusions that do not relate to the official business of the company are
neither given nor endorsed by the company. Thank You.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.01.org/pipermail/connman/attachments/20190430/625b160a/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 42, Issue 29
***************************************
