Getting wifi to work on FreeBSD is nearly impossible.

Fred Finster, [2/11/22 11:39 AM]
Here is detailed step by step manual setup of wifi. https://t.me/ghostbsd/94284 , refers to https://forums.ghostbsd.org URL links, near the bottom of this post.

are you using networkmgr? Ghostbsd, Left or right Click on the little WIFI icon in the upper left corner.
3 files are edited by networkmgr /boot/loader.conf /etc/rc.conf /etc/wpa_supplicant.conf wpa_supplicant.conf is where you edit in your password. The networkmgr saves the password and wifi ssid in the file /etc/wpa_Supplicant.conf.

If your internal wifi does not work, buy a cheap USB wifi dongle Edimax EW-7811un v1. V2 might work now on ghostbsd. Or TpLink TL-WN725N . Dont buy TL- WN823N rtl8188eu or ee cant remember That device driver for that chip, has a problem in the chipset_power_down() function inside the rtwn device driver. It uses a 2 step sequence, and other WORKING drivers use a 3 step sequence.

uname -a
kldstat
kldload ir_rtwn.ko if_rtwn_usb.ko if_rtwn_pci.ko # select usb or pci to match your Realtek device interface
pciconf -lv
usbconfig list
usbconfig ugenx.y dump_device_desc where you change x.y to 0.2 or 1.4 that matches your usb wifi device
sysctl net.wlan.dev

https://forums.freebsd.org/threads/edimax-ew-7811utc-how-do-i-connect-to-the-wifi.67485/post-542747

https://forums.ghostbsd.org/viewtopic.php?p=8143#p8143

https://forums.ghostbsd.org/viewtopic.php?f=64&t=526 nano usb wifi dongle, Edimax EW-7811un Version 1 , Version 2?? The USB product ID has to be updated in the FreeBSD wifi driver if_rtwn_usb.ko

https://forums.ghostbsd.org/viewtopic.php?f=64&t=570 RealTek RTL8188CE Wii-Fi PCI network hardware manual setup, a good reference post.

Wish you successful BSD computing with your chosen wifi device.

https://www.freshports.org/net-mgmt/networkmgr/
Wish you successful BSD computing with your chosen wifi device.

NetworkMgr is an open source, Network Manager based on the look of the Linux
Network Manager user interface. It use ifconfig and netif if make all work.

WWW: https://github.com/GhostBSD/networkmgr
 
I know this is late, but I just got on this forum. I also am somewhat new to FreeBSD, and would like to get it up and running on a box, and then configure it to my needs/liking. One thing I have learned in reading about it, is that FreeBSD is a network OS. So I guess wifi is more of an after thought only because more and more people are trying to use it as a daily driver. I have tried installing FreeBSD (various versions) on one of my machines, with little luck. What I found by accident is NomadBSD. It was able to install and my wifi card (Intel 7265) and it worked correctly. So I had to kind of work backwards, by installing NomadBSD, then looking at the config files, and copying some of them, etc. to be able to "fix" a plain FreeBSD install. You might try that, but since the hardware is so old, you might not luck out. If Broadcom or any other manufacturer doesn't publish the specs on their products, it's difficult to write drivers for those products. Even if they do publish the data, the good folks at FreeBSD cannot always get to it, because a certain company in Washington and another copy in California like to keep new hardware flowing out of China to keep good operating systems such as FreeBSD down. I'm not a programmer, but I have read that writing device drivers is pretty difficult. Just because Linux or some other OS has a driver for a particular device, doesn't mean FreeBSD or OpenBSD or anything else will have one. I am discovering that FreeBSD requires a lot of research to just get things going, and I'm reading Absolute FreeBSD 3rd Edition. Still lost though. I don't have a lot of time to be learning/fiddling with FreeBSD either, but for some reason, I keep trying. GhostBSD may also help you with some of those devices in your machine.
gentisle
 
Well, I didn't find it particularly difficult to install wifi - it somehow happened during basic installation without me caring about it, and afterwards, at every reboot, it just worked. (I notice it because DHCP sends a wrong DNS IP - so I know it works because I can notice that it does not work after receiving the new DHCP ;) ).
The problem is rather that it crashes after some 50 - 5000 MB of data, and requires a reboot.
 
iwlwifi. Something along the line of "program error in firmware code". I didn't look at it closely yet.
 
You must log in or register to reply here.
Back
Top