When I connect my smartphone in tethering to openSUSE Leap 15.1 a new connection is automatically created, the name is “Wired connection 1”.
When I disconnect smartphone connection is automatically deleted.
At work I need a “Wired ethernet” connection too but after creating this connection tethering don’t works anymore because “Wired connection 1” isn’t created when I connect smartphone.
Your description isn’t clear whether you’re still talking about the same machine.
If so,
Perhaps disconnect your machine from you company LAN before attaching your smartphone?
TSU
If your work computer is using NetworkManager, then it is likely using “Wired connection 1” for ethernet connection. But I would expect it to then create “Wired connection 2” for your smart phone.
But maybe your work computer is using “wicked” rather than “NetworkManager”.
My smartphone connects as a wifi device and works fine.
Are you using a USB connection to the smartphone with pdanet+ software? It worked with windows but I have yet to work with opensuse.
Yes, it’s my laptop that I use at home and at work.
If so,
Perhaps disconnect your machine from you company LAN before attaching your smartphone?
Whether connected or not after creating “Wired connection” tethering don’t works.
Sorry I forgot to write I’m sing KDE then Network Manager
.
… then it is likely using “Wired connection 1” for ethernet connection. But I would expect it to then create “Wired connection 2” for your smart phone…
In my pc tethering is automatically named “Wired connection 1”, “ethernet connection” has the name I give when I create connection.
My smartphone too works using wifi but I’d like to use in tethering
Are you using a USB connection to the smartphone
of course, tethering means smartphone connected to pc using usb cable
… with pdanet+ software?
I don’t know “pdanet”
Most Android phone cannot act like an ethernet gateway when a USB cable is attached - pdanet+ adds “ethernet” support to Android phone when the vendor disables USB and/or wifi tethering.
It (pdanet+) works great with Windows but not with Opensuse Linux ( some folks claim it works with this or that version of Linux but I have yet to see it work in Linux )
If your phone is Android and the vendor allows USB tethering Linux will find a new network option with a name like “auto usb0” (and not ethernet on my Galaxy SIII.) My newest phone does not allow USB tethering even with pdanet+ but does work fine wi-fi.
Iphone - I have no idea on them.
May be I’ve not been clear.
My smartphone is an Android (Huawei) and works well in tethering in openSUSE. But if I made an ethernet connection thethering don’t works. If I delete ethernet connection tethering works again.
In same laptop I have other Linux distribution and tethering works, also if I have ethernet connection.
Can you use the NetworkManager connection editor to manually create a working connection? I do that for my various defined ethernet and wifi connections.
I use Network Manager to create ethernet connection with manual IP. But as soon as ehternet connection is created tethering don’t works, as described in first message.
I do that for my various defined ethernet and wifi connections.
I use it to create several kind of connection excluding tethering. Tethering connection is (or should be) created automatically when insert usb cable and activate usb tethering in phone.
Ok, thanks for the additional clarification. If I understand you better now, you’re trying to use tethering at the same time you use the work-based ethernet connection? If so, capture the following information when that situation exists…
ip a
ip r
nmcli c
nmcli d
I haven’t “tethered” an Android for a long time, but AFAIK nothing has changed since the “old days” although it might be more reliable now than in years past.
First,
An overall understanding of what happens…
Android devices generally cannot operate as a modem for another device, rather the Android device makes its own connection over the carrier connection, then proxies the connection to the attached device.
The connection from the phone to the attached device over a USB connection is a fairly common USB serial connection.
Once you understand the above,
You should understand that the network connection is not managed from the attached device, so things like Network Manager are not typically relevant.
Typically the connection from the Android device to the attached device is accomplished by using an Android Tools utility called “adb” (Android Device Bridge).
It should be noted that over the years, the adb connection has been notoriously unreliable, sometimes working and sometimes not.
In fact, I personally avoid Android tethering nowadays by instead setting up an Android Device HotSpot… It’s been a standard feature of Android for many versions now… Maybe the last 3+ years. I’d highly recommend that anyone look for this feature and if it’s available to set that up instead… It’s reliable and always works. You simply enable the HotSpot feature, note the WiFi password and then configure that WiFi connection in NM (or other WiFi management).
If instead you really want to tether…
You’ll have to explain better how your tethering is set up, whether you’re using a feature built into Android or using a 3rd party application or setting up the connection manually.
TSU
Why would you expect that tethering and an active ethernet connection should work at the same time?
Although I supposed a DeviceID associated with the network connection can help, you’d have 2 default gateways to the Internet (or other networking) configured at the same time, breaking a cardinal rule of networking (Although you can have multiple routes, there should only be one Default Gateway).
TSU
Remembered something you always need to check…
When an Android device is detected,
It has to be recognized by the OS as either a communications or a storage device… You can’t have it both ways.
So, for instance if you recently read or transferred files from your Android, it would be recognized as a storage device… and until your Android is re-configured, you won’t be able to use it as a networking(communications) device.
TSU
My english isn’t so good but I try to explain.
configuration n° 1 - No ethernet connection created in Network Manager.
configuration n° 2 -** One “Wired ethernet” connection is created** (manual, static IP) in Network Manager.
If I delete “Wired ethernet” thethering works immediately. Then it seems that “Wired ethernet” connection (whether connected or not) avoid automatic creation of “Wired connection 1” used by tethering.
Why I don’t use wifi? Because I use my pc and smartphone in a high school where I teach and having wifi on during several hours is risky, my password can be decrypted.
This sounds very much like when you are connected to your LAN, your machine is configured with a Default Gateway specifying your LAN.
You can confirm by running the “traceroute” command to an Internet address, your machine will likely ping your LAN DG, then either fail or continue to ping each router to the Internet address.
Solution:
Configure your LAN connection without a Default Gateway.
This means disabling your connection as a DHCP client and configuring with a static address but leaving the DG empty.
Assuming your machine has a DG set for your Android device, you should then be using your Android to connect to the Internet.
And a reminder, an Android isn’t likely ever a modem device, and you should understand what this means to be able to troubleshoot and understand how your networking works.
To prevent others from hacking your device when connected using WiFi…
TSU
I my ethernet connection I’ve no gateway.
This means disabling your connection as a DHCP client and configuring with a static address
This is what i did, as I wrote in the message you quoted.
And a reminder, an Android isn’t likely ever a modem device, and you should understand what this means to be able to troubleshoot and understand how your networking works.
In other Linux distributions using tethering is very easy and don’t need any troubleshooting.
To prevent others from hacking your device when connected using WiFi…
- Most Access Points can restrict devices from discovering and connecting to other WiFi clients. Inspect your AP configuration
- Connect to your WiFi only as long as necessary.
Too time consuming, sometime I need internet twice per hour, sometime 10 per hour or one hour continuously. I need simply connection always ready.
Even if you had extremely easy encryption to crack, unless the hacker is fully automated and <very> lucky, It would take at least 10 minutes to hack a connection, ie typically by inserting as a MiM attack and that is under the most optimally favorable circumstances with some foreknowledge. Under normal circumstances, I highly doubt that your device would be hackable within a workday unless you’re dealing with really talented hackers.
I teach in a high school specialized in Information Technology then no problem to find talented hackers …
- If any of your students can even get halfway through hacking a WPA2 connection, they should contact your government’s crypto-security. They’re looking for people who have a talent for that kind of stuff…
Interesting but I’m a teacher not a head hunter for government agency
Please help me simply to use tethering that’s really simple and straightforward as it is in other Linux distribution.
So did you run traceroute as I described?
That was essential or at least recommended prior to configuring without an ethernet DG to identify the problem to be fixed.
Also,
I think you missed the point about my brief description of the general steps to hacking a WiFi connection, and actually doing something concrete (ie hijacking the network session). It’s very difficult to hack WPA2, there are numerous prerequisites including knowledge, tools, time, computing power and an enormous amount of luck. Bottom line, it would require practically a professional hacker to even have a chance of success, and might have to work at it for more than a year for even a single possible success.
Then,
I tried to impress on you that your preferred alternative to connect using a phone carrier is actually far less secure. Hacking carrier signals is not only relatively quite easy(well, subject to some details like filtering traffic if very busy), it also requires very cheap hardware, but this is why there are usually very heavy penalties for doing this kind of thing. But, if you’re truly concerned about secure Internet access, this is a poor choice unless you do the additional things I recommended.
TSU
I use ethernet at work only, then I’ve to wait till monday.
Also,
I think you missed the point about my brief description of the general steps to hacking a WiFi connection, and actually doing something concrete (ie hijacking the network session). It’s very difficult to hack WPA2, there are numerous prerequisites including knowledge, tools, time, computing power and an enormous amount of luck. Bottom line, it would require practically a professional hacker to even have a chance of success, and might have to work at it for more than a year for even a single possible success.
A colleague has been already hacked, and anyway I would prefer use tethering that’s very easy in many Linux distribution. In my opinion this is a openSUSE bug.
