IOGear GWU637 Ethernet-2-WiFi Adapter Setup Guide

This guide covers setting up the IOGear GWU637 Universal Wireless-N Adapter as a WiFi-to-Ethernet bridge on Linux and OS/2 Warp, with easy reconfiguration for different networks.

Sources: ManualsLib · manuals.plus · usermanual.wiki

Hardware Overview

The GWU637 operates in client/bridge mode: it connects to an upstream WiFi network and provides a standard Ethernet port to your device. Your machine sees an ordinary wired connection regardless of which WiFi the adapter is bridging.

Default device settings:

Web UI IP: 192.168.1.254
Subnet mask: 255.255.255.0
Default credentials: username and password are blank (leave both fields empty)

- Some firmware versions use admin / admin — try blank first, then admin/admin if blank fails

LED indicators:

LED	Behavior
WLAN	Flashes during wireless data activity; off when idle
Ethernet	On when port is linked; flashes during data transfer
WPS/Reset	Flashes when WPS is active

Browser compatibility warning: The GWU637 web UI's wireless site survey function does not work in Chrome or standard Edge. Use Firefox or Internet Explorer / Edge in IE compatibility mode to configure the adapter.

Factory Reset (GWU637)

Perform a factory reset before initial setup or when switching deployments.

Power on the device and wait ~30 seconds for it to fully boot.
Locate the RESET pinhole on the device body (shared with the WPS button on some units).
With the device powered on, insert a straightened paperclip into the RESET hole.
Hold for 5–10 seconds until the WPS/Reset LED flashes, then release.
The device will reboot. Wait ~60 seconds for it to fully restart.
The device is now restored to factory defaults (192.168.1.254, blank credentials).

Connecting to a New WiFi Network (Reconfiguration)

Each time you want to bridge a different WiFi network, follow this process.

Step 1 — Assign a Static IP on Your Machine

Connect your computer to the GWU637 via Ethernet cable.

On Linux:

# Find your Ethernet interface name
ip link show

# Assign a temporary static IP in the GWU637 subnet
sudo ip addr add 192.168.1.100/24 dev eth0   # replace eth0 with your interface
sudo ip link set eth0 up

On OS/2 Warp:

Open a command prompt:

ifconfig lan0 192.168.1.100 netmask 255.255.255.0

Or open the TCP/IP Configuration notebook in the System Setup folder, set your LAN adapter to IP 192.168.1.100, subnet mask 255.255.255.0, then restart the TCP/IP stack.

Step 2 — Log in to the Web Interface

Open a browser (Firefox on Linux; WebExplorer or Netscape on OS/2 Warp) and navigate to:

http://192.168.1.254

At the login prompt, leave both username and password blank and click Log In. If that fails, try admin / admin.

On Linux, if Firefox is not installed: ```bash

Debian/Ubuntu

sudo apt install firefox-esr

Fedora

sudo dnf install firefox ```

Step 3 — Scan for and Select a WiFi Network

The configuration utility loads in the browser.
Click Search (or Site Survey) to scan for nearby networks.
The Wireless Site Survey window opens, listing available SSIDs with signal strength and encryption type.
Select your target network and click Done.

Step 4 — Enter the WiFi Password

Confirm the Encryption type in the dropdown matches your network (WPA2-PSK is most common).
Enter the WiFi password in the Key or Password field.
Click Apply to save the settings.

Step 5 — Finish and Wait for Reboot

Click Finish to apply the configuration.
The adapter will reboot for approximately 90 seconds.
During reboot the Ethernet link will drop briefly — this is normal.
Once complete, the Wireless Connection status changes to ACTIVE and the WLAN LED will flash with traffic.

Step 6 — Switch Your Machine Back to DHCP

After the adapter reboots, remove the static IP and let the GWU637 forward a DHCP lease from the upstream WiFi router.

Linux:

# Remove the static IP
sudo ip addr del 192.168.1.100/24 dev eth0

# Request a DHCP lease
sudo dhclient eth0
# or with NetworkManager:
nmcli device connect eth0

OS/2 Warp:

In TCP/IP Configuration, switch the LAN adapter back to DHCP, then restart TCP/IP:

stop tcpip
start tcpip

Or simply reboot.

Linux — Full Setup Notes

Persistent DHCP Configuration

To avoid manually reconfiguring the interface each session, set the wired interface to DHCP in your network manager. Once the GWU637 is bridging a network it will pass through DHCP leases automatically.

NetworkManager:

nmcli connection modify "Wired connection 1" ipv4.method auto
nmcli connection up "Wired connection 1"

systemd-networkd — create /etc/systemd/network/20-wired.network:

[Match]
Name=eth0

[Network]
DHCP=yes

sudo systemctl enable --now systemd-networkd

WPS Alternative (Push-Button Setup)

If the target router supports WPS push-button pairing, you can skip the web UI entirely:

Press the WPS button on the GWU637 (the WPS/Reset LED will flash).
Within 2 minutes, press the WPS button on the WiFi router.
The devices will negotiate and connect automatically.
Set your machine to DHCP on the Ethernet interface — no web UI access needed.

Verifying Connectivity

# Check that an IP was assigned
ip addr show eth0

# Test internet access
ping -c 4 8.8.8.8

OS/2 Warp — Full Setup Notes

Requirements

OS/2 Warp 3 or 4 with IBM TCP/IP for OS/2 or MPTS installed.
A supported Ethernet NIC with an OS/2 NDIS 2 driver.

Browser for the Web UI

OS/2 Warp 3: WebExplorer (launch from the Internet folder or run EXPLORE.EXE).
OS/2 Warp 4: Netscape Navigator (included in the BonusPak) is preferred as it renders the GWU637 UI more reliably than WebExplorer.

Both browsers can access http://192.168.1.254 for configuration. The GWU637 web UI is simpler than many modern pages and renders adequately in both.

Static IP for Setup

In the TCP/IP Configuration notebook:

Select your LAN adapter.
Set IP Address to 192.168.1.100, Subnet Mask to 255.255.255.0.
Clear any default gateway entry (not needed for setup).
Save and restart TCP/IP or reboot.

Switching Back to DHCP After Setup

Re-open TCP/IP Configuration.
Enable Obtain IP address automatically (DHCP) for your LAN adapter.
Save and restart TCP/IP:

``[C:\] stop tcpip [C:\] start tcpip`` Or reboot — OS/2 Warp's TCP/IP stack sometimes requires a full reboot for DHCP to activate.

Verifying Connectivity on OS/2 Warp

ping 8.8.8.8

If ping is unavailable, use netstat -r to confirm a default route was received via DHCP, or try loading a web page in Netscape/WebExplorer.

Troubleshooting on OS/2 Warp

If http://192.168.1.254 does not load, run ifconfig lan0 to confirm the static IP 192.168.1.100 is active.
If the NIC is not detected, open MPTS (\IBMCOM\MPTS.EXE) and verify the NDIS 2 driver is bound to the adapter.
Some OS/2 TCP/IP versions do not honor DHCP without a reboot — if the machine has no IP after switching back, reboot.

Quick-Reference: Changing Networks in the Field

Power on the GWU637 and wait ~60 seconds.
Connect Ethernet from GWU637 to your machine.
Set your machine's IP to 192.168.1.100 / 255.255.255.0 (static).
Open Firefox (Linux) or Netscape/WebExplorer (OS/2 Warp) and go to http://192.168.1.254.
Log in with blank credentials (or admin / admin).
Click Search, select your network, enter the password, click Apply, then Finish.
Wait ~90 seconds for the adapter to reboot.
Set your machine back to DHCP. Done.

Tips

The GWU637 remembers the last configured WiFi network across power cycles — you only need to reconfigure when switching networks.
Do not use Chrome or standard Edge for the web UI — the site survey will not function. Use Firefox or IE/Edge IE mode.
The GWU637 supports 802.11 b/g/n on 2.4GHz only. The target network must be on 2.4GHz.
WPS push-button pairing is the fastest method when available — no static IP or browser required.
For security, change the admin password after initial setup via the Management section of the web UI.
If the web UI becomes unreachable, factory reset (5–10 second hold on RESET) and start over.