- ggCircuit Help Center
- ggRock User Manual
- Administration - Debian OS
-
ggLeap User Manual
- Sales - Point of Sale
- Management - Users
- Configuration - Games and Apps
- Troubleshooting
- Management - Machines
- Management - Consoles
- Sales - Client Orders
- Reporting - Finance
- Getting Started
- Configuration - ggLeap Client
- Configuration - ggLeap Web Admin
- Start Up Commands
- Sales - Prize Redemption
- ggLeap Client
- Web Admin Settings
- Single Sign On (SSO)
- Configuration - Game Licenses
- Management - Machine Groups
- Getting Started with ggLeap
- Reporting - Statistics
- Management - Employee
- Sales - Guest Accounts
- Loyalty System
- Booking
- Events / Arcade
-
ggRock User Manual
- General
- Installation - Debian OS
- Installation - ggRock Server Application
- Administration - ggRock
- Administration - ggLeap
- Administration - Windows
- Administration - Debian OS
- Administration - Games
- Administration - Hardware
- Administration - Network
- Troubleshooting - ggRock
- Troubleshooting - Network
- Troubleshooting - ggLeap
- Troubleshooting - Hardware
- Troubleshooting - Boot
- Troubleshooting - Windows
- Troubleshooting - Games
- Troubleshooting - Debian OS
-
ggLeap Product Tours
How to Check ggRock Server NIC Speed
This article describes steps necessary to check the NIC speed of your ggRock Server using the ifconfig command.
Check ggRock Server NIC Speed
-
Access the server console via a direct connection to the server, SSH, or via Debian Control Panel.
2. Log in with the root user, or another admin user on the system.
3. Check your network interface names with the "ifconfig" command. Take note of the interface which is connected to the address space of the LAN shared with your ggRock Machines.
4. Run the command
ethtool <interfacename> | grep Speed
where <interfacename> is the name of one of the interfaces from the previous command. Repeat for each interface name. Take note of the speed indicated for the interface that is connected to the LAN with your ggRock Machines. Ensure that this speed matches your expectation, otherwise there may be a configuration issue (e.g. misconfigured or missing network driver in Linux, damaged network cable, misconfigured switch port, etc).