Sponsored Content
Operating Systems BSD FreeBSD DHCP wpa_supplicant Wi-Fi Issues Post 302949535 by BrentBANKS on Monday 13th of July 2015 01:31:01 AM
Old 07-13-2015
FreeBSD DHCP wpa_supplicant Wi-Fi Issues

I just got FreeBSD up and running with an XFCE desktop on an old Gateway laptop. It works great, except the wireless setup is scaring me. I can connect to my home WiFi fine most of the time, but I'm concerned about other WiFi that I will need to connect to away from home.
I understand that I can use wpa_supplicant to determine what WiFi signal to connect to. But when I enable wpa_supplicant in my rc.conf file I get this message and no network connection.

Code:
wlan0: Ethernet address: xx:xx:xx:xx:xx:xx
starting wpa_supplicant.
starting dhclient.
wlan0: no link ...................... giving up
etc/rc.d/dhclient: WARNING: failed to start dhclient

/boot/loader.conf
Code:
if_bwi_loads="YES"
kern.vty=vt

/etc/rc.conf
Code:
hostname="name"
sshd_enable="YES"
# Set dumpdev to "AUTO" to enable crash dumps, "NO"to disable"
dumpdev="AUTO"

wpa_supplicant_enable="YES"

wlans_bwi0="wlan0"
ifconfig_wlan0="WPA SYNCDHCP"

hald_enable="YES"
dbus_enable="YES"

/etc/wpa_supplicant.conf
Code:
network={
     ssid="myID"
}

When I run 'ifconfig', under bwi0 and wlan0, it shows a status of no carrier.

Although, If I use this in my rc.conf instead.
Code:
ifconfig_wlan0="SYNCDHCP"

dhclient will give me this on startup
Code:
wlan0: ....link state change to UP
got link
bwiwi: need multicast multicast update callback

dhclient will usually go ahead and connect with my home WiFi and give me an IP address.

If anybody can help, I would greatly appreciate it! I've been working for hours straight and I am stumped.Smilie

Last edited by BrentBANKS; 07-13-2015 at 10:43 AM..
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

FreeBSD 4.7 X issues - assistance req'd please

question: i just installed FreeBSD 4.7 on my laptop, when i log in as root, i can startx no problem at all but when i try to start it as a user, i can't. otiginally it told me i needed to be a member of the group 'wheel' to do startx, no problem, added myself in /etc/group, but for some reason i... (1 Reply)
Discussion started by: Calum
1 Replies

2. UNIX for Advanced & Expert Users

snort installation on freebsd issues

i'm following the, "How to setup and secure Snort, MySQL and Acid on FreeBSD 4.6 Release" off of the snort.org website. in the documentation it says snort should be installed through the following: ----- make -DWITH_MYSQL -DWITH_FLEXRESP ; make install ----- later it says to do the... (13 Replies)
Discussion started by: xyyz
13 Replies

3. UNIX for Dummies Questions & Answers

Some FreeBSD issues

I have been using Linux for 3 years now, and I think I am getting enough knowledge (and confidence) to try some more 'traditional' unix variants. I installed FreeBSD 5.0-CURRENT. I have a couple of questions for the time being: 1) Frequently when I need to compile software packages they can't... (16 Replies)
Discussion started by: cbkihong
16 Replies

4. IP Networking

freebsd / dhcp

I'm trying to make a transition from linux to unix, but one of the major hang ups is my networked internet connection. (1) Cable Internet (Adelphia) (2) Modem -> Cat5 (3) Cat5 -> D-Link Router (4) D-Link Router -> Cat5 (5) Cat5 -> D-Link 10/100 Ethernet/USB Adapter On boot it says it sees... (1 Reply)
Discussion started by: xviddivxoggmp3
1 Replies

5. UNIX for Dummies Questions & Answers

dhcp command in FreeBSD?

Is there a dhcp command in FreeBSD 5.3? I know in Linux, there was a command "dhcpcd" that I had to use in order for my WiFi NIC to get all the information that it needed. Is there something similar to this? Thanks. (1 Reply)
Discussion started by: cosmotron
1 Replies

6. BSD

FreeBSD - Kernel Queries/Issues

All, I am a bit of a BSD newbie and haven't really played with it for years, but I have had a recent situation whereby someone attempted to load a custom kernel module and ended up breaking my BSD server. I managed to fix it by doing the following: Booting into loader mode: unload set... (3 Replies)
Discussion started by: drbabbers
3 Replies

7. Web Development

Using IP.Board on FreeBSD, having SQL/Apache Issues

Server: FreeBSD 7.2-RELEASE MYSQL Version: MYSQL 5.1.36 PHP Version: 5.2.10 (apache2handler) IP.Board Version: v3.0.2 Safe Mode: OFF For the most part previously IP.Board, forum software, has run fine without any issues. Regular web pages and .php pages seem to load fine without any issues.... (2 Replies)
Discussion started by: Dark Severance
2 Replies

8. UNIX for Dummies Questions & Answers

Resolved: htpasswd issues (-b) on FreeBSD

