1. What is Wireguard?

WireGuard is an open-source virtual private network (VPN) protocol and software that aims to provide a simpler, faster, and more secure way to establish encrypted network connections. It was designed with simplicity and efficiency in mind, and it has gained popularity for its modern approach to VPN technology.

WireGuard utilizes state-of-the-art cryptography to create secure point-to-point connections between devices. It operates at the kernel level, which allows it to offer high performance and low resource usage. The protocol uses a streamlined codebase and implements modern encryption algorithms, such as Curve25519 for key exchange and ChaCha20 for encryption.

Compared to traditional VPN protocols, WireGuard offers several advantages, including fast connection establishment, lower latency, and easier configuration. It is also designed to be resistant to network and session hijacking attacks.

Overall, WireGuard has gained a lot of attention due to its simplicity and efficiency, making it a popular choice for setting up secure VPN connections.

2. How does Wireguard work?

At a high level, WireGuard works by creating a secure network tunnel between two devices, commonly referred to as peers. This tunnel allows the devices to communicate with each other while keeping the data encrypted and protected from unauthorized access.

Here’s a simplified overview of how WireGuard works:

Key Exchange: When a WireGuard connection is established, the peers exchange a set of cryptographic keys. This is typically done during the handshake process using the Diffie-Hellman key exchange algorithm, specifically with Curve25519 elliptic curve cryptography. The keys are used to authenticate and encrypt the traffic between the devices.

Encryption and Decryption: Once the keys are exchanged, WireGuard encrypts the data using symmetric encryption, commonly with the ChaCha20 stream cipher, along with Poly1305 for message authentication. This combination provides confidentiality and integrity of the transmitted data.

Network Interface: WireGuard creates a virtual network interface (usually named wg0) on each device involved in the connection. This interface behaves like a traditional network interface, allowing applications and services to send and receive IP packets through it.

Secure Tunnel: WireGuard encapsulates the IP packets into UDP (or in some cases, other transport protocols) packets, which are then sent over the network between the peers. These packets carry the encrypted data, along with the necessary information to route and decrypt them on the receiving end.

Route Control: WireGuard controls the routing of the network traffic, ensuring that the encrypted packets are correctly directed through the secure tunnel. It uses a routing table to determine which packets should be sent through the WireGuard interface and which should follow regular network paths.

By establishing this secure tunnel and encrypting the data, WireGuard ensures that the communication between the peers is protected from eavesdropping and tampering. It also provides the ability to traverse NAT (Network Address Translation) devices, making it more convenient to use in various network setups.

Overall, WireGuard takes a lightweight and modern approach to VPN technology, simplifying the complexities of traditional protocols while maintaining strong security and performance.

3. What are the benefits of Wireguard for IoT?

WireGuard can indeed be used for securing communications in IoT (Internet of Things) environments. It offers several advantages that make it a suitable choice for IoT devices:

Lightweight and Efficient: WireGuard is designed to be lightweight and efficient, making it suitable for resource-constrained IoT devices with limited processing power and memory. It has a small codebase and operates efficiently even on devices with low computational capabilities.

Strong Security: WireGuard employs modern cryptographic algorithms, such as Curve25519 for key exchange and ChaCha20 for encryption. These algorithms provide strong security and help protect IoT devices and their data from potential threats.

Simplified Configuration: WireGuard simplifies the configuration process compared to traditional VPN protocols. This makes it easier to set up secure connections between IoT devices and networks, reducing administrative overhead and potential configuration errors.

Quick Connection Establishment: WireGuard is designed for fast connections. It establishes connections quickly, allowing IoT devices to establish secure communication channels rapidly, which is beneficial for real-time or time-sensitive applications.

Dynamic IP Support: IoT devices often operate in dynamic IP environments, where IP addresses can change frequently. WireGuard handles dynamic IPs seamlessly, adaptively updating the tunnel endpoints to accommodate the changing network conditions without requiring manual intervention.

NAT Traversal: Network Address Translation (NAT) is commonly used in IoT deployments. WireGuard is NAT-friendly, enabling IoT devices to establish secure connections even when they are located behind NAT devices.

Open Source and Audited: WireGuard is an open-source project that has undergone extensive security audits. The transparency of the codebase and the auditing process contribute to increased trust in the security and reliability of the protocol.

These features make WireGuard well-suited for securing IoT device communications, whether it’s for protecting data transmitted between IoT devices and cloud services or establishing secure connections between IoT devices within a local network.

4. Wireguard config page on IoT gateway

Note: Some of the articles is from AI, any questions, pls contact Bivocom

The post What are benefits of wireguard for IoT? appeared first on Bivocom.

1. MQTT Introduction

MQTT is a lightweight messaging protocol based on publish/subscribe model, specifically designed for IOT applications in low bandwidth and unstable network environments. It can provide real-time reliable messaging services for network-connected devices with minimal code. MQTT protocol is widely used in IOT, Mobile Internet, Smart Hardware, Internet of Vehicles, Smart Cities, Power, Oil, Energy, and other fields.

2. Transparent Test

Before the formal configuration, we can start with a transparent test to ensure the network connection between the client and server is normal, and understand the basic network environment through the test. The steps are as follows:

• Enter the WEBUI of configuration, then click the Basic Setting, enable the “Data Collect” feature, and set the Collect Period, Report Period, and other related options as you wish.

Data Collect: Enable or Disable the data collection feature, this is the switch of the whole data collection function

