K
krw
- Jan 1, 1970
- 0
Too difficult. I set up a friends laptop (Acer) and wirelessOn Mon, 8 Jan 2007 09:26:36 -0500, krw <[email protected]> Gave us:
MassiveProng wrote:
Frank Raffaeli wrote:
[spam snipped]
From Whois registry:
Report SPAM complaints to:
Shea, Thomas
17 Louise Street
Canton, MA 02021
US
It was posted from a Comcast cable modem with a fixed address.
[email protected]
It STILL may have been bounced through that IP addy owner's wireless
system, and not be him that did it at all. Hard IP address doesn't
mean shit when you leave ports open, and are on a system that doesn't
manage or police such activity. Either before or after the fact.
If someone doesn't secure their network, they are still at fault.
Its simple enough to only allow specific MACs to pass through a wireless
router. When I was setting up my wireless network, someone was trying
to use it. I would let them for a couple minutes, then delete them from
the DHCP user's table. After shutting him down about a dozen times, I
just blocked his MAC and he hasn't been back online. After that, I
decided to just allow the four wireless points on the system access it,
by switching to white listing the desired MAC addresses.
It's pretty easy to get around MAC whitelisting since the MAC is
part of every packet. You really need encryption too. AFAIK even
that isn't perfect.
My wireless router is set up to not broadcast its SSID, has a MAC
whitelist (one entry), and encryption enabled.
Now, if only we could get the ADSL and Cable access providers to
instruct their customers of such practices before, during and after
each install.
network. It took far too long to figure out what they (ComCast)
were doing with that box and I couldn't figure out how to convince
the software how to search for the proper network, so left it open.
When I get time I'll have to go back over and figure out what the
hell the Acer network software is doing. My ThinkPad was a piece
of cake to set up. It just knows where it is and how it's
connected (though the dialer is constantly popping up).
Boot his laptop with a recent Knoppix Live CD (or DVD), and I'd bet
that it brings up the wireless connection dialogs right after it
enters the desktop
gui.
How is that going to train WinBlows to do its thing?