GL-X300B Port Forwarding Configuration: Complete Setup

Port forwarding on the GL-X300B (Collie) enables remote access to devices and services on your local network by redirecting external traffic to specific internal devices. This guide walks you through the complete GL-X300B port forwarding setup, from accessing the firewall menu to configuring and testing your port forward rules.

Port Forwarding Basics on GL-X300B

What is Port Forwarding and Why You Need It

Port forwarding is a networking technique that allows inbound traffic on a specific port to reach a device behind your router’s firewall. Without port forwarding, external computers cannot directly access services running on your internal devices—your router blocks them by default. Port forwarding creates a rule that says: “When traffic arrives on port X from the internet, send it to device Y on my local network listening on port Z.”

Common use cases include hosting an FTP server, running a web server, setting up remote access to security cameras, or enabling game server access. The GL-X300B port forwarding setup allows you to define exactly which external ports map to which internal devices and ports.

Local LAN vs WAN Access Differences

Understanding the difference between LAN and WAN access is critical for port forwarding. Your Local Area Network (LAN) includes all devices connected to your GL-X300B—computers, phones, printers, and servers on your network. Your Wide Area Network (WAN) is the internet outside your router. Port forwarding creates a bridge between these two zones.

When you set up port forwarding on the GL-X300B, you specify both an External Zone (WAN—where traffic comes from) and an Internal Zone (LAN—where traffic goes). This tells the router to listen on the external zone for incoming connections and forward them to the internal zone. Devices on your local network can typically reach internal services without port forwarding, but remote users cannot.

Security Considerations for Exposed Ports

Opening ports exposes services to the internet, which increases your attack surface. Follow these security practices when configuring GL-X300B port forwarding:

• Use non-standard ports when possible—Instead of port 80 for HTTP, try port 8080. This reduces automated attacks targeting default ports.
• Change default passwords—Any service you expose must have a strong, unique password.
• Disable unnecessary services—Only forward ports for services you actively use.
• Monitor logs—Regularly check access logs on exposed services.
• Use VPN for sensitive access—Consider VPN instead of port forwarding for administrative access.
• Keep firmware updated—The GL-X300B receives security patches through firmware updates.

Accessing Port Forwarding Settings

Navigating to Firewall Menu

To begin your GL-X300B port forwarding configuration, log into the web admin panel by opening a browser and visiting http://192.168.8.1. Enter your admin password (the one you set during initial setup—minimum 5 characters). Once logged in, you’ll see the main dashboard.

Look for the FIREWALL menu option in the left navigation panel. Click it to expand the firewall options. The firewall section contains three main subsections: Port Forwards, Open Ports on Router, and DMZ. For remote access port mapping, you’ll use the Port Forwards section.

Port Forwards Tab Location

After clicking FIREWALL in the menu, select Port Forwards from the submenu. This opens the Port Forwards interface where all your existing rules appear in a table format. The table displays columns for:

• Name—Your custom rule name
• Protocol—TCP, UDP, or both
• External Ports—The port(s) the internet connects to
• Internal IP—The LAN device receiving traffic
• Internal Ports—The port on the internal device
• Status—Enabled or disabled toggle

Adding a New Port Forward Rule

On the Port Forwards page, look for the button labeled “Add a New One” or a “+” icon. Click it to open the port forward configuration form. This form contains all the fields needed to define a port forwarding rule. Each field corresponds to a parameter in the rule table—you’ll fill these in to create your mapping from external to internal ports.

Configuring Port Forward Parameters

Assigning Rule Names

The Name field accepts any custom text you choose. Use descriptive names that identify the service and its purpose. Examples:

• “FTP Server Main”
• “Web Server Port 80”
• “Game Server”
• “Security Camera Stream”
• “Remote Desktop PC-01”

Good naming conventions help you manage multiple rules without confusion. If you have several port forward rules, clear names make troubleshooting and updates much easier. Avoid generic names like “Rule 1” or “Test”—you won’t remember what they do in 3 months.

Selecting Protocol: TCP, UDP, or Both

The Protocol field determines which communication protocol the rule applies to. The GL-X300B port forwarding setup offers three options:

If you’re forwarding a standard service (web server, FTP), check the service documentation to determine the correct protocol. For example, HTTP uses TCP port 80, while DNS uses UDP port 53. If a service uses both (like some gaming protocols), select “Both” to ensure it works correctly.

