[SOLVED] wpa_supplicant collides with network service
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have wpa_supplicant configured and working along with the network service. eth1 is the designated wireless interface. If S10network and S12wpa_supplicant start up the usual way, "iwconfig eth1" will shows nothing, but instead 'iwconfig peth1' will show wireless signal. If I dont' start up network during boot up and just wpa_supplicant, then once the server is up, I bring up the network with "service network start", eth1 is configured nicely and "iwconfig eth1" will show signal. That will work fine. Any input is appreciated.
# cat /etc/sysconfig/wpa_supplicant
# Use the flag "-i" before each of your interfaces, like so:
# INTERFACES="-i eth1 -i wlan0"
INTERFACES="-i eth1"
# Use the flag "-D" before each driver, like so:
# DRIVERS="-D wext"
DRIVERS="-D wext"
# Other arguments
# -u Enable the D-Bus interface (required for use with NetworkManager)
# -f Log to /var/log/wpa_supplicant.log
OTHER_ARGS="-f /var/log/wpa_supplicant.log"
Edit: This has been solved by turning off network bridging in Xen.
Last edited by rotorstart; 07-17-2010 at 06:23 AM.
You might want to check your udev rule set(s) for network name settings. On most systems, udev is run as soon as the initial RAM file system transfers control to your initialization script. On my Fedora laptop the rule set looks like this:
Code:
$ cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.
# Atheros Communications Inc. AR5001 Wireless Network Adapter (rule written by anaconda)
# nVidia Corporation MCP67 Ethernet (rule written by anaconda)
# PCI device 0x10de:0x054c (forcedeth) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1e:68:46:73:a0", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x168c:0x001c (ath5k) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1f:3a:a3:53:5f", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.