Wireless shenanigens....

IceWolf20

New member
So, in my new apartment, I have not the ability to hardwire all my shit to the router, so my roommate has a wireless router setup. Its some ghetto ass piece of shit Buffalo or something...I've never heard of it. Basically, what I'm trying to do right now is just be abe to get on with a wireless network card on a laptop before trying to get a Linksys Bridge to connect to it. I have a Netgear (yeah, *sigh* I know) card that seemingly can get onto the network, but it can never resolve anything b/c its not connecting to the DHCP server (so it seems). I can leech off of other peoples' WAP's in the building that don't have encryption. My roommate is using 64-bit WEP encryption with a passphrase, and I can seemingly get on the network with it, but I can't get anywere. Anyone have any ideas as to why I wouldn't be able to get on?

<P ID="signature"><div align="center">
ZMD.gif

...the way to be!</div></P>
 
A couple of things you may have him check on his router:

1) Is MAC filtering enabled, and is the MAC address for your card added in to the list of accepted MAC addresses?

2) Is the IP address you are using within the range of allowed IP addresses configured in the router? (Via client filtering, or something similar).

That's the first 2 things that come to mind at the moment, aside from the usual recommendations for a driver update check for the card/firmware update on the router.

<P ID="signature"></P>
 
No connection + no data = bad pass or wrong SSID.
Connection + no data = MAC filtering.
Connection + data = teh w00ty.

<P ID="signature"><marquee direction=right scrollamount=10>
hsrun.gif
</marquee></P>
 
> 1) Is MAC filtering enabled, and is the MAC address for your
> card added in to the list of accepted MAC addresses?

No MAC filtering.

> 2) Is the IP address you are using within the range of
> allowed IP addresses configured in the router? (Via client
> filtering, or something similar).

I'm not explicitly setting the IP address...I have it on auto to recieve from the DHCP server on the router.

<P ID="signature"><div align="center">
ZMD.gif

...the way to be!</div></P>
 
> No connection + no data = bad pass or wrong SSID.
> Connection + no data = MAC filtering.
> Connection + data = teh w00ty.

Connection + no data + no MAC filtering = ???

<P ID="signature"><div align="center">
ZMD.gif

...the way to be!</div></P>
 
> Connection + no data + no MAC filtering = ???

Do an "ipconfig /all" on the wireless device to see what the card is doing.

If it can't get a DHCP lease, assign yourself a static address within his subet and try to ping the router. If it doesn't return anything, then the router is blocking you. Check the WEP key.

<P ID="signature"><marquee direction=right scrollamount=10>
hsrun.gif
</marquee></P>
 
> If it can't get a DHCP lease, assign yourself a static
> address within his subet and try to ping the router. If it
> doesn't return anything, then the router is blocking you.
> Check the WEP key.

That's what I've been saying, but my roommate insists that the passphrase is what he says it is. Unfortunately, I can't access the router to tell for sure and/or change it up. <img src=smilies/angryfire.gif>

Stupid Mac idiot...just b/c I use a PC doesn't mean that I'm network incompetent.

<P ID="signature"><div align="center">
ZMD.gif

...the way to be!</div></P>
 
The passphrase is unimportant. Get the hex key...not some stupid ascii text representation of what it is.

Edit: Oh yeah...64 bit means I can be on your network in 10-45 mins sitting in a car by your place on my shitty laptop.

<P ID="signature"><marquee direction=right scrollamount=10>
hsrun.gif
</marquee></P><P ID="edit"><FONT class="small">Edited by SwampGas on 01/25/05 06:07 PM.</FONT></P>
 
> ...try to ping the router. If it doesn't return anything, then the router is blocking you.

Possibly... unless the router has an option to discard ping requests, and it's enabled. Mine has the option, so it's entirely possible that one might as well I suppose.

<P ID="signature"></P>
 
> The passphrase is unimportant. Get the hex key...not some
> stupid ascii text representation of what it is.
>
> Edit: Oh yeah...64 bit means I can be on your network in
> 10-45 mins sitting in a car by your place on my shitty
> laptop.

It was the ghetto ascii passphrase. I changed it to a 26 digit HEX key in 128-bit encryption mode...and now it works. Aparetnly the algorithms for creating the keys were different....surprise surprise <img src=smilies/upeyes.gif>

Also enabled MAC filtering....so is that sufficient for privacy, or should I turn off SSID broadcast?

<P ID="signature"><div align="center">
ZMD.gif

...the way to be!</div></P>
 
> Also enabled MAC filtering....so is that sufficient for
> privacy, or should I turn off SSID broadcast?

If you want to....it'll stop the random wanna-be h4x0rZ from seeing your network, but anyone with a brain can find the SSID from the data.

<P ID="signature"><marquee direction=right scrollamount=10>
hsrun.gif
</marquee></P>
 
> Possibly... unless the router has an option to discard ping
> requests, and it's enabled. Mine has the option, so it's
> entirely possible that one might as well I suppose.

Ping requests from INSIDE the network? That's dumb.

<P ID="signature"><marquee direction=right scrollamount=10>
hsrun.gif
</marquee></P>
 
> Ping requests from INSIDE the network? That's dumb.
>

Oops... guess I didn't think of that earlier... yeah, I goofed, only affects external traffic. <img src=smilies/retard.gif>

<P ID="signature"></P>
 
Back
Top Bottom