Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-21-2005, 04:57 PM
|
#1
|
Member
Registered: Oct 2004
Posts: 309
Rep:
|
troubleshooting my wifi card
i just configured the wifi card(eth2) on my laptop and i think it's working so far. when i connect to a wap iwconfig shows this:
Code:
eth2 IEEE 802.11g ESSID:"linksys" Nickname:"notebook9"
Mode:Managed Channel:1 Access Point: 00:0F:66: D7:49:A8
Bit Rate=54Mb/s Tx-Power=20 dBm
Retry limit:7 RTS thr: off Fragment thr: off
Encryption key: off
Power Management: off
Link Quality:48/100 Signal level:-72 dBm Noise level:-87 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:11
is that good? the thing is, i'm not being assigned an ip address when i look at ifconfig:
Code:
eth2 Link encap:Ethernet HWaddr 00:0E:35: D4:62:28
inet6 addr: fe80::20e:35ff:fed4:6228/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:1
collisions:0 txqueuelen:1000
RX bytes:16809 (16.4 Kb) TX bytes:264 (264.0 b)
Interrupt:9 Base address:0x2000 Memory:e0206000-e0206fff
i guess the ultimate test would be getting internet access through the wireless card, but i'm also connected to another lan via my ethernet card and i dont know how to tell which card is doing what. for example, if i do a is it pinging my wap router or is it pinging my regular router? if i pull down a web page in firefox, is it coming thru the wifi card or the ethernet card? also, when i try to scan for waps with it says that eth2 doesnt support scanning. anybody know whats up with that?
Last edited by slinky2004; 09-21-2005 at 05:03 PM.
|
|
|
09-21-2005, 06:12 PM
|
#2
|
Senior Member
Registered: Aug 2003
Location: Sydney
Distribution: debian
Posts: 1,495
Rep:
|
How the card gets configured depends on the distro you are using. On Debian the IP numbers and/or other config info are in file /etc/network/interfaces.
If eth2 does not show an IP number I think you can be pretty sure no packets are travelling that way.
To really check if wireless is working just turn off the wired interface ('ifdown eth0' if that's the interface) or just disconnect the cable if you want to be sure
If both interfaces are present the actual one used is decided by the routing tables (shown by command 'route -n'). If one is not working I'm not sure what happens.
You should probably also post the card (exact model/version) and driver you are using.
Last edited by maroonbaboon; 09-21-2005 at 06:16 PM.
|
|
|
09-21-2005, 07:15 PM
|
#3
|
Member
Registered: Oct 2004
Posts: 309
Original Poster
Rep:
|
the card is an intel 2200bg wifi card. i had to install some firmware and the ipw2200 driver from ipw2200.sourceforge.net. after trying both turning eth0 down and unplugging the ethernet cable it seems like the card is connecting to the wap, but something else is going wrong and i'm not getting an ip from the wap and can't, which is wierd cuz it works fine in windows.
|
|
|
09-21-2005, 07:38 PM
|
#4
|
Senior Member
Registered: Aug 2003
Location: Sydney
Distribution: debian
Posts: 1,495
Rep:
|
My understanding is that the IP number gets assigned by the ifconfig command (e.g. ifconfig eth0 192.168.1.100). On Debian it is also set automatically according to lines in /etc/network/interfaces:
iface wlan0 inet dhcp
for dynamic and
iface wlan0 inet static
address 192.168.1.100
netmask 255.255.255.0
for static. When I tried out a wireless card I had to add one of these manually to that config file.
|
|
|
09-23-2005, 10:50 AM
|
#5
|
Member
Registered: Sep 2005
Distribution: PCLinuxOS 2007 / Suse 10.3
Posts: 228
Rep:
|
You might have to make sure you have the dhcp packets installed unless you are sure your lan card is obtaining an ip via dhcp, then it's probably installed. When I set up my lan and wan, I told my wlan0 and eth0 both to obtain an ip through dhcp. Then, I told the eth0 to only come on if the cord was plugged in. Last, I told my wireless card to come up on boot. So this way, you'll be using your wireless card all the time unless you plug in a cord for the eth0. Then, with the ping issue, if you know you are using the wireless card, you obviously are pinging the wireless access point. Also, sometimes if you don't tell the eth0 to only come on when a cord is plugged in, you can cause ip conflicts between the eth0 and wlan0. Your system has a hard time deciding which card you're wanting to use and what ip to use. This is where your routing table sorts things out. But it sounds like you've already received some good advice above though, so good luck.
|
|
|
09-23-2005, 03:07 PM
|
#6
|
Member
Registered: Oct 2004
Posts: 309
Original Poster
Rep:
|
well, eth0 definitely gets a dhcp ip from the router when i startup, but if i ever turn eth0 off and on, it wont work again until i restart, so maybe i have to run some kind of network routine that grabs the ip from the router? i like how you've set things up so that eth0 only comes up if it's plugged in, how did you do that? what distro are you using?
|
|
|
09-23-2005, 03:38 PM
|
#7
|
Member
Registered: Sep 2005
Distribution: PCLinuxOS 2007 / Suse 10.3
Posts: 228
Rep:
|
I'm running Suse 9.3 Pro. Just go into YaST and edit your network cards. Under Network Card Configurations, I simply looked at each card, went to edit, went into the "detailed settings" section, clicked "advanced" and then "detailed settings" again and changed the "device activation." Easy as click...click...click...click...well, you get the idea.
|
|
|
09-23-2005, 05:11 PM
|
#8
|
Member
Registered: Oct 2004
Posts: 309
Original Poster
Rep:
|
i'm running Slackware 10.1, i dunno what yast is.
|
|
|
09-23-2005, 07:09 PM
|
#9
|
Member
Registered: Sep 2005
Distribution: PCLinuxOS 2007 / Suse 10.3
Posts: 228
Rep:
|
Yeah, I don't know much about Slackware, but in Suse it's the major configuration utility and rpm installer. It's pretty slick. Did you get your wireless card issue figured out yet?
|
|
|
09-24-2005, 12:05 AM
|
#10
|
Member
Registered: Oct 2004
Posts: 309
Original Poster
Rep:
|
nope
|
|
|
All times are GMT -5. The time now is 05:17 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|