Collect Period: Set the period of data acquired from slave devices.

Report Period: Set the Period of data report to the server.

Enable Cache: Enable or Disable history data cache feature.

Cache Path: Choose where the cache data is stored.

Send minute, hour, and day data: Set the minute data period as you wish.

(2)Click the Interface Setting, and change the COM Protocol to “Transparent”, the other options must be set the same as a slave device.

(3)Click the Server Setting, Protocol select “TCP”, Encapsulation Type select “Transparent”, the “Server Address” and “Server Port” must be set the same as the TCP server. The Register Packet, Heartbeat Packet, and Heartbeat Interval can be set as you wish.

(4)Open the serial port tool, and open the specific serial port, then you can send any characters to the server.

Then the TCP server will receive the message from the client, and you can also send a message to the client.

So far, the transparent test has been done, the data is being transmitted to each other, and then we can proceed next step.

3. MQTT ClientConfiguration
   • Data Collect ThroughModbus RTU

(1) Enter the WEBUI of configuration, and click Interface Setting, this time, I use an RS485 serial port to connect the router and PC, of course, you can choose RS232, and change the COM Protocol into “Modbus”, the other options must set the same as a slave device.

(2)Click Modbus Rules Setting, then add a new one. The Order, Device Name, and Factor Name can be set to whatever you want. The Device ID, Function Code, Start Address, and Count must be set the same as a slave device.

ATTENTION: You need to select the corresponding interface according to the specific serial port.

(3)Click Server Setting, the specific configurations are as follows:

Protocol: Select “MQTT”

Encapsulation Type: Select “JSON”

Server Address: Bivocom has a regular address “isodev.picp.net”(for testing only)

Server Port:1883

Heartbeat Interval: the interval between data publication and subscription

MQTT Public Topic: the topic you wanna publish in the MQTT client

Client ID: Set a unique ID as you wish

After setting these parameters, remember to click “Save&Apply”, then the Connection Status will change to “CONNECTED”.

(4) Here I use Modbus Slave to simulate the slave device, open the simulate tool, set the corresponding interface parameters of the client router, and then click connect. In this case, I set the value as “111”.

Open the Slave Definition, the Function code select “03” which means read the register’s data.

After setup, you can see the Real-time data collection accepts the value just set.

(5)Open the MQTT.fx tool or other software can work as an MQTT client on a PC, The Broker Address must be the same as the Server Address you just set, and the Broker port is also 1883. Finally, click connect after setup.

Then subscribe to the public topic I just set in the client server which is “yes”. There will be the topic message from the MQTT Client.

We can also see the communication between the slave device and the gateway.

• Data Collect Through Modbus TCP

The setting is almost the same as the ModBus RTU protocol, the interface is changed into RJ45 instead of a ModBus serial port. The specific steps are as follows:

(1)Click Interface Setting, and enable the “TCP Server” option, The Server Address is the slave device’s IP address, COM Protocol select “Modbus-TCP”. The Server Port should be distinguished from the local TCP Server’s port, here I set as “9000”.

(2)Click Server Setting, the parameters are set as follows:

Protocol: Select “TCP”

Encapsulation Type: Select either JSON or Transparent

Server Address: the same as TCP Server “192.168.1.161”

Server Port: the same as TCP Server “8080”

After setting these parameters, remember to click “Save&Apply”, then the Connection Status will change to “CONNECTED”.

(3)Add a new Modbus Rule for the TCP interface, click ModBus Rules Setting, and select the interface as “TCP”, the other parameters are the same as COM.

(4) Open the slave’s connection Setup, Connection selects “Modbus TCP/IP”, the IP address is the same as the TCP server. The slave’s port and TCP server’s port need to be distinguished, in order to ensure that a port is not occupied.

(5)After that, we can see the connection is established in the TCP Server.

The slave and TCP server start transmitting data.

4. IO Setting
   • Relay Setting

• Click IO Setting, and add a new Relay Channel, the parameters are set as follows:

Device Name: The device name is set as you wish

Relay Channel: In relay interfaces, there are multiple channels available determined by a specific device

Factor Name: Corresponding report code of data collected

Reporting Center: data report center’s number

Relay Control: initial state of the relay, there are “open” and “close” two options

Once added, remember to click Save&Apply.

• Add an MQTT Subscribe Topic in the Server Setting, here I set “no”.

• Open MQTT.fx, and subscribe to the topic that is published in the MQTT Client, which will accept the initial state of relays.

• RemoteControl Relay

• If you want to control the relay’s state, you should publish the Subscribe Topic just set, and then issue the corresponding command.

Then the gateway will respond with the status “OK”

After a while, you’ll see the relay’s state has changed successfully.

• If you do not modify successfully, you should check whether the corresponding interface is configured, or check the command format. Because the control command is in JSON format, if your command is incorrect, it will not be executed.

The gateway will respond like this:

So before issuing the command, you have to change the corresponding control command into JSON format. This is very important.

You can try to issue different commands serval times to verify if the state of relays can be changed successfully.

• DI Setting

• Click IO Setting, you need to add a New DI Channel, the parameters are set as follows:

The other configurations are the same as the Relay Setting. Once added, remember to click Save&Apply.

• Open MQTT.fx and subscribe to the public topic, then you can see the initial state of the DI port.

(3) If you want to change the DI’s state, you just need to short-circuit the “DI” port and the “GND” port. Then you’ll see the state of DI change immediately. You can try serval times to verify that.

