hi guys

new to linux here but im geting the grip of it. of the gui part of it at least

anyways, i setup a wireless card with the 'wireless assistance' but i cant browse the web. what is weird is that 'kwifimangager' tells me im conected, although with 'AccessPoint: UNKNOWN' and the card (pcmcia) blinks as it is connected to the network, but i cant access it, why?

im using Back|Track 2
on the 'network cnfigurator' i set up the:

ip address;
subnet mask;
default gateway;
primary dns;
secondary dns.

just as i do in winxp.
any tips would be greatly appreced
thanks

Hey,

Sounds like you got a fun issue.

KWifiManager can be such a pain in the ass. it works when it wants to.

What Distro are you using? Also, what wireless card/chipset are you using?

Lastly, what kernel version are you running?

(e.g. Ubuntu 6.10, Linksys WPC54G/ Broadcomm 4318 chipset, Kernel v. 2.6.17.11)

The shell is so fun. You just have to warm up to it.

To get the above info, part of it you'll get by typing this exact command and hitting Enter:
uname -a

The rest type in and hit Enter:
lspci

You'll see you're wireless chipset listed on there.

One thing you can try in the shell to, to even see if you have an IP address:
/sbin/iwconfig

Hope this helps. Let me/us know if you have issues. Wireless can initially be a beast on Linux, but it's 10 times better than Windows once you get it. I tried getting Wireless to work on Slackware one time. That was a doozie :P

hey!

i also enjoy the idea of using the shell, but i still have almost no knowledge of the comands, im actually writing them down on paper as i see them writen

all version: Linux BT 2.6.18-rc5 #4 SMP i686 P4 GNU/Linux

my wireless card: Orinoco 8470-WD
ethernet controler is Atheros Comunications, Inc. AR5212 802.11abg (rev 01)

when i type in /sbin/iwconfig:
wifi0 no wireless extensions
ath0 all sort of info but no ip address

but when i type ifconfig:

ath0 has an ip address and a broadcast address (i did not assign a broadcast address)

...

ric

Hi Ricmetal,

Since you get the ip address successfully,I believe your problem come from below issue:-
-Wrong Default Gateway,type this to check which network card is your default gateway.
route
-wrong dns server
Check content inside the /etc/resolv.conf see correct or not

Regards,
Ks

resolv.conf - all is OK.

nameserver 192.168.xxx.xx
nameserver 192.168.xxx.xx

'route', the following appears:

Destination: loopback
Gateway : *
Genmask : 255.0.0.0
Flags : U
Metric : 0
Ref : 0
Use : 0
Iface : lo

'ifconfig', it shows:

Link encap: Local loopback
inet addr: 127.0.0.1 Mask: 255.0.0.0

Hey guys,

Now, the only thing to resolv.conf is mostly your DNS settings. You may be having a name resolution problem, but check this first.

Do:

ping -c 4 66.94.234.13 //Hit Enter

If you get packets back you're to the very least connected to the Internet.

If that works, then do this. Type:

ping -c 4 yahoo.com //Hit Enter

If you get a response back, then your DNS is working fine essentially.

Now, if all the above works, here's what you have to do. Go to the /etc/resolv.conf as mentioned before, however what you want to do is enter in the 2 DNS server addresses for your ISP. I've had an issue on both Debian 3.1 and RHEL 4, the same issue. It's annoying as hell.

What the problem ends/ended up being, is that the router was trying to intercept DNS requests, and act as it's own DNS server, when it reality, it sucks with name resolution. It basically filters everything over Port 53, and causes an issue. So, just type:

nano /etc/resolv.conf //Hit Enter
Remove 192.168.x.1 (whatever x is, 0 or 1 typically)
Add the 2 IP addresses, one under another of your ISP's DNS servers. Like:

68.87.85.98
68.87.89.146

Then hit Ctrl+O to save, and hit Ctrl+X to close out of the conf file. After that, then go:

/etc/init.d/network stop //Hit Enter
/etc/init.d/network start //Hit Enter
/sbin/dhclient //Hit Enter

Then try again. If it gives you grief still, reboot and you should be set.

hey jm

i tried to ping 66.94.234.13 and i get 'Destination Host Unreachable'.

ric

EDIT(2)

i have very little idea what to do, i've read some posts with similar problems and am currently trying diferent things, i dunno.

