The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.

[Hate On] Wireless Router issues

davidbarrydavidbarry Registered User regular
I'm here playing "IT guy" at my aunt's place. Fucking yay.

She has a DSL connection of the PPPoE variety. A tenant is wanting to connect to her router wirelessly, and I've got to figure out how to do this. The tenant's laptop is running Vista. Simply trying to connect (after typing in the appropriate WEP password) doesn't seem to work, so I assume I've got to change the connection type on the tenant's laptop to let it know it's a PPPoE connection and have it automatically enter the proper username and password prior to entering in the WEP key.

davidbarry.jpg
davidbarry on

Posts

  • exoplasmexoplasm Gainfully Employed Near Blizzard HQRegistered User regular
    edited September 2008
    No

    No

    No

    The router handles PPPoE, the client just connects to wireless with DHCP.

    exoplasm on
    1029386-1.png
    SC2 NA: exoplasm.519 | PA SC2 Mumble Server | My Website | My Stream
  • darkgruedarkgrue Registered User regular
    edited September 2008
    davidbarry wrote: »
    I assume I've got to change the connection type on the tenant's laptop to let it know it's a PPPoE connection and have it automatically enter the proper username and password prior to entering in the WEP key.

    Not having worked with PPPoE, this is just off the top of my head, but (assuming the wireless router is the first thing right after the DSL modem) I believe the PPPoE authentication has to occur on the router, and that the router must support it. Many, but not all, routers have PPPoE configuration pages.

    If the wireless router cames after the DSL modem and/or router, and another device is authenticating on behalf of the user, you should be able to just hook up the wireless router and configure everything as if you were on a stock, non-PPPoE network.

    Think you need to configure the router to authenticate on behalf of the user. Then you can set up the user's laptop to do wireless as usual. You may need to remove or disable the PPPoE client software from the laptop though if it interferes with network settings. I don't know that you can tunnel the authentication through the wireless router and have the laptop authenticate the connection, since the router isn't doing the authentication, I don't think the connection on the WAN side of the router will ever get brought up correctly. Someone who's more familiar with PPPoE may be able to offer a different solution.

    darkgrue on
  • davidbarrydavidbarry Registered User regular
    edited September 2008
    Okay, so I believe I've previously set up the router for use with my aunt's own laptop. (I'm using it right now, in fact.) It's a linksys WRT150n, the connection type is already set to PPPoE, and it is set as a DHCP server, so it should be a-ok.

    Except that the tenant's laptop is having zero luck connecting. Hrmm... It asks for the WEP password, but tells me it is invalid after typing it in. Thanks for the help thus far.

    davidbarry on
    davidbarry.jpg
  • LoneIgadzraLoneIgadzra Registered User regular
    edited September 2008
    WEP keys are only certain numbers of characters I believe (5, 13, + up). I've had trouble connecting a PC laptop to WEP networks where the password was something dumb like "home" while other PC's had no problem, and the issue was fixed after I changed the password to something more befitting the spec. I guess the handling of nonstandard keys may be driver-dependent, who knows.

    Also, WEP is terrible so if the computers involved aren't incredibly old use WPA instead - but even before that, you might want to get it working without security, just to narrow the problem down to encryption.

    LoneIgadzra on
  • davidbarrydavidbarry Registered User regular
    edited September 2008
    WEP keys are only certain numbers of characters I believe (5, 13, + up). I've had trouble connecting a PC laptop to WEP networks where the password was something dumb like "home" while other PC's had no problem, and the issue was fixed after I changed the password to something more befitting the spec. I guess the handling of nonstandard keys may be driver-dependent, who knows.

    Also, WEP is terrible so if the computers involved aren't incredibly old use WPA instead - but even before that, you might want to get it working without security, just to narrow the problem down to encryption.

    Thanks. It turns out that the WEP encryption was the problem; both laptops are working fine without security on the connection. Are there any weird character limits on WPA encryption that I should know about?

    davidbarry on
    davidbarry.jpg
  • LoneIgadzraLoneIgadzra Registered User regular
    edited September 2008
    No, but there are some different standards that can get confusing if you don't know what all your computers support. There's like an older, less-secure WPA and a newer one that's less-supported.

    LoneIgadzra on
  • darkgruedarkgrue Registered User regular
    edited September 2008
    Some vendors have a wep key generator which “translates” a passphrase into a hexadecimal WEP key. There are no standards for this. Very often they just pad short phrases with blanks, zeroes or other characters. However, usually the passphrases are filled with zeros up to the length of 16 bytes, and afterwards the MD5SUM of this bytestream will be the WEP Key.
    WEP keys are only certain numbers of characters I believe (5, 13, + up). I've had trouble connecting a PC laptop to WEP networks where the password was something dumb like "home" while other PC's had no problem, and the issue was fixed after I changed the password to something more befitting the spec.

    Probably exactly what you ran into, and what the OP is now experiencing. Every vendor can do this in a slightly different way, and so they may not be compatible.

    Suggest entering the password on the router and client as hexadecimal 10-digit (40/64-bit keylength) or 26-digit (128-bit keylength) key, and using that on both ends of the connection. PITA to enter (because it's easy to make typos), but it should work reliably. If the router fills in the Key 1-4 fields, pick a field (you probably ought to start with Key 1, some devices won't work correctly with a Key Index other than 1), and use that as the manual key on the client. Otherwise, get a random Hex number op the appropriate length, fill that in the Key 1 field, and use the same number on the client.

    You will probably have to reboot the router if you change any of the major wireless settings on the router like the key, so make sure you commit you changes on the router and reboot before trying to connect on the laptop.

    WEP and some of the other authentication methods can be really, really fussy, unfortunately.

    darkgrue on
  • LoneIgadzraLoneIgadzra Registered User regular
    edited September 2008
    I'm not sure what you are talking about with fields and stuff, but to the OP here is the technical scoop if you're bored: http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy

    Actually, come to think of it, I know of at least one old and shitty wireless card that can't connect my WPA-secured network, even though it detects the network's WPA-ness. Could a similar problem be at work?

    LoneIgadzra on
Sign In or Register to comment.