Wireless hosts do not return ping


Results 1 to 8 of 8

Thread: Wireless hosts do not return ping

Threaded View

  1. #6
    Join Date
    Jul 2002
    Location
    New Orleans, LA USA
    Posts
    986
    Quote Originally Posted by retsaw View Post
    Trilarian: If you use a random 10 character alphanumeric password for WPA (26 lowercase +26 uppercase + 10 numbers = 62 characters) that would give you 62^10 possible combinations which from your figures would take 507553 years to crack using the Tesla S1070. With a sufficiently strong password WPA is still pretty secure.
    Sorry - trying to multitask and flipped WPA and WEP when reading. WEP is the culprit that is ridiculously easy to crack.

    Still, WPA uses TKIP (Temporary Key Integrity Protocol) which is susceptible to the man-in-the-middle approach on a high usage network (or patient observance of a low usage network). Anyway, without getting too far off topic, use WPA2 if your router offers it. It is an improvement of WPA, and we can have another thread about encryption if you wish - don't want to hijack micro's thread any further.

    EDIT =>
    I knew I wasn't crazy, WPA can be cracked in under a minute using the man-in-the-middle approach. Read up on the exploit here.
    /End Edit

    Have you tried the wl driver? I have it working on my netbook and it is able to be pinged.

    Sorry for the lack of useful information to your problem. I've been so swamped with work that I draw a blank by the time I finally get off (and the girlfriend is staring at me now to go out for supper). I wanted to at least respond so the next response will trigger an email to me and remind me to come back to this (my memory is shot these days). I had a similar issue at a friend's house that was resolved when he got a separate router (Linksys I think) instead of using the interface on the modem. I do believe there is a better solution for you though, he was just upgrading to N wireless and the problem resolved itself in the process.

    Anyway point being I'll try and put some more thought into this tomorrow - work load should be less. There are lots of smart guys here, so someone may even beat me to the punch.

    Best of luck.

    EDIT2=> What makes me curious rereading this is that you have the same problem on other boxes and a windows machine so it isn't driver specific. On the wireless, can you ping outside the network?

    Code:
    ping www.google.com
    Or if that fails, try their IP address.

    Code:
    ping xxx.xxx.xxx.xxx
    where
    Code:
    trilarian@Debian-Server:~$ resolveip www.google.com
    IP address of www.google.com is 74.125.45.103
    IP address of www.google.com is 74.125.45.104
    IP address of www.google.com is 74.125.45.105
    IP address of www.google.com is 74.125.45.106
    IP address of www.google.com is 74.125.45.147
    IP address of www.google.com is 74.125.45.99
    Last edited by trilarian; 07-27-2010 at 03:40 PM.
    "Whenever you find yourself on the side of the majority, it's time to pause and reflect."

    -Mark Twain

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •