Wireless (continued)

[LT72884]

Ello people of the wonderful world of fedora.

Looks like i have finally found a forum that has more than 2 users logged in and viewing.

So here is my issue. Under network device control it says that my wireless is inactive. so i try to activate it and it says activation failed. I have the madwifi drivers and what not. The only way i have gotten it to work is when my boss came in and used some command line program to create a wlan0 link and attach it to my wifi0 device. But if i restart my laptop or turn it off, i have to recreate all those settings again and i have no idea how to do that. I have read the other thread named "fedora 8 and wireless" and i have noticed there is no way for it to automatically connect. I think the program is wlanconfig or something like that. my question is how do i use that or what is the easiest way to get wifi to work. I have MAC filtering and WEP turned on.

Thanx in advance

[FriedChips]

can you please post the output of:
cat /etc/modprobe.conf
You could probably recreate that same link with this:
su -
ln -s /dev/wifi0 /dev/wlan0
but as you have already found it will lose that link evertime you reboot.

[LT72884]

all right hold on bro. i need to turn me laptop on and redirect the output to a txt file and then put it on the windows network and blah blah blah.lol like 5 minutes dude.

[Dan]

LT72884:

While you're waiting for that to boot up, You might have a look at this page.

http://www.fedoraforum.org/?view=guide

Thanks.


Dan

[LT72884]

can you please post the output of:
cat /etc/modprobe.conf
You could probably recreate that same link with this:
su -
ln -s /dev/wifi0 /dev/wlan0
but as you have already found it will lose that link evertime you reboot.


Well its not a sym link. The term "link" is the only way i could understand what its actually doing. apparently when i do a ifconfig i get my eth0, wlan0, loopback and wifi0. wifi0 is my actual antena. apparently how it works is that you use iwconfig to create a so called software "device" kinda like a null device or temp device, that you have to attach to the actual antena or wifi0 hardware device. thats what is confusing. basically im creating my own device and reataching it to my hardware. any way here is the modprobe.conf output and ifconfig

alias eth0 forcedeth
alias scsi_hostadapter libata
alias scsi_hostadapter1 sata_nv
alias scsi_hostadapter2 pata_amd
alias wlan0 ath_pci
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0


eth0 Link encap:Ethernet HWaddr 00:14:0B:0B:19:0D
inet addr:192.168.0.72 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::214:bff:fe0b:190d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6537 errors:0 dropped:0 overruns:0 frame:0
TX packets:1705 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2878797 (2.7 MiB) TX bytes:188646 (184.2 KiB)
Interrupt:20 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4720 errors:0 dropped:0 overruns:0 frame:0
TX packets:4720 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6291409 (5.9 MiB) TX bytes:6291409 (5.9 MiB)

wifi0 Link encap:UNSPEC HWaddr 00-C0-A8-D4-EC-D5-B8-DF-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:178083 errors:0 dropped:0 overruns:0 frame:81331
TX packets:128453 errors:208 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:13868657 (13.2 MiB) TX bytes:4897625 (4.6 MiB)
Interrupt:19

wlan0 Link encap:Ethernet HWaddr 00:C0:A8:D4:EC:D5
inet6 addr: fe80::2c0:a8ff:fed4:ecd5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Notice how the wifi0 is receiving packets but wlan0 is not.

[LT72884]

LT72884:

While you're waiting for that to boot up, You might have a look at this page.

http://www.fedoraforum.org/?view=guide

Thanks.


Dan
DOH!!!! and there it is. DO NOT CROSS POST. my bad. i can copy and paste it all in there for you and then you can delete the thread

[FriedChips]

alias eth0 forcedeth
alias scsi_hostadapter libata
alias scsi_hostadapter1 sata_nv
alias scsi_hostadapter2 pata_amd
alias wlan0 ath_pci
alias snd-card-0 snd-hda-intel
options snd-card-0 index=0
options snd-hda-intel index=0
su -
cp /etc/modprobe.conf /etc/modprobe.bak
gedit /etc/modprobe.conf
modify
alias wlan0 ath_pci
to read
alias wifi0 ath_pci
and reboot

then you shouldn't have seperate wlan0 and wifi0 devices. Just make sure you check your configurations in
system-config-network
and you should be okay.

[Dan]

Not a problem. Toshiro kindly closed the other one for you. Just thought it might help.


Dan

[LT72884]

Not a problem. Toshiro kindly closed the other one for you. Just thought it might help.


