Data sharing between PCs
The PC-to-PC data sharing function is a function that allows thilmera, which has become the host, to send display contents from thilmera on other PCs so that they can be checked on the host PC.
There are plans to expand this data sharing function in the future, including audio transfer.
Port settings will not be applied unless you restart thilmera after making changes. (Please specify between 1024 and 65535. It is recommended that people who know how to open ports etc. change the settings).
Although it can be sent to a global IP, it is basically intended for use within an intranet (local network).
Ports need to be opened only on the PC where the server will be set up. (No need to change settings under normal intranet)
Please connect to the intranet PC using a private IP, not a global IP. To check the private IP, open a command prompt with "cmd" and enter "ipconfig".
Since the IP usually changes under management such as DHCP, it is best to communicate using the computer name.
Enter the computer name of thilmera that you want to use as a server or thilmera on the side you want to connect to the IP address, and press Send Data to start a transmission attempt.
For global IP, either host name or IP can be used.
When using a port with a global IP address, do not use the default port number.
Since data sharing does not exchange processing instructions such as commands or statements, this will not cause unexpected program execution.
Ports are isolated from the Internet when used within a normal intranet across a router.
Global IP+When using over the Internet, be sure to configure the firewall settings added from 0b167.
0b167 image transferIn 0b167, I changed the method from transmitting text data to transmitting window images, but this consumes about 1MB/s (8Mbps) of bandwidth if you turn on a sound analyzer etc. that changes the screen frequently. I understand that.
It will depend on future development priorities, but eventually I plan to develop video transfer instead of image transfer.
Specifying the number of simultaneous connections per IPYou can specify between 1 and 8.
For example, if you specify 1, additional communications will not be accepted and will be rejected while one or more connections are being made from the same IP (v4).
Reject connections from problematic IPs for a certain period of timeIf there is a communication with a different format or a different password, the communication will be disconnected and connections from that IP will be refused for a certain period of time.
Communication is also refused if the host and guest are not the same version.
Specify the interval for accepting new connections for each IPSpecifies the number of seconds until the next new connection is accepted for the IP with which communication has been established.
If a new connection is made from the same IP within that time, the communication will be rejected.
Added a denial time when consecutive accesses of denied IPs are made.If an IP that has denied communication is accessed again within the denial time, the specified number of seconds will be added as the denial time.
For example, if you specify 60 for this value, if access from the denied IP continues within 60 seconds, the denial will continue forever.
Specify passwordBy default, this field is blank, and if it is blank, password verification will be skipped.
The specified password will be hashed and sent, but please avoid using passwords that are easily predictable or short and simple.
If host and guest do not have the same password, communication will be refused.
thilmera7allow.ini - Permission/disapproval rulesBy writing to thilmera7allow.ini, you can specify whether or not to allow access using IPv4 and CIDR.
The description rule is [A/a/D/d] [IPv4](/CIDR).
Rules are judged in order from the top, and the judgment ends when the rule is approved or disallowed.
→ Reject all. The last line always has instructions similar to this one.
→ All allowed.
→ Allow connections from addresses from 192.168.0.1 to 192.168.0.254. First and last specified by CIDR. .0 and .255 in this case are rejected.
→ Rejected connection of 192.168.1.10. Other than that, connections from addresses 192.168.0.1 to 192.168.255.254 are allowed.
→ Reject connections from 192.168.1.1/24,192.168.50.1/24 and allow all others.
The following are interpreted as equivalent instructions.