5. RemoteTelemetry Function
   • Remote Telemetry Through MQTT

If you want to remotely modify the report factor’s value of the slave device, you should issue corresponding instructions through the MQTT Client or TCP Client. The command is also in JSON format. The specific steps are as follows:

• Add Modbus Rules, the exact method is the same as before. Here I add two factors, “A” and “B”.Then click Save&Apply.

• Click Server Setting, the configuration is also the same as above.

• Open Modbus Slave, and set initial values of two factors.

• Open MQTT.fx, and subscribe to the specific topic, then you can see the initial values of A and B.

• Publish the corresponding topic, and issue the command to modify the factor’s value, Pay attention to the command is also JSON format.

Then the gateway will respond to the status “OK”.

After a while, you’ll see the factor’s value has changed successfully.

• Remote Telemetry ThroughTCP

• Click Interface Setting, enable TCP Server, the configuration is the same as before, and click Save&Apply.

• Click Server Setting, change the Protocol to “TCP”, the Server Address and Server Port are the same as TCP Server, and click Save&Apply.

Then the TCP Server will accept the initial values of A and B.

The WEBUI also can accept the data.

• Issue the corresponding command to modify the factor’s values as you wish. If the command is correct, the server will respond “status”: “OK” immediately.

After a while, you’ll see the factor’s value has changed successfully.

The post How to configure data collection via MQTT on IoT gateway? appeared first on Bivocom.

1. Settings of Gateway

• Enable data collection

• Set baud rate of CAN port

• Set server protocol as Transparent

2. Test process and Data transmission

• Connection Diagram

• We will use USB-CAN converter to test. The converter is sent as follows:

(1) Serial frame transmits to CAN message(Base frame format)

(2) CAN message(Extended frame) transmits to Serial frame

• Base frame data transmission test

The CAN Base frame information is 11 bytes (3 + 8) and consists of two parts: information and data. The first 3 bytes are the information part.

① 8 bytes data, if the valid data is less than 8 bytes, 00 is added after it;

② 4byte ID, standard frame less than 11bit valid, extended frame less than 29bit valid Valid data length;

③ Effective data length, range 01-08, remote frame is the request;

④ Remote frame identification, 00 is the non-remote frame, 01 is the remote frame identifier;

⑤ Extended frame identification, 00 is the standard frame, 01 is the extended frame;

⑥ The prefix of the packet must be AA.

• Analog base frame serial frame data:

The base frame ID is valid at a minimum of 11 bits, that is, the maximum frame ID is 0x7ff.

AA 00 00 08 00 00 07 FF 00 01 02 03 04 05 06 07

AA 00 00 08 00 00 07 FF 08 09 0A 0B 0C 0D 0E 0F

• Extended frame data transmission test:

The CAN extended frame information is 13 bytes (5 + 8) and consists of two parts, the information and the data part. The first 5 bytes are the information part.

The extended frame ID is valid for a maximum of 29 bits, that is, 0x1fffff

AA 01 00 08 1F FF FF FF 00 01 02 03 04 05 06 07

AA 01 00 08 1F FF FF FF 08 09 0A 0B 0C 0D 0E 0F

Relevant resource:

Picture of Cover: https://www.youtube.com/watch?v=8nl3XkL1eTc

The post Controller Area Network(CAN) Test appeared first on Bivocom.

RTU stands for Remote Terminal Units, are devices used in industrial automation and control systems to monitor and control remote equipment and processes. RTU plays a crucial role in supervisory control and data acquisition (SCADA) systems.

RTUs are typically located in remote or hazardous environments, where they collect data from sensors and devices, and transmit it to a central control system for monitoring and analysis. They also receive commands from the central control system and control the connected devices and equipment accordingly.

The remote terminal unit is sometimes known as the remote telemetry unit or remote telecontrol unit.

Functions

Some key functions of RTUs include:

1. Data Acquisition: RTUs collect data from various sensors, meters, and devices such as pressure sensors, temperature sensors, flow meters, and switches.

2. Signal Processing: RTUs process the acquired data, performing calculations, filtering, and data transformation as required.

3. Communication: RTUs establish communication links, typically through wired or wireless networks, to transmit data to the central control system and receive commands.

4. Control: Based on the instructions received from the central control system, RTUs actively control devices and equipment connected to them, such as opening or closing valves, adjusting setpoints, or starting/stopping processes.

5. Alarm Monitoring: RTUs monitor alarm conditions and generate notifications or alerts when predefined thresholds or abnormal conditions are detected.

Overall, RTUs serve as the interface between the field devices and the central control system, enabling efficient monitoring and control of industrial processes across geographically dispersed locations.

Benefits

The benefits of deploying RTUs include improved operational efficiency, reduced downtime, and enhanced control of industrial equipment. For example, RTUs can be used to track and monitor energy usage, optimize equipment performance, and detect malfunctioning equipment before it causes severe damage.

Application Industry

RTU is widely used in various automation control fields, such as electric power, water conservancy, petroleum, chemical, transportation, and metallurgy industries.

In the electric power industry, RTU is extensively applied in areas like substations and distribution automation systems to achieve remote monitoring and control of power systems.

In the water conservancy industry, RTU finds wide applications in hydrological measurement, hydrological forecasting, hydrological monitoring, etc., enabling remote monitoring and control of water conservancy systems.

In the petroleum industry, RTU is widely used in oilfield automation control systems to achieve remote monitoring and control of oilfield production processes.

RTU for Water Level Monitoring

