Page 4 of 4

Re: WiFi Not Working

PostPosted: Sat Aug 19, 2017 12:51 am
by NevilleGoddard
By the way I would make a whole new install media before trying a fresh install and do a md5 check on your GhostBSD ISO image just to make sure it's OK.

Re: WiFi Not Working

PostPosted: Tue Aug 22, 2017 6:58 am
by wb7odyfred
Run wpa_supplicant(8) to associate to an access point defined in /etc/wpa_supplicant.conf.
Code: Select all
wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf

Line 3 from Command Line Manual Method section of

After suspend resume, you might have to manually run "wpa_supplicant" command to associate to an access point.

I was having trouble associating with my T-mobile phones Wi-Fi hotspot that was using WPA2 and forgot about using the wpa_supplicant command.

You might try

Code: Select all
service netif restart
service   routing    restart

Please comment if these solutions, do solve your wifi connection problem.

Re: WiFi Not Working. Use WPA_Supplicant command

PostPosted: Tue Aug 22, 2017 7:19 am
by wb7odyfred Does a good job of explaining the steps to get wifi working in GhostBSD. Creating the Passkey step 6.

Code: Select all
service netif restart
service routing restart

from Google Groups mailing lists messages;!topic/bsdmailinglist/ziNiU-m5AAg

I'm able to config the route via "service routing restart" - or manually as I did
otherwise. But I recall that I did a simple "service netif restart" in 11-CURRENT
recently and that worked.

Has there been a change? What is now the official way to restart network?

Kind regards,

The knowledge of the fact that I also have to restart routing via a
script is sufficient for me - also the fact to know that netif restart
doesn't restart routing.

Oliver Hartmann

As far as I am aware, this has always been this way, at least with
FreeBSD 6.0 and later. When you delete the interfaces, the route goes
away, then you recreate the interfaces but not the routes.

Allan Jude

Re: WiFi Not Working

PostPosted: Tue Aug 22, 2017 9:42 am
by ASX
I can't think of any reason why restarting netif should not restart routing too. :(
Must be one of those FreeBSD "peculiarities".