Dan

every forum is different so i get confused. mainly i was in a hurry and figured what the hey. any way its all good and now i just need to figurte this stuff out.

[LT72884]

su -
cp /etc/modprobe.conf /etc/modprobe.bak
gedit /etc/modprobe.conf
modify
alias wlan0 ath_pci
to read
alias wifi0 ath_pci
and reboot

then you shouldn't have seperate wlan0 and wifi0 devices. Just make sure you check your configurations in
system-config-network
and you should be okay.
ok so after that then what do i do. i have never ever ever never configured a wifi device in Linux before. first time man. im kinda hatin it but i HAVE to learn two to do this if i want my degree. lol

[LT72884]

i just noticed soemthing Dan. when i created this thread i only made it once but why did it create it twice. i thought i was shown the guidelines becasue i cross referenced another thread. i just looked a the main networking board and it shows "wireless (continued)" twice. one locked and this one. i wonder how it duplicated it. thats odd.

[Dan]

Hmmm.

OK. Once in a while the forums slow down, and it looks like the thread or post did not submit, a user will hit the button again. Then they end up with a double thread or post. That's likely what happened. If it does it to you again, just click the [ EDIT ] link in the upper right corner of the post, and delete the one you don't want.

BTW, good luck on the RHCE! Wish my old brain was still flexible enough to do that.


Dan

[FriedChips]

under system-config-network delete any wireless configurations you may see and then add a new device and use wifi0 as the device. It should be pretty easy to just follow through it and take most of the defaults just make sure that Activate on boot is NOT checked and DHCP is enabled, then make sure that NetworkManager and NetworkManagerDispatcher are enabled under runlevel 5. Like this:
su -
system-config-services
which by default will be already on runlevel 5, make sure the boxes for NetworkManager and NetworkManagerDispatcher are checked and click save and reboot. You then should see a network status symbol in the system tray, a click or right click should show you any available wireless networks. Another way to check for wireless networks is to do:
su -
iwlist scan wifi0
I have no experience with the madwifi drivers so i can't help you a whole lot beyond that... Good Luck and if you have questions just ask.

[LT72884]

under system-config-network delete any wireless configurations you may see and then add a new device and use wifi0 as the device. It should be pretty easy to just follow through it and take most of the defaults just make sure that Activate on boot is NOT checked and DHCP is enabled, then make sure that NetworkManager and NetworkManagerDispatcher are enabled under runlevel 5. Like this:
su -
system-config-services
which by default will be already on runlevel 5, make sure the boxes for NetworkManager and NetworkManagerDispatcher are checked and click save and reboot. You then should see a network status symbol in the system tray, a click or right click should show you any available wireless networks. Another way to check for wireless networks is to do:
su -
iwlist scan wifi0
I have no experience with the madwifi drivers so i can't help you a whole lot beyond that... Good Luck and if you have questions just ask.
i tired that earlier but there is one problem. when it asks to select device it still says wlan0 and not wifi0. also when it says select your wireless network interface it shows that there are no wireless network interfaces. then i have to choose from a list of about 50 common devices.

[FriedChips]

Hmmm. could you post the output of:
/sbin/lsmod
and
ifconfig

[LT72884]

sorry i was on lunch break. also the output for lsmod is pretty long. what do you want me to grep for. ath_pci?


ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:0B:0B:19:0D
inet addr:192.168.0.72 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::214:bff:fe0b:190d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5926 errors:0 dropped:0 overruns:0 frame:0
TX packets:1279 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1512621 (1.4 MiB) TX bytes:209695 (204.7 KiB)
Interrupt:20 Base address:0x4000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4431 errors:0 dropped:0 overruns:0 frame:0
TX packets:4431 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6280668 (5.9 MiB) TX bytes:6280668 (5.9 MiB)

wifi0 Link encap:UNSPEC HWaddr 00-C0-A8-D4-EC-D5-78-23-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:92058 errors:0 dropped:0 overruns:0 frame:548408
TX packets:20941 errors:16 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:11155495 (10.6 MiB) TX bytes:859846 (839.6 KiB)
Interrupt:19

wlan0 Link encap:Ethernet HWaddr 00:C0:A8:D4:EC:D5
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:1 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[FriedChips]

I'm not sure as I don't know what module the madwifi drivers use... You can try grepping for ath_pci which will tell us if the module originally called out in your modprobe.conf was right. I'm just really wondering why it is still showing 2 devices... Could you post also:
/sbin/lspci
I only need to see your wireless device(s)