RTUs can definitely be used for water level monitoring and integrating IP cameras. In such applications, the RTU collects data from water level sensors placed in bodies of water, such as rivers, reservoirs, or tanks. It then transmits this data to a central server or cloud platform for monitoring and analysis. Additionally, an IP camera can be connected to the RTU, allowing real-time video surveillance of the water area. This combination of water level monitoring and IP camera integration helps track water levels and provides visual monitoring for safety, security, and analysis purposes.

Here is field application pictures from one of our customer.

Insert gallery caption

Difference between RTU and DTU

RTU is generally used for applications related to monitoring, control, and data acquisition. It supports telemetry, telegraphy, telecontrol, and remote operations. Typically, it integrates analog and digital inputs and outputs, PWM control, counters, RS232 and RS485 interfaces, and also functions as a wireless router.

DTU refers to a wireless transparent transmission device. It is specifically used to convert serial data to IP data or vice versa and transmit it through a wireless communication network. It acts as a wireless terminal equipment.

Relevant articles:

1. How to transfer the data from RTU to IoT router?

The post What is a Remote Terminal Units (RTU)? appeared first on Bivocom.

With the development of technologies such as cloud computing, big data, and information networks, network virtualization has attracted increasing attention.

The traditional VLAN technology, which supports only up to 4094 VLANs and cannot span across different data partitions within the same data center or different data centers, is no longer able to keep up with the current trends in IT infrastructure.

VXLAN, on the other hand, serves as an extension to VLAN and allows for the creation of Layer 2 virtual networks based on Layer 3 network structures. It also enables the separation of virtual networks from infrastructures, thereby achieving network reliability and scalability. As a result, more and more enterprises are leveraging the advantages of VXLAN, such as high utilization, low cost, flexibility, and scalability, in their network architectures.

Based on the development of VXLAN, Bivocom focuses on the application of VXLAN technology and integrates advanced technologies such as IoT, AI, and edge computing. VXLAN is applied to flagship version gatewayTG463, mini 5G gateway, dual-port industrial router TR321, and 4G universal router TR341. By building an efficient data center network, it provides technical support for enterprise development.

Production Description

Currently, with the rapid expansion of mobile Internet of Things (IoT) application scenarios and industry businesses, the demand for infrastructure, such as networks, hosts, and databases, is to quickly respond to the deployment of upper-layer businesses and reduce cost inputs.

Bivocom Lamp Pole Gateway TG463, mini 5G gateway TG453, dual-port industrial router TR321, 4G router TR34, based on VXLAN technology, which can use a 24-bit VXLAN identifier to identify virtual networks, allowing multiple independent virtual networks to coexist. In addition, the above flagship products also support 5G, 4G, 2.4G/5.8G dual-band WiFi communication, automatically selecting faster frequency bands to provide users with a high-quality network environment.

It is worth mentioning that this product features multi-path transmission, which allows for the selection of the optimal path for data transmission based on network load and path availability. This provides high performance and reliability for applications in various industries.

Additionally, the flagship product incorporates VXLAN technology, enabling tunnel encryption to enhance data transmission security through IPsec or VPN. Currently, flagship products such as TG463, TG453, TR321, and TR341 are widely applicable in application scenarios such as smart cities, autonomous driving, drones, mobile medical vehicles, mobile media vehicles, and industrial control applications, etc.

Advantages of VXLAN

• 1. Based on the application of VXLAN technology, Bivocom flagship product uses a 24-bit VNI (Virtual Network Identifier) to identify virtual networks, supporting over 16 million virtual networks and providing independent layer 2 namespaces to meet the needs of large-scale data centers.

• 2. Even in environments with changes in network architecture and network devices, Bivocom products can be deployed and run on existing network infrastructure without changing the existing network framework, which promote construction and management of virtual network.

• 3. Making underlying IP network as the transport medium which enables network virtualization across physical network, and isolates the physical network between different servers. It provides better support for business and data processing.

• 4. Supporting various networking requirements such as cloud computing, big data, virtualization, and cross-data center, it enables the establishment of virtual network connections across different data centers to achieve resource sharing and business expansion between data centers.

Relevant Articles:

1. What is VXLAN ?
2. How to setup VXLAN?

The post Bivocom Applied VXLAN Technology to Router and Gateway appeared first on Bivocom.

• (1) Routing mode: Communication between different network segments

 End to End communication:

The two end devices establish a direct VXLAN tunnel, through which all data traffic is transmitted. The subnets on both devices form a unified Layer 2 subnet.

Multiterminal forward communication:

The objective is to establish a VXLAN tunnel between Device A and Device B, while simultaneously enabling Device C to also establish a VXLAN tunnel with Device B. This configuration facilitates the formation of a unified layer 2 subnet for the devices within subnets under both Device A and Device C, requiring potential data forwarding through multiple tunnels to reach its intended destination.

• (2) Bridge mode: Communicates with a Network Segment

 End to End communication:

The two end devices establish a direct VXLAN tunnel, through which all data traffic is transmitted. The subnets on both devices form a unified Layer 2 subnet.

Multiterminal forward communication:

Establish a VXLAN tunnel between Device A and Device B, while also configuring a VXLAN tunnel between Device C and Device B. This configuration enables the subnet devices under both Device A and Device C to form a unified layer 2 subnet, with data potentially being forwarded through multiple tunnels in order to reach its intended destination.

2. Settings of VXLAN

