![]() For this you can run the applications on different ports, and write IP table rules to bifurcate the traffic between them. I feel that by making two applications run on the same : you want to achieve some kind of load balancing. If however you want to have two applications on same TCP : combination, then the answer is no (An interesting exercise will be launch two VMs, give them same IP address, but different MAC addresses, and see what happens - you will notice that some times VM1 will get packets, and other times VM2 will get packets - depending on ARP cache refresh). One doubt that people have is if two applications are running on the same : combination, how will a client running on a remote machine distinguish between the two? If you look at the IP layer packet header ( ), you will see that bits 72 to 79 are used for defining protocol, this is how the distinction can be made. The concept of port is relevant on the transport layer of the TCP/IP stack, thus as long as you are using different transport layer protocols of the stack, you can have multiple processes listening on the same : combination. You can have two applications listening on the same IP address, and port number, so long one of the port is a UDP port, while other is a TCP port. However, you in most operating systems you can set up several IP addresses on a single interface (e.g., if you have 192.168.1.10 on an interface, you could also set up 192.168.1.11, if nobody else on the network is using it), and in those cases you could have separate applications listening on port 8000 on each of those two IP addresses. The Soulseek client sets up a listening port to accept incoming TCP connections. No, you can't have two applications listening on the same "TCP address," because when a message comes in, how would the kernel know to which application to give the message? To browse a users files, you need to be able to form a network (TCP) connection to that user, and not every two users on Soulseek can connect to each other. You will need to define an HTTP connector in order to. The reason you cannot connect via a browser is that the service listening on 8005 is not HTTP, but rather the default Tomcat listener for issuing management commands (like shutdown). ![]() When a server listens for connections, it can inform the kernel that it would like to listen to a specific IP address and port, i.e., one TCP address, or on the same port on each of the host's IP addresses (usually specified with IP address 0.0.0.0), which is effectively listening on a lot of different "TCP addresses" (e.g., 192.168.1.10:8000, 127.0.0.1:8000, etc.) These values should not be the same, and likely are causing one of the Connectors to fail to start. ![]() When you create a TCP connection, you ask to connect to a specific TCP address, which is a combination of an IP address (v4 or v6, depending on the protocol you're using) and a port.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |