MX Linux Forum

On MX 19.1 without systemd use the easytether drivers for debian 9 . Add 'source-directory interfaces.d' to /etc/network/interfaces file. Once phone is plugged into the usb port and usb option is checked on easytether app on your phone you may have to run easytether-usb and dhclient tun-easytether as root to connect. This is what has worked for me. No systemd needed.

Long story, but to try and make it as short as possible. ATT network discontinuing non-whitelisted phones in February. I got different phone, but my usual open source Azilink for tethering not working well with this phone. So trying EasyTether which I used in distant past. It works with windows fine, but in MX 19.3 it says connected after sudo easytether-usb, but sudo dhclient tun-easytether doesnt make it usable. Get network not reachable.

Suggestions? I think part of problem with Azilink is this is non-original and probably poor quality usb cable. Trying to find new higher quality cable that doesnt cost an arm and a leg. Lot fakes apparently. Azilink also doesnt seem to be as tenacious in maintaining its link as EasyTether.

I did finally get easytether working in MX-19. I had experimented just getting it to work in any linux, it does fairly easy in Fedora35 and whatever current version Manjaro. I couldnt get it working in ANY Debian or Debian based distribution.

Found this nice blog on getting it working in Debian, think this guy had Xubuntu. Anyway, he gives three methods. This is several years ago. First was a no go. Second "nmcli" method seemed to work, but still couldnt use the connection. And didnt try the third as it just automated the second. http://www.whatsmykarma.com/blog/?p=656

Cutting to the chase I installed a LXDE spin of Debian10, 32bit version I had laying around for other reasons. It uses Wicd by default as its network manager. Just try finding and installing manually a 32bit version openvpn and adb needed by Azilink.... LOL Figured mess with something different. Odd, always thought of Wicd as for wifi only but it lets one define line connections and use those too... So combining info in that blog namely setting IP to 192.168.117.2, Wicd filled in rest and then had to set the option to "use global DNS servers", meaning manually create a resolv.conf file and specify a nameserver like "nameserver 1.1.1.1" or "nameserver 8.8.8.8" Or whatever your cell company offers. Debian10 must have Wicd set to start immediately. Frankly I boot up and bingo I have connection.

So got to wondering in MX-19. I had connection via Azilink so used that to install Wicd. Fine, set it up like in Debian. It tries but nothing. Apparently network-manager or parts there of that default in MX blocked it. So "sudo apt purge network-manager". Reboot and little tinkering with Wicd and bingo, I am connected via Easytether. Now on MX since this is add on, each and every time, I have to manually in terminal "sudo easytether-usb" then once it gives tun-easytether, then bring up Wicd and click connect. Bingo. Oh if it says something is used by another process, unplug your phone, type "sudo killall adb", plug in phone, then run "sudo easytether-usb" again.

Now I am sure there is some setting that would let original default network-manager bits use the tun-easytether interface, but I am not smart enough to figure it out and all the Ubuntu stuff doesnt work. But yea, you want Easytether to work in MX, you can do it with Wicd.

Honestly Azilink is easier to set up, though lot steps to it. I am so used to using it that its second hand to me anymore, but that first time setting it up, it did seem like lot piecemeal steps. I made a script to automate all the steps. Oh by way after "sudo apt purge network-manager", it purged something that Azilink via openvpn uses to tether. So watch out on using purge command, it can remove more than you intend. I uninstalled openvpn and reinstalled it, no difference, so its not in openvpn itself, its some bit of networking that wasnt part of network-manager itself I think as I have both Easytether and Azilink working in Fedora35 and it uses NetworkManager.

Yea long post, but some of us out here in rural areas without ethernet or wifi and cell phone company wants to play games with tethering, blocking native Android app on phone unless they get more money. Apps like Easytether and Azilink that do an end run of such blocking are life savers. Azilink by way is open source, alas now deprecated though still works. It was originally intended for early Android phones that had no native tethering app. Last mention I found of Azilink online is post like ten years ago, well other than couple I have made. It will work in MAC and windows too, any system that offers some version openvpn and adb. There is an Android Azilink app you install on phone (sideload it, not in any Android store), but on computer is just an openvpn script that tells openvpn how to connect and communicate with the phone app.

So up to you, frankly unless your Debian based distribution comes with Wicd (or you are smarter than me to make it work with default network manager stuff) then honestly its going to be just as easy to use Azilink.

Learned that wicd is deprecated as of MX-21 along with its python2 dependency, meaning no more wicd for you. So been reading more about networking. Seems wicd is fancy frontend for ifup/ifdown combined with configuration app.. Ceni is just a configuration helper to create the necessary files to use ifup/ifdown. You still have to use ifup/ifdown via CLI. Great, seems nobody ever bothers to state the obvious. Once I had files set up for tun-easytether, then had wicd open but disconnected. Typed "sudo ifup -a" and wicd at bottom of its little window said CONNECTED. And I was connected. Tun-easytether only thing in /etc/network/interfaces. the -a option just tells ifup to use first live interface marked auto.

