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] dhcp: reduce socket creation/bind latency
(Daniel Wagner)
2. Re: Why I have no Scope:Global IPV6 address ? (Patrik Flykt)
3. Re: Make online service provides Internet to the other
services (Patrik Flykt)
4. Re: Make online service provides Internet to the other
services (Jose Blanquicet)
----------------------------------------------------------------------
Message: 1
Date: Mon, 17 Apr 2017 21:35:19 +0200
From: Daniel Wagner <[email protected]>
To: Tobias Klauser <[email protected]>
Cc: [email protected]
Subject: Re: [PATCH] dhcp: reduce socket creation/bind latency
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed
Hi Tobias,
On 04/12/2017 11:26 AM, Tobias Klauser wrote:
> When creating a PF_PACKET socket with subsequent bind() call - both using
> the same protocol argument - passing the protocol to socket() is
> redundant and omitting it can save some latency. This should drop the
> cost of the subsequent bind() to almost zero, see [1] for details.
>
> Reference:
> [1]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=902fefb82ef72a50c78cb4a20cc954b037a98d1c
>
> Signed-off-by: Tobias Klauser <[email protected]>
Patch applied. Sorry that it took so long. I was on vacation.
I dropped the SoB because we don't do it.
Thanks,
Daniel
------------------------------
Message: 2
Date: Tue, 18 Apr 2017 10:41:12 +0300
From: Patrik Flykt <[email protected]>
To: Pierre Couderc <[email protected]>, [email protected]
Subject: Re: Why I have no Scope:Global IPV6 address ?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
On Fri, 2017-04-14 at 10:39 +0200, Pierre Couderc wrote:
> Thank you very much. I have checked all that and it seems correct.
> Now I?suspect my Wifi router.
wireshark and filter on ICMPv6. There should be Router Advertisments if
your router attempts to provide IPv6.
Cheers,
Patrik
------------------------------
Message: 3
Date: Tue, 18 Apr 2017 10:55:03 +0300
From: Patrik Flykt <[email protected]>
To: Jose Blanquicet <[email protected]>
Cc: [email protected]
Subject: Re: Make online service provides Internet to the other
services
Message-ID: <[email protected]>
Content-Type: text/plain; charset="UTF-8"
Hi,
On Fri, 2017-04-14 at 10:03 +0200, Jose Blanquicet wrote:
> Hi Patrik
>
> On Thu, Apr 13, 2017 at 9:50 AM, Patrik Flykt wrote:
> > Simply enabling tethering for ethernet technology will cause
> > ethernet to use the online service as its upstream via NAT
> > masquerading and join ethernet into the 'tether' bridge. The latter
> > option is nice as now all tethered devices will be able to connect
> > each other, independent whether connected over Bluetooth, WiFi or
> > ethernet. DHCP and DNS will be shared between all the tethered
> > technologies as DHCP and DNS open their sockets on the bridge
> > interface.
>
> Very interesting, I tried it and it works pretty well. Now I think I
> fully understood the purpose of the 'tether' bridge, which I asked
> some time ago.
>
> However, I noticed that in case of multiple interfaces per
> technology, tethering on Ethernet does not work as on WiFi. I mean,
> if I enable tethering on WiFi, only one of my WiFi interfaces will
> play as AP and I still can use the others for other functions.
> Instead, if I enable tethering on Ethernet, I will "lose" all my
> Ethernet interfaces, all of them will join the 'tether' bridge and
> they will work as GW for the devices connected in the other ends.
> That's fine but in my case I would like to use one of my Ethernet
> interface as upstream and another for tether, how could I do this?
This is a bit of an artefact for WiFi. Each wifi device attempting to
tether has to have the capability to act as an Access Point, so only
those AP capable wifi devices can be used. Also, there is nothing to be
gained enabling AP mode on more than one wifi device, so ConnMan can
semi-accidentally continue to use the other WiFi devices for upstream
connections provided that wpa_supplicant manages to have all this
running at the same time.
With ethernet there are no such restrictions, as ethernet does not need
anything special in order to do tethering. In ethernet we can only
assume that each ethernet device is connected to a different network,
as bonding devices do not show up with their individual ethernet
devices. So with ethernet tethering has to happen over all the
interfaces in order to be understandable.
ConnMan does not have a notion of network devices exposed to the user
and is not a router either. If serious fine-grained configuration is
needed, for example systemd-networkd is there to bridge this gap.
Cheers,
Patrik
------------------------------
Message: 4
Date: Tue, 18 Apr 2017 09:50:59 +0000
From: Jose Blanquicet <[email protected]>
To: Patrik Flykt <[email protected]>
Cc: [email protected]
Subject: Re: Make online service provides Internet to the other
services
Message-ID:
<CAFC8iJLJO9G4QP57CPk4_k19=jpwzu-9sn4ln4epktntghc...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Hi Patrik,
On Tue, Apr 18, 2017 at 7:55 AM, Patrik Flykt wrote:
>> However, I noticed that in case of multiple interfaces per
>> technology, tethering on Ethernet does not work as on WiFi. I mean,
>> if I enable tethering on WiFi, only one of my WiFi interfaces will
>> play as AP and I still can use the others for other functions.
>> Instead, if I enable tethering on Ethernet, I will "lose" all my
>> Ethernet interfaces, all of them will join the 'tether' bridge and
>> they will work as GW for the devices connected in the other ends.
>> That's fine but in my case I would like to use one of my Ethernet
>> interface as upstream and another for tether, how could I do this?
>
> This is a bit of an artefact for WiFi. Each wifi device attempting to
> tether has to have the capability to act as an Access Point, so only
> those AP capable wifi devices can be used. Also, there is nothing to be
> gained enabling AP mode on more than one wifi device, so ConnMan can
> semi-accidentally continue to use the other WiFi devices for upstream
> connections provided that wpa_supplicant manages to have all this
> running at the same time.
>
> With ethernet there are no such restrictions, as ethernet does not need
> anything special in order to do tethering. In ethernet we can only
> assume that each ethernet device is connected to a different network,
> as bonding devices do not show up with their individual ethernet
> devices. So with ethernet tethering has to happen over all the
> interfaces in order to be understandable.
>
> ConnMan does not have a notion of network devices exposed to the user
> and is not a router either. If serious fine-grained configuration is
> needed, for example systemd-networkd is there to bridge this gap.
Understood. Thank you for the support.
Jose Blanquicet
------------------------------
Subject: Digest Footer
_______________________________________________
connman mailing list
[email protected]
https://lists.01.org/mailman/listinfo/connman
------------------------------
End of connman Digest, Vol 18, Issue 13
***************************************
