Port 1629 carries urgent priority traffic for LonTalk, the networking protocol that powers building automation systems around the world. When devices in a building need to communicate with high priority—a fire alarm activating, a security sensor triggering, a critical HVAC system failure—those messages flow through port 1629.
What LonTalk Does
LonTalk is part of the LonWorks platform, a control networking protocol developed by Echelon Corporation in 1989 and later standardized as ISO/IEC 14908.1 It's designed for automation in buildings, industrial control, smart grids, and transportation systems.
Think of it as the nervous system for buildings. Thermostats talk to chillers. Motion sensors talk to lights. Fire alarms talk to ventilation systems. All of these conversations happen over LonTalk, flowing over twisted pair wiring, power lines, fiber optics, or wireless links.2
The Two-Port System
LonTalk over IP uses two ports:3
- Port 1628 — Standard priority traffic
- Port 1629 — Urgent priority traffic
When a LonWorks device needs to send a message right now—something that can't wait in the regular queue—it uses port 1629. The separation ensures that critical commands aren't stuck behind routine status updates.
How It Works
LonTalk uses a protocol called IP-852 (also known as EIA-852 or CEA-852) to tunnel LonWorks packets over TCP/IP networks.3 This lets building automation devices communicate over standard Ethernet and IP infrastructure instead of requiring specialized wiring throughout the entire building.
The protocol is peer-to-peer. There's no single master controller. Devices talk directly to each other. A motion sensor can tell a light to turn on without asking permission from a central server. This decentralization makes the system resilient—one device failing doesn't bring down the network.4
Why Buildings Still Run on This
LonWorks has been running building automation systems since 1989. Many of these installations are still operating—thermostats adjusting HVAC systems, occupancy sensors controlling lights, security systems monitoring access—using protocols and hardware that predates the modern Internet.
The technology became an open international standard in ISO/IEC 14908, which means it's not proprietary to any single vendor. Buildings can mix and match devices from different manufacturers as long as they speak LonTalk.5
Security Considerations
LonTalk was designed in an era when building automation networks were isolated systems. Port 1629 traffic should never be exposed directly to the public Internet. Building automation networks typically run on separate VLANs or physically isolated networks.
If you see unexpected traffic on port 1629 and you're not running a building automation system, investigate. While the port has a legitimate registered purpose, unauthorized usage could indicate someone mapping your network or attempting to communicate with compromised devices.
Checking What's Using Port 1629
On Linux or macOS:
On Windows:
If you see a process listening on port 1629 and you're not running LonWorks building automation software, it warrants investigation.
Related Ports
- Port 1628 — LonTalk standard priority traffic
- Port 20000 — DNP3 (Distributed Network Protocol, used in SCADA systems)
- Port 47808 — BACnet (Building Automation and Control Networks)
The Bigger Picture
Port 1629 represents something interesting about the Internet's infrastructure: specialized protocols for industries most people never think about. While you're browsing on port 443 and sending email on port 25, port 1629 is quietly carrying urgent commands in buildings all over the world.
Your office building probably has dozens of devices speaking LonTalk right now. The thermostat sensing the temperature. The occupancy sensor watching for movement. The light controller dimming the fixtures. They're all talking to each other, making decisions, keeping the building comfortable and efficient—and when something urgent happens, that message goes through port 1629.
Was deze pagina nuttig?