Table of contents
2.1. Inbound rules and outbound rules
2.3. Steps to create a new inbound rule
1. Shared files
Collaboration and team work:
- Sharing files is key to collaboration and team work. Multiple people can access and edit shared files at the same time, promoting real-time collaboration and improving work efficiency.
Real-time updates and synchronization:
- Shared files are often stored in the cloud, allowing files to be synchronized between different devices in real time. This ensures that team members have access to the latest versions of files at any time and from any location.
Convenient file access:
- Shared files allow users to access files from different devices and locations, all they need is an internet connection. This is very important for people who work remotely, travel for business or work on the move.
version control:
- Shared file platforms usually provide version control functions that can track the modification history of files. This makes it easy to go back to previous versions and prevents data loss due to misuse.
Reduce data redundancy:
- On a shared file platform, team members can work directly on the same file without having to create multiple copies. This helps reduce data redundancy and avoid confusion and inconsistency.
Security and permission control:
- Shared file platforms often provide security and permission control features that can limit access to and editing of files. This ensures that sensitive information can only be accessed by authorized personnel and prevents unauthorized modification.
Save storage space:
- Cloud storage services usually offer large amounts of storage space, which means users don’t need to worry about local storage space limitations. This is very beneficial for the storage of large files and data sets.
IM:
- Some shared file platforms integrate instant messaging and comment functions, allowing team members to communicate, provide suggestions, and discuss directly on files.
Snapshot usage:
Create a snapshot:
- In virtual machine management software, snapshots can be created manually. Typically, an initial snapshot can be created when the virtual machine is in a stable state, such as when the operating system has just been installed and applications have been configured.
Backup and rollback:
- Snapshots provide a convenient backup mechanism. Before making major changes to a virtual machine or installing new software, a snapshot can be taken and if subsequent actions cause problems, it can be easily rolled back to the previous state.
Testing and development:
- Snapshots are very useful during software development and testing. Developers can conduct experiments on virtual machines. If a problem occurs, they can quickly roll back to the previous state to improve development efficiency.
Virtualization experiment:
- When you need to test new virtualization configurations, network settings, or other system changes, you can experiment after creating a snapshot. If an experiment fails, you can easily revert to a previous state.
Security updates and configuration changes:
- It is a good practice to create a snapshot before making security updates or important configuration changes to a virtual machine. If updates or changes cause system problems, they can be quickly restored.
Multiple environment testing:
- For testing teams, snapshots allow multiple test environments to be run on the same virtual machine without having to create an entirely new virtual machine for each environment.
Performance optimization:
- When optimizing the performance of a virtual machine, you can create snapshots on different configurations, compare their performance, and find the best configuration.
Quick recovery:
- In a production environment, if a virtual machine encounters a problem, administrators can quickly restore to a previous snapshot, reducing system downtime.
Although snapshots offer many advantages, there are some caveats:
- Snapshots take up storage space, so snapshots that are no longer needed need to be cleaned up regularly.
- Keeping too many snapshots for an extended period of time may impact performance.
- When creating a snapshot, it is best to do it when the virtual machine is powered off or in a stable state to ensure consistency.
Ordinary file:
Basic attributes: Ordinary files are files of a general nature, which may include documents, images, audio, videos, etc. They have no special permissions or version control.
Access permissions: Access permissions for ordinary files are usually based on general file sharing rules, such as read, write, and delete permissions. These permissions may be assigned by the file owner or administrator.
Version management: Ordinary files may lack detailed version management functions. Generally, only the latest file version can be viewed, and it is not easy to track the file modification history.
Sharing scope: Common files may be shared publicly or restricted to specific teams or individuals.
Advanced files:
Version Control: Advanced files often have more advanced version control features. This means that the modification history of a file is tracked, and users can view previous versions, revert to a specific version, and even compare differences between different versions.
Refined access permissions: Advanced files may allow more granular permission settings, such as permissions based on folder structure, user group permissions, read-only permissions, etc. This helps manage access to files more flexibly.
Audit function: Advanced files may provide audit functions to record the file's access history, modification history, and who made what changes.
Workflow integration: Some advanced file systems may integrate workflow management to allow files to flow more smoothly within the team, such as the document approval process.
Automation features: Advanced file systems may support automated tasks such as automatic backups, automatic archiving, automatic notifications, etc. to increase team efficiency.
Advanced search capabilities: Advanced file systems may have more powerful search capabilities, allowing users to more easily find the files they need, including full-text search, tag search, etc.
Enter your \\ plus IP address on the host to view your shared files
2. Firewall settings
2.1. Inbound rules and outbound rules
Inbound Rules:
Destination is local system: Inbound rules control traffic flowing into the system, that is, rules whose destination is the local computer or network. These rules govern the flow of data from an external network (such as the Internet) to your local system.
Security controls: Inbound rules can limit what types of data and requests are allowed into the local network. This prevents unauthorized access, malicious attacks, or harmful data from entering the system.
Typical setup: Inbound rules might include allowing specific types of incoming traffic on specific ports, such as allowing a web server to receive HTTP (port 80) or HTTPS (port 443) requests.
Protect internal networks: Inbound rules can also be used to protect internal networks from external threats. Potential security risks can be reduced by allowing entry only from specific sources or following specific protocols.
Outbound Rules:
Originate from local system: Outbound rules control traffic that originates from the local system, that is, rules that originate from the local computer or network. These rules govern the flow of data from the local network to the external network.
Security and Privacy Controls: Outbound rules can limit what types of data and requests are allowed to leave the local network to ensure there is no disclosure of sensitive information or unauthorized data transfer.
Typical setup: Outbound rules might include allowing a specific application or service to send data to the external network through a specific port, such as allowing an email client to send email using SMTP (port 25).
Prevent malicious behavior: Outbound rules can also be used to prevent devices that have infected internal systems from spreading malware or launching attacks.
Inbound rules and outbound rules are part of the firewall configuration and are used to manage the incoming and outgoing network traffic to enhance network security and protect the system from potential threats. These rules are set based on actual needs to balance the needs between security and network functionality.
2.2.Case demonstration
First turn off the remote settings:
At this time, the host's tomcat can still be accessed:
Then we checked the firewall status and found that it was closed:
At this time, if we open the firewall, the host's Tomcat will fail to access:
2.3. Steps to create a new inbound rule
Right-click the inbound rule to create a new rule:
Open port 8080:
Set allowed connections:
Add rules and descriptions:
At this point, you can access Tomcat8080 port with the firewall turned on.
