Re: KDE Network Manager doesn't allow editing of a Bluetooth dun connection

In data martedì 3 settembre 2019 18:21:09 CEST, gumb ha scritto:
> On 03/09/2019 12:17, stakanov wrote:
> > In data martedì 3 settembre 2019 11:40:58 CEST, gumb ha scritto:
> >> On 03/09/2019 07:34, stakanov wrote:
> >>> In data lunedì 2 settembre 2019 16:49:04 CEST, gumb ha scritto:
> >>>> Leap 15.1
> >>>> 
> >>>> The other day I had the need to connect to the Internet via my mobile,
> >>>> so having torn my hair out for a good twenty minutes trying and failing
> >>>> to create a mobile broadband connection via USB, I changed tack and
> >>>> looked in the Bluetooth settings. There I was able to configure a dun
> >>>> connection by selecting my country/operator, and it worked.
> >>>> 
> >>>> However, now on every boot/resume it tries to autoconnect to this
> >>>> bluetooth network. I reviewed the settings in KDE Network Connections,
> >>>> changed the priority to -1, unchecked 'Automatically connect to this
> >>>> network when it is available', but it's not possible to save these
> >>>> settings, neither with the Apply, OK buttons nor by selecting another
> >>>> network and hoping to be prompted, as happens on any other connection I
> >>>> change. The Apply button remains greyed out no matter what changes I
> >>>> make to the bluetooth connection.
> >>>> 
> >>>> My only choice hence is to completely delete the connection and to have
> >>>> to recreate it every time I might need it, because on my free mobile
> >>>> contract I only get 50mb of data per month, the rest is charged
> >>>> out-of-contract. I can't risk being unknowingly connected and running
> >>>> up
> >>>> a huge bill!
> >>>> 
> >>>> I assume this is a bug but should it go upstream? Can anybody reproduce
> >>>> it?
> >>>> 
> >>>> gumb
> >>> 
> >>> Yes I can reproduce it one on one.
> >>> I created a DUN connection with my 3G umts BT phone and as a result,
> >>> although the setting is -1 or even -100 (does not matter) the priority
> >>> is
> >>> disregarded. It always stays on "0". Also firewallsettings are not taken
> >>> over. I have thus a double connection for this device. DUN and NAP and I
> >>> use at the end the BT NAP settings.
> >>> All this happens also when you are on a wlan or ethernet.
> >>> I have "secure" settings, so the only annoyance I face is that I am
> >>> asked
> >>> the root password to change networksettings (which I -obviously- deny).
> >>> BTW try that out: it does not matter if your phone is switched on or in
> >>> reach or not. It just tries to connect "wildly" just like that.
> >>> Unfortunately I have bad news for you. If I am not wrong DUN will be
> >>> taken
> >>> off as capacity from BT if I am not wrong. You better check if this is
> >>> true, I read something about it, but did not pay excessive attention.
> >>> 
> >>> But I can confirm the bug for KDE (stock) in 15.1 openSUSE.
> >>> If you open a bug I will cc and even vote for it.
> >>> 
> >>> Tipp: check for your priority after a reboot. If I am not wrong your
> >>> priority is again at 0 for DUN when you reboot.
> >> 
> >> Thanks for checking. Potentially a shame if dun support is removed from
> >> bluetooth, although it's not something I use regularly. By the time it's
> >> gone I might well have another phone / solution.
> >> 
> >> Likewise, on my system it continually tries to connect every few
> >> minutes, indeed it is doing so right now as I type despite the fact that
> >> I have another active, stable wifi connection. Which seems to indicate
> >> that the edits I just made to the file in
> >> /etc/NetworkManager/system-connections/ have not had the desired effect.
> >> Unless I need to run a command for this file to be re-read.
> >> 
> >> I added the following lines in the [connection] section:
> >> autoconnect=false
> >> autoconnect-priority=-1
> >> zone=external
> >> 
> >> copying from what I see in files for other connections.
> >> 
> >> I'll file a bug when I have time and let you know the link. I recall
> >> once upon a time that for pretty much all KDE-related bugs it was
> >> advised to post them upstream on the KDE bug tracker, not openSUSE
> >> Bugzilla. I don't know if that's still the case.
> > 
> > Well for this one I highly advise KDE. It would be different if this would
> > be a case of bug fixed upstream, in this case you would have to file it
> > to opensuse (but to be honest with low hopes of getting a fix).
> > 
> > If you have e.g. a Nokia 4g 8110 banana phone, that one does work
> > flawlessly in wlan tethering and gives good results. BT dun is now really
> > rare these days (I guess because the f(x) has become really cheap when
> > wlan is present as AP on Smart and less smart phones.
> > 
> > Thanks for letting me know the bug number in case.
> 
> I've filed a bug here:
> https://bugs.kde.org/show_bug.cgi?id=411562
> 
> I also found that after a reboot, the changes I made in that file in
> /etc/NetworkManager/system-connections/ have thankfully taken effect,
> and show up in the Network Connections dialog.
> 
> gumb
Oh, thank you. 
I will then have some workaround for my DUN connect. Great. 

And thank you also for the feedback. 




_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de


-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]