15

I just installed a clean image of the latest Raspbian Stretch Lite.

Specifically - 2017-09-07-raspbian-stretch-lite.img

ifconfig shows that my wifi interface wlan0 is detected and up.

eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether b8:27:eb:c6:dc:d4  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 2516  bytes 144456 (141.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2516  bytes 144456 (141.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.165  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::d4dd:c202:d337:c0de  prefixlen 64  scopeid 0x20<link>
        ether 00:24:a5:36:ed:49  txqueuelen 1000  (Ethernet)
        RX packets 49461  bytes 49499638 (47.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36499  bytes 4455517 (4.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

However, trying to use the ifdown or ifup commands says that the device does not exist. 

[pi:~] sudo ifdown wlan0
ifdown: unknown interface wlan0

Perhaps, ifup and ifdown will only work if /etc/network/interfaces is used to manage the networking devices, and that is apparently not the case in the raspbian stretch lite version dated 2017-09-07

saraf
  • 571
  • 1
  • 5
  • 12

2 Answers2

24

What does work instead of 

sudo ifup wlan0
sudo ifdown wlan0

is

sudo ifconfig wlan0 up
sudo ifconfig wlan0 down
saraf
  • 571
  • 1
  • 5
  • 12
1

I had a similar problem after installing PiHole. I found this site to be helpful. https://raspberry-projects.com/pi/programming-in-c/tcpip/configuring-network-adaptors

In my case, I had tried to change the PiHole static IP after instalation and I had two IPs in the /etc/dhcpcd.conf file. Once I corrected the error my Pi is working on the wired connection again.

OnePuttMike
  • 11
  • 1