Hi, I installed madwifi-ng on my newly installed FC5 box. I could connected to my WEP protected network just fine using the 'modprobe', 'ifconfig', 'ifup', 'iwconfig', and 'route' commands. The problem is that I don't want to use those commands to connect. I simply want to use system-config-network to make a profile that I can use with the 'ifup' command.
system-config-network doesn't see ath0 when I select "New wireless device." It only sees wifi0 when I select "New ethernet device."
'iwconfig' sees ath0. 'ifconfig' sees lo, eth0, and wifi0. modprobe.conf has an entry 'alias wifi0 ath_pci'.
Something seems wrong. Why is there an "ethernet" device for my wireless device? Why does ifconfig see ath0, but system-config-network doesn't?
Thanks for the help.
On Mon, 2006-05-01 at 11:34 -0500, Christopher J. Bottaro wrote:
Hi, I installed madwifi-ng on my newly installed FC5 box. I could connected to my WEP protected network just fine using the 'modprobe', 'ifconfig', 'ifup', 'iwconfig', and 'route' commands. The problem is that I don't want to use those commands to connect. I simply want to use system-config-network to make a profile that I can use with the 'ifup' command.
system-config-network doesn't see ath0 when I select "New wireless device." It only sees wifi0 when I select "New ethernet device."
'iwconfig' sees ath0. 'ifconfig' sees lo, eth0, and wifi0. modprobe.conf has an entry 'alias wifi0 ath_pci'.
Something seems wrong. Why is there an "ethernet" device for my wireless device? Why does ifconfig see ath0, but system-config-network doesn't?
Leave the wifi0 - but add a line exactly like it that says ath0 instead of wifi0
Then you will be able to configure it with system-config-network and use the standard tools to bring it up and down etc.
On Mon, 2006-05-01 at 10:30 -0700, Michael A. Peters wrote:
On Mon, 2006-05-01 at 11:34 -0500, Christopher J. Bottaro wrote:
Hi, I installed madwifi-ng on my newly installed FC5 box. I could connected to my WEP protected network just fine using the 'modprobe', 'ifconfig', 'ifup', 'iwconfig', and 'route' commands. The problem is that I don't want to use those commands to connect. I simply want to use system-config-network to make a profile that I can use with the 'ifup' command.
system-config-network doesn't see ath0 when I select "New wireless device." It only sees wifi0 when I select "New ethernet device."
'iwconfig' sees ath0. 'ifconfig' sees lo, eth0, and wifi0. modprobe.conf has an entry 'alias wifi0 ath_pci'.
Something seems wrong. Why is there an "ethernet" device for my wireless device? Why does ifconfig see ath0, but system-config-network doesn't?
Leave the wifi0 - but add a line exactly like it that says ath0 instead of wifi0
Then you will be able to configure it with system-config-network and use the standard tools to bring it up and down etc.
See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187640
--Rob
Michael A. Peters wrote:
Leave the wifi0 - but add a line exactly like it that says ath0 instead of wifi0
Then you will be able to configure it with system-config-network and use the standard tools to bring it up and down etc.
Thank you.
Robert Locke wrote:
See: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=187640
Cool, I added a +1 there.
-- C
-
Christopher J. Bottaro -
Michael A. Peters -
Robert Locke