i typed in 'more /var/log/messages | grep ath0':

ADDRCONF(NETDEV_UP): ath0: link is not ready
ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready

the message is repeated a few times.

more so:
- im conecting a orinoco b/g gold pcmcia card to a linksys router (i don't think that shoould be a problem);
- im using static ip

Hey ric,

That tells me that you're not truly connected to your internet.

So, when you run ifconfig, it gives you a valid IP address on the subnet of your LAN?

So, with a Linksys, it will be probably be something like:

Address: 192.168.1.100
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.1

Is that what your seeing (similar at least )?

Make sure the DNS servers you setup, one of them IS NOT 192.168.1.1

Give your router the boot with DNS, and specify the 2 DNS addressed for your ISP. Also, if the TCP/IP is all setup properly, reset your router, and clear you're routing tables. Sometimes the routing tables get all clumped up.

Also, are you using any encryption? WEP, WPA, TLS, etc..?

KWifiManager is such a piece of garbage. I thought it was cool at fist on Knoppix, but then I realized how many flaws it had in it. I'm in the process of writing a seamless WiFi client w/ C or Java, that can run on Windows, Linux/UNIX, or Mac. Unfortunately, not soon enough! :P

In order to get network connectivity via wireless lan, you have to do two things:

First get the card associated with the accesspoint. You seem to be using Atheros card. Check out the Madwifi project homepage at http://madwifi.org/. There are many excellent HOWTO's there. The tools you probably want to use are "wlanconfig", "iwconfig" and "wpa_supplicant". With them you will be able to associate yourself to the Access point. Take a look at this if you want to use wpa_supplicant:

http://www.linuxquestions.org/questi...d.php?t=523028

Next, when you've associated, you need to get an IP address. This is usually done with an DHCP query, like this:

dhclient ath0

Your distribution might use some other dhcp-client like "pump" or "dhcpcd". You can also use your distribution's built-in tools like "ifup" to bring the interface up.

NOTE: You could alternatively take a look at "network-manager", which I hear works quite well. It's a GUI to do all the ugly stuff described here.

hey! thx for all tips so far.
basileus, im folowing your post and reading at madwifi.org and other places. i have to say that i can se my network in wirelçess assistant. anyways, im going to try and install the latest mad drivers without internet connection, wich seems not be be very comon in doing in the few 'how to's' about instaling madwifi drivers.

cheers

edit: i had a suddon change in dns after rebooting my router. the dns changed, dunno why. anyway, i changed it in bactrack2 using wireless assistant. i still cant connect to the internet but when i do ifconfig i get ip adress this time. everything seems correct. i also get ssid. one thing that appears though that i dont know how is the broadcastwhich i did not type in. cant ping yet.

crap i thought it would be easier.

edit 2: shit. i should probably have said that im connecting to a router on another pc. sorry

i know it sucks just to dump info hoping others to solve problem but im hoping it a simple issue and that i hopefully dont have to dwelve into ebooks and chm's to get the network going!

ipconfig
#####################################################################
ath0 Link encap:Ethernet HWaddr 00:20:A6:58:84:36
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::220:a6ff:fe58:8436/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:974 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:52227 (51.0 KiB) TX bytes:5754 (5.6 KiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:51 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4936 (4.8 KiB) TX bytes:4936 (4.8 KiB)

wifi0 Link encap:UNSPEC HWaddr 00-20-A6-58-84-36-00-00-00-00-00-00-00-00-00-00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:27408 errors:0 dropped:0 overruns:0 frame:10
TX packets:442 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:199
RX bytes:2135291 (2.0 MiB) TX bytes:24254 (23.6 KiB)
Interrupt:16 Memory:dd2c0000-dd2d0000
#####################################################################

Ok, now you say you're connecting to a router on another PC? So, the wireless router, is it on your local LAN? Or are you "piggy-backing" off a neighbors WLAN? And do you have any encryption setup?

Now, when you connect to the wireless network, are you connecting to an actual router, or are you connecting to a PC recieving wireless traffic and forwarding the traffic on? That's what's confusing me...

What you can also do is:

tracert -h 5 yahoo.com, and see where the route stops, that will give you an indication of where you're being "stopped in your tracks".

i teach u a simple way,
after the wireless network up, type this in command line (as root)

route add default gw 192.168.x.x(your gateway ip)
Don't worry to mad wifi or etc.
done.