Did you know LQ has a Linux Hardware Compatibility List?
Go Back > Forums > Linux Forums > Linux - Networking > Linux - Wireless Networking
User Name
Linux - Wireless Networking This forum is for the discussion of wireless networking in Linux.


  Search this Thread
Old 12-06-2012, 07:08 AM   #1
Registered: Mar 2003
Posts: 77

Rep: Reputation: 15
Backtrack - Next to no diagnosis on linux?

Hi everyone.

Please hear me out first, it could definitely be a problem with my inexperience but I'm finding one aspect of linux rather frustrating.

This is the apparent lack of diagnosis with regards to the command line network management. I was connecting to my network which has a default gateway of, and WEP encryption. Mucking around with cracking WEP so I set and easy password of A1B2C3D4E5. Wicd seemed to have an issue with connecting however, often kicking up 'bad password' or not taking advantage of the DHCP server and not assigning an IP. Anyway, I digress, not complaining about Wicd but explaining why I'm mucking around with command line.

Anyway, I enter the following commands.

ifconfig wlan0 netmask up
route add default gateway
iwconfig wlan0 essid network key A1B2C3D4E5
iwconfig wlan0 mode managed

Point being, that should connect to the network. ping's however went unresolved and it seems for whatever reason it could no connect (in windows it was fine). The most frustrating part was the inability to examine the reason for what was going wrong. Was it getting an authentication rejection? Some reason the IP wasn't being assigned? It also seemed a bit frustrating that there was no apparent way to "force" an association attempt and get feedback, i.e saying iwconfig wlan0 connect or something while outputting feedback.

Does this stuff simply not exist? Or am I being an idiot and I'm just not aware of it?

Old 12-07-2012, 06:31 AM   #2
Senior Member
Registered: Dec 2008
Location: /root
Distribution: Slackware & BSD
Posts: 1,229

Rep: Reputation: 233Reputation: 233Reputation: 233
It also seemed a bit frustrating that there was no apparent way to "force" an association attempt and get feedback, i.e saying iwconfig wlan0 connect or something while outputting feedback.
Simply find what's happening behind all those configurations and pinging you made, see them at /var/log/*

Try what happened of the packets if they were sent or not:

~$ tail /var/log/syslog
or you can even cat them all to see if wlan0 was noted by the kernel--

~$ cat /var/log/syslog | grep wlan

~$ cat /var/log/messages
~$ dmesg | tail
~$ netstat -s <to examine what you have for network>
~# cat /proc/net/wireless
Just read the manuals for many networking utilities for configuration and debugging net problems:

~$ man netstat [ man ifconfig, man route, man iwconfig ]
There are more ways than that. Just "PLAY" with your gnu/linux, but don't take it too seriously as to obfuscate the mind with emotions .

HOpe that helps.

Good luck.


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
disk diagnosis ginda Linux - Hardware 1 03-29-2007 03:02 AM
Any Automated Testinfg Tool for Diagnosis of linux os Basavaraj Linux - Software 1 02-08-2006 01:43 PM
Linux OS diagnosis.... rajsun Programming 2 02-02-2006 12:39 PM
diagnosis? humanveal Linux - General 3 10-16-2002 08:32 AM

All times are GMT -5. The time now is 12:34 PM.

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