Defining External and Internal Zones

The External Zone and Internal Zone fields define which network interfaces the rule applies to. In most home and small office setups, these are automatically set correctly:

• External Zone (WAN)—The internet-facing side. This is where incoming traffic arrives. Leave this as the default WAN zone in most cases.
• Internal Zone (LAN)—Your local network. Leave this as the default LAN zone.

In advanced scenarios where your GL-X300B has multiple WAN connections or unusual network setups, you might configure different zones. For standard port forwarding, the default zones work correctly and require no changes.

Entering External Port Numbers and Ranges

The External Ports field specifies which port(s) on the internet-facing side the router listens on. You have two options:

Single Port: Enter a specific port number like “80” or “21”. The router listens on this one port and forwards matching traffic.

Port Range: Enter a range using a hyphen, such as “100-300”. This creates a rule that forwards all ports from 100 to 300 (inclusive). Port ranges are useful for applications that use multiple ports or when you want to forward a block of sequential ports.

Important considerations:

• Avoid ports 1-1023 if possible (system ports).
• Don’t use ports already in use by the router itself (web interface on 80/443, DNS on 53, DHCP on 67-68).
• Choose ports above 1024 for custom services.
• If forwarding to port 80 (HTTP), ensure your ISP doesn’t block it. Many residential ISPs block port 80.

Setting Internal IP and Port Mapping

Finding Your Device’s Internal IP Address

The Internal IP field requires the local IP address of the device you want to forward traffic to. This is the IP address assigned by the GL-X300B’s DHCP server to your device on the LAN.

To find your device’s internal IP address:

Option 1: Check the CLIENTS page

1. Log into the GL-X300B admin panel
2. Click CLIENTS in the left menu
3. Find your device in the list—it shows device name, IP address, and MAC address
4. Copy the IP address (format: 192.168.8.X)

Option 2: Check on the device itself (Windows)

1. Open Command Prompt (cmd)
2. Type “ipconfig” and press Enter
3. Find “IPv4 Address” under your network adapter—this is your internal IP

Option 3: Check on the device itself (Mac/Linux)

1. Open Terminal
2. Type “ifconfig” and press Enter
3. Find “inet” address—this is your internal IP

Record the IP address. Important: If your device uses DHCP (automatic IP assignment), its IP address may change when it reconnects or restarts. For critical services, assign a static IP to the device to prevent the IP from changing.

Mapping External to Internal Ports

The relationship between External Ports and Internal Ports defines the actual mapping. In most cases, you’ll map the same port number from external to internal:

• External Port 80 → Internal Port 80 (web server)
• External Port 21 → Internal Port 21 (FTP server)

However, you can map different external and internal ports. For example:

• External Port 8080 → Internal Port 80 (forward internet port 8080 to internal web server on port 80)
• External Port 2222 → Internal Port 22 (forward internet port 2222 to SSH on internal port 22)

This flexibility lets you expose a service on a non-standard external port while the internal device runs on a standard port. This is useful for security (hiding which service runs on which port) and for avoiding ISP port blocking.

Leaving Port Blank When Ports Match

The GL-X300B port forwarding setup includes a convenient feature: if your external and internal port numbers are identical, you can leave the Internal Ports field blank. The manual states: “Leave it blank if it is same as the external port.”

Example: If you enter External Ports “80” and want to forward to Internal Ports “80” on your device, simply leave the Internal Ports field empty. The router interprets a blank internal port as matching the external port.

This reduces typing and potential errors when the port numbers are the same.

Multiple Devices on Same Rule

Each port forward rule maps to exactly one internal IP address and port combination. If you need to forward the same external port to multiple internal devices, you must create separate rules—one for each destination device. The GL-X300B doesn’t support load balancing or round-robin distribution of a single port across multiple devices through the port forwarding interface.

However, you can forward different external ports to the same internal device on different internal ports. For example:

• External Port 8001 → 192.168.8.50:8001
• External Port 8002 → 192.168.8.50:8002
• External Port 8003 → 192.168.8.51:8003

Practical Port Forwarding Examples

Web Server Port 80 Forwarding

Setting up a web server accessible from the internet is a common use case. Here’s the exact configuration:

Important note: Many ISPs block port 80 for residential accounts. If this rule doesn’t work, try forwarding external port 8080 to internal port 80 instead, then access your web server via http://yourip:8080.