• VTEP Name: VTEP name and virtual NIC device name; Example: vxlan0-n
• VTEP IP: Virtual network adapter device IPaddr;
• VNI: The unique identifier of the tunnel must be the same as the VNI of the peer device. The VNI rules must be unique;
• Local IP: The WAN IP address of the local VTEP;
• Remote IP: WAN IP address of the peer VTEP;
• Port: UDP port number used by the VXLAN. The default UDP port number is 8472;
• Remote Network: Specifies the subnet of the peer VTEP;
• Bridge: The default mode is route mode. Select Bridge mode to enable.

3. Example of VXLAN

End to End communication:

Device A settings:

Device B settings:

Test Result:

Ping subdevice of device A (192.168.2.139) from subdevice of device B (192.168.3.243)

Ping the subdevice of device B (192.168.3.243) from the subdevice of device A (192.168.2.139)

Multiterminal forward communication:

Device B settings:

Device A settings:

For Device A, also need to add new Static Routes of vxlan1(VTEP Name), add the Host IP of Device C. Here we set 192.168.3.0/255.255.255.0/0.0.0.0/0.

Device C settings:

For Device C, also need to add new Static Routes of vxlan2(VTEP Name), add the Host IP of Device A. Here we set 192.168.2.0/255.255.255.0/0.0.0.0/0.

Test Result:

Ping the subdevice of device C (192.168.3.243) from the subdevice of device A (192.168.2.139)

Ping the subdevice of device A (192.168.2.139) from subdevice of device C (192.168.3.243)

Relevant Resources：

1. What is  VALAN? And its role in IoT？

The post How to Setup VXLAN? appeared first on Bivocom.

You need MQTT connection more than you think.

MQTT (Message Queuing Telemetry Transport) is a lightweight messaging protocol designed for constrained devices and low-bandwidth, high-latency or unreliable networks. It enables communication between remote devices, such as smartphones and web apps, sensors, and other systems.

Additionally, MQTT is successfully implemented in many industries, such as automotive, logistics, manufacturing, smart home, consumer products, transportation, etc

Principle of MQTT

In traditional network communication, the client and server communicate directly with each other. The client requests resources or data from the server, and then the server processes it and sends back a response.

The principle of MQTT (Message Queuing Telemetry Transport) is based on the publish/subscribe pattern. It uses the TCP/IP protocol for communication and achieves message publishing and subscribing through the connection between the client and the broker (proxy server). It follows a publish-subscribe model where clients can publish messages to topics or subscribe to topics to receive messages.

In MQTT, message publishers publish messages to specific topics, while subscribers receive messages by subscribing to topics. The broker is responsible for receiving messages from publishers and distributing them to subscribers who have subscribed to the respective topics.

MQTT Broker and MQTT Client

When it comes to establish the MQTT connection, there are two important parts in its connection. They are MQTT broker and MQTT client.

1. MQTT Broker

An MQTT Broker can be an application or a device. It is the critical component responsible for handing client requests, including establishing connections, disconnecting, subscribing, unsubscribing, and forwarding messages.

When a device or application needs to send a message, they publish it to a specific topic on the MQTT broker. Other devices or applications that have subscribed to the same topic will receive these messages. The MQTT broker ensures reliable delivery of messages, even unstable network conditions or when connections are lost.

MQTT brokers are widely used in industries such as power, renewable energy, smart cities, smart homes, smart metering, internet of vehicles, finance and payments, and telecommunications.

      2. MQTT Client

An MQTT client is any device that runs an MQTT library and communicates with a server. If the client is sending messages, it acts a publisher; if it is receiving messages, it acts as a subscriber. Essentially, any device that uses MQTT for communication over a network can be referred to as an MQTT client device. For example, instant messaging applications using MQTT are clients, various sensors reporting data using MQTT are clients, and various MQTT testing tools are also clients.

Benefits

1. Simpler

MQTT is a messaging protocol that uses a publish/subscribe message pattern, providing one-to-many message distribution and decoupling of applications. Compared to other protocols, it is easier to develop with.

2. More Stable Network

It operates on the TCP/IP protocol, which provides a stable network connection.

3. Lightweight

MQTT has a small footprint and minimal overhead, minimizing protocol exchanges and reducing network traffic. It is suitable for low-bandwidth applications with small data payloads.

4. Wide Protocol Support

MQTT has broad support across various platforms and programming languages, making it easy to integrate into existing systems. There are numerous MQTT client libraries available, simplifying development for different devices and environments.

5. Openness

MQTT is an open protocol with source code, enabling its usage across different platforms.

In summary, MQTT is a simple, stable, open, and lightweight protocol with wide protocol support. It has broad applicability in areas such as information gathering, industrial control, smart homes, Internet of Things, small devices, and mobile applications, etc.

How to enable MQTT broker？How to Setup on Bivocom Platform?

Please visit below link

Article: How to enable MQTT Broker?

Video Instruction: Video of How to Enable MQTT Broker?

Relevant resources:

Picture of cover:  https://blog.paessler.com/why-mqtt-is-everywhere-and-the-security-issues-it-faces

The post What is MQTT? And What are MQTT Broker and MQTT Client? appeared first on Bivocom.

VXLAN, which stands for Virtual Extensible LAN, is a network virtualization technology that allows the creation of virtualized Layer 2 networks over an existing Layer 3 infrastructure. It was developed to address the scalability limitations of traditional VLANs (Virtual Local Area Networks) in large-scale data center environments.

