TRAFFIC
List simulcast, clerking, checkout, payment, camera, voice and staff-device traffic so the critical paths are visible before the network is built.
DOCUMENT 02NETWORK CONNECTIVITY
Auction House Internet & Network Connectivity
Build auction connectivity around the traffic that cannot stop: online bidding, simulcast audio and video, clerking, checkout and staff coordination across permanent facilities and mobile sale sites.
The useful question is not “how fast is the internet?” It is whether critical workstations have a stable path, whether upload remains usable under load, whether public devices are isolated from auction operations, and whether a primary WAN or power failure has a tested recovery route.
COVERSPrimary WANFailover internetWired EthernetStaff Wi-FiGuest isolationNetwork power
SYSTEM PLAN
Start with critical traffic and failure domains.
Auction networking is a continuity problem before it is a speed problem. Identify which systems must remain online, how they reach the internet, which components they share, and what single failure could interrupt more than one function at once.
CORE
Use wired Ethernet for fixed critical stations where practical, with a router and switching core that staff can identify and reach quickly.
RADIO
Plan staff Wi-Fi for actual work areas and keep guest access separate so crowd devices do not become part of the operational path.
RECOVERY
Define a second WAN path, protected power and the exact failover sequence before the first bidder depends on the system.
PRIMARY NETWORK PATHMAKE THE BACKUP WAN A DIFFERENT FAILURE DOMAIN
SIMULCAST PCETHERNET / SWITCHROUTER / FIREWALLPRIMARY WAN
SIMULCAST PCETHERNET / SWITCHFAILOVER ROUTESECONDARY WAN
WIRED CORE
Put fixed critical devices on Ethernet where practical.
Wi-Fi is excellent for mobility, but a fixed workstation does not gain much from adding a radio hop. A simple wired core reduces variables for the devices that handle bids, clerking, checkout and stream production.
Simulcast workstation
Prefer a direct Ethernet path to the managed network core so the bidding and streaming workstation is not competing with room-wide wireless traffic.
Clerking station
Use a stable wired connection where the clerk remains in one location. Label the cable and switch port so a damaged lead can be replaced quickly.
Checkout / payment
Keep fixed checkout hardware on a controlled network path where possible, especially when payment or buyer records depend on cloud services. Follow the payment processor’s network requirements and isolate payment systems from unrelated staff or guest devices where appropriate.
Access-point uplink
Feed fixed wireless access points by Ethernet rather than adding avoidable wireless hops. The radio edge is easier to understand when the backhaul is stable.
Operational rule
A wired connection is not automatically reliable. Keep spare patch cables, avoid crushed or improvised runs, label both ends, secure floor crossings and know which switch port serves each critical device.
UPSTREAM QUALITY
Measure the path under load, not the headline package speed.
Simulcast traffic depends on more than a large download number. The network must sustain upstream traffic while staff devices, cloud software and other venue activity are using the same connection.
Sustained uploadTest the upload path long enough to expose instability. Leave operating margin above the normal combined stream, bid-data and staff load.
LatencyRound-trip delay affects how quickly interactive systems respond. A fast speed test can still hide a path that becomes sluggish under congestion.
Packet lossEven modest intermittent loss can disturb live audio, video and interactive sessions. Treat repeated loss as a network problem, not a cosmetic metric.
Jitter & consistencyVariation in delay matters to real-time media. Compare repeated tests and watch what happens while other devices are actively using the link.
WAN REDUNDANCY
A second connection is useful only if it survives a different failure.
Two WAN devices do not automatically create redundancy. They may share the same carrier, building entry, upstream fiber, cellular tower area, router, electrical circuit or configuration mistake. The backup path is stronger when its likely failure domain differs from the primary path.
A permanent auction facility may pair a fixed broadband service with a cellular router or another provider. A mobile auction may use two cellular services on different carriers, or combine terrestrial service with another independent option where coverage and operating needs justify it.
Decide whether failover is automatic or manual. Automatic switching can reduce interruption, but staff still need to know how to confirm which WAN is active and how to recover when the automation does not behave as expected.
Test application recovery, not only router status. A platform session, VPN, payment terminal or DNS lookup may react differently when the public IP or upstream path changes.
Different carrierA second SIM from the same carrier may not protect against a carrier-wide or local tower problem.
Different mediumFixed broadband plus cellular can reduce dependence on one physical last-mile path.
Known switch methodDocument whether failover is automatic, one-button, cable-swap or configuration based.
Proven applicationsVerify the actual auction platform and payment workflow after the route changes.
WI-FI DESIGN
Design staff Wi-Fi for the full room, not an empty setup period.
Wireless conditions change when an auction fills with people, phones and other radios. A signal that looks excellent during setup can become less predictable when bidders arrive and guest devices begin scanning, associating or transferring data.
Place access points for the actual work zones, not simply beside the router. Walls, racks, vehicles, metal structures and dense crowds can change usable coverage. Avoid assuming that one powerful access point in a convenient office will serve every clerk, ring device and pickup area.
Keep operational devices on a staff network and public users on a guest network where practical. Separation can improve control and reduce direct competition, but it does not create extra internet capacity by itself: both networks still need sensible limits and sufficient upstream service.
Staff SSIDReserve for auction operations and known devices rather than publishing it for general attendee use.
Guest SSIDIsolate public access and apply sensible limits so bidder convenience does not dominate shared capacity.
Coverage walkTest clerk, ring, checkout and pickup positions with the room configured as it will be during the sale.
Wired fallbackKeep adapters or patch leads ready for critical mobile devices that can accept Ethernet when wireless conditions deteriorate.
NETWORK SEGMENTATION
Keep public access separate from the auction operations network.
Staff networkClerking, production and trusted operational devices.
Guest networkBidder convenience with isolation and appropriate limits.
Admin accessRestrict router, switch and access-point management to trusted staff paths.
ConfigurationExport or document the known-good setup before major sale-day changes.
Auction connectivity often mixes very different users: clerks, simulcast operators, payment devices, staff phones, cameras and bidder guest access. Putting every device on one flat network makes troubleshooting harder and can expose operational devices unnecessarily.
Where the router or managed network supports it, separate guest traffic from staff and production traffic using dedicated SSIDs and appropriate network segmentation. Restrict access between segments to what is actually required rather than assuming every device should see every other device.
Segmentation is not a substitute for secure configuration. Use strong administrative credentials, current firmware, documented device ownership and a configuration backup so the network can be restored without improvising during a sale.
POWER & RECOVERY
Keep the network alive long enough to make the next decision.
A short power interruption can reboot the modem, router, switch and access points even when laptops continue running on battery. The result may look like an internet outage when the real problem is that the network core is restarting one device at a time.
Place the low-draw devices required for the critical network path on an appropriately sized UPS: the service-provider terminal or modem, router or firewall, core switch and any access point needed by the sale workflow. Verify restart behavior after the UPS is exhausted or the generator is introduced.
Keep the recovery sequence simple. Staff should know which indicator shows the active WAN, how to reach the router locally if internet service is down, which cable or device creates the backup path and what limited offline work can continue while service is being restored.
Protected core
Modem or network terminal, router, switch and required access points on suitable backup power.
Local access
Known management address, credentials and a way to diagnose the LAN even when the WAN is unavailable.
Offline fallback
Document what clerking, bidder registration or checkout work can continue temporarily without cloud access.
ENVIRONMENT MATRIX
Connectivity priorities change with the auction format.
Do not copy one network plan into every sale. A permanent building, a simulcast-heavy room, an outdoor equipment auction and a mobile estate setup have different last-mile, coverage, power and deployment risks.
| Environment | Prioritize | Watch for | Useful recovery |
|---|---|---|---|
| Permanent auction facility | Wired core, managed staff Wi-Fi, fixed WAN, documented switching, UPS | Single router or switch, guest load, undocumented configuration changes | Independent second WAN, spare router or known bypass, configuration backup |
| Simulcast-heavy room | Stable upload, Ethernet production stations, separate staff/guest traffic, monitoring | Upload saturation, packet loss, Wi-Fi production devices, cloud-only dependencies | Automatic or rehearsed WAN failover plus a tested platform reconnect sequence |
| Outdoor equipment auction | Cellular or portable WAN, strong local Wi-Fi placement, weather-aware power | Variable cellular service, vehicles blocking radio paths, generators and long cable runs | Second carrier or independent path, battery/UPS and movable network position |
| Mobile estate / on-site sale | Fast-deploy router, compact switch, limited staff SSID, simple cabling | Unknown household internet, rushed setup, weak signal indoors, limited outlets | Second data device, Ethernet kit and a defined offline operating mode |
| Large public event | Capacity planning, multiple access points, guest isolation, controlled admin access | Dense client load, roaming issues, public traffic consuming shared WAN capacity | Critical stations wired, guest limits and a separate path for production where justified |
PRE-SALE TEST
A practical network test before bidding starts.
Do not stop after a browser opens or a single speed test looks good. Prove the complete auction path, then deliberately remove the primary connection while there is still time to fix the recovery process.
- Use the real workstations.Test from the simulcast, clerking and checkout positions using their actual Ethernet or staff Wi-Fi connections.
- Generate realistic load.Run representative platform, audio/video and cloud traffic long enough to observe sustained upload, delay and stability.
- Check platform requirements.Verify the auction platform’s current browser, firewall, port and network requirements on the exact workstation and venue connection that will be used for the sale.
- Walk staff wireless zones.Check ring, registration, checkout, loading and pickup areas with the building configured as it will be during the sale.
- Disconnect the primary WAN.Do not simulate failover only in software. Remove the primary path and confirm how long the network and auction applications take to recover.
- Test protected power.Verify the modem, router, switch and required access points remain available during the type of brief interruption the UPS is meant to bridge.
- Prove the staff procedure.Have the person who will actually operate the sale identify the active WAN, perform the planned recovery and explain the offline fallback.
TROUBLESHOOTING
Start with the affected layer, not random reboots.
Fast network troubleshooting is easier when staff first decide whether the problem is one device, the local network, Wi-Fi, the router, the WAN or a remote service. Change one thing at a time and preserve the known-good path whenever possible.
| Symptom | Likely area | First checks |
|---|---|---|
| One workstation is offline, others work | Device, cable, switch port or local configuration | Check link status, swap to a known-good patch cable or port, verify addressing and confirm the device can reach the local gateway. |
| Wi-Fi devices fail, wired devices work | Access point, SSID, radio conditions or DHCP path | Confirm the access point is powered and linked, verify the correct SSID, test near another access point and check whether clients receive valid network settings. |
| LAN works but internet services do not | WAN, DNS, provider or upstream router state | Reach the local gateway first, check WAN status and DNS behavior, then test the secondary WAN instead of rebooting every local device. |
| Speed collapses when the room fills | Wireless client density, guest load or WAN congestion | Compare wired performance, inspect guest and staff traffic, move critical devices to Ethernet and verify whether the bottleneck is radio capacity or upstream service. |
| Failover shows connected but platform stays down | Session recovery, routing, DNS or changed public IP | Test general internet access, restart only the affected application if appropriate and verify the platform's reconnect behavior on the backup path. |
| Everything drops after a brief power event | Unprotected network core or staged reboot sequence | Identify which modem, router, switch or access point lost power, confirm UPS load and check the order in which provider and local devices recovered. |
BUYING FILTER
What matters more than the largest speed number.
Useful auction networking equipment is equipment the crew can deploy, monitor, power and recover. Compare routers, switches and access points against the operating environment rather than a single throughput specification.
Failover control
Can the router use the intended secondary WAN, show which path is active and recover without a complicated sale-day configuration change?
Wired capacity
Are there enough reliable Ethernet ports, appropriate switching features and simple physical paths for fixed production, clerking and checkout devices?
Wireless management
Can staff and guest access be separated, access points be placed where needed and basic client or traffic problems be diagnosed without guessing?
Recovery simplicity
Can staff replace a cable, move to the backup WAN, restore a saved configuration or bypass one failed component without rebuilding the whole network?
FAQ
Auction connectivity questions
Short answers to the questions that usually appear when simulcast is added, a permanent network is being rebuilt or a mobile auction needs a more predictable internet path.
How much internet speed does a simulcast auction need?
There is no single speed number that fits every platform and production setup. Sustained upload capacity, latency, packet loss and stability matter alongside headline bandwidth. Test the exact simulcast workstation and audio or video workflow at the venue, then leave operating margin above the observed load.
Should auction workstations use Ethernet or Wi-Fi?
Fixed critical devices such as simulcast, clerking and checkout workstations should use wired Ethernet where practical. Wi-Fi is useful for mobile staff devices, but radio conditions can change as the room fills with people and phones.
What is a useful backup internet connection for an auction?
A useful backup is a second path that does not simply repeat the primary path's likely failure. Depending on the venue this may be cellular service from a different carrier, another wired provider or another independent connection. The backup must be powered, configured and tested before the sale.
Should guest Wi-Fi be separated from auction staff traffic?
Yes where the network equipment and venue allow it. Separating guest access from operational devices reduces accidental exposure and makes it easier to keep public traffic from competing directly with clerking, checkout and simulcast systems.
What network equipment should be on a UPS?
Protect the devices that keep the critical path alive, typically the modem or network terminal, router or firewall, core switch and any access point or small network device required by the sale workflow. Size the UPS for the actual load and the interruption you expect it to bridge.
What should be tested before an online or simulcast auction starts?
Test sustained upload from the real workstation, verify wired and staff wireless paths, confirm platform connectivity, disconnect the primary WAN to prove failover, check network equipment on backup power and confirm staff know the recovery sequence.
CONNECTIVITY / FIELD RULE
Stabilize the primary path, then prove the failure path.
Auction connectivity succeeds when critical devices stay on a controlled local network, upstream performance remains usable under real load and staff can move to an independent backup without inventing the recovery process while bidding is live.