hello
I have quite (to me) unexplained behavior in a wifi interface I defined
in /etc/network/interfaces config file.
I turned off NetworkManager
root@:~ # systemctl stop NetworkManager.service
root@:~ # systemctl disable NetworkManager
The /etc/network/interface file content
auto lo enp0s25
iface lo inet loopback
iface enp0s25 inet static
address 192.168.1.243
netmask 255.255.255.0
gateway 192.168.1.254
auto wlp3s0
iface wlp3s0 inet static
address 172.16.1.243
netmask 255.255.255.0
network 172.16.1.0
broadcast 172.16.1.255
gateway 172.16.1.1
wpa-essid essidname
wpa-psk abcdef0123456789a....
The /etc/wpa_supplicant.conf file content
network={
ssid="essidname"
#psk="pass"
psk=abcdef0123456789a...
}
After a smooth reboot my configuration looks like this:
root@:~ # ifconfig
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.243 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::221:ccff:c0a8:1f3 prefixlen 64 scopeid 0x20<link>
ether 00:21:cc:c3:ad:a8 txqueuelen 1000 (Ethernet)
RX packets 1460 bytes 361401 (352.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1264 bytes 158144 (154.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xf1500000-f1520000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 3416 bytes 284799 (278.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3416 bytes 284799 (278.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
if I add -a
root# ~ ifconfig -a
I get the same plus the wlp3s0 interface, which is disabled
wlp3s0: flags=4098<BROADCAST,MULTICAST> mtu 1500
inet 172.16.1.243 netmask 255.255.255.0 broadcast 172.16.1.255
ether 8c:70:5a:bb:2a:0c txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
A simple ping test with bad results
root@:~ # ping -c2 -W3 172.16.1.1
PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
--- 172.16.1.1 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1001ms
Just in case, I try to manually start the interface wlp3s0 which will
obviously fail
root@:~ # ifup wlp3s0
RTNETLINK answers: File exists
ifup: failed to bring up wlp3s0
the same in verobose mode will be
root@:~ # ifup -v wlp3s0
ifup: configuring interface wlp3s0=wlp3s0 (inet)
/bin/run-parts --exit-on-error --verbose /etc/network/if-pre-up.d
run-parts: executing /etc/network/if-pre-up.d/bridge
run-parts: executing /etc/network/if-pre-up.d/wireless-tools
run-parts: executing /etc/network/if-pre-up.d/wpasupplicant
wpa_supplicant: wpa-driver nl80211,wext (default)
wpa_supplicant: /sbin/wpa_supplicant -s -B -P
/run/wpa_supplicant.wlp3s0.pid -i wlp3s0 -D nl80211,wext -C
/run/wpa_supplicant
Starting /sbin/wpa_supplicant...
wpa_supplicant: creating sendsigs omission pidfile:
/run/sendsigs.omit.d/wpasupplicant.wpa_supplicant.wlp3s0.pid
wpa_supplicant: ctrl_interface socket located at
/run/wpa_supplicant/wlp3s0
wpa_supplicant: configuring network block -- 0
wpa_supplicant: wpa-ssid "essidname" -- OK
wpa_supplicant: wpa-psk ***** -- OK
wpa_supplicant: enabling network block 0 -- OK
/bin/ip addr add 172.16.1.243/255.255.255.0 broadcast 172.16.1.255
dev wlp3s0 label wlp3s0
RTNETLINK answers: File exists <---------------
ifup: failed to bring up wlp3s0 <---------------
The strange behavior is that after running the failed `ifup` then the
interface starts to work correctly!
I'm pretty convinced i'is a misconfiguration in my files.
I will apprecaite any help