[LT72884]

Module Size Used by
fuse 38485 4
rfcomm 36825 0
l2cap 25537 9 rfcomm
bluetooth 49317 4 rfcomm,l2cap
autofs4 20421 2
sunrpc 140765 1
wlan_wep 9600 0
nf_conntrack_ipv4 11717 10
ipt_REJECT 7617 2
iptable_filter 6465 1
ip_tables 14213 1 iptable_filter
nf_conntrack_netbios_ns 6465 0
nf_conntrack_ftp 10977 0
nf_conntrack_ipv6 18769 10
xt_state 6081 20
nf_conntrack 51977 5 nf_conntrack_ipv4,nf_conntrack_netbios_ns,nf_connt rack_ftp,nf_conntrack_ipv6,xt_state
nfnetlink 8281 3 nf_conntrack_ipv4,nf_conntrack_ipv6,nf_conntrack
xt_tcpudp 6977 24
ip6t_ipv6header 6209 2
ip6t_REJECT 8257 2
ip6table_filter 6337 1
ip6_tables 15109 2 ip6t_ipv6header,ip6table_filter
x_tables 14277 7 ipt_REJECT,ip_tables,xt_state,xt_tcpudp,ip6t_ipv6h eader,ip6t_REJECT,ip6_tables
cpufreq_ondemand 10317 1
dm_mirror 21697 0
dm_multipath 18249 0
dm_mod 46465 2 dm_mirror,dm_multipath
ipv6 245989 16 nf_conntrack_ipv6,ip6t_REJECT
snd_hda_intel 274529 2
snd_seq_dummy 6725 0
snd_seq_oss 29889 0
snd_seq_midi_event 9793 1 snd_seq_oss
snd_seq 44849 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device 10061 3 snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss 37569 0
snd_mixer_oss 16705 1 snd_pcm_oss
snd_pcm 63685 2 snd_hda_intel,snd_pcm_oss
snd_timer 20549 2 snd_seq,snd_pcm
firewire_ohci 18113 0
snd_page_alloc 11337 2 snd_hda_intel,snd_pcm
firewire_core 36097 1 firewire_ohci
snd_hwdep 10309 1 snd_hda_intel
snd 43461 13 snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,s nd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwd ep
crc_itu_t 6081 1 firewire_core
k8temp 8257 0
wlan_scan_sta 14464 1
pcspkr 6593 0
forcedeth 45641 0
hwmon 6469 1 k8temp
serio_raw 9029 0
soundcore 9633 1 snd
battery 14025 0
ath_rate_sample 14592 1
nvidia 6212560 36
ac 8133 0
ath_pci 84384 0
i2c_nforce2 9281 0
wlan 172740 5 wlan_wep,wlan_scan_sta,ath_rate_sample,ath_pci
ath_hal 193488 3 ath_rate_sample,ath_pci
button 10321 0
i2c_core 21825 2 nvidia,i2c_nforce2
joydev 11649 0
sg 31965 0
sr_mod 17509 0
cdrom 33889 1 sr_mod
pata_amd 13381 0
sata_nv 17989 4
ata_generic 8901 0
libata 99633 3 pata_amd,sata_nv,ata_generic
sd_mod 27329 5
scsi_mod 119757 4 sg,sr_mod,libata,sd_mod
ext3 110665 1
jbd 52457 1 ext3
mbcache 10177 1 ext3
uhci_hcd 23633 0
ohci_hcd 21445 0
ehci_hcd 31693 0

Hmm, under the module of wlan it shows its being used by ath_pci

__________________________________________________ ______________________
00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:03.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.3 Co-processor: nVidia Corporation MCP51 PMU (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev f1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev f1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
03:00.0 Ethernet controller: Atheros Communications, Inc. AR5006EG 802.11 b/g Wireless PCI Express Adapter (rev 01)
05:00.0 VGA compatible controller: nVidia Corporation G70 [GeForce Go 7600] (rev a1)
07:06.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev c0)

[LT72884]

ok i gots it workin. this is how we did it.

#wlanconfig create wlan0 wlandev wifi0 wlanmode sta

that command will take wlan0 and bind it to wifi0. after that we went into system-config-network and edited the settings for the wlan0 device. we put in our key and what not. after that we went into /etc/sysconfig/network and changed host name from localhost.localdomain to Matt. Then we restarted the network and in command prompt did iwconfig wlan0 to check our settings. They were all correct excpet we were not associated with a AP yet so we did a
#iwpriv wlan0 authmode 2