But at least seems I now know how to use ifup/ifdown if I have to go to system newer than MX-19/Debian10. Oh I am sure there is a way to make network-manager play nice with easytether since it works in Fedora and Manjaro. But I hope never to have to joust with that monstrosity ever again. I tried connman too, but seriously its kinda best buddies with network-manager, obfuscate, obfuscate, obfuscate. I will mourn the passing of wicd, wicd+easytether was match made in heaven. But not anymore complicated to manually create necessary files to use ifup/ifdown with Easytether than it is setting up Azilink. Once you figure it out, then it just becomes second nature. And can make script to avoid typing if one wants. Just click a desktop shortcut.

Alrighty finally tried it. Booted from the MX-21 demo dvd. No updates, no installs, no nothing. Phone with easytether app installed and debugging engaged.

First installed the easytether "deb" downloaded from mobile stream, its the one for Debian 10, they dont show one for Debian 11.

Installs, all dependencies met without installing anything extra. Now root thunar go to /etc/network/interfaces Nuke all content on this file. Replace with:

auto lo
iface lo inet loopback


auto tun-easytether
iface tun-easytether inet static
address 192.168.117.2
broadcast 192.168.117.255
gateway 192.168.117.1
netmask 255.255.255.0

Now create /etc/resolv.conf file Put nameserver 8.8.8.8 or whatever nameserver you want to use. has to be both word "nameserver" and the numerical address. Save.


Now open terminal. Type sudo easytether-usb It will tell you to ok it on your phone, there will be a popup. Ok then it will say root privileges fade to back ground. This creates interface tun-easytether.

Now type sudo ifup tun-easytether You are connected.

This is the super simple work around for tethering with Easytether when network-manager is uncooperative. Seems network-manager ignores any interface defined in /etc/network/interfaces. And doesnt block ifup using it. And you want only the above lines there, cause ifup doesnt always ignore commented out lines and can cause problems. You can of course define other interfaces there. Cant say if they will work with network-manager installed. It seems set to ignore IPtunnel interfaces. Maybe not wifi or ethernet....

So I have tried this on variety linux distributions. My copy antiX is old and it wont work on it. Also havent gotten it to work on any Puppy Linux, even FossaPup 9.5. They will install the easytether software but when run end at easytether: undefined. So something missing or in unexpected place.

It will work on newer Debian Dogs, a derivation of Puppy, but more Debian-like structure. The version I had it working on is Sparky-Bonsai. If it wont work in current AntiX then suggest either Sparky-Bonsai or BodhiLinux for small install that can use it.

Now eventually I will figure how to make Easytether work with Network Manager since it does so in Fedora35 and current release Manjaro. Manjaro is also especially friendly to Azilink as it comes with both openvpn and adb installed. Therefore you arent struggling to get them and their dependencies installed manually.

Oh also found out apparently wicd is being updated to work with python3 and GTK3. But seriously as simple as it is to paste the above content into /etc/network/interfaces, not sure there is a point to wicd or ceni, least as far as Easytether is concerned. If I was doing wifi connections without network-manager then wicd would be a good thing possibly. You would have to nuke network-manager to use wicd, least I couldnt get wicd to work in MX-19 until I nuked network-manager.

Hmmm. I am rural AF, and have never had problems tethering off my burner flip-fone. Is this an Android problem or a Linux problem?

genericmeatsack wrote: Thu Apr 07, 2022 6:29 pm Hmmm. I am rural AF, and have never had problems tethering off my burner flip-fone. Is this an Android problem or a Linux problem?

This is TIPS AND TRICKS, not a request for help. Its an EASYTETHER problem, not a native Android tethering problem, read the title of the thread. I am very happy you have no problems usb tethering your burner phone on whatever service you are using. But it has nothing to do with Easytether or at least you dont mention using Easytether. Pretending everybody has same situation as yourself well is probably inaccurate.

I am using MVNO called Red Pocket on ATT network. Red Pocket has no problem with tethering, they dont offer technical support it but they say upfront that if you can figure it out, more power to you. I am however using an ex-ATT phone (used and cheap) thanks to the mandatory VoLTE thing (ATT whitelisted phones ONLY) as of February, so it still has the ATT proprietary software. Try to use the built in Android tethering app and it will tell you to call ATT, even though I am not an ATT customer. The tethering app and the hotspot apps are LOCKED BY DEFAULT. ATT customers are told they need to pay more money to tether. It was a scam by ATT for direct ATT customers.

So I have to use a tunneling app that requires developer mode on phone and debugging activated. I have both Easytether and the venerable Azilink. Azilink is easy, you just need computer with both adb and openvpn installed. Though getting these installed without an alternative connection not easy. Easytether is easy if you are using windows, and was pretty easy with Manjaro and Fedora 35. Its truly painful with any Debian system using network manager. Thus my posting my work around on how to make it work. Ifup is great workaround that makes it easy. NetworkManager sucks IMHO, least far as Easytether goes. Your mileage may vary.

Again I am not asking for help, wrong place to post request for help in Tips and Tricks. I am offering my experience in hope it might help somebody else needing to use Easytether. This isnt a native tethering thing, this is about HOW TO GET EASYTETHER WORKING IN MX. Ok?

Flumoxxed wrote: Thu Apr 07, 2022 2:34 pm Alrighty finally tried it. Booted from the MX-21 demo dvd. No updates, no installs, no nothing. Phone with easytether app installed and debugging engaged.

TYFT