Connect to wifi, not ethernet?


#1

Hello everyone,

So I got yunohost to work, and it is now connected to ethernet. But I would like to be connected via wifi, is there an easy way to do that?


#2

Can you clarify a bit what’s your setup exactly (are you using a Raspberry Pi for instance ?)


#3

Yes, sorry. I’m using a raspberry pi 3.


#4

Well I don’t have any experience with this but I’m guessing there are tutorial on the internets regarding connecting the RPi to wifi…

I think YunoHost only wants an available internet connection on the machine, it doesn’t really care if it’s using Ethernet or Wifi. So just following carefully a tutorial for connecting the Pi to Wifi should do the trick.


#5

I’ll look around. I modified some config file before, but I didn’t manage to connect to wifi, and since yunohost is headless, it’s hard testing this kind of thing and not lose connection to the pi.

Thanks!


#6

Hi @neokei @CaptainSqrt2 ,

Some informations here : https://www.raspberrypi.org/documentation/configuration/wireless/ and there https://www.digikey.com/en/maker/blogs/raspberry-pi-3-how-to-configure-wi-fi-and-bluetooth/03fcd2a252914350938d8c5471cf3b63

Is wireless not blacklisted here in etc/modprobe.d/fbdev-blacklist.conf ?
http://avignu.wiki.tuxfamily.org/doku.php?id=documentation:yunohost-jessie-v2.5.x-rpi3b#pour_memoire

ppr


#7

Hi, thanks for your help,

the wpa_supplicant method that I tried before doesn’t work unfortunately, so I tried to see if wireless wasn’t blacklisted. Here is the content of the file:

This file blacklists most old-style PCI framebuffer drivers.

blacklist arkfb
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist kyrofb
blacklist matroxfb_base
blacklist mb862xxfb
blacklist neofb
blacklist pm2fb
blacklist pm3fb
blacklist s3fb
blacklist savagefb
blacklist sisfb
blacklist tdfxfb
blacklist tridentfb
blacklist vt8623fb


#8

here’s my result from ifconfig -a

eth0 Link encap:Ethernet HWaddr b8:27:eb:6c:5a:e4
inet addr:192.168.0.33 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::fe89:8feb:b5bb:4fed/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2235 errors:0 dropped:0 overruns:0 frame:0
TX packets:1553 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:535798 (523.2 KiB) TX bytes:221844 (216.6 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:683 errors:0 dropped:0 overruns:0 frame:0
TX packets:683 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:63365 (61.8 KiB) TX bytes:63365 (61.8 KiB)

wlan0 Link encap:Ethernet HWaddr b8:27:eb:39:0f:b1
inet addr:192.168.0.15 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::8602:c7aa:72c4:d87b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:825 errors:0 dropped:0 overruns:0 frame:0
TX packets:209 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:221467 (216.2 KiB) TX bytes:36291 (35.4 KiB)

It says ethernet on wlan0 but the IP is different, and both work (33 and 15). However the wifi doesn’t work.


#9

would still know an answer to this if it’s possible to change from ethernet to wi-fi without too much hassle