31 May
2017
31 May
'17
10:15 a.m.
Hi,
When I tether via WiFi to my Android phone I get:
minas-tirith:~ # ifconfig
...
wlan0 Link encap:Ethernet HWaddr 0C:EE:E6:D7:BB:5F
inet addr:192.168.43.53 Bcast:192.168.43.255 Mask:255.255.255.0
inet6 addr: fe80::eee:e6ff:fed7:bb5f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2558269 errors:0 dropped:0 overruns:0 frame:0
TX packets:1639469 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2837720447 (2706.2 Mb) TX bytes:191793814 (182.9 Mb)
minas-tirith:~ #
minas-tirith:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.43.1 0.0.0.0 UG 600 0 0 wlan0
192.168.43.0 * 255.255.255.0 U 600 0 0 wlan0
minas-tirith:~ #
This works.
However, if I tether via USB cable (which worked some months past, probably using openSUSE
13.1), it doesn't work.
[...]
After investigation (two hours), I noticed that NM was using an old configuration:
<1.5> 2017-05-31 10:31:12 minas-tirith nm-mine - - - Inside nm-mine
(dispatcher.d/mine), got 'usb0', 'down', '', '',
''
<1.5> 2017-05-31 10:31:12 minas-tirith nm-mine - - - Connection usb0 is going down
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - - ACCION=down
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - - BASH=/bin/sh
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASHOPTS=checkwinsize:cmdhist:complete_fullquote:extquote:force_fignore:hostcomplete:interactive_comments:progco
mp:promptvars:sourcepath
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - - BASH_ALIASES=()
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASH_ARGC=([0]="2")
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASH_ARGV=([0]="down" [1]="usb0")
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - - BASH_CMDS=()
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASH_LINENO=([0]="0")
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASH_SOURCE=([0]="/etc/NetworkManager/dispatcher.d/mine")
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASH_VERSINFO=([0]="4" [1]="3" [2]="42" [3]="1"
[4]="release" [5]="x86_64-suse-linux-gnu")
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
BASH_VERSION='4.3.42(1)-release'
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - - CONEXION=usb0
<3.6> 2017-05-31 10:31:12 minas-tirith nm-dispatcher 23735 - -
CONNECTION_FILENAME='/etc/NetworkManager/system-connections/Samsung mobile via
USB'
What surprises me is the reference to '/etc/NetworkManager/system-connections/Samsung
mobile via USB', as my current phone is a Motorola. And there I see:
[ipv4]
address1=192.168.1.129/24,192.168.1.1
dns=127.0.0.1;
dns-search=valinor;
may-fail=false
method=manual
So that is where NM gets the IP and GW from, not automatic. So I move that file away and
try to connect again.
But I still get the same IP and GW.
The NM applet informs that the current connection is "Auto Ethernet".
How do I correct the situation?
I have reinstated the "Samsung mobile via USB" profile set to autoIP, but
doesn't work. I then noticed that the UUID is wrong, so I renamed the file to
"Motorola USB", and changed the UUID. Now, finally, I get the IP set to
"192.168.42.18" and GW to 192.168.42.129, and networking finally works via USB
tethering.
There must be some GUI way of doing this!
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" (Minas Tirith))
31 May
31 May
7:07 p.m.
On 05/31/2017 05:15 AM, Carlos E. R. wrote:
This works.
However, if I tether via USB cable (which worked some months past, probably using
openSUSE 13.1), it doesn't work.
I just connected my computer to my cell phone via USB. Ifconfig shows:
usb0 Link encap:Ethernet HWaddr FE:2A:6B:B4:59:8F
inet addr:192.168.42.41 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::fc2a:6bff:feb4:598f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:116 errors:0 dropped:0 overruns:0 frame:0
TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28666 (27.9 Kb) TX bytes:44528 (43.4 Kb)
I can ping out, connected only via my cell phone, so it works here. I'm
running 42.2.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
7:30 p.m.
On 05/31/2017 11:07 AM, James Knott wrote:
On 05/31/2017 05:15 AM, Carlos E. R. wrote:
Same here. First: I never do this. With WIFI tethering, why bother
to cable up?
But I plugged in (probably for the first time in years) with usb
to my 42.2 machine an got a USB0 adaptor just like you, and was on
line quick as a flash.
I had to set the phone to allow usb tethering, (it popped up a warning
that it was set to charge only).
I also advise to check the USB cable to make sure you didn't pick up
a charge only cable. (Wired differently).
This isn't an opensuse problem.
--
After all is said and done, more is said than done
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
This works.
However, if I tether via USB cable (which worked some months past, probably using
openSUSE 13.1), it doesn't work.
I just connected my computer to my cell phone via USB. Ifconfig shows:
usb0 Link encap:Ethernet HWaddr FE:2A:6B:B4:59:8F
inet addr:192.168.42.41 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::fc2a:6bff:feb4:598f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:116 errors:0 dropped:0 overruns:0 frame:0
TX packets:174 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28666 (27.9 Kb) TX bytes:44528 (43.4 Kb)
I can ping out, connected only via my cell phone, so it works here. I'm
running 42.2.
7:41 p.m.
On 05/31/2017 02:30 PM, John Andersen wrote:
Same here. First: I never do this. With WIFI
tethering, why bother
to cable up?
WiFi tethering is hard on the battery. There have been a couple of
times I forgot to turn it off and wound up with a dead battery. With
USB, you're actually charging the batteries. Also, with iPhones (work
phone), WiFi tethering is pretty much useless.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
8:33 p.m.
On 05/31/2017 11:41 AM, James Knott wrote:
WiFi tethering is hard on the battery. There have
been a couple of
times I forgot to turn it off and wound up with a dead battery.
This tells me you never actually tried wifi tethering.
Because it shuts down a couple minutes after the last client disconnects.
Its been this way since Andorid 4 dot something.
I know a lot of people with current iPhones that wifi tether.
Maybe ask a any random teenager for some pointers?
--
After all is said and done, more is said than done.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
8:53 p.m.
On 05/31/2017 03:33 PM, John Andersen wrote:
On 05/31/2017 11:41 AM, James Knott wrote:
I have used it several times, most recently at work a few months ago,
when I couldn't tether to my work phone and didn't have a cable with
me. Regardless, WiFi tether requires power on top of the cell
connection and USB charges the battery.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
WiFi tethering is hard on the battery. There
have been a couple of
times I forgot to turn it off and wound up with a dead battery.
This tells me
you never actually tried wifi tethering.
Because it shuts down a couple minutes after the last client disconnects.
Its been this way since Andorid 4 dot something.
I know a lot of people with current iPhones that wifi tether.
Maybe ask a any random teenager for some pointers?
8:59 p.m.
On 05/31/2017 12:53 PM, James Knott wrote:
Regardless, WiFi tether requires power on top of the
cell
connection and USB charges the battery.
At the expense of encumbering your computer (or what ever) with another
corded thing to drag around. I just plug in the phone to its charger,
set it in the windowsill where it gets a great signal, and am free to move
around and have multiple devices connected via wifi.
I use this mostly for running wifi only tablets while riding in the car.
Keeps the grand kids happy.
--
After all is said and done, more is said than done.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
8:57 p.m.
On 05/31/2017 03:33 PM, John Andersen wrote:
I know a lot of people with current iPhones that wifi
tether.
Maybe ask a any random teenager for some pointers?
I even took it to the Apple store and their suggestion was to reset to
factory. Since it wasn't my phone, I declined. Same thing happened
with 2 different phones.
Seems I'm not the only one with that issue:
https://www.google.ca/search?q=iphone+wifi+tether&ie=UTF-8&gws_rd=c…
On the other hand, WiFi tethering on my Android phones has always just
worked.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
1 Jun
1 Jun
4:19 a.m.
31.05.2017 21:41, James Knott пишет:
Also, with iPhones (work
phone), WiFi tethering is pretty much useless.
Could you elaborate? I just used it couple of day ago without any
problems, nor do I remember any issues in the past.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
12:03 p.m.
On 05/31/2017 11:19 PM, Andrei Borzenkov wrote:
31.05.2017 21:41, James Knott пишет:
Very often the computer can't see the SSID to connect to. If you can
connect, it works fine, but more often than not, you can't connect.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Also, with iPhones (work
phone), WiFi tethering is pretty much useless.
Could you elaborate? I just used it couple of day ago without any
problems, nor do I remember any issues in the past.
4:19 p.m.
On June 1, 2017 4:03:51 AM PDT, James Knott <james.knott(a)rogers.com> wrote:
On 05/31/2017 11:19 PM, Andrei Borzenkov wrote:
You get to set the SSID the iPhone will use, and you can also set it to something illegal,
unsuported, or just plain hard to type which may well be your problem.
Once set, connected to and tested, the laptop will remember it and connect instantly.
Of course I wouldn't put it past Apple to have screwed this up on some models perhaps
at the behest of the carriers, and simply walked away from the problem.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
31.05.2017 21:41, James Knott пишет:
Very often the computer can't see the SSID to connect to. If you can
connect, it works fine, but more often than not, you can't connect. Also, with iPhones (work
phone), WiFi tethering is pretty much useless.
Could you elaborate? I just used it couple of day ago without any
problems, nor do I remember any issues in the past.
4:45 p.m.
On 06/01/2017 11:19 AM, John Andersen wrote:
The problem is not setting the SSID. The problem is when trying to
connect to the iPhone, the computer often cannot see the SSID in the
list of available networks. If you can't see it, you can't connect to
it. Even if though I had previously connected to it, I couldn't count
on being able to connect to it later.
And I have no doubt Apple does things "different". I wonder if a Mac
would have the same problem connecting.
BTW, the super secret SSID I used was "JKnott_iPhone".
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
Very often the
computer can't see the SSID to connect to. If you can
>connect, it works fine, but more often than not, you can't connect.
You
get to set the SSID the iPhone will use, and you can also set it to something illegal,
unsuported, or just plain hard to type which may well be your problem.
Once set, connected to and tested, the laptop will remember it and connect instantly.
Of course I wouldn't put it past Apple to have screwed this up on some models perhaps
at the behest of the carriers, and simply walked away from the problem. 
8:12 a.m.
James Knott wrote:
Also, with iPhones (work
phone), WiFi tethering is pretty much useless.
That's not my experience, works perfectly fine here. My wife and my son
both have iPhones, the hotspot is on android.
--
Per Jessen, Zürich (19.8°C)
http://www.dns24.ch/ - your free DNS host, made in Switzerland.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
31 May
31 May
10:09 p.m.
On 2017-05-31 20:30, John Andersen wrote:
Battery and privacy.
Not wanting other devices nearby, that know the password, to connect.
Yes, you say connect to the charger. Means getting out the charger from
the suitcase, and not forgetting to pack it again later.
Yesterday I used WiFi.
On 05/31/2017 11:07 AM, James Knott wrote:
> On 05/31/2017 05:15 AM, Carlos E. R. wrote:
I can ping
out, connected only via my cell phone, so it works here. I'm
running 42.2.
Same here. First: I never do this. With WIFI tethering, why bother
to cable up? But I plugged in (probably for the first time in
years) with usb
to my 42.2 machine an got a USB0 adaptor just like you, and was on
line quick as a flash.
I had to set the phone to allow usb tethering, (it popped up a warning
that it was set to charge only).
I also advise to check the USB cable to make sure you didn't pick up
a charge only cable. (Wired differently).
This isn't an opensuse problem.
Yes, it is, my problem is with Network Manager configuration. I had to
edit the text files, manually. Create a new file.
* Once I did, it worked perfectly. *
Check on connection properties what profile yours is using. Mine used
the default ethernet profile, which is set on "manual" here.
My question is how to tell NM to create a new profile for the USB
connection so that I can edit it.
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
10:13 p.m.
On 05/31/2017 05:09 PM, Carlos E. R. wrote:
Yes, it is, my problem is with Network Manager
configuration. I had to
edit the text files, manually. Create a new file.
* Once I did, it worked perfectly. *
Check on connection properties what profile yours is using. Mine used
the default ethernet profile, which is set on "manual" here.
My question is how to tell NM to create a new profile for the USB
connection so that I can edit it.
I also use the network manager and it works fine. I just plugged it in
and it worked. I've never had to change anything.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
1 Jun
1 Jun
11:15 a.m.
On 2017-05-31 23:13, James Knott wrote:
On 05/31/2017 05:09 PM, Carlos E. R. wrote:
That had been my experience till now, but.
The problem is that, apparently, NM uses the default ethernet profile
for that connection, and currently in my laptop that profile is set to a
fixed IP and GW, which happens to be quite different from what the phone
gives.
You probably have that profile on DHCP.
Thus I had to change the profile.
And I had to do it manually, because NM GUI did not offer to create a
new profile for the USB.
13.1 did offer the profile creation somehow.
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
Yes, it is, my problem is with Network Manager
configuration. I had to
edit the text files, manually. Create a new file.
* Once I did, it worked perfectly. *
Check on connection properties what profile yours is using. Mine used
the default ethernet profile, which is set on "manual" here.
My question is how to tell NM to create a new profile for the USB
connection so that I can edit it.
I also use the network manager and it works fine. I just plugged it in
and it worked. I've never had to change anything.
12:17 p.m.
On 06/01/2017 06:15 AM, Carlos E. R. wrote:
The problem is that, apparently, NM uses the default
ethernet profile
for that connection, and currently in my laptop that profile is set to a
fixed IP and GW, which happens to be quite different from what the phone
gives.
You probably have that profile on DHCP.
Yes, I do. At home I get a "static" IP by configuring the DHCP server
to map the IP address to the MAC.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
12:21 p.m.
On 2017-06-01 13:17, James Knott wrote:
On 06/01/2017 06:15 AM, Carlos E. R. wrote:
Well, that's the difference, mine is set to static.
And the USB takes that profile set to static, and fails because the IP
are wrong.
And NM did not offer to create a new profile for the USB tether. I had
to take an old one with an editor and change its UUID.
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" at Telcontar)
The problem is that, apparently, NM uses the
default ethernet profile
for that connection, and currently in my laptop that profile is set to a
fixed IP and GW, which happens to be quite different from what the phone
gives.
You probably have that profile on DHCP.
Yes, I do. At home I get a "static" IP by configuring the DHCP server
to map the IP address to the MAC.
1:28 p.m.
On 06/01/2017 06:15 AM, Carlos E. R. wrote:
And I had to do it manually, because NM GUI did not
offer to create a
new profile for the USB.
You can still create separate profiles for static and DHCP. Have one be
selected on connection and the other you can start manually.
--
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
6:30 p.m.
On 2017-06-01 14:28, James Knott wrote:
On 06/01/2017 06:15 AM, Carlos E. R. wrote:
Of course, but again: on USB connection it chooses the default profile
for ETH network, not a specific one for USB network.
Click add new network, there is none for USB.
Click Edit connections, the one that I'm actually using:
/etc/NetworkManager/system-connections/Motorola X-Play mobile via USB
is not listed, so I can not edit it!
--
Cheers / Saludos,
Carlos E. R.
(from 42.2 x86_64 "Malachite" (Minas Tirith))
And I had to do it manually, because NM GUI did
not offer to create a
new profile for the USB.
You can still create separate profiles for static and DHCP. Have one be
selected on connection and the other you can start manually.
1333
days inactive
1334
days old
19 comments
6 participants
participants (6)
-
Andrei Borzenkov -
Carlos E. R. -
Carlos E. R. -
James Knott -
John Andersen -
Per Jessen