Jonathan Berry wrote:
> On 7/6/05, Lovell Mcilwain <lovell.mcilwain@xxxxxxxxx> wrote:
>
>>Jonathan Berry wrote:
>>
>>>On 7/6/05, Lovell Mcilwain <lovell.mcilwain@xxxxxxxxx> wrote:
>>>
>>>>I am running the most up-to-date kernel (I basically did a yum update for everything in fc4 to be
>>>>current on it all when I first loaded it on my system)
>>>>[root@Whistler broadcomwifidriver]# uname -r
>>>>2.6.12-1.1387_FC4
>>>>
>>>>When I ran your command I got the following:
>>>>[root@Whistler broadcomwifidriver]# yum list kernel-module-ndiswrapper
>>>>Setting up repositories
>>>>livna 100% |=========================| 951 B 00:00
>>>>updates-released 100% |=========================| 951 B 00:00
>>>>extras 100% |=========================| 1.1 kB 00:00
>>>>base 100% |=========================| 1.1 kB 00:00
>>>>Reading repository metadata in from local files
>>>
>>>
>>>If you read really closely, you'll see that the command I wrote was:
>>>yum list "kernel-module-ndiswrapper*"
>>>
>>>Notice the quotes and the *. You have to give it the kernel version
>>>as well. The * matches anything else so you will see all the kernel
>>>versions. Regardless, since you are up-to-date, you can just run the
>>>other command I gave you.
>>>
>>>yum install kernel-module-ndiswrapper-2.6.12-1.1387_FC4
>>>
>>>By the way, the practice on this list is not to "top post" (meaning
>>>putting your reply above what you are replying to). It's preferred if
>>>you place your reply inline (like I have done) or below the original
>>>text. This makes it easier to see the discussion flow.
>>>
>>>Jonathan
>>>
>>>[snip]
>>>[references]
>>>
>>>
>>>>>Hmm, did you install the Livna package using the "yum install
>>>>>ndiswrapper"? I guess you need to explicitly tell it to get you the
>>>>>kernel module as well.
>>>>>
>>>>>yum list "kernel-module-ndiswrapper*"
>>>>>
>>>>>will give you a list of the avialable kernel modules. Install the one
>>>>>for your kernel version ("uname -r" will tell you the one you are
>>>>>running). If you are running the latest FC4 kernel
>>>>>(2.6.12-1.1387_FC4, which you should update to) then your install
>>>>>command will be:
>>>>>
>>>>>yum install kernel-module-ndiswrapper-2.6.12-1.1387_FC4
>>>>>
>>>>>Unfortuntely, the list will not show you the whole package name, so
>>>>>you need to tack on the "FC4" part to the end.
>>>>>
>>>>>Jonathan
>>>>>
>>>
>>>
>>Thanks for the insight on the post rules, sorry for the violation. For whatever reason whenever I
>
>
> No problem.
>
>
>>ran that command that you gave me it wouldn't install properly but once I rebooted my machine it
>>actually worked. Im not sure why rebooting worked but Im happy that it does.
>
>
> Quite strange indeed. But, hey, if it's working...
>
>
>>So I ran I have started on my last few commands:
>>[root@Whistler scripts]# modprobe ndiswrapper
>>[root@Whistler scripts]# iwconfig wlan0 essid ***
>>[root@Whistler scripts]# iwconfig wlan0 key ****
>>[root@Whistler scripts]# dhcpcd wlan0
>>-bash: dhcpd: command not found
>>
>>So now I'm wondering did I type this command wrong?
>
>
> On Fedora it's called "dhclient" instead of "dhcpd" Not sure why,
> perhaps it is different. Running "dhclient wlan0" should get you in
> business, assuming everything else is correct. You probably should
> check your auth settings for WEP. If you are using open
> authentication you will need to change your key command to:
> iwconfig key open ****
> If you are used restricted (also called shared key) authentication,
> then the default is fine. You can run just "iwconfig" to see if you
> have associated with your AP (if you see the essid, then you have
> associated).
>
> Jonathan
>
**Last minute question at the bottom**
Thanks that was the last step I needed:
[root@Whistler network-scripts]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: wlan0: No such file or directory
Listening on LPF/wlan0/00:90:4b:9f:**:**
Sending on LPF/wlan0/00:90:4b:9f:**:**
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from "dhcp server"
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from "dhcp server"
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: wlan0: No such file or directory
bound to 192.168.11.10** -- renewal in 40342 seconds.
When I do an ifconfig -a I get:
wlan0 Link encap:Ethernet HWaddr 00:90:4B:9F:**:**
inet addr:192.168.*.* Bcast:192.168.*.* Mask:255.255.255.0
inet6 addr: fe80::290:4bff:fe9f:999e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 Thanks that was the last step I needed:
[root@Whistler network-scripts]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: wlan0: No such file or directory
Listening on LPF/wlan0/00:90:4b:9f:**:**
Sending on LPF/wlan0/00:90:4b:9f:**:**
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from "dhcp server"
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from "dhcp server"
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: wlan0: No such file or directory
bound to 192.168.11.10** -- renewal in 40342 seconds.
When I do an ifconfig -a I get:
wlan0 Link encap:Ethernet HWaddr 00:90:4B:9F:**:**
inet addr:192.168.*.* Bcast:192.168.*.* Mask:255.255.255.0
inet6 addr: fe80::290:4bff:fe9f:999e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000Thanks that was the last step I needed:
[root@Whistler network-scripts]# dhclient wlan0
Internet Systems Consortium DHCP Client V3.0.2
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: wlan0: No such file or directory
Listening on LPF/wlan0/00:90:4b:9f:**:**
Sending on LPF/wlan0/00:90:4b:9f:**:**
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 3
DHCPOFFER from "dhcp server"
DHCPREQUEST on wlan0 to 255.255.255.255 port 67
DHCPACK from "dhcp server"
/sbin/dhclient-script: configuration for wlan0 not found. Continuing with defaults.
/etc/sysconfig/network-scripts/network-functions: line 51: wlan0: No such file or directory
bound to 192.168.11.10** -- renewal in 40342 seconds.
When I do an ifconfig -a I get:
wlan0 Link encap:Ethernet HWaddr 00:90:4B:9F:**:**
inet addr:192.168.*.* Bcast:192.168.*.* Mask:255.255.255.0
inet6 addr: fe80::290:4bff:fe9f:999e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:42 errors:0 dropped:0 overruns:0 frame:0
TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6812 (6.6 KiB) TX bytes:1472 (1.4 KiB)
Memory:e8100000-e8101fff
So it looks like I got an address so I think that I'm pretty good here. Actually I just unplugged
from the wire and I am able to send this.
Thanks for all of you help, I would have not been able to get this far without it.
RX bytes:6812 (6.6 KiB) TX bytes:1472 (1.4 KiB)
Memory:e8100000-e8101fff
So it looks like I got an address so I think that I'm pretty good here. Actually I just unplugged
from the wire and I am able to send this.
Thanks for all of you help, I would have not been able to get this far without it.
overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:6812 (6.6 KiB) TX bytes:1472 (1.4 KiB)
Memory:e8100000-e8101fff
So it looks like I got an address so I think that I'm pretty good here. Actually I just unplugged
from the wire and I am able to send this.
Thanks for all of you help, I would have not been able to get this far without it.
--------------------
I did have one last question maybe you could help me with:
1. Because I am using ndiswrapper does this mean that I have to do this through the command line
each time I want to authenticate to a network.
Note: I ask this because when I look at the network cards through the gui this card doesn't show up,
just my internal network card that was discovered natively.
2. If I do use authenticate to another essid with another encryption key, will the one that I
entered for my network be wiped out? or will it be retained?
