This guide covers setting up a Vonets 2.4GHz WiFi bridge/repeater (VAP11G-300 or similar) for use as a portable WiFi-to-Ethernet adapter on Linux and OS/2 Warp, with easy reconfiguration for different networks.

Hardware Overview

The Vonets bridge operates in WISP (Wireless ISP) mode: it connects to an upstream WiFi network and provides a wired Ethernet port to your device. Your machine sees a standard Ethernet connection regardless of which WiFi the Vonets is bridging.

Default device settings:

• Web UI IP: 192.168.254.254
• Default SSID (AP mode): VONETS_XXXXXX (last 6 chars of MAC)
• Default credentials: admin / admin

Factory Reset (Vonets 2.4GHz Models)

Perform a factory reset before initial setup or when switching to a new deployment.

1. Power on the device and wait ~30 seconds for it to fully boot.
2. Locate the RESET pinhole on the device body.
3. With the device powered on, insert a straightened paperclip or pin into the RESET hole.
4. Hold for 10 seconds until the status LED flashes rapidly, then release.
5. The device will reboot. Wait ~60 seconds for it to fully restart.
6. The device is now restored to factory defaults (192.168.254.254, admin/admin).

Note: Some Vonets models (VAP11N, VAR11N-300) use a side button instead of a pinhole. Hold it for 10 seconds with the device powered on.

Connecting to a New WiFi Network (Reconfiguration)

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

Step 1 — Access the Web UI

Connect your computer to the Vonets device via Ethernet cable.

On Linux:

# Find your Ethernet interface name
ip link show

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

On OS/2 Warp:

Open a command prompt and run:

ifconfig lan0 192.168.254.100 netmask 255.255.255.0

If using IBM TCP/IP for OS/2, you can also set this in the TCP/IP Configuration notebook in the System Setup folder.

Step 2 — Log in to the Web Interface

Open a web browser and navigate to:

http://192.168.254.254

Log in with:

• Username: admin
• Password: admin (or your changed password)

Step 3 — Configure the WiFi Uplink

1. Click WISP or WiFi Repeater from the menu (exact label varies by firmware).
2. Click Scan to list available WiFi networks.
3. Select your target network from the list.
4. Enter the WiFi password when prompted.
5. Click Save or Apply.
6. The device will reboot and connect to the new network (allow ~60 seconds).

Step 4 — Verify Connection

After reboot, the device's WAN/Internet LED should be solid. Test connectivity:

Linux:

# Remove the static IP assigned earlier
sudo ip addr del 192.168.254.100/24 dev eth0

# Let DHCP take over (the Vonets will now provide an address from the upstream router)
sudo dhclient eth0
# or with systemd-networkd / NetworkManager:
nmcli device connect eth0

OS/2 Warp:

In the TCP/IP Configuration notebook, switch the LAN adapter back to DHCP (if it was set to static for setup). Then restart the TCP/IP stack:

[C:\] stop tcpip
[C:\] start tcpip

Or reboot. The Vonets will hand off a DHCP lease from the upstream WiFi network.

Linux — Full Setup Notes

Persistent Network Configuration

To avoid manually reconfiguring the Ethernet interface each time, configure your network manager to use DHCP on the wired interface. When the Vonets is connected and bridging a network, it will serve DHCP automatically.

NetworkManager (most desktop distros):

# Ensure the wired connection is set to DHCP
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

Then:

sudo systemctl enable --now systemd-networkd

Reconfiguring Without a GUI Browser

Use curl to access the Vonets web UI from the command line during setup:

# Authenticate and trigger a WiFi scan (exact paths vary by firmware version)
curl -u admin:admin http://192.168.254.254/goform/WifiBasicSet \
  -d "ssid=YourNetworkName&key=YourPassword&enc=3"

For reliable scripting, use a browser with the web UI — the form field names differ across Vonets firmware versions.

OS/2 Warp — Full Setup Notes

Requirements

• OS/2 Warp 3 or 4 with IBM TCP/IP for OS/2 or MPTS (Multi-Protocol Transport Services) installed.
• A supported Ethernet NIC with an OS/2 NDIS driver (e.g., NE2000-compatible, 3Com, Intel cards with OS/2 drivers).

Initial TCP/IP Configuration

1. Open System Setup folder on the Desktop.
2. Open TCP/IP Configuration.
3. Select your LAN adapter (e.g., IBMTOK0, SLIPLINK0, or LAN0 depending on your NIC driver).
4. Set IP Address to 192.168.254.100 and Subnet Mask to 255.255.255.0 for initial Vonets setup access.
5. Save and restart the TCP/IP stack or reboot.

Browser for the Web UI

OS/2 Warp includes WebExplorer (Warp 3) or Netscape Navigator (Warp 4 bonus pack). Either can access the Vonets web UI at http://192.168.254.254.

• WebExplorer: launch from the Internet folder or via EXPLORE.EXE.
• Netscape: standard launch from the desktop.

Switching Back to DHCP After Setup

Once the Vonets is configured and bridging your WiFi network:

1. Open TCP/IP Configuration again.
2. For your LAN adapter, check Obtain IP address automatically (DHCP).
3. Save and restart TCP/IP or reboot.

The Vonets will forward a DHCP lease from the upstream WiFi router to your OS/2 machine.

Command-line alternative (TCP/IP for OS/2):

ifconfig lan0 dhcp

Or edit \MPTN\ETC\SETUP.CMD and set DHCP=YES for your adapter, then restart.

Troubleshooting on OS/2

• If http://192.168.254.254 does not load, verify the static IP was applied: run ifconfig lan0 and confirm the address shows 192.168.254.100.
• Some OS/2 TCP/IP stacks require a full reboot after IP changes rather than a stack restart.
• If your NIC is not detected, confirm the NDIS 2 driver is bound in MPTS (run MPTS.EXE from \IBMCOM\).

Quick-Reference: Changing Networks in the Field

1. Plug the Vonets into power and wait 60 seconds.
2. Connect Ethernet from Vonets to your machine.
3. Set your machine's IP to 192.168.254.100/24 (static).
4. Browse to http://192.168.254.254, log in as admin/admin.
5. Go to WISP settings, scan, select network, enter password, save.
6. Wait for reboot (~60 seconds). Set your machine back to DHCP.
7. Done — the Vonets bridges to the new WiFi and your machine gets internet over Ethernet.

Tips

• The Vonets remembers the last configured WiFi network across power cycles. You only need to reconfigure when switching networks.
• If the web UI becomes unreachable, perform a factory reset (see above) and start over.
• For security, change the admin password in the web UI after initial setup: Management > Password.
• The Vonets 2.4GHz models do not support 5GHz networks. Ensure your target network is on 2.4GHz.

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:

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.

1. Power on the device and wait ~30 seconds for it to fully boot.
2. Locate the RESET pinhole on the device body (shared with the WPS button on some units).
3. With the device powered on, insert a straightened paperclip into the RESET hole.
4. Hold for 5–10 seconds until the WPS/Reset LED flashes, then release.
5. The device will reboot. Wait ~60 seconds for it to fully restart.
6. 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

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

Step 4 — Enter the WiFi Password

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

Step 5 — Finish and Wait for Reboot

1. Click Finish to apply the configuration.
2. The adapter will reboot for approximately 90 seconds.
3. During reboot the Ethernet link will drop briefly — this is normal.
4. 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:

1. Press the WPS button on the GWU637 (the WPS/Reset LED will flash).
2. Within 2 minutes, press the WPS button on the WiFi router.
3. The devices will negotiate and connect automatically.
4. 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:

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

Switching Back to DHCP After Setup

1. Re-open TCP/IP Configuration.
2. Enable Obtain IP address automatically (DHCP) for your LAN adapter.
3. 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

1. Power on the GWU637 and wait ~60 seconds.
2. Connect Ethernet from GWU637 to your machine.
3. Set your machine's IP to 192.168.1.100 / 255.255.255.0 (static).
4. Open Firefox (Linux) or Netscape/WebExplorer (OS/2 Warp) and go to http://192.168.1.254.
5. Log in with blank credentials (or admin / admin).
6. Click Search, select your network, enter the password, click Apply, then Finish.
7. Wait ~90 seconds for the adapter to reboot.
8. 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.