Who is online now

Jasper Lin (mailto:jasperln@mit.edu): iPaq63
Address: ipaq-63.no-ip.org
Port: 2000 (receives triplets - upload yours here), 2001 (sends my triplet), 2002 (sends random triplet), 2003 (tracker/proxy - see below)
Check Availability (http://scripts.mit.edu/~jasperln/ipaq-up.py) (Lastest check was: iPaq63 is as of )
Available Triplet Servers (http://scripts.mit.edu/~jasperln/servers-up.py)
Broke up sending/receiving into different servers to make it as easy to write a compatible client as possible. Most clients should work with little or no modification. Ipaq should stay on pretty much all the time and all servers are threaded, nohup'd, and write to file so hopefully they should stay up unless the ipaq is actively moving around.. Drop me a line if you're having any problems.
Update (2/17): Changed ports to 2000, 2001. After much communication with Zahoor, we discovered a potential problem with communicating between MIT and Singapore when using high ports. It seems some overzealous router between us is filtering ports leading to much confusion. When trying to communicate between MIT and Singapore, it is suggested to pick a port below 6000 otherwise you may run into weird problems.
Update (2/17): Just for fun. Added port 2002 that sends a triplet randomly chosen from my logs. Also a convenient way to publish and disseminate your triplet if you don't have a long-standing server running. Just upload your triplet to port 2000 and it's automatically added. This may be especially useful for those on the Singapore side that currently can only talk to MIT via client. Right now this limits them from sending their triplets to anyone else except those on the MIT side with active servers running. Upload to my server and I'll help spread your triplet=) The output is purposely anonymous and random so if there are other servers running you're highly encouraged to connect to them as well.
Update (2/20): Added a new triplet tracker/proxy (http://scripts.mit.edu/~jasperln/servers-up.py) on port 2003. I thought it was kind of a bummer how there was no server tracker that updated in real-time and how MIT iPaqs could not connect to SMA iPaqs. So I tried to come up with a solution that would solve both problems=) See below for instructions on how to add your server.

Features of tracker/proxy (http://scripts.mit.edu/~jasperln/servers-up.py):

1) Directory of available triplet servers.
2) Short description of each server.
3) Supports any triplet server unmodified.
4) Availability and current IP of servers updates in real-time.
5) Tunnels through NATs allowing iPaqs such as those behind SMA's network to be reached.
6) Servers automatically reconnect and reregister after temporary network outage.
7) Supports several concurrent connections to each server.
8) Primitive version checking. If there is a new version of proxy.py the tracker will inform you.

How to use tracker/proxy:

