All run correctly, on IPv4 and IPv6!

Thanks @all, but specially @HoaS

No, it's not all things!
But others lines concern iface lo and eth0. Do you want really?!

The file start with this line:

source /etc/network/interfaces.d/*

(…)
allow-hotplug wlx00e0250d7ef2
iface wlx00e0250d7ef2 inet dhcp
#	wpa-driver wext
#	wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf	
	wpa-ssid SH
	wpa-psk ***xyz***

well when someone tells me a story i dont want to hear just the end of it !

The file start with this line:

source /etc/network/interfaces.d/*

(…)
allow-hotplug wlx00e0250d7ef2
iface wlx00e0250d7ef2 inet dhcp
#	wpa-driver wext
#	wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf	
	wpa-ssid SH
	wpa-psk ***xyz***

i dont believe you need the wpa-ssid and wpa-psk in /etc/wpa_supplicant/wpa_supplicant.conf if you already have them in /etc/network/interfaces ?

see head on a sticks comment from another thread on wpagui wpa_supplicant.

http://dev1galaxy.org/viewtopic.php?pid=26890#p26890

$ cat /etc/wpa_supplicant/wpa_supplicant.conf 
ctrl_interface=/run/wpa_supplicant
update_config=1

network={
	id_str="sh"
	ssid="SH"
	psk=***xyz***
}

/etc/network/interfaces:

allow-hotplug wlx00e0250d7ef2
iface wlx00e0250d7ef2 inet dhcp
#	wpa-driver wext
#	wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf	
	wpa-ssid SH
	wpa-psk ***xyz***

as ralph mentions you should read the manual for wpa_supplicant

OK, before yours replies, I set the wpa_supplicant file config.
(today, I installed too connman; wicd seems not available - it's not the problem).

When I plug the dongle USB, it receives one adress IP, but not the gateway's one.
(but, my Android smartphone receive correctly the datas, and can connect on the Internet, for instance)

It seems when I connect with the dongle USB, it not receives or configure the default route:

$ ip route
192.168.xyz.0/24 dev wlx00e0250d7ef2 proto kernel scope link src 192.168.xyz.144 

When I use the ethernet wired:

$ ip route
default via 192.168.abc.1 dev eth0 
192.168.abc.0/24 dev eth0 proto kernel scope link src 192.168.abc.47 
192.168.abc.1 dev eth0 scope link 
192.168.xyz.0/24 dev wlx00e0250d7ef2 proto kernel scope link src 192.168.xyz.144 

One idea?

Why is it so so complicated?

Because wpa_supplicant is generally used as a back-end for more "user-friendly" networking solutions such as NetworkManager, connman & wicd.

You can try wpagui but that will still need a basic configuration file that declares the control interface file and allows the configuration to be changed. Also note that the wpa_supplicant package does not configure the routing table (so you will need to either do that manually or run a separate DHCP client) and it does not supply a sysvinit script (so you will have to create one yourself if you want to run it without a front end).

There is iwd, which is a more modern alternative to wpa_supplicant that also has a command line interface (iwctl) but doesn't require you to create a configuration file beforehand, but that also doesn't supply a sysvinit script. It does include DHCP functionality and it has fewer dependencies than wpa_supplicant.

But I would recommend ifupdown instead: https://wiki.debian.org/WiFi/HowToUse#W … d_WPA2-PSK

$ apt policy eudev
eudev:
  Installé : 3.2.9-8
  Candidat : 3.2.9-8
 Table de version :
 *** 3.2.9-8 500
        500 http://deb.devuan.org/merged ceres/main amd64 Packages
        100 /var/lib/dpkg/status

Why is it so so complicated?

https://raspberrypi.stackexchange.com/q … t-wlan0-re

This is also mentioned in the ArchWiki:

https://wiki.archlinux.org/index.php/Wp … th_wpa_cli

And I'm curious as to why your interface is using the predictable nomenclature — are you using eudev?

apt policy eudev

I bought few days ago a usb dongle, recognized by lsusb as:

Bus 001 Device 003: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter

On dmesg:

[  878.416457] usb 1-1.4: reset high-speed USB device number 3 using ehci-pci
[  878.531504] mt7601u 1-1.4:1.0: ASIC revision: 76010001 MAC revision: 76010500
[  878.551495] mt7601u 1-1.4:1.0: firmware: direct-loading firmware mt7601u.bin
[  878.551504] mt7601u 1-1.4:1.0: Firmware Version: 0.1.00 Build: 7640 Build time: 201302052146____
[  878.956971] mt7601u 1-1.4:1.0: EEPROM ver:0d fae:00
[  879.183994] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[  879.184474] usbcore: registered new interface driver mt7601u
(…)
[  879.258512] mt7601u 1-1.4:1.0 wlx00e0250d7ef2: renamed from wlan0

lsmod:

$ lsmod | grep mt
mt7601u               135168  0
mac80211              983040  1 mt7601u
cfg80211              974848  2 mt7601u,mac80211
usbcore               323584  6 xhci_hcd,ehci_pci,usbhid,mt7601u,ehci_hcd,xhci_pci

module seems loaded!

ip address:

3: wlx00e0250d7ef2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:e0:25:0d:7e:f2 brd ff:ff:ff:ff:ff:ff

iw show the hardware:

$ sudo iw dev wlx00e0250d7ef2 info
Interface wlx00e0250d7ef2
	ifindex 3
	wdev 0x1
	addr 00:e0:25:0d:7e:f2
	type managed
	wiphy 0
	txpower 0.00 dBm

rfkill show no block:

$ sudo rfkill list
0: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

I installed wpa_supplicant, wpa_gui… but it's not appear!

$ sudo wpa_cli -i wlx00e0250d7ef2
wpa_cli v2.9
Copyright (c) 2004-2019, Jouni Malinen <j@w1.fi> and contributors

This software may be distributed under the terms of the BSD license.
See README for more details.

Interactive mode

Could not connect to wpa_supplicant: wlx00e0250d7ef2 - re-trying
^C

How can I use this USB hardware?