Alright, I did a little poking around, and found an amazing tutorial on
setting up wireless on ndiswrapper's website, and now wireless is setup.
The next question, I suppose, is this. How can I have the network setup on
boot instead of having to reinstall the driver each time?
On 6/19/07, Alex Winfield <lordadonis@???> wrote:
>
> Thanks for the quick response Richard, I was trying out the various
> things you said as well as a few others.
> iwconfig eth0 essid "NETGEAR" successfully changed the essid, but that was
> all.
> There is no password on the network, I'm certain of this.
> To my eyes, dmesg indicates that the card was initialized without
> incident.
>
> ifconfig eth0 up gives the following:
> [d:b] ~ #ifconfig eth0 up
> SIOCSIFFLAGS: No such file or directory
> zsh:7531 exit 255 ifconfig eth0 up
>
> I'm not sure what that means, but I went ahead and tried another
> approach. From within Windoze, the wireless network is accessed without
> problems, and with a Dell utility I was able to get the AP, among other
> info. But when I do " iwconfig eth0 ap 00:18:4D:84:1C:8C " followed by "
> iwconfig ", the AP remains unchanged from "Invalid".
>
> Again, any/all help is greatly appreciated,
> Alex
>
>
> Richard Griffith wrote:
>
> > Alex,
>
> The part that says "Access Point: Invalid" is the point to consider. This means the
> wireless card is not talking to any access point/wireless router. Of course, why is a
> bit harder. If you have something that works on this network to look at for clues, it
> might make thing easier. Here are some things that might cause this problem.
>
> ESSID might need to be set for the conversation to get started, i.e.
> iwconfig eth0 essid "Right Name"
>
> You might need a WEP/WPA key set to be able to talk to the access point, i.e.
> iwconfig eth0 key s:password
>
> Also check with dmesg to see if there are any indications of errors while the card is
> initialized.
>
> Also, note that the command would be "ifconfig eth0 up" not "iwconfig". iwconfig sets
> the wireless specific options, ifconfig sets things on the tcp/ip level.
>
> Good luck,
> - -Richard
>
> Alex Winfield wrote:
>
> I'm having a little trouble setting up a wireless connection. Here's
> iwconfig:
> [d:b] ~ #iwconfig
> lo no wireless extensions.
>
> eth0 IEEE 802.11b/g ESSID:off/any Nickname:"Broadcom 4318"
> Mode:Managed Access Point: Invalid
> RTS thr:off Fragment thr:off
> Encryption key:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
> eth1 no wireless extensions.
>
> Elsewhere, I saw the following suggestion:
> > iwconfig eth0 up
> > dhcpcd
>
> Which gives me:
> [d:b] ~ #iwconfig eth0 up
> Error : unrecognised wireless request "up"
> zsh: 8041 exit 255 iwconfig eth0 up
> [d:b] ~ #
>
> Any ideas on what I should do next?
> Thanks in advance,
> Alex
>
> _______________________________________________
> dynebolic mailing list
> dynebolic@???http://lists.dyne.org/mailman/listinfo/dynebolic
>
> > _______________________________________________
> dynebolic mailing list
> dynebolic@???http://lists.dyne.org/mailman/listinfo/dynebolic
>
>
--
All Your Base Are Belong To Us
::
Re: [dyne:bolic] wireless setup