VXLAN encapsulates Layer 2 Ethernet frames within Layer 3 UDP (User Datagram Protocol) packets, enabling the extension of Layer 2 segments across Layer 3 boundaries. This allows for the creation of logical networks or overlays that can span multiple physical network devices, data centers, or even geographical locations.

          Key features and benefits of VX include:

• (1) Scalability:

VXLAN uses a 24-bit segment identifier called the VXLAN Network Identifier (VNI), which allows for up to 16 million unique virtual networks, compared to the limited 4,096 VLANs in traditional Ethernet networks.

• (2) Multi-tenancy:

VXLAN enables the isolation and segmentation of network traffic for different tenants or applications, providing enhanced security and flexibility in multi-tenant environments.

• (3) Network virtualization:

By decoupling the logical network from the underlying physical infrastructure, VXLAN facilitates the creation of virtual networks that can be provisioned, managed, and migrated independently of the physical network.

• (4) Overcoming Layer 2 domain limitations:

VXLAN extends Layer 2 connectivity across Layer 3 boundaries, enabling the seamless movement of virtual machines (VMs) and workloads between different physical hosts data centers without the need for manual reconfiguration.

• (5) Compatibility:

VXLAN is designed to work with existing IP networks and leverages standard networking protocols such as UDP and IP, making it compatible with a wide range of networking equipment and software.

VXLAN has gained popularity in modern data center architectures, particularly in cloud computing and virtualized environments, where flexible and scalable network virtualization is essential to support the dynamic nature of workloads and applications.

2. Communication mode of VXLAN

      (1) Routing mode: Communication between different network segments

• End to End communication:

The two end devices establish a direct VXLAN tunnel, through which all data traffic is transmitted. The subnets on both devices form a unified Layer 2 subnet.

• Multiterminal forward communication:

The objective is to establish a VXLAN tunnel between Device A and Device B, while simultaneously enabling Device C to also establish a VXLAN tunnel with Device B. This configuration facilitates the formation of a unified layer 2 subnet for the devices within subnets under both Device A and Device C, requiring potential data forwarding through multiple tunnels to reach its intended destination.

       (2) Bridge mode: Communicates with a Network Segment

• End to End communication:

The two end devices establish a direct VXLAN tunnel, through which all data traffic is transmitted. The subnets on both devices form a unified Layer 2 subnet.

• Multiterminal forward communication:

Establish a VXLAN tunnel between Device A and Device B, while also configuring a VXLAN tunnel between Device C and Device B. This configuration enables the subnet devices under both Device A and Device C to form a unified layer 2 subnet, with data potentially being forwarded through multiple tunnels in order to reach its intended destination.

3. VXLAN vs VLAN

VXLAN (Virtual Extensible LAN) and VLAN (Virtual Local Area Network) are both network technologies used to segment and isolate traffic within a network, but they operate at different layers of the networking stack and have distinct characteristics. Here’s a breakdown of the differences between VXLAN and VLAN:

• (1) Layer: VLAN operates at Layer 2 of the OSI model, while VXLAN operates at Layer 3.

• (2) Scalability: VLANs are limited to 4,096 unique VLAN IDs due to the 12-bit VLAN identifier field in Ethernet frames. In contrast, VXLAN uses a 24-bit VXLAN Network Identifier (VNI), allowing for a much larger number virtual networks (over 16 million).

• (3) Encapsulation: VLAN tags are added to Ethernet frames by modifying the 802.1Q header, which adds a 4-byte VLAN tag. VXLAN encapsulates Ethernet frames within UDP packets, adding a 50-byte VXLAN header.

• (4) Addressing: VLANs use VLAN IDs to identify and separate traffic, typically assigned statically or through protocols like VLAN Trunking Protocol (VTP). VXLAN uses VNI values to identify virtual networks, and these values are dynamically assigned.

• (5) Spanning multiple Layer 3 domains: VLANs are limited to a single Layer 3 domain, requiring additional mechanisms like VLAN trunks or Layer 3 routing to extend them across multiple domains. VXLAN, on the other hand, can span multiple Layer 3 domains, enabling more flexible network designs and easier scalability.

• (6) Overlays: VXLAN is often used as an overlay network technology, allowing virtual networks to created and extended over an existing physical network infrastructure. VLANs, on the other hand, are typically used within a single physical network.

• (7) Multitenancy: VXLAN provides better support for multitenancy scenarios, where multiple customers or organizations share the same physical infrastructure while maintaining isolation. VXLAN’s larger address space allows for more granular segmentation and separation of traffic.

Overall, VXLAN designed to address the limitations of VLANs in terms of scalability, flexibility, and multitenancy. It is commonly used virtualized and cloud environments where there is a need for large-scale network segmentation and overlay networks.

4. VXLAN vs VPN

VXLAN (Virtual Extensible LAN) and VPN (Virtual Private Network) are both technologies used in networking, but they serve different purposes.

• (1) VXLAN:

VXLAN is a network virtualization technology that allows the creation of virtual Layer 2 networks over an existing Layer 3 infrastructure. It extends Layer 2 segments across Layer 3 boundaries by encapsulating Ethernet frames within IP packets. VXLAN is primarily used in data center environments to enable network virtualization and facilitate the creation of overlay networks. It helps overcome the limitations traditional VLANs by providing scalability, flexibility, and multi-tenancy support.

• (2) VPN:

A Virtual Private Network (VPN) is a secure connection established over a public network, typically the internet, that allows users access a private network remotely. VPNs provide encryption and authentication mechanisms to ensure the confidentiality and integrity of data transmitted between the user’s device and the private network.

      Key features of VPNs include:

• (1) Secure remote access:

VPNs allow users to securely connect to a private network from remote locations, such as home or public Wi-Fi networks, by encrypt their traffic and establishing a secure tunnel.

• (2) Privacy and anonymity:

By encrypting data and masking the user’s IP address, VPNs provide privacy and anonymity, making it difficult for third parties to monitor or track online activities.

• (3)Site-to-site connectivity:

VPNs can also be used establish secure connections between different networks, such as branch offices or multiple data centers, creating a virtual private network over the public internet.

In summary, VXLAN is a technology for network virtualization and overlay networks within data center environments, while VPN is a technology for secure remote access and site-to-site connectivity over public networks like the internet.

5. What role will VXLAN play in IoT?

VXLAN (Virtual Extensible LAN) is primarily a network virtualization technology used in data centers to provide overlay networks. While VXLAN itself is not directly tied to IoT (Internet of Things), it can play a role in supporting IoT deployments in certain scenarios.

Here are a few ways VXLAN can be relevant to IoT:

• (1) Scalability:

IoT devices generate massive amounts of data, and as the number of devices increases, traditional network architectures may struggle to handle the scale. VXLAN can help address this challenge by providing a scalable overlay network that allows for efficient communication between IoT devices and gateways.

• (2) Segmentation and Isolation:

In IoT deployments, it’s often necessary to segment and isolate different types of devices or groups devices for security, performance, or management reasons. It enables the creation of virtual networks overlays, allowing for logical separation of IoT devices while sharing the same physical infrastructure.

• (3) Multitenancy:

In scenarios where multiple organizations or tenants share the same IoT infrastructure, it can facilitate multitenancy by providing isolated virtual networks for each tenant. This allows for secure and independent operation of IoT services for different entities on a shared infrastructure.

• (4) Mobility and Flexibility:

IoT devices can be mobile or deployed in dynamic environments. VXLAN’s overlay network approach can provide flexibility and mobility support by decoupling the logical network from the underlying physical infrastructure. This allows IoT devices to move across different physical locations or networks without requiring reconfiguration of the underlying network infrastructure.

It’s important to note that while VXLAN can offer benefits in certain IoT use cases, there are other networking technologies and protocols specifically designed for IoT, such as MQTT (Message Queuing Telemetry Transport) and CoAP (Constrained Application Protocol), which focus on lightweight messaging and resource-constrained devices. The choice of networking technology in an IoT deployment depends on various factors, including the specific requirements, scale, and constraints of the IoT solution.

Relevant Article:

1. How to enable MQTT broker?
2. How to connect Bivocom IoT Router to Ubidots via MQTT?
3. How to set up MQTT on industrial cellular router?

The post What is VXLAN? And its role in IoT? appeared first on Bivocom.

1. Foreword

In this case, we will need 2pcs TR321 and a PC, one of it works as MQTT Broker, another TR321 and PC works as MQTT Client. All of these devices connected with the same LAN of gateway.

2. MQTT Broker Settings

• (1) Open the WEBUI of MQTT Broker router, check the network status, the WAN IP will be the MQTT Broker address.

• (2) Enable MQTT Broker feature at the Data Collect, then Save&Apply.

3. MQTT Client Settings

• (1) Network status of Client router

• (2) Diagnostics

Come to Setup-Diagnostics, we can check communication between MQTT Broker router and Client router here.

• (3) Data Collect

Now setup data collection at the Data Collect part. Enable data collect then set collect and report period.

Setup the corresponding interface parameters of slave device.

If using Modbus devices, need to setup Modbus Rules.

• (4) Server Settings

Chose the server protocol as Modbus, server address will be the WAN IP of MQTT Broker router, port is 1883, then set the public topic as you wish and setup a unique client ID. After click Save&Apply, you can see the connection status changes to CONNECTED.

• (5) Modbus Slave Setting

Here we use Modbus Slave to simulate slave device, setup the corresponding interface parameters of Client router then click connect. In this case, we set the value as 28, the data also can be checked at WEBUI.

• (6) MQTT.fx Settings

Open MQTT.fx or other software to works as MQTT client at PC, the Broker Address should be the WAN IP of Broker router, and Broker port will be 1883, click Connect after setup.

Then subscribe to the public topic which Client router set, here we set is as test123. We will receive the topic message from MQTT Client router.

Relevant MQTT Video: https://www.youtube.com/watch?v=qPBpjeokEwU

The post How to Enable MQTT Broker? appeared first on Bivocom.

What is MIPS?

MIPS or Microprocessor without Interlocked Pipelined Stages, is a reduced instruction set computing (RISC) architecture developed by MIPS Technologies, Inc. MIPS processors are used in a variety of applications, including networking equipment, digital signal processing, and embedded systems.

Like other RISC architectures, MIPS processors use a simplified instruction set to reduce the number of clock cycles required to execute instructions. This allows MIPS processors to achieve higher performance than traditional complex instruction set computing (CISC) architectures while using less power.

MIPS processors have been widely used in the past for desktop computers, servers, and video game consoles. However, they have since been mostly replaced by other architectures such as x86 and ARM in those markets. Nonetheless, MIPS remains popular in certain specialized areas where its strengths in embedded systems and signal processing are valued.

What is ARM?

ARM or Advanced RISC Machines, is a British semiconductor and software design company that specializes in the development of microprocessors, system-on-chip (SoC) designs, and related technologies. ARM processors are widely used in smartphones, tablets, laptops, smart TVs, and other embedded systems. The ARM architecture is based on a reduced instruction set computing (RISC) approach, which aims to simplify the processor design and improve performance by reducing the number of instructions executed per cycle. This allows ARM processors to consume less power, generate less heat, and offer better performance than traditional processors based on complex instruction set computing (CISC) architectures.

What is x86？

x86 is a family of instruction set architectures (ISAs) based on the Intel 8086 microprocessor and its successors. It is the most widely used ISA in personal computers, servers, and workstations.

The x86 architecture was introduced by Intel in 1978 with the release of the 8086 microprocessor, which was later succeeded by the 80286, 80386, and 80486 processors. These processors were used in early IBM-compatible personal computers and established the dominance of the x86 architecture in the PC market.

Today, x86 processors are produced by a number of manufacturers, including Intel, AMD, and VIA Technologies. They are used in a wide range of computing devices, from desktop and laptop computers to servers and supercomputers.

The x86 architecture has evolved over the years, adding new instructions and features while maintaining backward compatibility with older software. Today’s x86 processors can execute both 32-bit and 64-bit code, as well as virtualization instructions that allow multiple operating systems to run simultaneously on the same hardware.

What are the differences between MIPS, ARM, and x86?

MIPS, x86, and ARM are all different types of computer processor architectures. Here are some key differences between them:

1. Instruction Set Architecture (ISA): MIPS, x86, and ARM processors have different instruction sets, which dictate how they execute commands. MIPS is a Reduced Instruction Set Computing (RISC) architecture, while x86 is a Complex Instruction Set Computer (CISC) architecture. ARM processors use a hybrid of RISC and CISC concepts.
2. Endianness: MIPS and ARM processors are typically little-endian, meaning that the least significant byte of a word is stored at the lowest memory address. x86 processors can be either little-endian or big-endian.
3. Applications: MIPS was originally designed for embedded systems and has been used extensively in networking equipment, such as routers and switches. x86 processors are commonly found in desktop and laptop computers. ARM processors are used in a wide range of devices, including smartphones, tablets, and low-power embedded systems.
4. Performance: MIPS processors tend to have high performance per watt, making them well-suited for embedded systems where power consumption is a concern. x86 processors are often used in high-performance desktops and servers. ARM processors are known for their low power consumption and efficiency, making them ideal for mobile devices.
5. Instruction Set Compatibility: x86 processors have a long history and are widely used, so many software programs are specifically written to run on x86 processors. This has led to a large compatibility advantage for x86 based systems, however, ARM and MIPS processors also have their own sets of compatible software.

Overall, each architecture has its own strengths and weaknesses, and the choice of architecture ultimately depends on the specific requirements of the application being developed.

What are the advantages and disadvantages of MIPS, ARM and x86?

MIPS, ARM, and x86 are different processor architectures used in modern computing devices. Each architecture has its own set of advantages and disadvantages, which I will outline below:

MIPS: Advantages:

• Simple and easy to learn
• Reduced instruction set architecture (RISC) reduces complexity and increases performance
• Good for embedded systems and real-time applications

Disadvantages:

• Limited software support
• Not widely used outside of niche areas
• Less power efficient compared to newer architectures like ARM

ARM: Advantages:

• Power-efficient design makes it a popular choice for mobile devices and Internet of Things (IoT) devices
• Wide range of software and hardware support
• Good balance between performance and power consumption

Disadvantages:

• More complex than MIPS
• Limited support for legacy software
• Difficult to program in assembly language

x86: Advantages:

• Widely used in personal computers and servers
• Extensive software support
• High performance and flexibility

Disadvantages:

• Complex instruction set architecture (CISC) can make it slower than RISC architectures like MIPS or ARM
• High power consumption compared to ARM
• Limited use in embedded systems and IoT devices due to its high power consumption and complexity.

Overall, the choice between MIPS, ARM, and x86 depends on the specific needs of an application and the resources available. ARM is often the preferred choice for mobile and IoT devices due to its power efficiency, while x86 remains the dominant architecture in personal computers and servers. MIPS is typically used in niche areas such as embedded systems and specialized applications.

MIPS, ARM, x86 for IoT routers

MIPS, ARM, and x86 are all viable options for IoT routers, each with their own advantages and disadvantages. Here are some brief explanations of each:

1. MIPS: MIPS is a popular architecture choice for IoT devices due to its low power consumption and relatively simple instruction set. It is often used in embedded systems, including routers, where power efficiency is critical. However, the MIPS architecture is not as widely supported as some other architectures, and development tools and libraries may be more limited.
2. ARM: ARM is another popular architecture choice for IoT devices, offering a balance between power efficiency and performance. It is widely used throughout the industry and has a large ecosystem of development tools, libraries, and support resources available. ARM-based processors are found in a wide range of devices, including routers, smartphones, and tablets.
3. x86: x86 is a well-established architecture that is commonly used in desktop and server environments. It offers high performance and compatibility with many existing software applications but may not be as power-efficient as other architectures. However, with the rise of low-power Intel Atom processors, x86 has become a viable option for IoT devices, including routers.

Ultimately, the choice of architecture depends on the specific requirements of the IoT router project in question, including power consumption, performance, cost, and available development tools and resources.

The post Cons and Pros of MIPS, ARM and x86 in IIoT Industry appeared first on Bivocom.