1.) Is it possible to block/prevent attackers from running any sort of traceroute into your DMZ?
If your router doesn't ever respond with ICMP messages of any type, this effectively breaks traceroute in all its flavors iirc. I believe you may also encounter the distinction in traceroute implementations where Cisco and Linux use UDP packets for the probe while Windows use ICMP echo requests. The "sensing" mechanism on all OS's I believe relies on ICMP replies.
http://www.cisco.com/warp/public/105/traceroute.shtml2.) Using a 802.11b wireless nic on your laptop with Netstumbler installed, you would like to scan an 802.11g network? Why is this not possible?
b and g use the same frequency, however b is the older slower standard, g the newer. g is by standard backward compatible with b, but b hardware can't grok g traffic. If you want to get very technical about it, the difference between the two is the modulation scheme. CCK is the scheme used by b, OFDM is used by g, but by standard, g hardware can deal with
CCK.
http://en.wikipedia.org/wiki/802.11#802.11bBut nothing I recall of the CEH exam got anywhere near that technical regarding modulation.
3) You are doing IP spoofing while you scan your target. You find that the target has port 23 open. Anyway you are unable to connect. Why?
Just think about this for bit. If you spoof your IP address in your scan, where will the target send the reply packets?
4) I notice repeated probes to port 1080. I learn that the protocol being used is designed to allow the host outside of a firewall to connect transparently and securely through the firewall.what would be your inference of what is happening/happened? Could someone be using SOCKS on the network to communicate through the firewall?
Have a look at /etc/services on a linux box. Or the IANA list of common ports
http://www.iana.org/assignments/port-numbersI'm not sure I'd come to the conclusion someone is communicating through my fw with SOCKS just because of some probes, but I might conclude that the probes are perhaps hunting for a listening SOCKS server.