A simple Java Peer-Peer Application
Sharath Chandrashekhara - sc296@buffalo.edu
Sanket Kulkarni - sanketku@buffalo.edu
CSE 589 Project - 1
Echoer is a simple Java Application which echoes the messages it gets on the TCP/UDP connections. Echoer can also make TCP/UDP connection to other Echoer applications running on remote machines and send messages to them. The Application provides a Shell like interface, with the ability to execute the commands enumerated below.
- cd in to root directory of the application and run "make"
- Step 1 will generate *.class files
- To run the application Enter the below command: "java Echoer TCP_port_number UDP_port_number"
- TCP_port_number UDP_port_number are port numbers on which the TCP and UDP servers of the application will listen to. The port numbers should be in the range of 1025 - 65534.
- To quit the application use the command "bye"
- make clean can be used to clean up the work space.
- connect: Establish a TCP connection with a remote machine Usage: connect remote_ip_address port_number
- send: Send a message through an already established connection_ID Usage: send connection_id message
- sendto: Send a UDP message to a remote machine Usage: sendto remote_ip_address port_number message
- disconnect: Disconnect an already established TCP connection Usage: disconnect connection_id
- show: Show all the Outgoing and Incoming connections Usage: show
- info: Displays info about the system Usage: info
- bye: Exits the program gracefully Usage: bye
-
After making a TCP connection to a server, if the Server ends the sessions abruptly, the client continues to show the connection in the show. The connection would be removed only after the client tries to make a unsuccessful send command
-
The logic used in disconnect is:
- The connection_id which is disconnected will be removed from the list and would no longer be displayed in the show command
- The connection_ids of the already established connections would not be disturbed.
- When a next connection is made, the lowest unused connection ID available would be allocated
- When disconnect is issued, message appears on both ends
-
We are using a floating buffer in send command. But in sendto command as it is a UDP connection, we have restricted the buffer size to 1024 bytes
-
The number of incoming and outgoing connections are not restricted. But we have not tested the program for very large number of connections
-
The IP address of the Local machine is obtained by making a DNS call to the google public DNS machine. If the network is not connected to Internet, this will fail.
-
The TCP connections made, have a default connection timeout which depends on the OS (1 min on Linux). This is not changed.
-
UDP connection have a connection timeout of 10 seconds.
-
We are providing an extra feature to the user to gracefully exit the program through bye command. We are taking care of closing all the client sockets. The unclosed server sockets would be reclaimed by the OS.
-
Blocking all loopback addresses ranging from 127.0.0.1 to 127.255.255.254 in connect and sendto commands.
-
As workaround on some Linux machines, notably Debian, 2 hostnames are present in /etc/hosts. We are not considering this scenario.
-
We have considered concurrent access to data structures and using suitable synchronization mechanisms to prevent data corruption.
- Extra whitespaces in commands is handled.
- Extra "Enter" on the Interface is ignored.
- Validity of IP is tested through a RegEx
- Send attempts to unconnected servers is blocked
- Connections to local machine and duplicate machines is blocked
- Port number is validated. We are not allowing to start/connect on well known ports (1-1024)
- TCP and UDP port numbers should be different. This check is added.
- Number of arguments to all commands is validated and suitable error message is shown.
Project is hosted on github : https://github.com/sharathcshekhar/Echoer