I wrote a script to batch-create directories with .htaccess and .htpasswd files. I am using the following line to create the .htpasswd file: htpasswd -cb .htpasswd $USER $PASS However, I keep getting this message in return: Usage: htpasswd passwordfile username The -c flag creates a new... (1 Reply)
Discussion started by: Spetnik
1 Replies

9. BSD

FreeBSD AMD NFS over TCP issues

Hi! I have a major issue with FreeBSD 7.1 i386. We did a change in our Unix env where we exchanged home storage from a NetAPP running udp to a NetAPP running tcp. Now I cant mount homedirs since NFS/AMD seem to fallback to udp :( Trying to force it with amd options nfs_proto=tcp and so on. ... (0 Replies)
Discussion started by: Esaia
0 Replies

10. AIX

Networking Issues - Opera, FreeBSD, AIX

(1) Hi, Am working on FreeBSD 7.4/i386 and installed Opera 11.01 through ports collection manually... But when I run first time am getting "opera: cannot connect X server. Error: Unknown error: 0" What is this error all about???? Please help me to sort out this issue!!! (2) Hi, currently am... (12 Replies)
Discussion started by: Priya Amaresh
12 Replies
wifi-radar.conf(5)						File Formats Manual						wifi-radar.conf(5)

NAME
wifi-radar.conf - configuration file for WiFi Radar SYNOPSIS
wifi-radar.conf DESCRIPTION
wifi-radar.conf is the configuration file for WiFi Radar (wifi-radar(1)) a PyGTK2 utility for managing WiFi profiles in GNU/Linux. The file is an ini-type format with three global sections: [DEFAULT], [DHCP], and [WPA]. These are followed by zero or more profile sec- tions. The settings contained in the configuration file can all be edited from within WiFi Radar, either through the Preferences button or the Edit button. But you are free to edit the configuration file manually if you like. Interpolated Strings It is possible to use configuration options in the value of other options. To use interpolated strings, surround any option from the con- figuration file with %( and )s. So, to use the interface option from the [DEFAULT] section in the value of any other option, use %(inter- face)s in the option's value. Global Settings [DEFAULT] General options. auto_profile_order Comma-separated list of profiles, surrounded by square brackets, specifying the order of profiles in the main window. An example value: ['test:00:00:00:00:00:00', 'WinterPalace:'] (default: []) commit_required Set to True if iwconfig(8) commit should be used after each iwconfig command. (default: False) ifconfig_command Specify the path to ifconfig(8), the command to use when manipulating the IP settings of the NIC. (default: /sbin/ifconfig) ifup_required Set to True if the NIC must be activated (i.e. ifconfig wlan0 up) before scanning will work. (default: False) interface Specifies the interface to scan. Set to the name of your NIC (e.g. eth1 or wlan0). The special value 'auto_detect' will use the first- found WiFi interface. (default: auto_detect) iwconfig_command Specify the path to iwconfig(8), the command to use when trying to associate with a network. (default: /sbin/iwconfig) iwlist_command Specify the path to iwlist(8), the command to use for scanning for access points. (default: /sbin/iwlist) logfile Sets the location of the log file. (default: /var/log/wifi-radar.log) loglevel This sets the verbosity of messages sent to the logfile. The number given here is a threshold value, only those messages emitted by WiFi Radar which exceed loglevel will be written to the logfile. The maximum (and default) value of 50 means to only save the most critical messages and a loglevel of 0 means to save all messages to the logfile. (default: 50) route_command Specify the path to route(8), the command to use to set up network routing if DHCP is not used. (default: /sbin/route) speak_command Specify the path to the command to use to speak status messages. This can be any program which takes a string on the command line. (default: /usr/bin/say) speak_up Set to True to use the speak command. (default: False) version The version of WiFi Radar which created this configuration file. This value is overwritten by WiFi Radar each time the configuration file is saved. [DHCP] Options for the DHCP client used by WiFi Radar. args The parameters to pass to the DHCP client when acquiring a lease (i.e. setting up a connection). (default: -D -o -i dhcp_client -t %(timeout)s) command The command to use to automatically set up the IP networking. This can be any DHCP client, like dhcpcd(8) or dhclient(8), which forks into the background or exits when it acquires an IP address or fails. (default: /sbin/dhcpcd) kill_args The parameters to pass to the DHCP client when disconnecting from a network. (default: -k) pidfile Specify where the DHCP client saves its state info. This file is used if the standard DHCP disconnect does not work and WiFi Radar must kill the client on its own. (default: /etc/dhcpc/dhcpcd-%(interface)s.pid) timeout The time (in seconds) to allow the DHCP client to try to acquire a lease. If the DHCP client does not stop itself after this length of time plus five seconds, WiFi Radar will force the client to end. (default: 30) [WPA] Options for the WPA supplicant used by WiFi Radar. args The parameters to pass to the WPA supplicant when associating with the network. (default: -B -i %(interface)s -c %(configuration)s -D %(driver)s -P %(pidfile)s) command Specify the command to use as the WPA supplicant. (default: /usr/sbin/wpa_supplicant) configuration The WPA supplicant's configuration file. (default: /etc/wpa_supplicant.conf) driver The WPA supplicant driver to use. (default: wext) kill_command The command to use to end the WPA supplicant. The default is an empty value. pidfile Specify where the WPA supplicant saves its state info. (default: /var/run/wpa_supplicant.pid) Per-profile Settings Each profile header consists of the network name (a.k.a. ESSID), followed by a colon, and optionally followed by the network address (a.k.a. BSSID). The BSSID may be blank if the profile is a roaming profile. So a sample roaming profile section name could look like [WinterPalace:]. available Used internally by WiFi Radar to indicate whether an access point is currently detected, it should always be False in the configuration file. (default: False) bssid A copy of the BSSID in the section name, it is used to calculate the section name. The BSSID is the network address, it usually matches the AP address. It may be blank in a roaming profile. (default: 00:00:00:00:00:00) channel The channel to use to connect with the network. (default: auto) con_postscript The command to run after connecting to the network. The default is an empty value. con_prescript The command to run before connecting to the network. The default is an empty value. dis_postscript The command to run after disconnecting from the network. The default is an empty value. dis_prescript The command to run before disconnecting from the network. The default is an empty value. dns1 The primary DNS server. Part of the static configuration to use when not using DHCP. The default is an empty value. dns2 The secondary DNS server. Part of the static configuration to use when not using DHCP. The default is an empty value. domain The domain (e.g. winterpalace.org) of the network. Part of the static configuration to use when not using DHCP. The default is an empty value. encrypted Whether the network is encrypted. The value for this option is determined by scanning and will be overwritten if changed manually in the configuration file. (default: False) essid The network name. This is a copy of the ESSID in the section name and is used to calculate the section name. The default is an empty value. gateway The IP address of the gateway to other networks. Part of the static configuration to use when not using DHCP. The default is an empty value. ip The fixed IP address to use on this network. Part of the static configuration to use when not using DHCP. The default is an empty value. key The WEP encryption key. This is not used with WPA. The default is an empty value. known This is used internally by WiFi Radar to indicate whether an access point has a configured profile, it should always be True in the configuration file. (default: True) mode This is the association mode to use. This is not the same as the mode reported by the AP. In fact, this should be a reflection of the AP mode (i.e. Master mode AP should be Managed mode here). (default: auto) netmask The netmask (e.g. 192.168.1.0/255) to use. Part of the static configuration to use when not using DHCP. The default is an empty value. protocol The WiFi protocol used by the access point (AP). This is only used as a place to store the protocol read from the AP. This will be overwritten the next time the AP is scanned. (default: g) roaming Set to True if this is a roaming profile. (default: False) security This should/will be the security mode (i.e. open or restricted), but as it currently causes crashes, it is not used. The default is an empty value. signal The signal level read from the access point (AP). This is used internally by WiFi Radar, the value will be overwritten each time the configuration file is saved. (default: 0) use_dhcp When set to True, WiFi Radar will ask the DHCP client to configure the IP settings. (default: True) use_wpa When set to True, WiFi Radar will ask the WPA supplicant to handle associating with the access point. (default: False) wpa_driver The card driver the WPA supplicant should use. The default is an empty value. EXAMPLE
[DEFAULT] auto_profile_order = ['test:00:00:00:00:00:00', 'WinterPalace:'] commit_required = False ifconfig_command = /sbin/ifconfig ifup_required = True interface = auto_detect iwconfig_command = /sbin/iwconfig iwlist_command = /sbin/iwlist logfile = /var/log/wifi-radar.log loglevel = 50 route_command = /sbin/route speak_command = /usr/bin/say speak_up = False version = 2.0.s02 [DHCP] args = -D -o -i dhcp_client -t %(timeout)s command = /sbin/dhcpcd kill_args = -k pidfile = /etc/dhcpc/dhcpcd-%(interface)s.pid timeout = 30 [WPA] args = -B -i %(interface)s -c %(configuration)s -D %(driver)s -P %(pidfile)s command = /usr/sbin/wpa_supplicant configuration = /etc/wpa_supplicant.conf driver = wext kill_command = pidfile = /var/run/wpa_supplicant.pid [test:00:00:00:00:00:00] available = False bssid = 00:00:00:00:00:00 channel = auto con_postscript = con_prescript = dis_postscript = dis_prescript = dns1 = dns2 = domain = encrypted = False essid = test gateway = ip = key = known = True mode = auto netmask = protocol = g roaming = False security = signal = 0 use_dhcp = True use_wpa = False wpa_driver = [WinterPalace:] available = False bssid = channel = auto con_postscript = con_prescript = dis_postscript = dis_prescript = dns1 = dns2 = domain = encrypted = True essid = WinterPalace gateway = ip = key = 123456789ABCDEF known = True mode = auto netmask = protocol = g roaming = True security = signal = 0 use_dhcp = True use_wpa = False wpa_driver = FILES
/etc/wifi-radar/wifi-radar.conf BUGS
Probably lots! SEE ALSO
wifi-radar(1) wpa_supplicant.conf(5) WiFi Radar 2.0 July 2009 wifi-radar.conf(5)
All times are GMT -4. The time now is 04:52 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy