Unintentional Wireless Jacking
DOOManiac
Worst. Critic. Ever. Join Date: 2002-04-17 Member: 462Members, NS1 Playtester
Worst. Critic. Ever. Join Date: 2002-04-17 Member: 462Members, NS1 Playtester
in Off-Topic
<div class="IPBDescription">r00fles</div>heh. We're fooling around w/ the boss's new laptop here at work, its got a built in wireless nic. Funny thing is, the computer store below us has a wireless LAN completely unsecured and set for DHCP...
Heh. Too bad we're nice guys eh?
Heh. Too bad we're nice guys eh?
Comments
Heh. Too bad we're nice guys eh? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Make a note NEVER to buy computer equipment from those guys. <!--emo&:)--><img src='http://www.unknownworlds.com/forums/html//emoticons/smile.gif' border='0' style='vertical-align:middle' alt='smile.gif' /><!--endemo-->
If I remember correctly DHCP is what you want to do to have a sort of "central server" in a network, so that you don't have to daisy chain all your computers together.
a DHCP is a server that gives you a IP adress. When you start your computer, your computer asks the DHCP server for a IP adress and he gives him one (this is a oversimplification i know...)
a DHCP is a server that gives you a IP adress. When you start your computer, your computer asks the DHCP server for a IP adress and he gives him one (this is a oversimplification i know...) <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
Yea, as I said, a computer or router or whatever acts as a "centrral server", and assigns dynamic IPs, as opposed to daisy chaining a crapload together and setting static IP.
new IP every time you log onto the network, makes it easier to track what is going on with the network
and it's a good thing you are a nice guy doomeh
Umm... Not a central server. And there's no daisy-chaining involved if you manually choose IP addresses for machines. DHCP just makes things a bit easier if you've got a lot of machines, and want DOOManiac upstairs to h4x0r them in his lunch break without him having to figure out the IP address system you're using.
You can run a DHCP server on an old 486, or even a hardware router - my ADSL router's got such a capability, but I don't use it because I manually set up stuff for my home network some time ago, and don't want to lose the hostnames. Use of DHCP (or not) makes no difference to network cabling or anything like that.
Heh. Too bad we're nice guys eh? <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
You've never heard of war driving, have you?
<a href='http://www.wardriving.com/' target='_blank'>http://www.wardriving.com/</a>
Turning DHCP off does not involve daisy-chaining anything. It just means that your IP is always the same. You can't use port forwarding with DHCP (without special software, at least). DHCP was mostly created to make setting up a network, particularly a variable one, much easier to do. And it works nicely.
I run my wireless network as a free public service. If it were unsecured, like DM said theirs was, that's a bad choice, but it doesn't have to be. Someone can connect to my wireless network and access the internet, but not any of the computers inside it. I monitor the usage of the network, and have thus far banned the MAC addresses of two of my bandwidth-hogging neighbors. Otherwise, it's cool with me if somebody wants to make use of my hardware.
Heh. Too bad we're nice guys eh? <!--QuoteEnd--></td></tr></table><div class='postcolor'><!--QuoteEEnd-->
You've never heard of war driving, have you?
<a href='http://www.wardriving.com/' target='_blank'>http://www.wardriving.com/</a> <!--QuoteEnd--> </td></tr></table><div class='postcolor'> <!--QuoteEEnd-->
I have, but we weren't driving, we were in our office. :P