-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yes Chris, as well as MAC address filtering (not bulletproof, but helps). Also you should not advertise your SSID (turn it off).
But please excuse my ignorance, if you run a "public" access point to which no control is done, do you really expect people not to log in when they discover it? It's like people running public ftp servers where anyone can upload / download... not the smartest thing in the world to do. Basically they are using your network, and are IN your network (bye bye firewall rules and certain things specific to internal interaction aswell). If you run an smtp server too in your network, you had better pray he's not a spammer (unlikely, but still the risk is there). Nice computer by the way ... Oh, I just let myself into your house ~ the front door was unlocked and open, with a big sign above the door telling me that ;-) Greetings Ralph Chris Cox wrote: > Last night I just happen to connect to http://192.168.1.1/DHCP.htm and > noticed > something odd that I haven't seen before. There was a 2nd Wireless IP > address on my local LAN. But I only have 1 wireless card connected on a > Windows 2k machine. This one had a different Hostname on it so I'm thinking > someone in the area was using my bandwidth/ broadband connection. So my next > question is how should I prevent this in the furture? Should turning on WEP > on my router fix this? > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFCKe2YAWKxH5yWMT8RAtGAAJ4oJoQOTDU7olUkQ2P2+W3ugQMuaQCfWQgA zl6w/olXG+nGOclHtpmB7cc= =LTIk -----END PGP SIGNATURE----- -- [email protected] mailing list
