ax0n

Ostensibly, most open ports are services, so you should connect to the remote PC's open ports with the client that utilizes them. Port 21 is usually FTP. 22 is usually SSH. 80 is usually HTTP (web server) and so on and so forth. THIS may help you out. You can try to use a command line tool to see if the port responds. I usually choose netcat (nc.exe on windows, nc on Linux/BSD/OS X). In the case of both telnet and netcat, just use the following syntax: telnet (or nc) hostname port Here, I'll use nc to connect to the SSH port on my DMZ box: chimaera:~ axon$ nc bouncer.labs.h-i-r.net 22 SSH-2.0-OpenSSH_5.1 Protocol mismatch. Telnet is not only "noisier" (displaying a lot of extra stuff to you) but it doesn't always generate a clean TCP session that contains ONLY what you type. It tries to perform a telnet handshake, which can throw some results off. Regardless, this is the same thing done with telnet. chimaera:~ axon$ telnet bouncer.labs.h-i-r.net 22 Trying 192.168.0.10... Connected to bouncer.labs.h-i-r.net. Escape character is '^]'. SSH-2.0-OpenSSH_5.1 Protocol mismatch. Connection closed by foreign host. Hope this helps.

If several neighbors have wide-open WiFi, any WEP or WPA-PSK will keep the casual leeches away. If you have curious or bored neighbors, WPA2 with EAP might be in order. Or you can just run wide-open WiFi and sandbox it to where it can only hit OpenVPN or some other encrypted tunnel setup.

Vidalia/Tor is a good solution but slowish. Before Tor, back in 2000 or so, I was using MultiProxy on my windows machines. http://www.multiproxy.org/multiproxy.htm You feed it a list of known good proxy servers (which the OP just helped with) and it will randomly pick proxies.

Yes but 1,6,11 and 7 are all being used nearby. All else being equal (as in, if the signal strength is the same on all four of those channels) I'd use 3. If any of 1, 6, or 11 are very weak, I'd just use one of those. Keep in mind 7 overlaps a little bit with 11 and more with 6. There's a reason that people get paid actual money to do a site survey. It's because there are too many variables to just tell you. It's got to do with where you plan on putting your access point, how strong other neighboring networks are, and a few other things. Really, I just pick 1, 6, or 11 and go to town. I don't worry about changing channels unless I have connectivity or bandwidth issues.

Yeah? Damn, I've been missing out! That's the main reason I haven't been messing with BT3 in Parallels or VirtualBox. Thanks for the heads up!

Not all IP addresses will respond to ping. If a firewall or router drops (ignores, blocks) certain kinds of ICMP traffic, for example, it won't work. EDIT: NM, loftrat covered it.

No, you must mount it first with TrueCrypt, which means you need the password. An alternative option is to use a PGP Variant. You can encrypt all kinds of stuff using the public key, but you need the private key (and thus, the password for the private key) to decrypt.

Assuming you can SSH to your dell: 1) Install Squid on the dell (ubuntu) 2) Configure squid proxy to allow anything from localhost to get to anything on the Internet. This might work (change paths if needed, run squid -z to initialize cache, then run squid to start it) acl all src all acl localhost src 127.0.0.1/32 acl to_localhost dst 127.0.0.0/8 acl CONNECT method CONNECT http_access allow all http_port localhost:3128 hierarchy_stoplist cgi-bin ? access_log /var/squid/logs/access.log squid refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 acl apache rep_header Server ^Apache broken_vary_encoding allow apache coredump_dir /var/squid/cache 3) Tunnel your port 3128 to port 3128 on the dell. http://www.h-i-r.net/2008/02/sysadmin-sund...-dirty-ssh.html 4) Configure your browser to use http://localhost:3128 as the proxy server If you can't access SSH on your home box from within starbucks, try running sshd on port 443, 53, or 80. You may need to set it up as a PAT (Port Address Translation, sometimes called Port Forwarding or Virtual IP) on your router(s).

No problem. I've been meaning to put something like that together for a while. You just prodded me into thinking of ways to trigger the reverse connection -- which is where I kind of got hung up when I was putting together the "quick and dirty tunneling" article. I was in a hurry when I wrote that one in February. Plus, I needed something to pass time. In another terminal, I was compiling Firefox 3 from source in NetBSD on a 110MHz SparcStation 20. An arduous process, rest assured.

Relatively short list, but I'll take quality over quantity any day. Nothing more frustrating than trying to weed through a list of 1000 proxy servers to find that one that's both active and works through the web filter. Thanks!

Here's a write-up I did in response to this thread. It was blog-post worthy and a bit lengthy for a forum reply.

Also consider the fact that many wireless tools that come with BT3 really work best with an Atheros chipset, and there are no Atheros USB adapters. That's one of the main reasons you see people digging into their Netbooks to swap out the WiFi. If you're scanning for access points with BT3 though, you can't beat the Alfa awus036h with Kismet.

MacBook, 10.5 Leopard. This should work for MBP too. chimaera:~ axon$ sudo ifconfig en1 ether 00:12:34:56:78:90 chimaera:~ axon$ ifconfig en1 en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 inet6 fe80::219:e3ff:fe02:9a55%en1 prefixlen 64 scopeid 0x6 inet 192.168.0.103 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:12:34:56:78:90 (see?) media: autoselect status: active supported media: autoselect Sometimes, you need to do "sudo ifconfig [iface] down" before changing the ethernet address. Here's how to do it on most popular platforms.