to set it upfor a shared key. after
#ifconfig wlan0 up

we were connected. now the main question is. every time we disconnect or reboot we have to do the iwpriv command again. for some reason it will not keep the shared key settings? any ideas on how to fix this.. \

Thanx for all the help thus far..

[FriedChips]

glad to hear you got it working mostly... one option to make sure it works on every boot is to add the commands that you need to do after reboot to your rc.local file
su
gedit /etc/rc.local
mine looks like this right now, I have not added anything to it yet...
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

touch /var/lock/subsys/local
hope that helps :)

[LT72884]

ok we will try that. one question for you though. Did you have to go through all this to get your wifi up. Did you have to bind your wlan0 to your wifi0 like we had to? What drivers are you using for you wifi and how did you set it up?

Thanx in advance. Im just wondering why its so different for me than it was for you or the others.

[FriedChips]

No I use ndiswrapper for mine because there are no native linux drivers for me to use. No I did not have to bind wlan0 my wireless card comes up as wlan0 because that's what I set the alias to in my modprobe.conf as I tried to do with yours. ndiswrapper uses windows drivers so my process would have been different than yours. I have not read of anyone having to do what you did. I'm really not even sure what you did LOL. Once I got ndiswrapper setup i just ran system-config-network added my device, made sure NetworkManager and Dispatcher were on and rebooted..

[LT72884]

No I use ndiswrapper for mine because there are no native linux drivers for me to use. No I did not have to bind wlan0 my wireless card comes up as wlan0 because that's what I set the alias to in my modprobe.conf as I tried to do with yours. ndiswrapper uses windows drivers so my process would have been different than yours. I have not read of anyone having to do what you did. I'm really not even sure what you did LOL. Once I got ndiswrapper setup i just ran system-config-network added my device, made sure NetworkManager and Dispatcher were on and rebooted..


C'mon are you serious. Man alive this bugs me. The reason we did it this way is because we found a tutorial on the web for using madwifi with FC7 and 8. Im wondering if i could do it the same way as you did. If so that would be really nice. What was your alias before the wlan0 and why do we need the alias.? Oh by the way, are we allowed to talk about wireshark and airsnort in these forums because i have tons of questions on how to use it. Mainly its how to capture packets when your not actually connected to the network.

[LT72884]

Well this morning my wifi is all jacked up again. here is the ouput from iwconfig

--------------------------------

[root@Matt ~]# iwconfig
lo no wireless extensions.

wifi0 no wireless extensions.

wlan0 IEEE 802.11g ESSID:"" Nickname:"Matt"
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Bit Rate:1 Mb/s Tx-Power:16 dBm Sensitivity=1/1
Retry:off RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=5/70 Signal level=-90 dBm Noise level=-95 dBm
Rx invalid nwid:492 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

eth0 no wireless extensions.
------------------------------------------

For some reason i receive crapy signal from the AP that is less than 5 feet away from me. I have checked the security to make sure that my MAC is in there and it is. My key is correct. For some reason iwconfig shows that the key and power management are off and that my signal is 5 of 70. BUT under sytem-config-network it shows my key is in there for security and it is the same key from yesterday when it worked. i have not touched it. i have tried all the steps i did yesterday to get it working and still its a man down. i have no idea what to do.

[FriedChips]

You can give ndiswrapper a try, no guarantees but many people have good luck with it. Just make sure you are using the proper driver.. ie. 32 or 64bit depending on your install. There is a script out there called aircrack which is the only thing like that I have experimented with but it seems very up front. Unfortunately ndiswrapper does not support "monitor mode" with my card...

[LT72884]

Heya; FC, i want to send you some documentation on MADWIFI. i found a great PDF about how it all works. Apparently you set up VAP's or Virtual Access Points on one interface. The PDF explains how to use wireshark with MADWIFI also. if your interested let me know.

[FriedChips]

If you can provide a link to it I will try to check it out tonight. I don't know that it will help me help you though.. I really think that ndiswrapper may be a good/simple way to go. It can't hurt anything to try..

[LT72884]

http://www.willhackforsushi.com/books/377_eth_2e_06.pdf

its more of what MADWIFI is and how to use wireshark with it.

[FriedChips]

http://www.aircrack-ng.org/doku.php
that will certainly be of some interest to you...