March 16th, 2004, 02:19 AM
Then the only good way to implement this will be to put the WAP behind it's own firewall. Then you can limit the places that the WAP-connected clients can go.
--Ben
March 16th, 2004, 02:12 AM
I do security full time in the 'real world', so I'll kinda describe that route.....and how I got there.
Experience is worth more than anything else in the security world. A formal education helps...
March 16th, 2004, 01:57 AM
In an ideal situation, you'd hang the AP off of a DMZ interface of your firewall. I'm not familiar with the Watchguard line, but a quick look at their website indicates that most of their boxes have...
March 16th, 2004, 01:14 AM
It's quite possible that they have a program that reads the abuse mailbox, attempts to parse it and sends out notifications without ever having an actual human intervene. Maybe the auto...
March 16th, 2004, 01:00 AM
I'd recommend hping. It's a pretty complete packet generator, allowing you to modify most portions of the packet from the IP protocol on down.
March 11th, 2004, 06:59 PM
Couple of things.
- if you can avoid deploying wireless at all, do so
- if you must deploy wireless, here are few tips:
- do NOT put the WAP on your internal network, hang it off of a DMZ on...
March 11th, 2004, 02:02 AM
You need to decide on a technology to use first, the two most prominent would be:
PGP - good open source support, not supported out of the box by most MUA's
S/MIME - pretty good open source...
