EvilZone
Hacking and Security => Hacking and Security => : lucid September 01, 2013, 07:12:53 AM
-
Well I'll just cut to the chase. I reluctantly decided to ask you guys for help after exhausting all the options that I could think of.
Here's a few symptoms:
- Ethernet works, Wlan doesn't.
- This is the case for both Arch and Windows on my pc
- All other devices can connect wirelessly
- The only thing I can ping at all is loopback.
- I got this error which I don't think I've encountered while pinging the gateway:
Pinging 192.168.1.1 with 32 bytes of data:
General failure.
General failure.
General failure.
Very strange.
Some background. Again, installing debian on this fucking USB seems to be ruining my life. I installed debian on USB. In the device detection part of the install I had to do it eth0 for some reason. Normally when I'm installing a *nix I almost always have to use eth0. Don't know why, but it's never affected my other operating systems. All I know, is that I went through the install process, successfully, and then when I restarted and booted into my regular system(both windows and arch) could not detect wlan0 at all. I even switched to a GUI manager in linux, but it doesn't even see the wireless network. Wireless broadcasting is on I've double-checked the router configurations. Running ip link set wlan0 up only tells me that device wlan0 doesn't exist. It seems to be a driver issue but I don't really know honestly. Everything was perfectly fine before. Then after the install wlan0 was fucked. Again, all other devices are connected wirelessly on my network. I've also tried powercycling, and resetting the router. Nothing. I can't imagine why my wireless driver would have disappeared for no reason. I tried modprobing the appropriate module in linux. Nothing there either. At this point, and at my meager skill level, I can't think of anything else to try.
-
It's obviously a driver issue, or an unsupported wlan card, or a broken wlan card. If the computer COULD see wlan0 and not be able to connect, then you would be worrying about the wifi router. Now the problem is in your computer.
If you can, maybe swap wifi cards? what does lspci say?
-
Can you post the output of ifconfig?
-
Trying known good hardware and a fresh driver install can be helpful as well. (delete the driver files manually, then re-install dont just overwrite) Also try re-seating the card, check for resource conflicts(unlikely), also as crazy as it sounds check to see if your region settings somehow got screwed up(unlikely). All wireless devices(and cd drives etc) have different "region" codes, that can be messed with intentionally or unintentionally.
Less likely but possible:
I would also recommend running a ping of a known stable site from something that is connecting correctly, see if you are getting a lot of dropped packets/failed pings, as that would be indicative of your router going bad. I say this because just a few months back i saw a linksys router that was going bad, that would allow some devices to connect but not others, but when viewing a ping through it wirelessly vs one through ethernet it was getting anywhere from 3%-15% dropped.
well thats about it for now, i just woke up so brain is only firing on about 1/3rd of one cylinder. Time for coffee and to work more around the house...let us know if any of this works, if not im sure i can come up with more things to check.
-
Wow. You guys are going to be really mad at me. I turned on my computer today and everything is fine :/
Which is actually really annoying because now I'll probably never know why that happened. Sorry for wasting all of your time, but this is solved..I think.
-
Wow. You guys are going to be really mad at me. I turned on my computer today and everything is fine :/
Which is actually really annoying because now I'll probably never know why that happened. Sorry for wasting all of your time, but this is solved..I think.
Ah sounds like a case of the all mighty PEBKAC, hate those. ;)
but i guess if it resurfaces and none of this helps let us know. Like i said i wrote mine half a sleep i could come up with at least half a dozen more things to look into....damn computers are complicated....i think im gonna switch back to my light-bright, more my speed.
-
Ah sounds like a case of the all mighty PEBKAC, hate those. ;)
I think in this situation it's actually an ID-10T error(usually my problem)
Yeah, the other thing too is that I was kind of looking forward to having another problem to solve. That happens to me all the time actually. I'll have some problem, and I'll think:
"Well at least I have a nice juicy problem to work on.." Then out of nowhere it fixes itself.
My computer obviously doesn't need me. :P
-
I think in this situation it's actually an ID-10T error(usually my problem)
Yeah, the other thing too is that I was kind of looking forward to having another problem to solve. That happens to me all the time actually. I'll have some problem, and I'll think:
"Well at least I have a nice juicy problem to work on.." Then out of nowhere it fixes itself.
My computer obviously doesn't need me. :P
you could always tazer it for behaving TOO well, then i GUARANTEE you have a problem to fix...
-
you could always tazer it for behaving TOO well, then i GUARANTEE you have a problem to fix...
I'd rather just wait for the next Arch update when I find out that ALL of the packages I was relying on have suddenly become deprecated at the same damn time..
Bleeding edge never leaves a man bored.
-
Check rfkill.
-
I probably should have looked into that sooner. Good info for the future though thanks.
lucid@machine ~ >> rfkill list wlan
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
lucid@machine ~ >> rfkill list wifi
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
All good now.