FTP Server Port 21 Configuration

FTP (File Transfer Protocol) requires specific port forwarding. Here’s the configuration for a GL-X300B FTP server port opening:

Additional consideration: FTP also uses port 20 for data transfer in active mode. Modern FTP clients use passive mode, which only requires port 21. However, if your FTP server requires active mode support, create an additional rule forwarding port 20.

Custom Application Port Ranges (100-300)

Some applications use multiple consecutive ports. Here’s how to set up port range forwarding on your GL-X300B:

When you leave Internal Ports blank with a port range in External Ports, the GL-X300B automatically maps the same range internally. External port 100 goes to internal port 100, external 101 to internal 101, and so on through 300.

If your internal server uses a different port range, you must enter it explicitly. For example, if your game server listens on ports 200-400 internally but you want to expose it as 100-300 externally, enter “200-400” in the Internal Ports field.

Activating and Testing Rules

After entering all parameters, click Apply or Submit to save the rule. The rule appears in the Port Forwards table with a Status toggle. Ensure the toggle is enabled (usually a green checkmark or ON state).

To test your port forwarding:

1. Test from external network: Use a phone on mobile data (not connected to your Wi-Fi) to access your service using your external IP and port. For example, visit http://123.45.67.89:8080 in your browser.
2. Check from another network: Ask a friend outside your network to test the connection.
3. Use online port checking tools: Websites like canyouseeme.org or portchecker.co can verify if a port is open and reachable.
4. Check logs on your service: If you have logs on your web server or FTP server, verify that external connection attempts appear in the logs.

If testing fails, verify:

• The internal device’s IP address hasn’t changed (assign static IP if needed)
• The service is running on the internal device
• The port number in the rule matches the port the service listens on
• Your ISP hasn’t blocked that port (try a different port)
• The rule is enabled (status toggle is ON)

Troubleshooting Port Forwarding Issues

Port Rules Not Taking Effect

If you’ve created a port forward rule but it’s not working, the rule may not be active. Check the following:

1. Verify the rule is enabled: Open the Port Forwards page and look at the Status column. Each rule has a toggle—confirm it shows enabled (green/ON state). A disabled rule won’t forward any traffic, even if correctly configured.

2. Confirm the rule was saved: After clicking Apply, the rule should appear in the table immediately. If you don’t see it in the list, the save failed. Try adding it again and watch for any error messages.

3. Check if another rule conflicts: If you have multiple rules, ensure none have overlapping ports. For example, don’t create two rules both using external port 80. The GL-X300B will apply the first matching rule and ignore others.

4. Verify the internal device is reachable: On your local network, test if you can reach the internal device and its service directly. From another computer on your LAN, try connecting to 192.168.8.50:80 (if that’s your internal IP and port). If the local connection works but remote doesn’t, the problem is in the port forwarding configuration. If local access fails, the problem is with the internal service, not the router.

Connection Timeout Errors

When remote users experience timeout errors (“Cannot connect” or “Connection timed out”), the router is receiving the connection attempt but traffic isn’t reaching the internal device. Debug this:

1. Verify the internal IP address: Open CLIENTS and confirm the internal device is listed with the same IP you entered in the port forward rule. If the IP is different (e.g., the device reconnected and got a new DHCP address), update the rule with the correct IP.

