LinuxQuestions.org
Visit Jeremy's Blog.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Password
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.

Notices


Reply
  Search this Thread
Old 08-13-2004, 03:27 PM   #1
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Rep: Reputation: 0
problem connecting wireless to DLINK DI-524 using ndiswrapper/BCM94306/Slackware 10


Before I started the wireless setup I was able to connect to the router by cable using the onboard ethernet card.
Here's what I've done so far:
compiled and installed latest (0.9) ndiswrapper.
configured it with bcmwl5.inf.
modprobe ndiswrapper (dmesg and ndiswrapper indicates bcmwl5 loaded ok).
ran ifconfig eth0 down. eth0 is 192.168.0.2 255.255.255.0 gw 192.168.0.1
ran ifconfig to add wlan as 192.168.0.3.
added 192.168.0.1 to route with route add -net default gw 192.168.0.1
ran iwconfig to add channel, essid, key and ap.
ran iwlist wlan0 scan which shows my ap (and my two neighbors' access points).
ran iwconfig which shows everything I configured except the AP address, which is all 0's.
removed the cable, just to be sure.
Gnome wireless link monitor shows 100% strength.
ran ping 192.168.0.1, got Destination Host Unreachable.
Did I miss something obvious?
 
Old 08-14-2004, 08:07 AM   #2
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
Welcome to LQ!

I don't think you missed anything obvious.

Quote:
ran iwconfig to add channel, essid, key and ap.
You may want to mess with the order in which you set these. When you get all 0's or F's in the AP address it means something isn't working right. In my experience, the only parts you must set are the essid and the key. You may have to set the mode to Auto instead of Managed in order to get the essid to stick.

I would also try doing this from a boot when eth0 was never plugged into the router.
 
Old 08-14-2004, 11:24 AM   #3
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
When I removed WEP everything worked fine. So it must be something to do with the format of the key. I copied it from the web interface to the router, so the value is right. I must need to format it differently or something.
 
Old 08-15-2004, 07:28 AM   #4
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
As long as the WEP key is a string of valid hex characters (0-9 and a-f), your format should be fine. Capitalization doesn't matter. However, there are numerous examples here of people having difficulty getting WEP keys to take. You may try issuing the command a few times in a row and see if that does the trick.

<edit>
By the way, you may want to experiement with open versus restricted encryption. So iwconfig wlan0 key open XXXXXXXX and iwconfig wlan0 key restricted XXXXXXX.
</edit>

Last edited by Hangdog42; 08-15-2004 at 07:32 AM.
 
Old 08-16-2004, 10:37 PM   #5
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
Thanks for the suggestions, but that doesn't seem to be effective in my situation. Not sure if it's my hardware, firmware or wireless tools. I should just be satisfied that I have a pretty good wireless connection, but it really bugs me that I can't have WEP too.
 
Old 08-17-2004, 07:35 AM   #6
Hangdog42
LQ Veteran
 
Registered: Feb 2003
Location: Maryland
Distribution: Slackware
Posts: 7,803
Blog Entries: 1

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
What happens when you try to set your WEP key? You might want to post the command you are using and the results. Someone may be able to spot something.


I know this next bit of advice sounds goofy, but it might be worth dropping back a couple of versions to ndiswrapper 0.7 and seeing if that behaves better. In my opinion, both the 0.8 and 0.9 versions of ndiswrapper have had some serious problems. For some combinations of cards and drivers it seems to work flawlessly, but for other combinations, it doesn't work at all. Or even worse, it has intermittent problems. I've seen a number of people have success by trying different combinations of ndiswrapper versions and windows drivers.
 
Old 08-17-2004, 12:38 PM   #7
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
>What happens when you try to set your WEP key?
Nothing happens. There is no feedback. I just don't have an access point. This is what had me so confused to begin with. It appeared that everything worked but iwconfig showed an access point address of all 0's and pinging anything gave me some routing error.

> . . . it might be worth dropping back a couple of versions to ndiswrapper 0.7 and seeing if that behaves better.
That doesn't sound too difficult. I'll give it a try.
 
Old 09-29-2004, 10:41 PM   #8
DyeKid
Member
 
Registered: Apr 2003
Distribution: Slackware 10.2 (AMD64 Desktop, HP ZV5120US & IBM T20 Laptops) Suse 10.1 (IBM T23 Laptop)
Posts: 58

Rep: Reputation: 15
kirkross - welcome to LQ!
seems that we share the same tastes in more than one way.
Same Distro (and version), Same laptop, and same problem...

I managed to get my ap recognized tonight by reading what you did, and verifying status of the link from time to time.
For the record, I am using a linksys 54gAP and the default ip numbers are alittle different. My gw is 192.168.1.1

In short, this is how I got the ap up. I'll begin after the install of ndiswrapper, and the bcmwl5.inf driver.

modprobe ndiswrapper
<<ifconfig to check net status ..eth0, lo both up >>
ifconfig eth0 down
<< verify eth0 down >>
ifconfig wlan0 192.168.1.110
<<verify wlan0 up >>>
<<route -- verify gw is associated to wlan0 -- it's not so ..>>
route add -net default gw wlan0 192.168.1.1
<<route -- verify gw is associated to wlan0 >>
*** current status is card is up, has an IP# and now has gateway ***
iwconfig wlan0 channel #
iwconfig wlan0 mode auto
iwconfig wlan0 essid ESSIDNAME

At this point, iwconfig is telling me that it sees the ap,
ping, however, acts pretty funny at this point.
My Lan cable is unplugged, but it's still using the LAN address for net instead of the wireless.

(ifconfig reveals that eth0 is back up!!!)

ifconfig eth0 down
<<< ifconfig - verify the link is DOWN - now lo and wlan0 are UP ! >>>

Ping again is having problems... destination unreachable...
(try to ping the gateway gives same result)

route - reveals that it has been reset -

route add -net default gw wlan0 192.168.1.1 (again)

Now, route reveals that the default gateway for wlan0 is valid


At this point, I ping myself, but still can't reach outside to the net.


I think we are both CLOSE... please continue to post your results, and if you can shed some light on my ALSA problems, I would be real grateful
 
Old 09-30-2004, 12:09 AM   #9
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
I got it working by running this in a startup script:
ifconfig eth0 down
ifconfig wlan0 192.168.0.3 broadcast 192.168.0.255 netmask 255.255.255.0
route add -net default gw 192.168.0.1 metric 1 dev wlan0
iwconfig wlan0 essid default key blah

it brings down eth0, but I can bring it back up if I plug in the cable.
I got alsa working by downloading the latest version and compiling it. I'm using both right now without problems. Have been since right after I posted the problem.
 
Old 11-08-2004, 11:28 AM   #10
Gerardoj
Member
 
Registered: May 2003
Location: Somewhere over the Rainbow
Distribution: Slackware 9.x, Knoppix, Damn Small Linux, RedHat.
Posts: 465

Rep: Reputation: 30
Hi kirkross I was looking on the below page that you are the author
http://www.linuxquestions.org/hcl/sh...&cat=521&page=

I recently got an HP Pavillion zv5000 series laptop for use on Slackware 10. Pretty much everything worked right out of the box with the exception of ALSA.

One thing that I need to do yet is get the video resolution to 1280x800 to take advantage of the widescreen display.

Does you have any idea on how to get 1280x800 out of the ATI Radeon 9000 IGP Mobility chipset? or maybe with VESA? I tried changing the HorizSync and VertRefresh but nothing changed.

Thanks in advance
 
Old 11-08-2004, 11:32 PM   #11
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
1280x800 resolution

I'm using 1024x768 but it takes full advantage of the wide screen. I haven't tried to get anything better. It seems fine for my needs, but now that you mention it, higher res would be nice.
 
Old 11-08-2004, 11:53 PM   #12
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
resolution

I normally start with a conservative configuration, so that's why I was at 1024x768. But I backed up /etc/X11 and ran xorgconfig, answering with what seemed to me to be the obvious choices and it works quite nicely. What's the problem? Oh, and thanks for the motivation to change it. It's better!
 
Old 11-09-2004, 04:20 PM   #13
Gerardoj
Member
 
Registered: May 2003
Location: Somewhere over the Rainbow
Distribution: Slackware 9.x, Knoppix, Damn Small Linux, RedHat.
Posts: 465

Rep: Reputation: 30
Hi again kirkross, Thank you for your replys, I'm so interested on a couple of questions:

1.- Are you running the ATI drivers for 9000 Radeon? or just VESA config?

2.- Could you please post your config to give me a hand on how did you got the 1280x800? or maybe the HorizSync, VertRefresh?

I will appreciate it a lot.

Last edited by Gerardoj; 11-09-2004 at 04:23 PM.
 
Old 11-09-2004, 08:19 PM   #14
kirkross
LQ Newbie
 
Registered: Aug 2004
Distribution: Slackware
Posts: 10

Original Poster
Rep: Reputation: 0
xorg.conf

This is what I have for now. I have to add ZAxisMapping back and I'll probably add 1024x768, too.

# File generated by xf86config.

#
# Copyright (c) 2004, by the X.Org
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of X.Org shall
# not be used in or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# X.Org.
#

# **********************************************************************
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

Load "dbe" # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Load "type1"
Load "speedo"
Load "freetype"
# Load "xtt"

# This loads the GLX module
Load "glx"
# This loads the DRI module
# Load "dri"

EndSection

# **********************************************************************
# Files section. This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.

RgbPath "/usr/X11R6/lib/X11/rgb"

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath "/usr/X11R6/lib/X11/fonts/local/"
FontPath "/usr/X11R6/lib/X11/fonts/misc/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/X11R6/lib/X11/fonts/Speedo/"
FontPath "/usr/X11R6/lib/X11/fonts/Type1/"
FontPath "/usr/X11R6/lib/X11/fonts/TTF/"
FontPath "/usr/X11R6/lib/X11/fonts/cyrillic/"
FontPath "/usr/X11R6/lib/X11/fonts/75dpi/"
FontPath "/usr/X11R6/lib/X11/fonts/100dpi/"

# The module search path. The default path is shown here.

# ModulePath "/usr/X11R6/lib/modules"

EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is
# received. This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

# Option "NoTrapSignals"

# Uncomment this to disable the <Crtl><Alt><Fn> VT switch sequence
# (where n is 1 through 12). This allows clients to receive these key
# events.

# Option "DontVTSwitch"

# Uncomment this to disable the <Crtl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

# Option "DontZap"

# Uncomment this to disable the <Crtl><Alt><KP_+>/<KP_-> mode switching
# sequences. This allows clients to receive these key events.

# Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

# Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client.

# Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings.

# Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

# Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

Identifier "Keyboard1"
Driver "Keyboard"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

# Option "Protocol" "Xqueue"

Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"

# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"

# These are the default XKB settings for X.Org
# Option "XkbRules" "__XKBDEFRULES__"
# Option "XkbModel" "pc101"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""

# Option "XkbDisable"

Option "XkbRules" "xorg"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto"
Option "Device" "/dev/mouse"

# Mouse-speed setting for PS/2 mouse.

# Option "Resolution" "256"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

# Option "Protocol" "Xqueue"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

# Option "BaudRate" "9600"
# Option "SampleRate" "150"

# Emulate3Buttons is an option for 2-button Microsoft mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"

# ChordMiddle is an option for some 3-button Logitech mice

# Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the XF86Config man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

Identifier "My Monitor"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

HorizSync 31.5 - 64.3

# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

VertRefresh 50-70

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
Identifier "Standard VGA"
VendorName "Unknown"
BoardName "Unknown"

# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.

# Chipset "generic"

# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

Driver "vga"
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.

# BusID "PCI:0:10:0"

# VideoRam 256

# Clocks 25.2 28.3

EndSection

# Device configured by xf86config:

Section "Device"
Identifier "** ATI Radeon (generic) [radeon]"
Driver "radeon"
#VideoRam 16384
# Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
Identifier "Screen 1"
Device "** ATI Radeon (generic) [radeon]"
Monitor "My Monitor"
DefaultDepth 24

Subsection "Display"
Depth 8
Modes "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 16
Modes "1280x1024"
ViewPort 0 0
EndSubsection
Subsection "Display"
Depth 24
Modes "1280x1024"
ViewPort 0 0
EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
Identifier "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.

Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"

EndSection

# Section "DRI"
# Mode 0666
# EndSection
 
Old 11-11-2004, 11:31 AM   #15
Gerardoj
Member
 
Registered: May 2003
Location: Somewhere over the Rainbow
Distribution: Slackware 9.x, Knoppix, Damn Small Linux, RedHat.
Posts: 465

Rep: Reputation: 30
Hey again kirkross, I still don't get the 1280x800 resolution, I really don't know whats going on with the screen, But I will keep trying.

Also I would like to know how did you got the sound works? Could you please give a hand on ALSA?

I'll really appreciate it.

Thanks
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Connecting to Wireless Network with ndiswrapper shimano55 Linux - Newbie 12 04-26-2006 08:32 PM
DLink DI-524 and Virtual Server paddyjoy Linux - Networking 4 11-14-2005 02:24 AM
Broadcom (BCM94306) + ndiswrapper mewgle Linux - Hardware 1 09-29-2005 02:04 AM
DLink 524 router and VNC kylenewton Linux - Networking 2 08-02-2005 05:29 PM
ndiswrapper problem with DLink G520+ lawrencm Linux - Wireless Networking 0 10-10-2004 04:33 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking

All times are GMT -5. The time now is 10:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration