Introduction

HeadSpin & # x27; s introduce a groundbreaking feature called the HS Tunnel. This characteristic enables secure connections between HeadSpin devices and local or staging environments, benefiting organisation, teams, and individual users.

This blog situation dives into the HS Tunnel, exploring its feature and providing easy-to-follow instructions for seamless usage.

Understanding HS Tunnel: What You Need to Know

The HS Tunnel feature in HeadSpin facilitates routing network traffic from outside HeadSpin devices through your local network. This tool opens up the possibility of access intranet services and other resources to test a device within the local network immediately from your.

Common scenario where users leverage this puppet include:

• Testing applications with intranet resources
• Trying out non-public variation of apps
• Configuring ad-hoc regional routing to try devices within network locations

With HS Tunnel, you can seamlessly integrate your testing environment with your local net resources, enhancing your testing capacity effortlessly.

Unlocking the Functionality of HeadSpin Tunnel

• Connecting Remote Devices to Client Networks: When a guest requires the remote device to be on the same network, HeadSpin Tunnel comes to the rescue. For instance, when a test covering operates solely within a customer & # x27; s intranet or expect approach to data on a company meshwork, the tunnel enables the remote device to join the client & # x27; s meshing where the Command Line Interface (CLI) is running.
• Installation and Setup: Clients can install the CLI on any server or laptop connected to their meshing. This let routing web traffic from remote devices and admittance to the same network seamlessly, bridge the gap between testing environments and client networks effortlessly.
• Network Log Capture: HeadSpin Tunnel widen its functionality to capturing network logs using tools like Charles. When the remote test device must be on the same network as the device running Charles, the burrow facilitates this connection, enabling efficient network log analysis and debugging.
• Accessing Hosted Servers: Another valuable use suit is accessing servers hosted on specific machines. Clients can efficiently relate their remote devices to the network and access the desired server instance by providing the IP address of the hosting machine and use the burrow.

HeadSpin Tunnel offers versatile answer for integrating distant testing environments with node networks, ensuring unlined testing experiences and enhanced collaboration.

Read:

Using HS Tunnel: Key Information

• Command Usage: To utilize the HeadSpin Tunnel creature, use the main commandhs tunnelvia the HeadSpin Command Line Interface (CLI). Ensure you have the latest CLI version available for download on the User Settings page under & # x27; Downloads & # x27; for optimal performance.
• Pre-requisites: HeadSpin Tunnel is contrive for sessions enchant network data. Therefore, the network data should be enamour before utilize the HS tunnel instrument. Ensure your organization & # x27; s permissions are right configured, specially thetunnel_featureorg permission. To acquire more about configure networks outside of a capture session, delight refer to our documentation on network formation, which is available.
• Configuration Options: The HS Tunnel tool offers tractability with multiple upstream path for raw traffic and DNS resolution. Configure these itinerary using the--proxy and --dnsoptions, along with rules evaluated using-- proxy-rule and -- dns-rule. Define the telescope of access using the--scopeoption, ranging from user to establishment level.
• Priority of Usage: Properly configured HS Tunnel to automatically route network traffic remotely during network capture. Routes are prioritise in deign order: user-scoped, team-scoped, and org-scoped tunnels. Multiple tunnels can coexist for redundancy or to serve different meshwork portions.
• Team and Org Configurations: Teams or brass can set up tunnels for corporate use, streamline accession without individual configuration. Utilize the-scopeflag to achieve this. Refer to the for farther details on available iris.
• Limitations: Currently, HS Tunnel has limited compatibility with browser, as DNS request are not route through tunnels. Testing networking service via HS Tunnel in browsers may require public DNS. Additionally, check compatibility with meshwork surroundings expend proxies or firewalls, as additional steps may be necessary to ensure correct functionality within your network & # x27; s protection parameters.

Prerequisites: Installing the HS CLI Tool

To start using the HS Tunnel, you must install the HS CLI creature, which is uncommitted for MAC, Linux, and Windows. Follow these steps to download and establish the instrument:

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

1. Accessing Settings:Click on your name and Org gens at the top right corner of the UI.

2. Navigating to Settings:From the drop-down menu, select & quot; Settings. & quot;

3. Downloading the CLI Tool:Scroll to the bottom of the Settings page, where you & # x27; ll find the CLI tool link. Choose the suitable version for your OS (MAC, Linux, or Windows) and continue with the installation process.

4. Verifying Installation:After installation, confirm if you have the modish version of the CLI instrument by typing& quot; hs -V & quot;in your pole.

After instal the CLI tool, you can pioneer the HS Tunnel.

5. Ensuring API Server Configuration:Ensure the API server is configured properly before using the tunnel. If you encounter an authorization error, try running the command provided below.

hs config server https: //api-dev.headspin.io

Also read:

Using the Tunnel Tool: Step-by-Step Instructions

1. Download the CLI:Make sure you have the CLI downloaded, as you & # x27; ll need it to execute bidding.

2. Select Device and Start Session: Choose a device from your organization & # x27; s device list and begin a session on that device. Once the remote-control session commence, tick the & # x27; Tools & # x27; icon in the right-hand sidebar. Scroll downwardly to find the Local Environment Tunnel box on the Remote-Control window & # x27; s tools page.

3.Activate Network Capture:In the upper-right corner of the Remote-Control window, click the second icon from the left, resembling a camera. A drop-down menu will appear with two recording options; choose & # x27; With Network. & # x27; This activates net capture for your session, which is essential for the HS Tunnel tool. If you don & # x27; t see this option, ascertain your organization & # x27; s permissions are correctly set by consulting your org and HeadSpin administrators.

4. Configure Tunnel Options: Modify your tunnel & # x27; s settings either through the drop-down option in the Local Environment Tunnel box on the UI or by using API commands.

5. Check IP Addresses: Verify your twist & # x27; s and local machine & # x27; s IP addresses. This verification ensures that your tunnel & # x27; s contour is applied correctly. You can find your IP address use online puppet like whatismyipaddress.com.

6. Execute Tunnel Command: Copy thehs tunnelcommand from the Local Environment Tunnel box and paste it into your CLI. Run the command. Upon checking your twist & # x27; s IP address, it should now match your local machine & # x27; s IP, rather than the twist & # x27; s geographical location.

Check:

Running the HS Tunnel

Executing the HS burrow is a square process. Follow these simple instructions:‍

1. Access Device Tools: Open your device and navigate to the Tools tab for Android device or the Overview tab for iOS device.

2. Set Tunnel Rules:Configure the rules and conditions in the & quot; Local Environment Tunnel & quot; section. This return a bidding that can be executed via the bidding line.

3. Copy and Run Command: Copy the render command and paste it into your terminal. Execute the command to initiate the burrow.

‍4. Verification: Confirm the connection of hosts by comparing the hosts displayed in the terminal with those listed in the UI. Each device & # x27; s hostname can be base on the right side under the & quot; Hostname & quot; column.

Once all horde are connected to your local machine, start the device you wish to connect to your local environment and click the capture button.

Upon snap the capture push, you & # x27; ll hold two options: & quot; With Network & quot; and & quot; Without Network. & quot; Choose & quot; With Network & quot; to connect your device and your local surround.

After discharge these measure, control the public IP address on the cloud gimmick. It should display the IP speech of your home or office network.

Bottom Line

In conclusion, the HS Tunnel feature by HeadSpin marks a significant leap forward in testing and development processes. With its, exploiter can effortlessly connect their devices to local networks, enabling effective testing and debugging. The unproblematic setup process, from downloading the CLI instrument to executing burrow commands, ensures accessibility for all users.

Moreover, HS Tunnel offers advanced functionalities like network shaping and configuration pick, raise testing precision. While users must be mindful of compatibility with existing network environments, proactive collaboration with administrator can palliate challenges. In essence, HS Tunnel empowers users to transcend geographic boundary and streamline testing environment, foster innovation in software development and user experience.

FAQs

Q1. What sets porthole forwarding apart from tunneling?

Ans:Port forwarding directs traffic from one port to another on the same or remote devices, while tunneling encapsulates data from one network protocol into another.

Q2. How do user tunnels differ from twist tunnels?

Ans:Device burrow connect to designated VPN server before exploiter logins, serve pre-login connectivity and device management motivation. In contrast, user tunnels establish connections after user logins, enabling admittance to organizational resources via VPN servers.

4 Parts

Connet Now