Re: manage bluetooth devices using NetworkManger
Hi, On Mon, 2020-10-05 at 23:29 +0530, NIKHIL PATIL wrote: > Hi, >1) yes. I added networkmanager with bluetooth support. > My networkmanager_1.10.6.bbappend file :- > PACKAGECONFIG_append = " bluez5" > > Is this fine for bluetooth support or need to be extra in > networkmanager_1.10.6.bb file ? Possibly. I am not familiar with yocto or your build setup. What matters is that you have a file like "libnm-device-plugin- bluetooth.so", and that the logfile indicates that the bluetooth plugin is loaded. >2) default bluez5 (bluetooth package ) is dealing with connman , > how we can make so bluez5 will deal with networkmanager in yocto? bluez is a service that provides a (D-Bus based) API for dealing with bluetooth. Connman and NetworkManager are services that provide an API for configuring network interfaces, they both may do so by interacting with bluez. It is Connman/NetworkManager who talks to bluez, not the other way around. This means, if you want NetworkManager to configure your bluetooth devices, then do it in NetworkManager (by setting it up correctly, like having the bluetooth plugin working, and activating a bluetooth connection profile in NetworkManager). NetworkManager isn't aware of what other services (connman) you have running. Not sure what your question is, but of course if you currently have another layer (like a GUI application) that is based on Connman's API, then you need to convince that other layer to talk to NetworkManager instead. Which might not be possible, because most upper layers (GUIs) either talks to NetworkManager or Connman, not both). In that case, use a upper layer tool that is on top of NetworkManager instead of Connman. best, Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: manage bluetooth devices using NetworkManger
Hi, 1) yes. I added networkmanager with bluetooth support. My networkmanager_1.10.6.bbappend file :- PACKAGECONFIG_append = " bluez5" Is this fine for bluetooth support or need to be extra in networkmanager_1.10.6.bb file ? 2) default bluez5 (bluetooth package ) is dealing with connman , how we can make so bluez5 will deal with networkmanager in yocto? On Mon, Oct 5, 2020 at 8:06 PM Thomas Haller wrote: > Hi, > > On Mon, 2020-10-05 at 13:11 +0530, NIKHIL PATIL wrote: > > We are using Redpine module (rsi9113) which support bluetooth + > > wifi . > > OS - yocto based linux. > > NetworkManager version :- 1.10.6 > > > >1) for WIFI we are able to manage using nmcli commands . > >-> nmcli device > >DEVICE TYPE STATE CONNECTION > > wlp0s21f0u4wifi connectedtest > > > > 2) for bluetooth can we except like these ( bluetooth interface (eg. > > bnp0)) using nmcli commands . > > > > My networkmanager_1.10.6.bbappend file :- > > PACKAGECONFIG_append = " modemmanager" > > PACKAGECONFIG_append = " ppp ifupdown wifi bluez5" > > > >I added bluez5 in .bbappend file , i thought it will manage > > through these , but not happening , > > i think by default bluez5 is dealing with connman , how we can > > switch bluez5 with networkmanager . > > 1.10.0 was released almost 3 years ago (and the minor update 1.10.6 > five months after that). If possible, I wouldn't bother with such an > old version and use something more recent. > > Anyway, did you build NetworkManager with bluetooth support enabled? > > Under `nmcli device` you would see the paired bluetooth devices (that > support network related bluetooth profiles). > > > Did you look at the log file? > > > >3) using nmcli commands will show bluetooth device is connected or > > not ? > > nmcli device > nmcli connection > > > > > best, > Thomas > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: New "tc qdisc" options
OK, adding it to my backlog (;-)) --dave On 2020-10-05 11:56 a.m., Beniamino Galvani wrote: On Mon, Oct 05, 2020 at 11:52:32AM -0400, Dave Collier-Brown wrote: I can absolutely propose a patch/MR based on that example, but I'm fallible (;-)) Do you prefer an MR in github or a git-format-patch via email? A MR on gitlab is the preferred way: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests Thanks, Beniamino -- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest dav...@spamcop.net | -- Mark Twain ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: New "tc qdisc" options
I can absolutely propose a patch/MR based on that example, but I'm fallible (;-)) Do you prefer an MR in github or a git-format-patch via email? --dave On 2020-10-05 10:32 a.m., Beniamino Galvani wrote: On Mon, Oct 05, 2020 at 06:35:19AM -0400, Dave Collier-Brown via networkmanager-list wrote: I see code in https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/libnm-core/nm-setting-tc-config.c which implements setting tc qdisc, and a brief mention in https://developer.gnome.org/NetworkManager/stable/ However the man pages do not mention tc. Can you provide a hint on setting, for example, /tc qdisc replace dev enp0s25 root cake bandwidth 20mbit/ in network manager? "cake" is currently not supported. Until that is added, the intended solution is to use a dispatcher script. See `man NetworkManager`. Alas, that's the first place I looked (:-() Cake doesn't need to be supported in network manager, as I can work around it's lack with fq_codel. However, I do need to discover the location and notation interpreted by nm-setting-tc-config.c 1) can you help me with that? To configure fq_codel, you can use nmcli in this way: $ nmcli connection modify $myconnection tc.qdiscs \ "root fq_codel limit 2000 target 3000 interval 4" $ nmcli connection up $myconnection $ tc qdisc show dev $mydev qdisc fq_codel 8003: root refcnt 2 limit 2000p flows 1024 quantum 1514 target 3.0ms interval 40.0ms memory_limit 32Mb ecn 2) is adding (the name of) the cake qdisc on your backlog? Currently NM doesn't support configuring CAKE parameters. IOW, if you set "root cake bandwidth 100Mbit", you will see in the tc output that cake was set but with default parameters. Yes, I think it will be useful to have CAKE support in NM, but I can't say when it will be implemented. Of course, patches are always welcome; if anybody is interested in contributing it, please have a look at the work that was done to support SFQ: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/b22b4f9101b1cbfde49b65d9e2107e4ae0d817c0 Beniamino -- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest dave.collier-br...@indexexchange.com | -- Mark Twain CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: New "tc qdisc" options
On Mon, Oct 05, 2020 at 11:52:32AM -0400, Dave Collier-Brown wrote: > I can absolutely propose a patch/MR based on that example, but I'm > fallible (;-)) > > Do you prefer an MR in github or a git-format-patch via email? A MR on gitlab is the preferred way: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests Thanks, Beniamino signature.asc Description: PGP signature ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: manage bluetooth devices using NetworkManger
Hi, On Mon, 2020-10-05 at 13:11 +0530, NIKHIL PATIL wrote: > We are using Redpine module (rsi9113) which support bluetooth + > wifi . > OS - yocto based linux. > NetworkManager version :- 1.10.6 > >1) for WIFI we are able to manage using nmcli commands . >-> nmcli device >DEVICE TYPE STATE CONNECTION > wlp0s21f0u4wifi connectedtest > > 2) for bluetooth can we except like these ( bluetooth interface (eg. > bnp0)) using nmcli commands . > > My networkmanager_1.10.6.bbappend file :- > PACKAGECONFIG_append = " modemmanager" > PACKAGECONFIG_append = " ppp ifupdown wifi bluez5" > >I added bluez5 in .bbappend file , i thought it will manage > through these , but not happening , > i think by default bluez5 is dealing with connman , how we can > switch bluez5 with networkmanager . 1.10.0 was released almost 3 years ago (and the minor update 1.10.6 five months after that). If possible, I wouldn't bother with such an old version and use something more recent. Anyway, did you build NetworkManager with bluetooth support enabled? Under `nmcli device` you would see the paired bluetooth devices (that support network related bluetooth profiles). Did you look at the log file? >3) using nmcli commands will show bluetooth device is connected or > not ? nmcli device nmcli connection best, Thomas signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: New "tc qdisc" options
On Mon, Oct 05, 2020 at 06:35:19AM -0400, Dave Collier-Brown via networkmanager-list wrote: > > > I see code in > > > > > > https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/libnm-core/nm-setting-tc-config.c > > > > > > which implements setting tc qdisc, and a brief mention in > > > > > > https://developer.gnome.org/NetworkManager/stable/ > > > > > > However the man pages do not mention tc. > > > > > > Can you provide a hint on setting, for example, /tc qdisc replace dev > > > enp0s25 root cake bandwidth 20mbit/ in network manager? > > "cake" is currently not supported. Until that is added, the intended > > solution is to use a dispatcher script. See `man NetworkManager`. > > Alas, that's the first place I looked (:-() > > Cake doesn't need to be supported in network manager, as I can work > around it's lack with fq_codel. > > However, I do need to discover the location and notation interpreted by > nm-setting-tc-config.c > > 1) can you help me with that? To configure fq_codel, you can use nmcli in this way: $ nmcli connection modify $myconnection tc.qdiscs \ "root fq_codel limit 2000 target 3000 interval 4" $ nmcli connection up $myconnection $ tc qdisc show dev $mydev qdisc fq_codel 8003: root refcnt 2 limit 2000p flows 1024 quantum 1514 target 3.0ms interval 40.0ms memory_limit 32Mb ecn > > 2) is adding (the name of) the cake qdisc on your backlog? Currently NM doesn't support configuring CAKE parameters. IOW, if you set "root cake bandwidth 100Mbit", you will see in the tc output that cake was set but with default parameters. Yes, I think it will be useful to have CAKE support in NM, but I can't say when it will be implemented. Of course, patches are always welcome; if anybody is interested in contributing it, please have a look at the work that was done to support SFQ: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/b22b4f9101b1cbfde49b65d9e2107e4ae0d817c0 Beniamino signature.asc Description: PGP signature ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: manage bluetooth devices using NetworkManger
Hi Team, We are using Redpine module (rsi9113) which support bluetooth + wifi . OS - yocto based linux. NetworkManager version :- 1.10.6 1) for WIFI we are able to manage using nmcli commands . -> nmcli device DEVICE TYPE STATE CONNECTION wlp0s21f0u4 wifi connected test 2) for bluetooth can we except like these ( bluetooth interface (eg. bnp0)) using nmcli commands . My *networkmanager_1.10.6.bbappend* file :- PACKAGECONFIG_append = " modemmanager" PACKAGECONFIG_append = " ppp ifupdown wifi bluez5" I added *bluez5* in .bbappend file , i thought it will manage through these , but not happening , i think by default bluez5 is dealing with *connman , *how we can switch bluez5 with* networkmanager .* 3) using nmcli commands will show bluetooth device is connected or not ? On Mon, Oct 5, 2020 at 12:26 PM Thomas Haller wrote: > On Mon, 2020-10-05 at 12:22 +0530, NIKHIL PATIL via networkmanager-list > wrote: > > hi , > > any update on these ? > >we badly stuck here. > > > > On Tue, Sep 22, 2020 at 11:21 AM NIKHIL PATIL > > wrote: > > > Hi , > > > We are using Redpine rsi9113 bluetooth module connected > > > via USB to Soc board. > > > processor - intel 3930 . > > > platform - yocto based linux . > > > How we can manage bluetooth device using NetworkManager (nmcli) > > > commands. > > > Hi, > > > recent NetworkManager version interact (only) with bluez5. > > As always in NetworkManager, create a suitable connection profile and > activate it. Actually, NetworkManager will automatically generate a > profile for all paired devices, so you should see the respective > profiles. > > And, read the logfile if something doesn't work (enable level=TRACE > logging. See > > https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 > ). > > Also, your question on this list is lacking detail. Explain what you > are doing, what *exactly* you want to achieve, and what you think is > happening. > > > best, > Thomas > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: New "tc qdisc" options
On 2020-10-05 2:58 a.m., Thomas Haller wrote: Hi, On Sun, 2020-10-04 at 11:47 -0500, dav...@spamcop.net wrote: I need to set tc under network manager to enable CAKE in Fedora/Red Hat 8/Centos 8/Ubuntu for a community of users badly affected by "bufferbloat". On my test machine, I can the appropriate options with tc, but it is almost immediately reset by Network Manager. How did you set the tc options? From the command-line, below. I see code in https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/master/libnm-core/nm-setting-tc-config.c which implements setting tc qdisc, and a brief mention in https://developer.gnome.org/NetworkManager/stable/ However the man pages do not mention tc. Can you provide a hint on setting, for example, /tc qdisc replace dev enp0s25 root cake bandwidth 20mbit/ in network manager? "cake" is currently not supported. Until that is added, the intended solution is to use a dispatcher script. See `man NetworkManager`. Alas, that's the first place I looked (:-() Cake doesn't need to be supported in network manager, as I can work around it's lack with fq_codel. However, I do need to discover the location and notation interpreted by nm-setting-tc-config.c 1) can you help me with that? 2) is adding (the name of) the cake qdisc on your backlog? --dave -- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest dave.collier-br...@indexexchange.com | -- Mark Twain CONFIDENTIALITY NOTICE AND DISCLAIMER : This telecommunication, including any and all attachments, contains confidential information intended only for the person(s) to whom it is addressed. Any dissemination, distribution, copying or disclosure is strictly prohibited and is not a waiver of confidentiality. If you have received this telecommunication in error, please notify the sender immediately by return electronic mail and delete the message from your inbox and deleted items folders. This telecommunication does not constitute an express or implied agreement to conduct transactions by electronic means, nor does it constitute a contract offer, a contract amendment or an acceptance of a contract offer. Contract terms contained in this telecommunication are subject to legal review and the completion of formal documentation and are not binding until same is confirmed in writing and has been signed by an authorized signatory. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