As a server:
1) Run normal triplet server
2) Download proxy.py (http://web.mit.edu/jasperln/web_scripts/download/proxy.py)
3) python proxy.py ServerPort [Description]
4) Check tracker (http://scripts.mit.edu/~jasperln/servers-up.py) to see if you have been added
ServerPort is the port your server listens on. Description is whatever text you want to put. Text with
whitespace should be enclosed in quotes. Html tags are supported. Those behind a NAT (such as SMA iPaqs)
should put their internal IP as well so clients behind same NAT can connect directly. Proxy can be safely
backgrounded or nohup'd. If you leave it open, it displays attempts to contact tracker.

As a client:
Look at tracker (http://scripts.mit.edu/~jasperln/servers-up.py) for available servers. If the IP is public or on the same side of a NAT then you can
connect directly with your ordinary client. Otherwise lookup the server number (it's the number that precedes
the colon) and connect your client to ipaq-63.no-ip.org:2003 instead with the small modification that your
client should send the server number on a line by itself as the first thing it does. This can easily be done
by s.sendall(str(server_number)+"\n"). I recommend modifying your existing client slighty to take an optional
server number argument instead of rewriting one.
This causes your client to connect to iPaq63. The tracker on iPaq63 maintains an open connection with all
servers it's tracking. The tracker then sends a message through this connection to proxy.py running on the
other side. This informs the proxy to connect to the triplet server and open another connection back to the
tracker which joins this connection with the client's connection. All together the connection looks like:
client(local iPaq)--->tracker(iPaq63)--->proxy.py(remote iPaq)--->server(remote iPaq)

Andrew Wang: iPaq60
Address:ipaq-60.no-ip.org
Port: 2020
*Currently Unavailable*
Server should be up all the time. It receives triplets. Please report outages to me, <zephyrus at mit.edu>.

Zhu Tao

My Server is up: IP: 137.132.69.133 Port: 4381 It is a multithreaded server, so do not worry that your message will flood it. :P

Up time: I will try to keep it up 24 hours.

This is a public address so the MIT people will also be able to access it. The server will echo back whatever the client sends and send back my triplet in one line (only will see when your client receives data).

If it is down that means I am restarting. :)

At Singapore

Zahoor Zafrulla (mailto:zahoor.zafrulla@nus.edu.sg)

• Important Note (history!)

Currently on the Singapore side we are facing problems getting the iPAQ's to connect to the NUS network because of LEAP authentication problems. If someone can find the leap authentication module that installs properly on the iPAQ let me know. So for the meantime I suggest we just form a network with the iPAQ's alone just for the Singapore side. The MIT ip 18.95.6.111 is acessible from here and we can exchange tuples successfully . For the moment configure your iPAQ's as follows:

 1. Settings -> Network Setup -> Wlan0
 2. Select static ip and assign an address from the class B address 169.254.xxx.xxx (any ip with the
    prefix 169.254 will do)
 3. Set the Net mask as 255.255.0.0
 4. There is a configure button. Click that and change the ESSID to "SMA" and choose ad-hoc mode
    and your are done 

We dont have to do this now !!. Look at Kok hong's post on how to connect to the NUS network here Connect to NUS OPEN (http://org.csail.mit.edu/mode/index.php/Login_to_NUSOPEN_network_on_iPAQ). Also lookout for Jasperln's post on how to facilitate MIT iPAQ's to connect to iPAQ's on the NUS side. People having problems getting their iPAQ's to connect to the NUS network may use the earlier procedure to test things.

• My Message Server (up)

 IP Address: 172.18.176.140 (this is a NUS internal network ip)
 Port: 5000
 The server sends a triple and optionally receives from client

• Status Server (down)

 IP Address: 172.168.176.140
 Port: 6500
 You can use telnet to communicate with this server, just use as follows: 
   telnet 172.168.176.140 6500

 This server follows a simple protocol
 1. To register you server send a message of the format "100: <servename> <ip:port> <likelytimes>"
 2. To remove your server send a message of the format "200: <servername>"
 3. To enquire about alive servers send a message of the format "300:"

Rudianto Sugiyarto (mailto:g0502261@nus.edu.sg)

• Hi, my message server

 IP Address: 172.18.176.77
 Port: 5080
 The server receive a triplet from client and then send its triplet to the client

Zhu Tao (http://www.zhutao.tk)

• My Server is up:
  

 IP: 137.132.69.133 

 Port: 4381 

 It is a multithreaded server, so do not worry that your message will flood it. :P
 Up time: I will try to keep it up 24 hours. Please report outage to me. Thanks

This is a public address so the MIT people will also be able to access it. The server will echo back whatever the client sends and send back my triplet in one line (only will see when your client receives data).

Currently not available, reinstalling os....

//Received Boylston, Wellington,Porter, Zahoor, Wonderland,Buonavista, Serangoon, Zhou Yu, Huang Xin, Khue and Vikki 's triplets.

Khue Nguyen (mailto:g0502259@nus.edu.sg) Just want to feed back that I have successfully received triplet from: Corey, McCarrey, Evelyn, ZhuTao, Jasper Lin.

Kokhong Cheng (mailto:khcheng@nus.edu.sg)

• My Message Server

 IP Address: 169.254.3.33
 Port: 3000
 The server sends its triplet and waits 3 seconds for the client to send its triplet

• Extra credit

 Connect to port 3001 to READ a list of lines of the form
 <name> <ip> <port>
 <name> <ip> <port>
 ...
 Connect to port 3002 to PUBLISH your address and port information.
 Enter a line of the form <name> <ip> <port>, followed by a new line.
 E.g. khcheng 169.254.3.33 3000
 Blank lines will be ignored. 
 The connection will be closed after a 'valid' line + newline is entered. 
 Connection will also be closed if no input is received for 5 seconds.