2. Confirm the service is running: On the internal device, verify the service is running and listening on the correct port. From the device itself, test local access (e.g., http://127.0.0.1:80 or http://localhost:80). If the service isn’t responding locally, it’s not running or listening.

3. Check the protocol: Ensure you selected the correct protocol (TCP vs UDP). If your service uses TCP and you selected UDP, traffic won’t reach it. Most standard services use TCP.

4. Test with a different port: Create a test rule using a different external port (e.g., 9999 instead of 80) pointing to the same internal device. This rules out ISP port blocking on specific ports. If the new port works, your ISP likely blocks the original port.

5. Check if a firewall on the internal device is blocking traffic: The internal device itself may have a local firewall (Windows Firewall, iptables, etc.) that blocks incoming connections on the port. Temporarily disable the local firewall on the internal device and test. If it works, configure the local firewall to allow traffic on that port.

Checking External Zone Configuration

The External Zone field determines which WAN interface the rule applies to. In most home setups, you have one WAN connection and the default External Zone (typically labeled “WAN” or “wan”) is correct. However, if your GL-X300B has multiple WAN connections (redundant connections, failover, etc.), verify you selected the right zone.

To check your WAN connection:

1. Go to INTERNET in the admin panel
2. Note which connection type is active (Cable, Repeater, or 3G/4G Modem)
3. Return to Port Forwards and confirm the External Zone matches your active connection

If you’re using a Cable (Ethernet) connection to the WAN port, the External Zone should be set to “WAN” (or whatever label the router uses for that port). The Internal Zone should remain “LAN”.

Verifying Internal IP Hasn’t Changed

DHCP assigns IP addresses dynamically, meaning an internal device might receive a different IP address after restarting or reconnecting. If your port forward rule suddenly stops working, the most common cause is a changed internal IP address.

Solution 1: Assign a static IP to the device

This is the best long-term fix. Configure your device to use a static (fixed) IP address instead of DHCP:

Windows:

1. Go to Settings → Network & Internet → Change adapter options
2. Right-click your network adapter → Properties
3. Select “Internet Protocol Version 4 (TCP/IPv4)” → Properties
4. Select “Use the following IP address” and enter:
   IP Address: 192.168.8.50 (or any address in your LAN range)
   Subnet Mask: 255.255.255.0
   Default Gateway: 192.168.8.1
   Preferred DNS: 192.168.8.1
5. Click OK

Mac/Linux:

1. Open System Preferences → Network
2. Select your connection → Advanced
3. Go to TCP/IP tab
4. Change “Configure IPv4” to “Manually”
5. Enter IP, subnet mask, router (gateway) as above
6. Click OK

Solution 2: Reserve the IP in the router’s DHCP settings

Some routers allow you to reserve a DHCP IP for a device based on its MAC address, so it always receives the same IP. Check if your GL-X300B admin panel has a “DHCP Reservation” or “Reserved IP” option.

Solution 3: Manually update the rule

If the device’s IP changes infrequently, periodically check the device’s current IP and update the port forward rule accordingly. Open CLIENTS to see the device’s current IP, then edit the Port Forwards rule with the new IP.

Frequently Asked Questions

Can I forward the same external port to multiple internal devices on the GL-X300B?

No, each port forward rule maps one external port (or port range) to one internal IP address and port. The GL-X300B doesn’t support port sharing or load balancing through port forwarding rules. If you need to forward one external port to multiple devices, you must use more advanced techniques like a reverse proxy or load balancer running on an internal device, which then distributes traffic to multiple backends. Alternatively, forward different external ports to different internal devices, e.g., external port 8001 to device A and external port 8002 to device B.

What’s the difference between “Port Forwards” and “Open Ports on Router”?

Port Forwards (6.1) redirects external traffic to internal devices on your LAN. Open Ports on Router (6.2) opens ports directly on the router itself to expose the router’s own services (like its web interface, FTP server running on the router, etc.) to the internet. For remote access to devices behind your router (like a home server), use Port Forwards. For exposing services running on the router itself, use Open Ports on Router.

Why is my port forward working on my local network but not from the internet?

If you can access your service internally (192.168.8.50:80 from another device on your LAN) but not externally (your-external-ip:80 from outside), the issue is typically: (1) Your external IP is correct and the port forward rule exists, but (2) your ISP is blocking that port. Try forwarding to a different external port above 1024. Additionally, test from a mobile device on cellular data (not your home Wi-Fi) to truly test external access. Some routers don’t support “hairpin” NAT, which prevents local devices from accessing port-forwarded services using the external IP from within the network.

Can I use port forwarding for HTTPS (port 443)?

Yes, create a port forward rule with External Ports “443” and Protocol “TCP” pointing to your internal device on port 443 (or a different internal port if you want). However, port 443 (HTTPS) is frequently blocked by ISPs on residential connections. If blocked, forward external port 8443 to internal port 443, then access your service via https://yourip:8443. Ensure your internal device has a valid SSL certificate; browsers will reject connections with certificate warnings.

How do I test if my port forwarding is working without accessing it remotely?

Use an online port checking tool like canyouseeme.org or portchecker.co. Enter your external IP address and port number, and the tool will attempt to connect from its servers (outside your network) and report whether the port is open and accepting connections. This confirms the port forward is working before you attempt to run an actual service. Alternatively, temporarily enable SSH on port 22 (or change it to a test port) and try connecting from a remote machine using a terminal.