GRD44B-5R User Manual: Difference between revisions

From Silbo Networks
No edit summary
No edit summary
 
(31 intermediate revisions by the same user not shown)
Line 19: Line 19:
Type the command '''Ipconfig'''
Type the command '''Ipconfig'''


[[File:How to connect with the SILBO RB44 application.png|frameless|620x620px]]
[[File:How to connect with the SILBO RB44 application.png|frameless|1024x1024px]]


It will provide the Ip address/url of that device through which the application can be accessed.
It will provide the Ip address/url of that device through which the application can be accessed.


[[File:Connecting_via_LAN_RB44.png|frameless|624x624px]]
[[File:Connecting_via_LAN_RB44.png|frameless|1024x1024px]]


== Log In ==
== Log In ==
Line 30: Line 30:
It will show the log in page of the application.
It will show the log in page of the application.


[[File:Login to device.png|frameless|620x620px]]
[[File:Login to device.png|frameless|1024x1024px]]


Give the valid credentials for the username and password to login to the application page.
Give the valid credentials for the username and password to login to the application page.
Line 40: Line 40:
The “Status” landing page shows all the detailed specification of the device like system, memory storage and connection tracking etc.
The “Status” landing page shows all the detailed specification of the device like system, memory storage and connection tracking etc.


[[File:GRD44B-5R Dashboard.png|frameless|620x620px]]
[[File:GRD44B-5R Dashboard.png|frameless|1024x1024px]]


The application is divided in to 8 Modules.
The application is divided in to 8 Modules.
Line 64: Line 64:
* Kernel Log
* Kernel Log


[[File:GRD44B-5R Info Section.png|frameless|620x620px]]
[[File:GRD44B-5R Info Section.png|1024x1024px]]


=== 1.1 Overview ===
=== 1.1 Overview ===
In overview module it displays all the specification categorically of a device like System, Memory, storage, Connection tracking, DHCP Lease.
In overview module it displays all the specification categorically of a device like System, Memory, storage, Connection tracking, DHCP Lease.


[[File:GRD44B-5R Dashboard.png|frameless|620x620px]]
[[File:GRD44B-5R Dashboard.png|1024x1024px]]


'''System:'''
'''System:'''
Line 75: Line 75:
In this section it displays the hardware configured specification of the device.
In this section it displays the hardware configured specification of the device.


[[File:GRD44B-5R System Section.png|frameless|620x620px]]
[[File:GRD44B-5R System Section.png|975x975px]]


The specifications details are as follows,
The specifications details are as follows,
Line 86: Line 86:
|1
|1
|Hostname
|Hostname
|45A05240882
|45A27240005
|This field  displays the router serial number of the device
|This field  displays the router serial number of the device
|-
|-
Line 96: Line 96:
|3
|3
|Firmware Version  and IPK Version
|Firmware Version  and IPK Version
|1.16_1.13_RC4
|1.17_1.15
|This field  displays the firmware version and IPK version
|This field  displays the firmware version and IPK version
|-
|-
|4
|4
|Application  Firmware version and IPK version
|Application  Firmware version and IPK version
|1.03_1.12
|1.03_1.13
|This field  displays the software version of the device.
|This field  displays the software version of the device.
|-
|-
Line 107: Line 107:
|Kernel Version
|Kernel Version
|4.14.180
|4.14.180
|This field  displays the kernel version of the device
|This field displays the kernel version of the device
|-
|-
|6
|6
|Local Time
|Local Time
|Friday, July 19, 2024 at 11:52:23 AM
|Wednesday, December 18, 2024 at 12:56:00  PM
|This field  displays the local time
|This field  displays the local time
|-
|-
|7
|7
|Uptime
|Uptime
|1h 48m 3s
|5h 27m 5s
|This field  displays the uptime of the device
|This field  displays the uptime of the device
|-
|-
|8
|8
|Load Average
|Load Average
|0.66 0.29 0.17
|0.31 0.27 0.19
|This field  displays the average load
|This field displays the average load
|}
|}
'''Memory:'''
'''Memory:'''
Line 128: Line 128:
In this section it displays the memory configured specification of the device.
In this section it displays the memory configured specification of the device.


[[File:IAB44C Memory Section.png|frameless|620x620px]]
[[File:IAB44C Memory Section.png|1024x1024px]]


The specifications details are as follows.
The specifications details are as follows.
{| class="wikitable"
{| class="wikitable" style="height:auto; width:100%; text-align:center;"
|SN
!SN
|Field name
!Field name
|Sample value
!Sample value
|Description
!Description
|-
|-
|1
|1
Line 163: Line 163:
In this section it displays the status of storage as root and temporary usage specification of the device.
In this section it displays the status of storage as root and temporary usage specification of the device.


[[File:IAB44C Storage Section.png|frameless|620x620px]]
[[File:IAB44C Storage Section.png|975x975px]]




Line 188: Line 188:
In this section you can monitor IPv4 WAN status.
In this section you can monitor IPv4 WAN status.


[[File:IPv4 Wan Status.png|frameless|620x620px]]
[[File:IPv4 Wan Status.png|1024x1024px]]


The specifications details are as follows.
The specifications details are as follows.
Line 229: Line 229:
This section displays SIM details only when the SIM card is active.
This section displays SIM details only when the SIM card is active.


[[File:IAB44C Sim Information.png|frameless|620x620px]]
[[File:IAB44C Sim Information.png|1024x1024px]]


'''Connection Tracking:'''
'''Connection Tracking:'''
Line 235: Line 235:
In this section it displays the status of connection tracking for the device.
In this section it displays the status of connection tracking for the device.


[[File:Connection Tracking.png|frameless|620x620px]]
[[File:Connection Tracking.png|1024x1024px]]


The specifications details are as follows.
The specifications details are as follows.
Line 255: Line 255:
In this section it displays the DHCP lease of the temporary assignment of an IP address to a device on the network.
In this section it displays the DHCP lease of the temporary assignment of an IP address to a device on the network.


[[File:IAB44C DHCP Leases.png|frameless|620x620px]]
[[File:IAB44C DHCP Leases.png|1024x1024px]]


The specifications details are below.
The specifications details are below.
Line 289: Line 289:
This page provides on screen System logging information. In this page the user gets to view the system logs.
This page provides on screen System logging information. In this page the user gets to view the system logs.


[[File:System Log.png|frameless|620x620px]]
[[File:GRD44B-5R System log.png|1024x1024px]]


=== 1.3 Kernel Log ===
=== 1.3 Kernel Log ===
Line 296: Line 296:
In this page the user gets to view the Kernel logs.
In this page the user gets to view the Kernel logs.


[[File:Kernel Log.png|frameless|620x620px]]
[[File:GRD44B 5R Kernel Log.png|1024x1024px]]
 




Line 305: Line 306:


* Network
* Network
* VLAN
* Sim Switch
* Sim Switch
* Internet
* Multi-WAN
* VPN
* VPN
* Firewall
* Firewall
* Loopback Rule
* Loopback Rule
* VRRP
* Remote Monitoring
* Remote Monitoring
* Tunnel
* Tunnel


[[File:Settings.png|frameless|620x620px]]
[[File:GRD44B 5R Settings.png|1024x1024px]]


=== 2.1 Network ===
=== 2.1 Network ===
In this section the user does all the setting related configuration with reference to network like Ethernet Setting, Cellular Setting, Band lock and Operator Lock, Wi-Fi, Guest Wi-Fi, Wireless Schedule, SMS Setting, Loopback IP.
In this section the user does all the setting related configuration with reference to network like Ethernet Setting, Cellular Setting, Band lock and Operator Lock, Wi-Fi, Guest Wi-Fi, Wireless Schedule, SMS Setting, Loopback IP.


[[File:IAB44C Network Settings .png|frameless|620x620px]]
[[File:GRD44B-5R Network configuration.png|1024x1024px]]


'''Ethernet Setting:'''
'''Ethernet Setting:'''
Line 324: Line 327:
In this page it will display all the configured port that is attached with the device.
In this page it will display all the configured port that is attached with the device.


For this device 5 ports are configured. Ethernet mode can be configured as WAN and as LAN as well. Ethernet LAN Connection settings can be configured as DHCP server or Static.
For this device 5 ports are configured.
 
Ethernet mode can be configured as WAN and as LAN as well.
 
Ethernet WAN Connection settings can be configured as DHCP, Static and PPOE.
 
[[File:GRD44B-5R Ethernet settings.png|1024x1024px]]
 
'''EDIT:'''
 
To add a new Interface, click on ‘Add’.
 
To edit the existing device the user needs to click on the edit option.


[[File:Setting_Ethernet_Settings.png|frameless|620x620px]]
Once the changes are done click on the update button to save all the changes.


'''For port 5 settings,'''
Click on the deleted button to delete the existing device detail.


Kindly select the option '''LAN''' for '''Port 5 mode LAN/WAN'''. Based on the option selected the field will also change. The user needs to configure all the required field and click on save.
[[File:GRD44B-5R Network configuration edit.png|1024x1024px]]


[[File:For_port_5_setting.png|frameless|620x620px]]
Specification details are given below:  '''Type: WAN'''
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field Name
|Sample value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Port 5 mode LAN/WAN
|Physical Device
|LAN
|Ex: eth0.5
|This field displays the port mode selection
|This indicates a network interface on which our  network is connected. This setting is by default (Editable).
|-
|-
|2
|2
|Port 5 Ethernet Protocol  [LAN Eth0.1]
|Type
|1.) DHCP Server
|'''WAN'''/LAN
|This designates whether the interface is part  of the WAN or LAN.


2.) Static
WAN: Connects the device to the internet.
|This field  displays the  Ethernet mode selection
 
LAN: Connects the device to the internal network.
|-
| colspan="4" |                                                                     '''Protocol: Static'''
|-
|-
|3
|3
|Port 5 DHCP Server IP
|Static IP Address
 
|Ex: 192.168.1.10
Port 5 Static IP
|The manually assigned IP address for the  interface.
|1.) 192.168.10.1
 
2.) 5.6.7.8
|This field displays DHCP server and static IP configured.
|-
|-
|4
|4
|Port 5 DHCP and Static Netmask
|Static Netmask
|255.255.255.0
|Ex: 255.255.255.0
|This field displays DHCP server and static Netmask address configured
|Subnet mask corresponding to the IP address.
|-
|-
|5
|5
|Port 5 DHCP Start Address
|Static Gateway
|100
|Ex: 192.168.1.1
|This field displays DHCP server start address configured
|The IP address of the gateway (router) that the  interface will use to send traffic outside its own subnet.
|-
| colspan="4" |                                                                     '''Protocol: DHCP'''
|-
|-
|6
|6
|Port 5 DHCP Limit
|DHCP Gateway
|50
|Ex: 10.1.1.1
|This field displays DHCP server limit
|The IP address of the DHCP server (often the same as the router or gateway).
|}
Kindly select the option '''EWAN2''' for '''Port 5 mode LAN/WAN'''. Based on the option selected the field will also change. The user needs to configure all the required field and click on the save to save the required fields.
 
[[File:Port_5_mode_LAN-WAN.png|frameless|620x620px]]
 
The specifications details are below.
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|1
| colspan="4" |                                                                     '''Protocol: PPPoE'''
|Port 5 mode WAN
|EWAN2
|This  field displays the port mode selection
|-
|-
|2
|7
 
|Username
|Any Name
|The username provided by your ISP for PPPoE  authentication.
|-
|8
|Password
|*****
|The password provided by your ISP for PPPoE  authentication.
|-
|9
|Access Concentrator
|
|Typically, the name of the ISP's PPPoE server.
|-
|10
|Service Name
|
|Sometimes required by ISPs, this field  specifies a particular service offered by the ISP.
|-
|11
|Gateway
|Ex: 0.0.0.0
|The IP address used as the default route.
|-
|12
|MAC Address
|Ex: D0:93:95:B0:98:6B
|The hardware (MAC) address of the network  interface. This is unique to every network device.
|-
|13
|Override MAC Address
|Ex: D0:93:95:B0:98:6B
|This field allows you to manually set a  different MAC address if needed.


If left blank, the default MAC address is used.
|-
|14
|Create Firewall Zone
|Enable/Disable
|You can assign this interface to a particular  firewall zone, which determines its access rules (e.g., WAN zone for internet  traffic, LAN zone for internal traffic).
|-
| colspan="4" |'''Advanced Settings: Enable/Disable'''
|-
|15
|Broadcast
|Ex: 192.168.123.34
|Broadcast address for the network, typically  calculated based on the IP and subnet mask.
|-
|16
|Override MTU
|Ex: 1500
|MTU size controls the maximum packet size that  can be sent over the network.


Default is usually 1500 bytes.
|-
|17
|Delegate
|Enable/Disable
|If checked, it allows delegation of prefixes  for IPv6, often left unchecked unless needed.
|-
|18
|Force Link
|Enable/Disable
|Forces the interface to be up even if no  physical link is detected.
|-
|19
|IPv4 Route Table
|Enable/Disable
|This field is used to specify static routes for  IPv4.
|-
|20
|Table No.
|'''254''': Default  main routing table.


'''100''': Custom  routing table for specific purposes.
|'''Default Table (Main Table)''': Usually, there is a default routing table  (often Table No. 254 or 255) where all the routes are stored by default.


|Ethernet Protocol Port 5 WAN
'''Custom Table''': You can  specify a different table number if you are managing multiple routing policies (e.g., VoIP traffic, VPN traffic).
|1.) DHCP client
|}


2.) Static


3.) PPPoE
'''Type: LAN'''


4.) PPTP
[[File:Grd44b 5r LAN config.png|1024x1024px]]


5.) L2TP
|1.) Automatically obtains IP  address and network configuration from a DHCP server.


2.) Manually set a fixed IP  address and network configuration.
Specification details are given below:
 
{| class="wikitable"
3.) Point-to-Point Protocol  over Ethernet, used for connecting to DSL services.
|SN
 
|Field  Name
4.) Point-to-Point Tunnelling  Protocol, used for establishing VPN connections.
|Sample  Value
 
5.) Layer 2 Tunnelling  Protocol, another VPN protocol option.
|-
|3
|Gateway
|192.168.1.1
|This field displays gateway address  configured
|}
Click on the save once all the configuration is done and click on the update button to update all the information.
 
 
'''SW_LAN settings,'''
 
In this part the user can configure the setting for SW_LAN.
 
'''Note:''' After any changes made, save and update the page below.
 
[[File:SW_LAN_Settings.png|frameless|620x620px]]
 
The specifications details are below.
{| class="wikitable"
|SN
|Field  name
|Sample  value
|Description
|Description
|-
|-
|1
|1
|SW_LAN Ethernet Protocol
|Physical Device
|DHCP  Server
|Ex: eth0.1
|This field  displays the Ethernet  mode selection.
|This is the network interface identifier.
|-
|-
|2
|2
|SW_LAN DHCP Server IP
|Type
|192.168.10.1
|WAN/'''LAN'''
|This field displays DHCP server IP configured which can be changed accordingly.
|This designates whether the interface is part  of the WAN or LAN.
 
WAN: Connects the device to the internet.
 
LAN: Connects the device to the internal network.
|-
|-
|3
|3
|SW_LAN  DHCP Netmask
|Protocol
|255.255.255.0
|Static
|This field displays DHCP server Netmask  address configured.
|This means that the IP address, netmask, and  other network settings are manually configured rather than being  automatically assigned by a DHCP server.
|-
|-
|4
|4
|SW_LAN  DHCP Start Address
|IP Address
|100
|Ex: 192.168.10.1
|This field displays DHCP server start address configured.
|This is the static IP address assigned to the interface. It acts as the gateway IP address for devices connected to this  LAN.
|-
|-
|5
|5
|SW_LAN  DHCP Limit
|Static Netmask
|50
|Ex: 255.255.255.0
|This field displays DHCP server limit.
|This is the subnet mask for the network.
|-
|-
|6
|6
|DNS  Server
|MAC Address
|1
|Ex: D0:93:95:B0:98:6C
|This filed display number of DNS server availability.
|This is the hardware (MAC) address of the network interface, which uniquely identifies this device on the network.
|-
|-
|7
|7
|DNS  Server Address
|Override MAC Address
|8.8.8.8
|
|This filed display the DNS  server address.
|This allows you to manually enter a different  MAC address if needed.
|}
|-
|8
|Enable DNS
|Enable/Disable
|If this option is enabled, the interface will  act as a DNS resolver for the devices on the LAN, using the specified DNS  server.
|-
|9
|DNS Server Address
|Ex: 8.8.8.8
|This is the IP address of the DNS server that will be used by devices on the LAN to resolve domain names to IP addresses.


More than one DNS Address can be added.
|-
|10
|Enable DHCP Server
|Enable/Disable
|If enabled, this setting allows the interface  to function as a DHCP server, automatically assigning IP addresses to devices  connected to the LAN.
|-
|11
|DHCP Start Address
|70
|The DHCP server will begin assigning IP  addresses starting from 192.168.10.70
|-
|12
|DHCP Limit
|100
|This specifies the number of IP addresses the  DHCP server can assign. Starting at 192.168.10.70 and with a limit of 100,  the server can assign addresses up to 192.168.10.169.
|-
|13
|Lease Time Duration
|Hours-(H)


After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
Minutes-(M)
 


'''Static option for SW_LAN Ethernet Protocol:'''
Seconds-(S)
|'''Hours-(H)''': This  indicates that the lease time for each IP address assignment is measured in  hours.


Select the option of static from the drop-down menu for SW_LAN Ethernet Protocol.
'''Minutes-(M):''' This  indicates that the lease time for each IP address assignment is measured in minutes.


'''Note:''' After any changes made, save and update the page below.
'''Seconds-(S):''' This  indicates that the lease time for each IP address assignment is measured in seconds.
 
|-
[[File:Static_option_for_SW_LAN_Ethernet_Protocol.png|frameless|620x620px]]
|14
 
|Lease Time
The specifications details are below.
|12
{| class="wikitable"
|The DHCP lease time is set to 12 hours. After  this period, a device must renew its IP address lease with the DHCP server to  continue using the assigned IP address.
|SN
|Field name
|Sample value
|Description
|-
|-
|1
|15
|SW_LAN Ethernet Protocol
|Create Firewall Zone
|Static
|Enable/Disable
|This field displays the Ethernet mode selection
|You can assign this interface to a particular firewall zone, which determines its access rules (e.g., WAN zone for internet traffic, LAN zone for internal traffic).
|-
|-
|2
|16
|SW_LAN static IP
|Internet Over SW_LAN
|192.168.5.1
|Enable/Disable
|This field displays static server IP configured.
|Allow all outbound traffic from the LAN to the internet.
|-
|-
|3
| colspan="4" |'''Advanced Settings: Enable/Disable'''
|SW_LAN  Netmask
|255.255.255.0
|This field displays static server Netmask  address configured
|-
|-
|4
|17
|DNS  Server
|Broadcast
|1
|Ex: 192.168.123.34
|This filed display number of DSN server availability
|Broadcast address for the network, typically calculated based on the IP and subnet mask.
|-
|-
|5
|18
|DSN  Server Address
|Override MTU
|8.8.8.8
|Ex: 1500
|This filed display the DSN server address.
|MTU size controls the maximum packet size that can be sent over the network.
|}


Default is usually 1500 bytes.
|-
|19
|Delegate
|Enable/Disable
|If checked, it allows delegation of prefixes  for IPv6, often left unchecked unless needed.
|-
|20
|Force Link
|Enable/Disable
|Forces the interface to be up even if no  physical link is detected.
|-
|21
|IPv4 Route Table
|Enable/Disable
|This field is used to specify static routes for  IPv4.
|}
Save and Update once configuration changes have been made.
'''Relay Server:'''
A relay server typically functions in a network to forward requests (usually DHCP or DNS) from clients to
a designated server when the server is on a different network segment.
[[File:GRD44B 5R Relay server.png|1024x1024px]]
'''EDIT:'''
To edit the existing device the user needs to click on the edit option.
Once the changes are done click on the save button to save all the changes.
Click on the deleted button to delete the existing device detail.


After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
[[File:GRD44B 5R Relay server edit.png|1024x1024px]]
 
 
'''Cellular Setting:'''
 
In this page, the user needs to configure the various details with respect to the SIM.


Select single cellular single sim where the user must configure the APN details of the sim used for the router device. The Configurations can be done based on the SIM usage, with respect to IPV4 or IPV6.


[[File:Cellular Setting.png|frameless|620x620px]]
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field Name
|Sample  value
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|Cellular Enable
|Interface
|Checkbox
|1.)    eth0.1
|Check this box to  enable cellular functionality.
 
2.)    ra0
|1) eth0.1  typically represents a VLAN where the relay will listen for client requests.
 
2) If your  device is broadcasting a Wi-Fi network on the ra0 interface, any DHCP or DNS  relay settings will apply to devices connected via this wireless interface.
|-
|-
|2
|2
|Cellular Operation Mode
|Start IP Address
|1.) Single Cellular with Dual Sim
|Ex: 192.168.10.100
 
|This is the beginning IP address of the range that will be leased out to clients.
2.) Single Cellular with  Single SIM
|1.) This mode allows you to use one cellular modem with two SIM cards.
 
2.) This mode allows you to use one cellular modem with single SIM card.
|-
|-
|3
|3
|Cellular  Modem 1
|End IP  Address
|QuectelEC200A
|Ex: 192.168.10.150
|This  field displays the modem name.
|An IP address  that is in the same subnet as the Start IP Address and allows sufficient  addresses to be leased.
|-
|4
|Netmask
|Ex: 255.255.255.0
|A valid  subnet mask such as 255.255.255.0 (for a /24 network), or 255.255.0.0 (for a  /16 network).
|-
|5
|Lease Time
|For a 24-hour  lease time, set this value to 86400.
|This is the  amount of time that an IP address is assigned to a client before it needs to  request a renewal from the DHCP server.
|}
Save and update.
 
 
'''Cellular Setting:'''
 
In this page, the user needs to configure the various details with respect to the SIM.
 
Select single cellular single sim where the user must configure the APN details of the sim used for the router device. The Configurations can be done based on the SIM usage, with respect to IPV4 or IPV6.
 
[[File:GRD44B 5R Cellular settings.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|1
|Cellular Enable
|Checkbox
|Check this box to  enable cellular functionality.
|-
|2
|Cellular  Operation Mode
|1.) Single Cellular with Dual Sim
 
2.) Single Cellular with  Single SIM
|1.) This mode  allows you to use one cellular modem with two SIM cards.
 
2.) This mode allows you to  use one cellular modem with single SIM card.
|-
|3
|Cellular  Modem 1
|QuectelEC200A
|This  field displays the modem name.
|-
|-
|4
|4
Line 592: Line 741:
|-
|-
|10
|10
|SIM 1 MTU
|Ex: 1500 (a common MTU size)
|'''MTU (Maximum  Transmission Unit)''' defines the largest size of a data packet that can be  transmitted over the network.
|-
|11
|Choose SIM 2 APN Mode
|Choose SIM 2 APN Mode
|1.) Auto
|1.) Auto
Line 600: Line 754:
2.) Choose manual to enter the APN settings manually in case of  M2M SIM cards.
2.) Choose manual to enter the APN settings manually in case of  M2M SIM cards.
|-
|-
|11
|12
|SIM 2 Access Point Name
|SIM 2 Access Point Name
|airtelgprs.com
|airtelgprs.com
|Enter the APN  provided by your cellular service provider in case of M2M sim. For regular  sim cards APN name will be displayed automatically.
|Enter the APN  provided by your cellular service provider in case of M2M sim. For regular  sim cards APN name will be displayed automatically.
|-
|-
|12
|13
|SIM 2 PDP Type
|SIM 2 PDP Type
|IPV4
|IPV4
|Choose the  PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
|Choose the  PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
|-
|-
|13
|14
|SIM 2 Username
|SIM 2 Username
|
|
|Enter the  username if required by the APN. Leave blank if not required.
|Enter the  username if required by the APN. Leave blank if not required.
|-
|-
|14
|15
|SIM 2 Password
|SIM 2 Password
|
|
|Enter the  password if required by the APN. Leave blank if not required.
|Enter the  password if required by the APN. Leave blank if not required.
|-
|-
|15
|16
|SIM 2 Authentication Protocol
|SIM 2 Authentication Protocol
|None
|None
|Choose the  authentication protocol. Options typically include None, PAP, or CHAP.
|Choose the  authentication protocol. Options typically include None, PAP, or CHAP.
|-
|-
|16
|17
|SIM 2 MTU
|Ex: 1500 (a common MTU size)
|'''MTU  (Maximum Transmission Unit)''' defines the largest size of a data packet  that can be transmitted over the network.
|-
|18
|Primary SIM Switchback Enable
|Enable/Disable
|When enabled,  the device will automatically switch back to the primary SIM (SIM 1) after  switching to SIM 2, under certain conditions (e.g., SIM 1 regains network  availability).
|-
|19
|Primary SIM Switchback Time (In Minutes)
|Primary SIM Switchback Time (In Minutes)
|10
|10
|Enter the  time in minutes after which the system should switch back to the primary SIM  if it becomes available.
|Enter the  time in minutes after which the system should switch back to the primary SIM  if it becomes available.
|}
|}
After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.


'''Band lock and Operator Lock:'''
'''Band lock and Operator Lock:'''
Line 638: Line 806:
Bands available in the drop-down list.
Bands available in the drop-down list.


[[File:Band lock and Operator Lock.png|frameless|620x620px]]
[[File:GRD44B 5R Band and operator lock.png|1024x1024px]]


'''2G/3G option:'''
'''2G/3G option:'''


2G/3G: - 3G allows additional features such as mobile internet access, video calls and mobile TV. While the main function of 2G technology is the transmission of information through voice calls.
2G/3G: - 3G allows additional features such as mobile internet access, video calls and mobile TV.
[[File:2G-3G option.png|frameless|620x620px]]
 
The user should select the band check box available for 2g/3g from the given list. Bands available for selection under LTE for the bands available in that area.
While the main function of 2G technology is the transmission of information through voice calls.
 
 
''*Refer the image below*''
 
[[File:GRD44B 5R 2g-3g.png|1024x1024px]]  
 
The user should select the band check box available for 2g/3g from the given list. Bands available for selection under LTE for the bands available in that area.


'''Operator Selection Mode:'''
'''Operator Selection Mode:'''
Line 652: Line 827:
Once the check box is clicked there will be a dropdown list of the operator modes from which the user needs to select the mode. The user needs to select the operator mode from the given dropdown list.
Once the check box is clicked there will be a dropdown list of the operator modes from which the user needs to select the mode. The user needs to select the operator mode from the given dropdown list.


[[File:Band and Operator Lock settings 2.png|frameless|620x620px]]
[[File:GRD44B 5R Operator selection mode.png|1024x1024px]]
 


If the user selects the mode “Manual” or “Manual-Automatic” then one more text box will appear where the user must provide the operator code.
If the user selects the mode “Manual” or “Manual-Automatic” then one more text box will appear where the user must provide the operator code.


[[File:Band lock and Operator Lock 1.png|frameless|620x620px]]
[[File:GRD44B 5R Operator code.png|1024x1024px]]


After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.


'''Wi-Fi Setting:'''
'''Wi-Fi Setting:'''
Line 664: Line 841:
In this, router has the general setting and change country code, channel, radio mode, radio passphrase as per the requirement after clicking on enable Radio button.
In this, router has the general setting and change country code, channel, radio mode, radio passphrase as per the requirement after clicking on enable Radio button.


The user needs to select the respective radio mode based on its need.  
The user needs to select the respective radio mode based on its need.
 
[[File:Wifi General Settings .png|frameless|620x620px]]


[[File:GRD44B 5R Wifi settings.png|1024x1024px]]


It has 3 radio modes.
It has 3 radio modes.
Line 677: Line 853:
Access point and client
Access point and client


[[File:Access Point mode.png|frameless|620x620px]]
[[File:GRD44B 5R Access point.png|1024x1024px]]  
 


'''Access Point mode:'''
'''Access Point mode:'''
Line 683: Line 860:
In Access Point mode, a configuration in which a router, allows wireless devices to connect to a wired network by creating a Wi-Fi hotspot.
In Access Point mode, a configuration in which a router, allows wireless devices to connect to a wired network by creating a Wi-Fi hotspot.


[[File:Access Point mode.png|frameless|620x620px]]
[[File:GRD44b 5R Access point.png|1024x1024px]]  




'''Client point:'''  In client mode, the access point connects your wired devices to a wireless network. This mode is suitable when you have a wired device with an Ethernet port and no wireless capability, for example, a smart TV, Media Player, or Game console and you want to connect it to the internet wirelessly, select the Client Mode and give the Radio SSID & client passphrase.
'''Client point:'''  
 
In client mode, the access point connects your wired devices to a wireless network. This mode is suitable when you have a wired device with an Ethernet port and no wireless capability, for example, a smart TV, Media Player, or Game console and you want to connect it to the internet wirelessly, select the Client Mode and give the Radio SSID & client passphrase.
 
[[File:GRD44B 5R Client point.png|1024x1024px]]


[[File:Client Point RC44.png|frameless|620x620px]]


'''Access point and client point''':
'''Access point and client point''':
Line 694: Line 874:
Select this option for both type of connection, give both SSID and passphrase.
Select this option for both type of connection, give both SSID and passphrase.


[[File:Access point and client point.png|frameless|620x620px]]
[[File:GRD44B 5R Access point and client point.png|1024x1024px]]


After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.


The specifications details are below.
The specifications details are below.
Line 789: Line 968:
(50 value is default)
(50 value is default)
|}
|}
Click on save once changes have been made.  
Click on save once changes have been made.
 
 
 
'''Guest Wifi:'''
 
This option enables a separate Wi-Fi network for guests, isolated from the main network to enhance security and privacy. Guest Wi-Fi allows visitors or temporary users to connect to your network without accessing the main LAN resources.
 
[[File:GRD44B 5R GUEST WIFI.png|1024x1024px]]


'''Wireless Schedule:'''
'''Wireless Schedule:'''
Line 799: Line 986:
'''Note:''' This section is turned off by default, tick the box to activate it.
'''Note:''' This section is turned off by default, tick the box to activate it.


[[File:Wireless Schedule.png|frameless|620x620px]]
[[File:GRD44B 5R WIRELESS SCHEDULE.png|1024x1024px]]  


After configuring all the required information, the user should click on save and then click on update to update all the required information.
After configuring all the required information, the user should click on save and then click on update to update all the required information.
Line 805: Line 992:
The user can select more than one “day of the week” for scheduling the Wi-Fi working hours.
The user can select more than one “day of the week” for scheduling the Wi-Fi working hours.


[[File:Wifi Schedule.png|frameless|620x620px]]
[[File:GRD44B 5R SCHEDULE WIFI.png|965x965px]]


'''Loop back IP settings:'''
'''SMS Settings:'''


The loopback IP address, often referred to as “localhost.” it is used to establish network connections within the same device for testing and troubleshooting purpose.
User needs to enable SMS option in SMS settings page.


The loopback IP address, commonly represented as 127.0.0.1, is a special address used for testing network connectivity on a local machine.
This option is to validate the mobile numbers using which controlling commands could be sent to the


It allows a device to send network messages to itself without involving external networks, making it useful for troubleshooting and diagnostics.
router device.


1 to 5 mobile numbers can be authenticated by choosing from “Select Valid SMS user numbers” and


However, this IP can be changed as per requirement and to do that, Navigating to Setting>>Network configuration>> Loopback IP settings can be changed/updated.
adding the mobile numbers below respectively.


[[File:Loopback Update.png|frameless|620x620px]]
API key is the pass key used in the commands while sending SMS.


After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
Displayed in the below screen is the default API key which can be edited and changed as per choice.


After addition of the mobile number’s user needs to click on save button for changes to take place. 


'''SMS Settings:'''
''*Refer the image below*''


User needs to enable SMS option in SMS settings page.
[[File:GRD44B 5R SMS ENABLE.png|1024x1024px]]


This option is to validate the mobile numbers using which controlling commands could be sent to the router device.


1 to 5 mobile numbers can be authenticated by choosing from “Select Valid SMS user numbers” and adding the mobile numbers below respectively.
1.) Select valid user number max. 5 and add authorized phone number in the tab where you want to find the alert and click on '''‘SMS Response Enable’''', '''‘save’''' and '''‘update’''' button.
 
API key is the pass key used in the commands while sending SMS.
 
Displayed in the below screen is the default API key which can be edited and changed as per choice. After addition of the mobile number’s user needs to click on save button for changes to take place.
 
[[File:SMS Settings V2.png|frameless|620x620px]]
 
1.) Select valid user number max. 5 and add authorized phone number in the tab where you want to find the alert and click on '''‘SMS Response Enable’''', '''‘save’''' and '''‘update’''' button.  


2.) Now send SMS commands from the configured mobile number.
2.) Now send SMS commands from the configured mobile number.
Line 844: Line 1,024:


4.) After that it will send the router’s status once it has rebooted and is operational again.
4.) After that it will send the router’s status once it has rebooted and is operational again.


Mentioned below are a few commands which can be sent from the configured mobile number to the router device. Below two commands are One for rebooting the router device and another to get the uptime.
Mentioned below are a few commands which can be sent from the configured mobile number to the router device. Below two commands are One for rebooting the router device and another to get the uptime.
Line 852: Line 1,031:
2) {"device”: ["passkey ","API key"],"command”: “uptime"}
2) {"device”: ["passkey ","API key"],"command”: “uptime"}


'''Loop back IP settings:'''
The loopback IP address, often referred to as “localhost.” it is used to establish network connections within the same device for testing and troubleshooting purpose.
The loopback IP address, commonly represented as 127.0.0.1, is a special address used for testing network connectivity on a local machine.


After configuring all the required information, the user should click on save and then click on update to update all the required information.
It allows a device to send network messages to itself without involving external networks, making it useful for troubleshooting and diagnostics.
 
 
However, this IP can be changed as per requirement and to do that, Navigating to Setting>>Network configuration>> Loopback IP settings can be changed/updated.
 
[[File:GRD44 5R LOOPBACK IP SETTINGS.png|1024x1024px]]
 
After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.
 
=== 2.2 VLAN ===
'''VLAN (Virtual Local Area Network)''' is a network within a network that segregates traffic into different logical networks on the same physical hardware. VLANs help in managing traffic more effectively and securely.
 
It is further divided into 2 sections,
 
Port-Based VLAN


=== 2.2 SIM Switch ===
Tagged Port Configuration
In this page the user needs to configure the Sim for the given device.


[[File:SIM Switch.png|frameless|620x620px]]The user needs to select from the drop-down menu on which basis the sim needs to be switched.


[[File:Sim Switch Configuration.png|frameless|620x620px]]
'''Port-Based VLAN:'''


Once the user selects on “'''signal strength'''” then the parameters related to signal strength will pop up and the user needs to configure the parameters based on the requirement.
A VLAN configuration method where network ports are assigned to specific VLANs.


[[File:SIM Switch Configuration.png|frameless|620x620px]]
[[File:GRD44B 5R VLAN.png|1024x1024px]]


'''EDIT:'''


'''Threshold RSRP:'''
To add a new VLAN ID, click on ‘Add Device’.


This Needs to be set appropriately. Incorrect setting may cause unnecessary SIM switching. (In General, a BAD RSRP value range is -140 to -115 and FAIR RSRP value range is -115 to -105).
To edit the existing device the user needs to click on the edit option.


'''Threshold SINR:'''
Once the changes are done click on the save button to save all the changes.


This Needs to be set appropriately. Incorrect setting may cause unnecessary SIM switching. (In General, a BAD SNR value range is -20 to 0 and FAIR SNR value range is 0 to 13)
Click on the deleted button to delete the existing device detail.


Once the user selects on “'''Data Limit'''” then the parameters related to Data Limit will pop up and the user needs to configure the parameters based on the requirement.
[[File:GRD44B 5R VLAN CONFIG.png|1024x1024px]]


[[File:Threshold SINR.png|frameless|620x620px]]
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field Name
|Sample  value
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|SIM Switch Based on
|'''VLAN ID'''
|Data Limit
|1
|The user needs to select from the drop-down menu on what basis the sim needs to be switched.
|This is a unique identifier for a VLAN within a network.
 
|-
|-
|2
|2
|SIM 1 Data Usage Limit (In MB)
|'''Port 0'''
|1000
|Untagged
|The user needs to  set the limit for the data usage for SIM 1.
|When a port is set as untagged for a VLAN, it  means that traffic entering or exiting this port is automatically associated  with that VLAN without any VLAN tags being added to the frames.
|-
|-
|3
|3
|SIM 2 Data Usage Limit (In MB)
|'''Port 1'''
|1000
|Untagged
|The user needs to  set the limit for the data usage for SIM 2.
|
|-
|-
|4
|4
|Periodicity
|'''Port 2'''
|Daily
|tagged
|The user needs to  set the pattern/frequency to switch the sims.
|When a port is set as tagged for a VLAN, it  means that traffic on this port will include VLAN tags in the Ethernet  frames. These tags carry the VLAN ID, allowing switches and other devices to  know which VLAN the traffic belongs to.
|-
|-
|5
|5
|Day Of Month
|'''Port 3'''
|For Ex: 16
|Untagged
|The user needs to set the day for switching the sim.
|
|-
|6
|'''Port 4'''
|OFF
|When a port is marked as off for a VLAN, it means that the port is not participating in that VLAN at all. It will neither  send nor receive traffic associated with that VLAN.
|}
|}
Save and update the page.


=== 2.3 Internet ===
In this page the user needs to configure the internet connection to set the priority from the diverse options. The user should decide what kind of connection it needs to provide to the device like LAN, WAN etc. Once the connections are configured then click on save option and then on update.


[[File:Internet Connection Configurtion.png|frameless|620x620px]]
'''Tagged Port Configuration:'''


If the user needs to edit on the existing configuration, then the user should click on the “EDIT” button.
[[File:GRD44B 5R TAGGED BASED VLAN.png|1024x1024px]]


[[File:EWAN2 Edit Options.png|frameless|620x620px]]
'''EDIT:'''
 
To add a new VLAN ID, click on ‘Add Device’.
 
To edit the existing device the user needs to click on the edit option.


The specifications details are below.
Once the changes are done click on the save button to save all the changes.
 
Click on the deleted button to delete the existing device detail.
 
[[File:GRD44B 5R TAGGED BASED VLAN CONFIG.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field Name
|Sample  value
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|Name
|Type
|EWAN2
|802.1Q
|This field displays the name of the WAN connection
|'''IEEE 802.1Q''' is the standard protocol for VLAN tagging in Ethernet networks.
|-
|-
|2
|2
|Priority
|Parent Interface
|1
|Port 2
|In this dropdown  box the user needs to select the priority.
|It is the underlying physical interface like port 2 that carries the VLAN-tagged traffic.
|-
|}
|3
Save and update the page.
|Select Track IP Numbers
 
|2
=== 2.3 SIM Switch ===
|In this dropdown  the user needs to select the track number for the Ips. This specifies  the number of IP addresses that will be used for tracking the status of the  connection.
In this page the user needs to configure the Sim for the given device.
|-
|4
|TrackIP1
|8.8.8.8
|This is the first IP address used for tracking the connection. <code>8.8.8.8</code>  is a public DNS server provided by Google.
|-
|5
|TrackIP2
|8.8.4.4
|This is the second IP address used for  tracking the connection. <code>8.8.4.4</code>  is another public DNS server provided by Google.
|-
|6
|Reliability
|1
|This indicates the reliability threshold  for considering the connection as up. A value of <code>1</code> typically means that only one successful ping  response is needed to deem the connection reliable.
|-
|7
|Count
|1
|This specifies the number of consecutive  pings sent to the track IP addresses.
|-
|8
|Up
|1
|This indicates the number of successful  pings required to consider the connection as up.
|-
|9
|Down
|1
|This indicates the number of failed pings  required to consider the connection as down.
|}
Once the user is done with modification click on the save button to save all the changes and then click on the update button.


=== 2.4 VPN ===
[[File:GRD44B 5R SIM SWITCH CONFIGURE.png|1024x1024px]]
VPN stands for '''Virtual Private Network''', it establishes a connection between the system and a remote server, which is owned by a VPN provider.


Creating a point-to-point tunnel that encrypts the personal data, masks the IP address, and allows to block the required website to blocks via firewalls on the internet.
The user needs to select from the drop-down menu on which basis the sim needs to be switched.


Navigate to settings >= VPN, general settings and you will see all VPN options you wish to use.
[[File:GRD44B 5R SIM SWITCH CONFIGURE 2.png|1024x1024px]]


Refer the below figure.


[[File:VPN Configuration General Settings.png|frameless|620x620px]]
Once the user selects on “'''signal strength'''” then the parameters related to signal strength will pop up and the user needs to configure the parameters based on the requirement.


There are 5 types of setting available under VPN configuration.
[[File:GRD44B 5R SIM SIGNAL STRENGTH.png|1024x1024px]]


* General Settings
'''Threshold RSRP:'''
* IPSEC
* Open VPN
* Wireguard
* Zerotier


'''General Settings:'''
This Needs to be set appropriately. Incorrect setting may cause unnecessary SIM switching. (In General, a BAD RSRP value range is -140 to -115 and FAIR RSRP value range is -115 to -105).


In this page the user must choose which type of VPN connection is required for the device. The user must select from IPSEC, Open VPN, Wireguard or Zerotier based on its requirement. If required, the user can select all the options. The user needs to click on the save after selecting the option based on its use.
'''Threshold SINR:'''


[[File:VPN General Settings RC44.png|frameless|620x620px]]
This Needs to be set appropriately. Incorrect setting may cause unnecessary SIM switching. (In General, a BAD SNR value range is -20 to 0 and FAIR SNR value range is 0 to 13)


'''IPSEC:'''
Once the user selects on “'''Data Limit'''” then the parameters related to Data Limit will pop up and the user needs to configure the parameters based on the requirement.
 
IPSEC VPN is used to create a VPN connection between local and remote networks.
 
To use IPSEC VPN, the user should check that both local and remote routers support IPSEC VPN feature.
 
In this page the user can add/edit/delete the IPSEC VPN connection for the device.
 
[[File:IAB44C Ipsec VPN Dashboard.png|frameless|620x620px]]
 
The user needs to click on the update button once the required configuration is completed.
 
In IPSEC the user needs to click on edit button to edit the configuration of an existing VPN connection.
 
[[File:IAB44C Ipsec Edit Options.png|frameless|620x620px]]


Click on update once done with configurations.
[[File:GRD44B 5R DATALIMIT SET.png|1024x1024px]]
 
The tunnel will show established, showing the connection has been made.
 
[[File:VPN Configurtaion IPSEC .png|frameless|620x620px]]
 
 
Detailed specifications are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 1,030: Line 1,181:
|-
|-
|1
|1
|IPSEC
|SIM Switch Based on
|Site to Site VPN
|Data Limit
|In this dropdown the user should select the  IPSEC connection type.
|The user needs to select from the drop-down menu on what basis the sim needs to be switched.
 
|-
|-
|2
|2
|IPSEC Role
|SIM 1 Data Usage Limit (In MB)
|Client/Server
|1000
|In this dropdown  box the user needs to select the IPSEC role. The device is acting as a  client in the VPN setup (in this example).
|The user needs to set the limit for the data usage for SIM 1.
|-
|-
|3
|3
|Connection Type
|SIM 2 Data Usage Limit (In MB)
|Tunnel
|1000
|In this dropdown  the user needs to select the connection type. The user should select on the connection enable check box.
|The user needs to set the limit for the data usage for SIM 2.
|-
|-
|4
|4
|Connection mode
|Periodicity
|Route/add/'''start'''/trap
|Daily
|In this drop down list the user should select the mode for the connection. In this example '''start'''  is selected which means the VPN connection is initiated automatically.
|The user needs to set the pattern/frequency to switch the sims.
|-
|-
|5
|5
|Remote Server IP
|Day Of Month
|********
|For Ex: 16
|The IP address of the remote VPN server.
|The user needs to  set the day for switching the sim.
|}
After configuring all the required information, the user should click on the save.
 
=== 2.4 Multi-WAN ===
As shown below, this section has 4 categories,
 
'''Status'''
 
'''General settings'''
 
'''Failover'''
 
'''Load Balancing'''
 
[[File:GRD44B 5R MULTI WAN CONFIG.png|1024x1024px]]
 
 
In '''‘Status’''' tab user can see the active network connections on the device as shown above.
 
'''General Settings:'''
 
In general settings, select any one option from the drop-down menu which you wish to imply and click on save and update.
 
[[File:GRD44B 5R FAILOVER .png|1024x1024px]]
 
 
Click on save and update.
 
'''Failover:'''
 
'''NOTE:''' Please verify that the name to be added is in the interface section of the status tab.
 
[[File:GRD44B 5R FAILOVER 1.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:GRD44B 5R FAILOVER CONFIG.png|1024x1024px]]
 
 
The specifications details are below.
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|-
|6
|1
|Local ID
|Priority
|3.3.3.3
|Ex: 5
|The user needs to set the local id. It is the identification for the local VPN client.
|Setting a priority of 1 means this connection has the highest priority and will be used before any others with a higher  priority number.
|-
|-
|7
|2
|No. of local subnets
|Select Track IP Numbers
|1
|2
|In this dropdown the user needs to select how many subnets will be connected.
|In this dropdown the user needs to select the  track number for the Ips. This specifies the number of IP addresses  that will be used for tracking the status of the connection.
|-
|-
|8
|3
|Local Subnet 1
|TrackIP1
|172.16.31.25/32
|8.8.8.8
|In this text box  the user needs to put the specific local subnet included in the VPN.
|The system  will ping this IPV4 IP address to check if the connection is up and working.  You can even add any whitelisted IP.
|-
|-
|9
|4
|Remote id
|TrackIP2
|1.1.1.1
|8.8.4.4
|In this text box  the user needs to put the id of the remote connection. It is the identification for the remote VPN server.
|The system  will ping this IPV4 IP address to check if the connection is up and workingYou can even add any whitelisted IP.
|-
|-
|10
|5
|No of remote subnet
|Reliability
|1
|1
|In this dropdown the user needs to select how many subnets it will be connected remotely.
|If reliability is set to 1, it might mean the connection is considered reliable  if it successfully pings at least one of the tracked IP addresses.
|-
|-
|11
|6
|Remote subnet
|Count
|10.1.1.0/24
|1
|In this text box the user needs to put the address of the remote subnet. The specific remote subnet included in the VPN.
|Setting Count to 1 means the device will send one ping to each IP address to check for connectivity.
|-
|-
|12
|7
|Key exchange
|Up
|Ikev1
|3
|In this dropdown the user should select the which key exchange version to be selected.
|If set to 3, the connection will be considered "up" only if all three pings are  successful.
|-
|-
|13
|8
|Aggressive
|Down
|Yes/No
|3
|In this dropdown the user should select either yes or no.
|If set to 3, the connection will be considered "down" if all three pings fail.
|}
Click on save and update tab.
 
'''Load Balancing:'''
 
Load balancing is a network management technique used to distribute traffic across multiple network connections or servers to optimize resource use, maximize throughput, minimize response time, and ensure reliability.
 
'''Task''': Distributes network traffic evenly across multiple connections (e.g., multiple WAN links) or servers.
 
'''Purpose''': This ensures that no single connection or server is overwhelmed with too much traffic, which could lead to congestion and slower performance.
 
[[File:GRD44B 5R LOAD BALANCING.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:GRD44B 5R LOAD BALANCING CONFIG.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|14
|1
|IKE Lifetime (In Seconds)
|Traffic Distribution Ratio
|86400
|Ex: 60%
|The lifetime of the IKE phase in seconds  (1 day).
|If you have  two connections and set one to 60% and the other to 40%, traffic will be  distributed accordingly.
 
The ratio must be the same for CWAN1_0 and CWAN1_1.
|-
|-
|15
|2
|Lifetime (in seconds)
|Select Track IP Numbers
|28800
|2
|The lifetime of the IPsec SA (Security Association) in seconds (8 hours).
|The system  will track two IP addresses to determine if the network connection is active and reliable.
|-
|-
|16
|3
|Enable DPD Detection
|TrackIP1
|'''1'''
|8.8.8.8
 
|The system will ping this IPV4 IP address to check if the connection is up and workingYou can even add any whitelisted IP.
0
|Indicates whether Dead Peer Detection is enabled to detect a lost connection. Enable this option as per server-side settings.
|-
|-
|17
|4
|Time Interval (In Seconds)
|TrackIP2
|60
|8.8.4.4
|This option is available only if DPD  Detection is enabled. The time interval is the interval for DPD checks.
|The system  will ping this IPV4 IP address to check if the connection is up and working. You can even add any whitelisted IP.
|-
|-
|18
|5
|Action
|Reliability
|'''Restart'''/clear/hold/
|1
 
|With a reliability setting of 1, the connection might be considered reliable if at least one ping is successful.
trap/start
|'''Restart''': Action to take when DPD detects a lost connection (restart the connection). Select as per server-side setting.
|-
|-
|19
|6
|Authentication Method
|Count
|'''PSK'''
|1
|'''PSK''': Pre-shared  key is used for authentication. Select this option for authentication as per  sever side setting.
|The system  will send one ping to each tracked IP to check the connection's status.
|-
|-
|20
|7
|Multiple Secrets
|Up
|1/'''0'''
|3
|Indicates whether multiple PSK secrets are used. Enable only if required.
|The system requires 3 successful pings for the connection to be marked as  "up."
|-
|-
|21
|8
|PSK Value
|Down
|******
|3
|Pre-shared key value (masked for security).
|If 3 pings fail, the system will mark the connection as "down," and it may  switch to an alternate connection if available.
|}
|}
{| class="wikitable"
Click on save and update tab.
| colspan="7" |'''Proposal settings Phase I'''
|-
|22
| colspan="2" |'''Encryption Algorithm'''
| colspan="3" |AES 128


AES 192
=== 2.5 VPN ===
VPN stands for '''Virtual Private Network''', it establishes a connection between the system and a remote server, which is owned by a VPN provider.
 
Creating a point-to-point tunnel that encrypts the personal data, masks the IP address, and allows to block the required website to blocks via firewalls on the internet.
 
Navigate to settings >= VPN, general settings and you will see all VPN options you wish to use.


'''AES 256'''
Refer the below figure.


3DES
[[File:GRD44B 5R VPN CONFIGURATION.png|1024x1024px]]
|'''AES 256''': Encryption algorithm  for Phase I. Select as per server-side configuration. Both server and client  should have same configuration.
|-
|23
| colspan="2" |Authentication Phase I
| colspan="3" |SHA1


MD5
There are 7 types of setting available under VPN configuration.


SHA 256
* General Settings
* IPSEC
* Open VPN
* Wireguard
* Zerotier
* PPTP
* L2TP


SHA 384


'''SHA 512'''
'''General Settings:'''
|'''SHA 512''': Authentication  algorithm for Phase I.


Select as per  server-side configuration. Both server and client should have same  configuration.
In this page the user must choose which type of VPN connection is required for the device. The user must select from the above VPN based on its requirement. If required, the user can select all the options. The user needs to click on the save after selecting the option based on its use.
|-
|24
| colspan="2" |DH Group
| colspan="3" |MODP768(group1)


MODP1024(group2)
[[File:GRD44B 5R VLAN CONFIG GENERAL SETTINGS.png|1024x1024px]]


MODP1536(group5)
'''IPSEC:'''


'''MODP2048(group14)'''
IPSEC VPN is used to create a VPN connection between local and remote networks.


MODP3072(group15)
To use IPSEC VPN, the user should check that both local and remote routers support IPSEC VPN feature.


MODP4096(group16)
In this page the user can add/edit/delete the IPSEC VPN connection for the device.
|'''MODP2048 (group14)''':  Diffie-Hellman group for key exchange.


Select as per  server-side configuration. Both server and client should have same  configuration.
[[File:GRD44B 5R VPN CONFIGURATION IPSEC.png|1024x1024px]]The user needs to click on the update button once the required configuration is completed.
|-
| colspan="7" |'''Proposal settings Phase II'''
|-
| colspan="2" |25
| colspan="2" |Hash Algorithm
|AES 128


AES 192
In IPSEC the user needs to click on edit button to edit the configuration of an existing VPN connection.


'''AES 256'''
[[File:GRD44B 5R VPN CONFIGURATION IPSEC CONFIGURATION.png|1024x1024px]]


3DES
Click on update once done with configurations.
| colspan="2" |'''AES 256''': Encryption algorithm  for Phase II. Select as per server-side configuration. Both server and client  should have same configuration.
|-
| colspan="2" |26
| colspan="2" |Authentication Phase II
|SHA1


MD5
The tunnel will show established, showing the connection has been made.


SHA 256
[[File:GRD44B 5R ipsec configured.png|1024x1024px]]


SHA 384
IPSEC VPN has been Eshtablished.


'''SHA 512'''
Detailed specifications are below:
| colspan="2" |'''SHA 512''': Authentication algorithm for Phase II.
{| class="wikitable"
 
|SN
Select as per  server-side configuration. Both server and client should have same configuration.
|Field name
|Sample value
|Description
|-
|1
|IPSEC
|Site to Site VPN
|In this dropdown the user should select the IPSEC connection type.
|-
|-
| colspan="2" |27
|2
| colspan="2" |PFS Group
|IPSEC Role
|MODP768(group1)
|Client/Server
 
|In this dropdown box the user needs to select the IPSEC role. The device is acting as a  client in the VPN setup (in this example).
MODP1024(group2)
 
MODP1536(group5)
 
'''MODP2048(group14)'''
 
MODP3072(group15)
 
MODP4096(group16)
| colspan="2" |'''MODP2048 (group14)''': Perfect  Forward Secrecy group.
 
Select as per server-side configuration. Both server and client should have same  configuration.
|}
Click on save and then update the page for changes to reflect.
 
'''Open VPN:'''
 
In the OpenVPN connection, the home network can function as a server, and the remote device can access the server through the router which acts as an OpenVPN Server gateway.
 
To use the VPN feature, the user should enable OpenVPN Server on the router, and install and run VPN client software on the remote device.
 
[[File:Open VPN Settings .png|frameless|620x620px]]
 
The user needs to “upload” the respective certificate from a valid path and then click on the “Update.
 
Once the OpenVPN connection starts the user will get an option to enable/disable the VPN connection as and when required.
 
By clicking on the enable/disable button, the user can start/stop the VPN connection.
 
[[File:Open VPN Dashboard.png|frameless|620x620px]]
 
VPN has been established.
 
'''WireGuard:'''
 
'''WireGuard''' is simple, fast, lean, and modern VPN that utilizes secure and trusted cryptography.
 
Click on “Edit” to start configurations as needed.
 
[[File:Wire Guard RC44.png|frameless|620x620px]]
 
EDIT:
 
[[File:Wire Guard RC44 Setttings.png|frameless|620x620px]]
 
Click on the save button after the required configuration.
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|-
|1
|3
|Wireguard Role
|Connection Type
|Client/Server
|Tunnel
|In this dropdown box the user needs to select the wireguard role.
|In this dropdown the user needs to select the connection type. The user should select on the  connection enable check box.
|-
|2
|Listen Port
|51820
|The UDP port on which the WireGuard client listens for incoming connections.
|-
|3
|IP Addresses
|10.0.0.1/24
|The IP  address and subnet mask assigned to the WireGuard client's interface. This  address is used within the VPN.
|-
|-
|4
|4
|Allowed PeerIPs
|Connection mode
|10.1.1.1
|Route/add/'''start'''/trap
|The IP address of the allowed peer(s) that can connect to this WireGuard client. This might need adjustment based on the actual peer IPs used in the network.
|In this drop down list the user should select the mode for the connection. In this example '''start''' is selected which means the VPN connection is initiated automatically.
|-
|-
|5
|5
|Endpoint HostIP
|Remote Server IP
|10.1.1.1
|********
|The IP address of the WireGuard server (the endpoint to which the client connects).
|The IP address of the remote VPN server.
|-
|-
|6
|6
|Endpoint HostPort
|Local ID
|51820
|3.3.3.3
|The port on the WireGuard server to which the client connects.
|The user needs to set the local id. It is the identification for the local VPN client.
|-
|-
|7
|7
|PeerPublicKey
|No. of local subnets
|*****
|1
|The public key of the peer (the server) the client is connecting to. This key is part of  the public-private key pair used in WireGuard for encryption and  authentication.
|In this dropdown the user needs to select how many subnets will be connected.
|-
|-
|8
|8
|Enable Preshared key
|Local Subnet 1
|Yes/No
|172.16.31.25/32
|This option indicates that a pre-shared key (PSK) is used in addition to the public-private key pair for an extra layer of security.
|In this text box the user needs to put the specific local subnet included in the VPN.
|-
|-
|9
|9
|Preshared key
|Remote id
|*****
|1.1.1.1
|The actual pre-shared key value shared between the client and the server. This option appears only if you have enabled preshared key.
|In this text box the user needs to put the id of the remote connection. It is the identification for the remote VPN server.
|}
|-
'''Zerotier:'''
|10
 
|No of remote subnet
ZeroTier is a tool that lets you create your own private network over the internet.
|1
 
|In this dropdown  the user needs to select how many subnets it will be connected remotely.
Go to ZeroTier Central and sign up for a free account. In ZeroTier Central, click on "Create a Network". This will generate a unique 16-digit network ID for your new network.
|-
 
|11
Go to settings => VPN, in general settings, enable ZeroTier and save.
|Remote subnet
 
|10.1.1.0/24
[[File:Zero Tier Enabling.png|frameless|620x620px]]
|In this text box  the user needs to put the address of the remote subnet. The specific  remote subnet included in the VPN.
 
|-
Copy and paste the unique 16-digit network ID in the edit section.
|12
 
|Key exchange
[[File:Zero tier Unique ID.png|frameless|620x620px]]
|Ikev1
 
|In this dropdown  the user should select the which key exchange version to be selected.
[[File:Zerotier Connection.png|frameless|620x620px]]
|-
 
|13
Click on the save button after the required configuration.
|Aggressive
{| class="wikitable"
|Yes/No
|SN
|In this dropdown  the user should select either yes or no.
|Field name
|Sample  value
|Description
|-
|-
|1
|14
|NetworkID
|IKE Lifetime (In Seconds)
|Ad2769hfkw2345f4
|86400
|In this dropdown box the user needs to paste the unique 16-digit network id.
|The lifetime of the IKE phase in seconds (1 day).
|-
|-
|2
|15
|Listen Port
|Lifetime (in seconds)
|9993
|28800
|Default
|The lifetime of the IPsec SA (Security  Association) in seconds (8 hours).
 
|-
|16
|Enable DPD Detection
|'''1'''
 
0
|Indicates whether Dead Peer Detection is  enabled to detect a lost connection. Enable this option as per server-side  settings.
|-
|17
|Time Interval (In Seconds)
|60
|This option is available only if DPD  Detection is enabled. The time interval is the interval for DPD checks.
|-
|18
|Action
|'''Restart'''/clear/hold/
 
trap/start
|'''Restart''':  Action to take when DPD detects a lost connection (restart the connection).  Select as per server-side setting.
|-
|19
|Authentication Method
|'''PSK'''
|'''PSK''': Pre-shared  key is used for authentication. Select this option for authentication as per  sever side setting.
|-
|20
|Multiple Secrets
|1/'''0'''
|Indicates whether multiple PSK secrets  are used. Enable only if required.
|-
|21
|PSK Value
|******
|Pre-shared key value (masked for  security).
|}
|}
{| class="wikitable"
|
| colspan="6" |'''Proposal settings  Phase I'''
|-
|22
| colspan="2" |'''Encryption Algorithm'''
| colspan="3" |AES 128


=== 2.5 Firewall ===
AES 192
A firewall is a layer of security between the network and the Internet. Since a router is the main connection from a network to the Internet, the firewall function is merged into this device. Every network should have a firewall to protect its privacy.


[[File:Firewall General Settings.png|frameless|620x620px]]
'''AES 256'''


There are 6 types of setting available under firewall.
3DES
|'''AES 256''': Encryption algorithm  for Phase I. Select as per server-side configuration. Both server and client  should have same configuration.
|-
|23
| colspan="2" |Authentication Phase I
| colspan="3" |SHA1
 
MD5
 
SHA 256
 
SHA 384
 
'''SHA 512'''
|'''SHA 512''': Authentication  algorithm for Phase I.


* General Settings
Select as per  server-side configuration. Both server and client should have same  configuration.
* Port forwards
|-
* Traffic Rules
|24
* SNAT traffic Rules
| colspan="2" |DH Group
* Parental Control
| colspan="3" |MODP768(group1)
* Zone Forwarding


'''General Settings:'''
MODP1024(group2)


General settings are subdivided into 2 parts,
MODP1536(group5)


1.) General settings
'''MODP2048(group14)'''


In general settings, the settings that are made are default settings and can be changed according to user’s preference.
MODP3072(group15)


[[File:Firewall Configuration 1.png|frameless|620x620px]]
MODP4096(group16)
|'''MODP2048 (group14)''': Diffie-Hellman group for key exchange.


{| class="wikitable"
Select as per  server-side configuration. Both server and client should have same configuration.
|'''SN'''
|'''Field Name'''
|'''Sample Value'''
|'''Description'''
|-
|-
|1
| colspan="7" |'''Proposal settings Phase II'''
|Enable SYN-flood protection
|Enabled
|This is enabled by default; setting can be changed  if required.
|-
|-
|2
| colspan="2" |25
|Disable IPV6
| colspan="2" |Hash Algorithm
|Disabled
|AES 128
|This is enabled by default; setting can be changed  if required.
|-
|3
|Drop invalid packets
|Disabled
|This is enabled by default; setting can be changed  if required.
|-
|4
|TCP SYN Cookies
|Disabled
|This is enabled by default; setting can be changed  if required.
|-
|5
|Input
|Reject/Accept
|By default, the setting is ‘Reject’ but this needs  to be changed to ‘Accept’ compulsory.
|-
|6
|Output
|Reject/Accept
|By default, the setting is ‘Reject’ but this needs  to be changed to ‘Accept’ compulsory.
|-
|7
|Forward
|Reject/Accept
|By default, the setting is ‘Reject’ but this needs  to be changed to ‘Accept’ compulsory.
|}
2.) Zone settings


In zone settings, there’s an option to add “New Zone”, according to user’s requirement.
AES 192


[[File:Firewall Zone Settings.png|frameless|620x620px]]
'''AES 256'''


'''Port Forwards:'''
3DES
 
| colspan="2" |'''AES 256''': Encryption algorithm  for Phase II. Select as per server-side configuration. Both server and client  should have same configuration.
Port forwarding is a feature in a router or gateway that allows external devices to access services on a private network.
|-
| colspan="2" |26
| colspan="2" |Authentication Phase II
|SHA1
 
MD5
 
SHA 256


It maps an external port on the router to an internal IP address and port on the local network, enabling applications such as gaming servers, web servers, or remote desktop connections to be accessed from outside the network.
SHA 384


This helps in directing incoming traffic to the correct device within a local network based on the port number, enhancing connectivity and accessibility.
'''SHA 512'''
[[File:Firewall Enabled.png|frameless|620x620px]]EDIT:
| colspan="2" |'''SHA 512''': Authentication  algorithm for Phase II.
[[File:Firewall Configuration 2.png|frameless|620x620px]]


Click on the save button after the required configuration.
Select as per  server-side configuration. Both server and client should have same configuration.
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|1
| colspan="2" |27
|Name
| colspan="2" |PFS Group
|Example: <code>Web_Server_Forward</code>
|MODP768(group1)
|Field must  not be empty. Provide a name for the rule to easily identify it.
 
|-
MODP1024(group2)
|2
 
|Protocol
MODP1536(group5)
|Example: <code>TCP+UDP</code>
|Select the protocol  for the rule.


Options  typically include TCP+UDP, TCP, UDP, ICMP, Custom.
'''MODP2048(group14)'''
|-
 
|3
MODP3072(group15)
|Source zone
 
|Example: <code>SW_LAN</code>
MODP4096(group16)
|Select the source zone where the traffic is originating  from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
| colspan="2" |'''MODP2048 (group14)''': Perfect Forward Secrecy group.
|-
 
|4
Select as per server-side configuration. Both server and client should have same configuration.
|Source MAC address [optional]
|Example: <code>any</code>
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|-
|5
|Source IP address[optional]
|Example: Leave blank if not needed.
|Optionally  specify an IP address or range.
|-
|6
|Source port
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|Specify the source port or port range.
|-
|7
|Destination zone
|Example: <code>SW_LAN</code>
|Select the destination zone where the traffic is heading to.
|-
|8
|Destination IP address
|Leave blank if not needed.
|Optionally specify  the destination IP address or range.
|-
|9
|Destination port
|Example: <code>80</code>  (if redirecting to a web server port)
|Specify the destination port or port range.
|}
|}
'''Traffic Rule:'''
Click on save and then update the page for changes to reflect.
 
'''Open VPN:'''


"Traffic rules" refer to the policies and regulations that govern the flow of data packets within a network.  
To use the VPN feature, the user should enable OpenVPN Server on the router and install and run VPN client software on the remote device.


To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.
[[File:GRD44B 5R OPEN VPN.png|1024x1024px]]The user needs to “upload” the respective certificate from a valid path and then click on the “Update.


[[File:Firewall Traffic Rule Dashboard.png|frameless|620x620px]]
Only the '''TAP''' connection needs a '''bridge'''. The tun connection does not require a bridge. Here we have established a '''TUN''' connection.


EDIT:
By clicking on the enable/disable button, the user can start/stop the VPN connection.


[[File:Firewall Edit Options .png|frameless|620x620px]]
[[File:GRD44B 5R OPEN VPN CONFIG.png|1024x1024px]]
{| class="wikitable"
 
|SN
VPN TUN has been established.
 
Same way VPN TAP can also be established with the help of bridging.
 
'''WireGuard:'''
 
'''WireGuard''' is simple, fast, lean, and modern VPN that utilizes secure and trusted cryptography.
 
Click on “Edit” to start configurations as needed.
 
[[File:GRD44B 5R WIREGURD.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:GRD44B 5R WIREGURD CONFIG.png|1024x1024px]]
 
Click on the save button after the required configuration.
 
Specifications details are given below:
{| class="wikitable"
|SN
|Field name
|Field name
|Sample value
|Sample value
|Description
|Description
|-
|-
|1
|1
|Name
|Wireguard Role
|Example: Allow_HTTP_and_HTTPS
|Client/Server
|Field must not be empty: Provide a descriptive name for the traffic rule.
|In this dropdown box the user needs to select the wireguard role.
|-
|-
|2
|2
|Restrict to Address Family
|WireGuard Tunnel Over
 
|IPV4/IPV6
|1.       Options: IPv4, IPv6
|'''IPV4''': Use this if your network and endpoint (WireGuard server) support only IPv4.


Example: IPv4 if  dealing with typical internet traffic.
'''IPV6''': Use this if  your network and endpoint support IPv6.
|Select the address family to generate  iptables rules for.
|-
|-
|3
|3
|Protocol
|Enable Failover
|Example: TCP+UDP
|Enable/Disable
|TCP+UDP: Match incoming traffic using the  given protocol.
|This option  allows the VPN connection to automatically switch to a backup connection if the primary connection fails.
|-
|-
|4
|4
|Match ICMP Type
|Enable IPV4
|Example: any
|Enable/Disable
|Match all ICMP types if set to any.  Specific types can be chosen if needed.
|This enables IPv4  traffic to be routed through the WireGuard tunnel.
|-
|-
|5
|5
|Source Zone
|Enable IPV6
|Example: LAN
|Enable/Disable
|Specifies the traffic source zone.
|Enable this if  your network and the destination support IPv6.
|-
|-
|6
|6
|Enable DDoS  Prevention
|Listen Port
|Example:  ‘Checked’ if you want to enable DDoS prevention measures
|51820
|Enable or disable Distributed Denial of Service (DDoS) prevention.
|This is the default port that WireGuard uses to listen for incoming connections.
|-
|-
|7
|7
|Source MAC  Address
|Endpoint Host port
|Example: any
|51820
|any: Match traffic from any MAC address or specify a particular MAC address.
|This is the port on the WireGuard server that the client will connect to.
|-
|-
|8
|8
|Source Address
|Peer Publickey
|Example:  192.168.1.0/24
|*****
|Match incoming traffic from the specified source IP address or range.
|This is the public key of the WireGuard server that the client uses to establish a secure connection.
|-
|-
|9
|9
|Source Port
|Enable Default Route
|Example: any if all source ports should be matched
|Enable/Disable
|any: Match incoming traffic from the specified  source port or port range.
|Enable this if you want all network traffic (not just specific routes) to be routed through the WireGuard VPN.
|-
|10
|Destination Zone
|Example: WAN
|Specifies the traffic destination zone.
|-
|11
|Action
|Example: ACCEPT
|Options: ACCEPT, DROP, REJECT. Specify the action to take for matched traffic.
|-
|12
|Limit
|Example:  10/minute to limit matches to 10 times per minute.
|Maximum average matching rate; specified  as a number, with an optional /second, /minute, /hour, or /day suffix.
|-
|13
|Extra arguments
|Example:  --log-prefix "Blocked: " to add a log prefix to log messages for  this rule.
|Passes additional arguments to iptables.  Use with care as it can significantly alter rule behaviour.
|}
|}
Click on save once configured.
Save and update the page after configuration has been done.
 
 


'''SNAT Traffic Rule:'''
'''Zerotier:'''


For configuring SNAT (Source Network Address Translation) traffic rules, you can control how outbound traffic from your local network is translated to a different IP address as it exits the network.
ZeroTier is a tool that lets you create your own private network over the internet.


To add new source NAT,
Go to ZeroTier Central and sign up for a free account.


Click on “ADD” in “New Source NAT:”
In ZeroTier Central, click on "Create a Network". This will generate a unique 16-digit network ID for your new network.


[[File:SNAT Traffic Rule.png|frameless|620x620px]]
Go to settings => VPN, in general settings, enable ZeroTier and save.


'''EDIT:'''
[[File:GRD44B 5R Zerotier.png|1024x1024px]]


[[File:SNAT Edit Options RC44.png|frameless|620x620px]]


Specification details are below:
Copy and paste the unique 16-digit network ID in the edit section.
 
[[File:GRD44B 5R ZEROTIER ENABLING.png|1024x1024px]][[File:GRD44B 5R ZEROTIER CONFIG.png|1024x1024px]]Click on the save button after the required configuration.
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field name
|Sample  value
|Sample  value
|Description
|Description
|-
|-
|1
|1
|Name
|NetworkID
|Example: SNAT_WAN_to_LAN
|Ad2769hfkw2345f4
|'''Field must not be empty''': Provide a unique and descriptive name for the SNAT rule.
|In this dropdown box the user needs to paste the unique 16-digit network id.
|-
|-
|2
|2
|Protocol
|Listen Port
|Example: TCP+UDP
|9993
|'''TCP+UDP''':  Select the protocols that the SNAT rule will apply to.
|Default
 
|}
 
 
'''PPTP:'''
 
This configuration is for setting up a PPTP (Point-to-Point Tunnelling Protocol) VPN connection.
 
PPTP is a protocol that enables secure data transmission across public networks like the internet, often used to connect to remote networks or access resources securely.
 
''*Refer the image below*''
 
[[File:GRD44B-5R PPTP.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:GRD44B-5R PPTP Config.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|3
|1
|Source Zone
|PPTP Role
|Example: wan
|Client/Server
|'''wan''': Specifies the source zone from which the traffic originates.
|'''Client:''' meaning it will initiate the connection to the remote PPTP server.
|-
 
|4
'''Server:''' means this device will accept incoming PPTP connections from clients, which  can be users or devices that need remote access to the local network or  internet via this server.
|Source IP Address
|Example: any or a specific range like 192.168.1.0/24
|'''-- please  choose --''': Specify the source IP address or range. Leave empty if the rule applies to any source IP.
|-
|-
|
|
|
|
|
|
|  
|
|-
| colspan="4" |'''PPTP Role: CLIENT'''
|-
|2
|Default  Route
|Enable/Disable
|Enabling  the default route means that all network traffic will be routed through the  VPN tunnel once the connection is established.
|-
|3
|Metric
|Ex: 0
|The  metric is a value that defines the priority of this route among other  available routes. Lower metrics indicate higher priority.
|-
|4
|Server  IP
|Ex: 192.168.10.1
|This  is the IP address of the PPTP server the client will connect to.
|-
|-
|5
|5
|Source Port
|Interface
|Example: any
|Any
|'''any''': Specify the source port or port range from which the traffic originates.
 
EWAN5
|Selecting the correct interface is essential because it tells the system which network  adapter should be used to establish the VPN connection.
|-
|-
|6
|6
|Destination Zone
|Username
|Example: lan
|******
|'''lan''': Specifies the destination zone to which the traffic is directed.
|This field is the login username for the PPTP server.
|-
|-
|7
|7
|Destination IP Address
|Password
|Example: any or a specific IP like 192.168.1.100
|****
|'''-- please  choose --''': Specify the destination IP address or range. Leave empty if  the rule applies to any destination IP.
|This  is the password associated with the username.
|-
| colspan="4" |'''PPTP Role: SERVER'''
|-
|-
|8
|8
|Destination port
|Local  IP
|Example: any
|Ex: 192.168.0.1
|'''any''': Specify the destination port or port range to which the traffic is directed.
|This  IP address (192.168.0.1) is the local IP of the PPTP server on its network. Clients connecting to the VPN will see this address as their gateway or endpoint within the VPN.
|-
|-
|9
|9
|SNAT IP Address
|Remote  IP Range
|Example: 203.0.113.5 (an external IP address)
|Ex: 192.168.0.20-30
|'''-- please choose --''': Specify the IP address to which the source IP should be translated.
|This range defines the pool of IP addresses that the server will assign to  connected VPN clients. Here, any client connecting to the server will receive  an IP address between 192.168.0.20 and 192.168.0.30, which provides up to 11 possible addresses for simultaneous connections.
|-
|-
|10
|10
|SNAT Port
|Username
|Example: Leave empty if not needed, or specify a port like ‘12345’
|ExUser1
|Optionally, rewrite matched traffic to a specific source port. Leave empty to only rewrite the IP address.
|This is a username that the client will use to authenticate with the PPTP serverIn this case, User1 is designated as an authorized user.
|-
|-
|11
|11
|Extra Arguments
|Password
|Example: --log-prefix "SNAT_traffic: " (to add  a log prefix to log messages for this rule)
|*****
|Pass additional arguments to iptables. Use with care as it can significantly alter  rule behaviour.
|The password associated with User1 is required to complete the authentication.
|}
|}
Click on save once configured.
Once Configured, click on save and update.


'''Parental Control:'''
'''L2TP:'''


For configuring parental control rules, you want to set restrictions based on time, source, and
L2TP (Layer 2 Tunnelling Protocol) is a network protocol used to establish secure tunnels for transferring data between remote devices or networks, often in VPNs, by encapsulating data for encryption and routing.


destination zones, as well as specific devices.
''*Refer the image below*''


To add parental control in firewall,
[[File:GRD44B 5R L2TP.png|1024x1024px]]
 
Click on “Add and Edit” in “New parental control:” field.
 
[[File:Parental Control.png|frameless|620x620px]]


'''EDIT:'''
'''EDIT:'''


[[File:Parental Control Edit Options RC44.png|frameless|620x620px]]
[[File:GRD44B 5R L2TP Config.png|1024x1024px]]


Specification details are given below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Name
|L2TP Role
|Example: Parental_Control_Sunday
|Client/Server
|'''Field must  not be empty''': Provide a unique and descriptive name for the parental control rule.
|'''Client''': connecting to an L2TP server to  establish a secure tunnel for communication.
 
'''Server''': the  server listens for incoming client connections.
|-
| colspan="4" |'''L2TP Role: CLIENT'''
|-
|-
|2
|2
|Proto
|Default Route
|all
|Enable/Disable
|'''all''': This specifies that the rule will apply to all protocols.
|If enabled, all outbound traffic will be routed  through the L2TP connection.
 
If disabled, only specific traffic destined for the L2TP network will use the tunnel.
|-
|-
|3
|3
|Source Zone
|Metric
|Example: lan
|Ex: 1
|'''Field must not be empty''': Please look at Firewall->Zone Settings to find zone names.
|The system uses this metric to decide which route to prioritize if multiple routes exist.
 
L2TP connection with Metric 1 will take precedence over a LAN or WAN route with Metric 10.
|-
|-
|4
|4
|Destination Zone
|Server IP
|Example: wan
|Ex: 192.168.10.1
|'''Field must not be empty''': Please look at Firewall->Zone Settings to find zone names.
|This is the '''IP address of the L2TP server''' to which the client will connect.
 
'''Local Networks''': If connecting  within a LAN, the server might have an IP like 192.168.x.x.
 
'''Remote Connections''': The server IP might be a public address like 203.0.113. x.
|-
|-
|5
|5
|Source MAC Address
|Checkup  Interval Time (in sec)
|Example: 00:1A:2B:3C:4D:5E
|Ex: 30/60 secs
|'''Field''': Enter the MAC address of the device you want to apply the parental control rule to. This is useful for restricting specific devices.
|Setting 30 seconds ensures the client checks the connection every half-minute. If the  tunnel drops, the client can quickly reconnect.
|-
|-
|6
|6
|Target
|Interface
|Example: Reject
|Any
|'''Accept''': This specifies the action to take. For parental controls, you might want to  use ‘Reject’ or ‘Drop’ to block traffic.
|Example interfaces might include eth0, usb0, or ra0.
|-
|-
|7
|7
|Weekdays
|Username
|Example: Sunday
|Ex: User
|'''Sunday''': Specify the days of the week when the rule should be active.
|The server verifies the username to grant or deny access.
 
Must match  credentials configured on the L2TP server.
|-
|-
|8
|8
|Month Days
|Password
|Example: All
|******
|'''All:''' Specify the days of the month when the rule should be active.
|Should be kept secure and match the configuration on the server.
 
Masked for  privacy during configuration.
|-
|-
|9
|9
|Start Time (hh:mm:ss)
|MPPE Encryption
|Example: 18:00:00 (6:00 PM)
|Enable/Disable
|'''Field must  not be empty:''' Specify the start time when the rule should begin to apply.
|'''Enabled''': Encrypts  traffic using MPPE, enhancing security (recommended).
 
'''Disabled''': Transmits  data unencrypted, reducing overhead but exposing traffic to potential risks.
|-
| colspan="4" |'''L2TP Role: SERVER'''
|-
|-
|10
|10
|Stop Time (hh:mm:ss)
|Local IP
|Example: 22:00:00 (10:00 PM)
|Ex: 192.168.0.1
|'''Field must not be empty:''' Specify the stop time when the rule should end.
|This is the '''local IP address of the L2TP server'''. It serves as the gateway for clients  connected via the L2TP tunnel.
|-
|11
|Start
|Ex: 192.168.0.20
|Specifies the  first IP address that can be assigned to connected clients.
|-
|12
|Limit
|Ex: 192.168.0.30
|Creates an IP  pool for clients (from 192.168.0.20 to 192.168.0.30 in this case).
|-
|13
|Username
|Ex: User1
|Ensures that  only authorized users can connect.
 
The server  verifies this username against its authentication database.
|-
|14
|Password
|******
|The server  verifies the password along with the username.
 
The password  must match the one configured on the server for successful authentication.
|}
|}
'''Zone Forwarding:'''


Zone forwarding in network configuration allows traffic to be directed from one zone to another.
=== 2.6 Firewall ===
A firewall is a layer of security between the network and the Internet.


To ADD new zone,
Since a router is the main connection from a network to the Internet, the firewall function is merged into this device.


Click on “Add” in “New Zone Forward:” field.
Every network should have a firewall to protect its privacy.


[[File:Zone Forwarding RC44.png|frameless|620x620px]]
To configure a Firewall, navigate to settings <= firewall,


'''EDIT:'''
[[File:GRD44B 5R Firewall overview.png|1024x1024px]]


[[File:Parental Control Zone Configuration.png|frameless|620x620px]]
There are 6 types of setting available under firewall.


Specification details are below:
* General Settings
{| class="wikitable"
* Port forwards
|SN
* Traffic Rules
|Field  Name
* SNAT traffic Rules
|Sample  Value
* Parental Control
|Description
* Zone Forwarding
|-
|1
|Source Zone
|Example options: lan, wan, etc.
|'''--please  choose--''': Select the source zone from which the traffic originates.
|-
|2
|Destination Zone
|Example options: lan, wan, etc.
|'''--please  choose--''': Select the destination zone to which the traffic is directed.
|}


=== 2.6 Loopback Rule ===
'''General Settings:'''
In this page the user can configure the port where he wants to forward the traffic to. Here the user can add/edit/delete different ports as per the requirement.


[[File:Parental Control Zone Loopback Rule.png|frameless|620x620px]]
General settings are subdivided into 2 parts,


The user should click on ‘add’ and then ‘edit’ to do the required changes in the port and enter the valid information in each section to configure the port for forwarding.
1.) General settings


'''EDIT:'''
In general settings, the settings that are made are default settings and can be changed according to user’s preference.


[[File:Parental Control Zone Loopback Rule 1.png|frameless|650x650px]]
[[File:GRD44B 5R Firewall general settings.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|'''SN'''
|Field Name
|'''Field Name'''
|Sample Value
|'''Sample Value'''
|Description
|'''Description'''
|-
|-
|1
|1
|Name
|Enable SYN-flood protection
|Example: loopback
|Enabled
|Provide a descriptive name for the rule.
|This is enabled by default; setting can be changed if required.
|-
|-
|2
|2
|Protocol
|Disable IPV6
|Example: TCP+UDP
|Disabled
|'''TCP+UDP''': Select the protocols that the rule will apply to.
|This is enabled by default; setting can be changed if required.
|-
|-
|3
|3
|Source IP Address [Optional]
|Drop invalid packets
|Example: any or a specific IP range like 192.168.1.0/24
|Disabled
|Optionally specify the source IP address or range. Leave empty if the rule should apply  to any source IP.
|This is enabled by default; setting can be changed if required.
|-
|-
|4
|4
|Source Port [Optional]
|TCP SYN Cookies
|Example: any
|Disabled
|'''any''': Specify the source port or port range from which the traffic originates. any allows  traffic from all ports.
|This is enabled by default; setting can be changed if required.
|-
|-
|5
|5
|Loopback IP Address
|Input
|Example: 127.0.0.1
|Reject/Accept
|Specify the  loopback IP address. Typically, this is 127.0.0.1.
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|-
|-
|6
|6
|Port
|Output
|Example: any
|Reject/Accept
|'''any''':  Specify the destination port or port range to which the traffic is directed. any allows traffic to all ports.
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|-
|-
|7
|7
|Action
|Forward
|Example: DNAT
|Reject/Accept
|This specifies the action to take either DNAT or SNAT.
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|-
|}
|8
 
|Internal IP Address
 
|Example: 192.168.1.100
 
|'''Field must  not be empty''': Specify the internal IP address to which the traffic should  be redirected.
'''2.) Zone settings'''
|-
 
|9
In zone settings, there’s an option to add “New Zone”, according to user’s requirement.
|Internal Port
|Example: any
|Redirect  matched incoming traffic to the given port on the internal host.
|}
Once the user is done with the required configurations, should click save button and then click on the update to save the changes.


=== 2.7 Remote Monitoring ===
[[File:GRD44B 5R Zone settings.png|1024x1024px]]
In this page the user can select which equipment needs to be monitored remotely.


Once the user selects the type of RMS click on save.


[[File:Remote Monitoring.png|frameless|620x620px]]
'''Port Forwards:'''


'''NMS:'''
Port forwarding is a feature in a router or gateway that allows external devices to access services on a private network.


IN this page the user should type the server IP or domain name in the URL then click on save.
It maps an external port on the router to an internal IP address and port on the local network, enabling applications such as gaming servers, web servers, or remote desktop connections to be accessed from outside the network.


Click on upload and start (Once key is uploaded and this option is clicked, NMS automatically starts, and this router device gets registered with the NMS server provided).
This helps in directing incoming traffic to the correct device within a local network based on the port number, enhancing connectivity and accessibility.  


[[File:Remote Management System NMS Configuration.png|frameless|620x620px]]
[[File:GRD44B 5R Port forwards.png|1024x1024px]]


'''EDIT:'''


'''TR_069:'''
[[File:GRD44B 5R Port forwards edit.png|1024x1024px]]


To enable the TR_069 the user needs to click on the enable check box.


[[File:TR 069.png|frameless|620x620px]]
Click on the save button after the required configuration.
 
Once the user clicks on the check box of enable it will display all the required filed to configured.
 
 
[[File:Remote Monitoring Tr-069.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample Value
|Sample value
|Description
|Description
|-
|-
|1
|1
|Serving  Interval
|Name
|300
|Example: <code>Web_Server_Forward</code>
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|Field must not be empty. Provide a name for the rule to easily identify it.
|-
|-
|2
|2
|Interface
|Protocol
|This can  be something like eth0 or wan.
|Example: <code>TCP+UDP</code>
|This specifies the network interface used for TR-069 communication.
|Select the  protocol for the rule.
 
Options  typically include TCP+UDP, TCP, UDP, ICMP, Custom.
|-
|-
|3
|3
|Username
|Source zone
|Example: User
|Example: <code>SW_LAN</code>
|The username used to authenticate with the ACS.
|Select the source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
|-
|-
|4
|4
|Password
|Source MAC address [optional]
|••••
|Example: <code>any</code>
|The password used to authenticate with  the ACS.
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|-
|-
|5
|5
|URL
|Source IP address[optional]
|<nowiki>http://example.com</nowiki>
|Example: Leave blank if not needed.
|The URL of the ACS. This is where the CPE (customer-premises equipment) will send its requests and where it will receive configurations and updates from.
|Optionally  specify an IP address or range.
|}
|-
The user should fill all the required fields and click on the save button.
|6
|Source port
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|Specify the  source port or port range.
|-
|7
|Destination zone
|Example: <code>SW_LAN</code>
|Select the destination zone where the traffic is heading to.
|-
|8
|Destination IP address
|Leave blank if not needed.
|Optionally specify  the destination IP address or range.
|-
|9
|Destination port
|Example: <code>80</code> (if redirecting to a web server port)
|Specify the destination port or port range.
|}  


=== 2.8 Tunnel ===
'''Traffic Rule:'''
Tunnels are a method of transporting data across a network using protocols which are not supported by that network.


It is further categorised into 3 sections,
"Traffic rules" refer to the policies and regulations that govern the flow of data packets within a network.


1.) General Settings
To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.  


2.) GRE Tunnel
[[File:GRD44B 5R TRAFFIC RULES.png|1024x1024px]]
 
3.) IPIP Tunnel
 
[[File:Tunnel Settings.png|frameless|620x620px]]
 
 
'''General Settings:'''
 
In this page the user needs to select under which type of tunnel it needs to send the data.
 
[[File:Tunnel General Settings 1.png|frameless|620x620px]]
 
Once the user selects the type of tunnel then click on the save button.
 
'''GRE Tunnel:'''
 
A GRE (Generic Routing Encapsulation) tunnel configuration involves setting up a virtual point-to-point connection between two endpoints over an IP network.
 
Here the user can add/edit/delete the details of the tunnel.
 
[[File:GRE Dashboard.png|frameless|620x620px]]
 
Once the required update is done then click on update to save the changes.


'''EDIT:'''
'''EDIT:'''


[[File:GRE Tunnel.png|frameless|620x620px]]
[[File:GRD44B 5R TRAFFIC RULES EDIT.png|1024x1024px]]


Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample Value
|Sample value
|Description
|Description
|-
|-
|1
|1
|Tunnel  name
|Name
|Example:  GRETunnel
|Example:  Allow_HTTP_and_HTTPS
|'''GRETunnel''': The name of the GRE tunnel.
|Field must not be empty: Provide a  descriptive name for the traffic rule.
|-
|-
|2
|2
|Local external IP
|Restrict to Address Family
|Example:  10.1.1.66
 
|The IP address of the local endpoint that will initiate the GRE tunnel.
|1.      Options: IPv4, IPv6
 
Example: IPv4 if dealing with typical internet traffic.
|Select the address family to generate iptables rules for.
|-
|-
|3
|3
|Remote external  IP
|Protocol
|Example: 10.1.1.40
|Example: TCP+UDP
|The IP address of the remote endpoint that will terminate the GRE tunnel.
|TCP+UDP: Match incoming traffic using the  given protocol.
|-
|-
|4
|4
|Peer  tunnel IP
|Match ICMP Type
|Example: 10.1.1.4
|Example: any
|The IP address of the peer's tunnel interface.
|Match all ICMP types if set to any. Specific types can be chosen if needed.
|-
|-
|5
|5
|Local  tunnel IP
|Source Zone
|Example: 10.1.1.6
|Example: LAN
|The IP address of the local tunnel  interface.
|Specifies the traffic source zone.
|-
|-
|6
|6
|Local tunnel net mask
|Enable DDoS Prevention
|Example:  255.255.255.0
|Example:  ‘Checked’ if you want to enable DDoS prevention measures
|The subnet mask of the local tunnel interface.
|Enable or disable Distributed Denial of  Service (DDoS) prevention.
|-
|-
|7
|7
|Remote IP
|Source MAC  Address
|Example: 192.168.10.0/24
|Example: any
|The remote network that is reachable through the GRE tunnel.
|any: Match traffic from any MAC address or specify a particular MAC address.
|-
|-
|8
|8
|Enable  Tunnel Link
|Source Address
|Check to enable
|Example: 192.168.1.0/24
|Enable or disable the GRE tunnel link.
|Match incoming traffic from the specified  source IP address or range.
|-
|-
|9
|9
|Interface  type
|Source Port
|Example:  EWAN2
|Example: any if all source ports should be matched
|'''EWAN2''': The type of network interface used for the GRE tunnel.
|any: Match incoming traffic from the specified source port or port range.
|-
|-
|10
|10
|MTU
|Destination Zone
|Example: 1476
|Example: WAN
|'''1476''': Maximum  Transmission Unit size for the GRE tunnel.
|Specifies the traffic destination zone.
|-
|-
|11
|11
|TTL
|Action
|Example: 64
|Example: ACCEPT
|'''64''': Time To Live value for the packets within the GRE tunnel.
|Options: ACCEPT, DROP, REJECT. Specify the action to take for matched traffic.
|-
|-
|12
|12
|Tunnel  key
|Limit
|Example:  12345678
|Example:  10/minute to limit matches to 10 times per minute.
|'''12345678''': A unique key used to identify the GRE tunnel.
|Maximum average matching rate; specified  as a number, with an optional /second, /minute, /hour, or /day suffix.
|-
|-
|13
|13
|Enable  keep alive
|Extra arguments
|Check to enable
|Example: --log-prefix "Blocked: " to add a log prefix to log messages for this rule.
|Enable or disable the keep-alive  feature to monitor the tunnel's status.
|Passes additional arguments to iptables. Use with care as it can significantly alter rule behaviour.
|-
|14
|Keep  alive interval
|Example10
|'''10''': Interval in seconds for the keep-alive packets.
|}
|}
Once the required update is done then click on update to save the changes.
Click on save once configured.  
 
'''SNAT Traffic Rule:'''


'''IPIP Tunnel:'''
For configuring SNAT (Source Network Address Translation) traffic rules, you can control how outbound traffic from your local network is translated to a different IP address as it exits the network.


An IPIP (IP-in-IP) tunnel is a simple tunnelling protocol used to encapsulate IP packets within IP packets. This is like GRE but without additional features such as keying and type fields.
To add new source NAT,


Here the user can add/edit/delete the details of the tunnel.
Click on “ADD” in “New Source NAT:”


[[File:Ipip config.png|frameless|620x620px]]
[[File:GRD44B 5R SNAT TRAFFIC RULES.png|1024x1024px]]


'''EDIT:'''
'''EDIT:'''


[[File:IPIP Tunnel.png|frameless|620x620px]]
[[File:GRD44B 5R SNAT TRAFFIC RULES CONFIG.png|1024x1024px]]


Once the required update is done then click on update to save the changes.


 
Specification details are below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample Value
|Sample value
|Description
|Description
|-
|-
|1
|1
|Tunnel  name
|Name
|Example: IPIPTunnel
|Example: SNAT_WAN_to_LAN
|'''IPIPTunnel:''' The name of the IPIP tunnel.
|'''Field must  not be empty''': Provide a unique and descriptive name for the SNAT rule.
|-
|-
|2
|2
|Local  external IP
|Protocol
|Example: 10.1.1.66
|Example: TCP+UDP
|The IP address of the local endpoint  that will initiate the IPIP tunnel.
|'''TCP+UDP''':  Select the protocols that the SNAT rule will apply to.
|-
|-
|3
|3
|Remote  external IP
|Source Zone
|Example: 10.1.1.40
|Example: wan
|The IP address of the remote endpoint  that will terminate the IPIP tunnel.
|'''wan''': Specifies  the source zone from which the traffic originates.
|-
|-
|4
|4
|Peer  tunnel IP
|Source IP Address
|Example: 10.1.1.4
|Example: any or a specific range like 192.168.1.0/24
|The IP address of the peer's tunnel interface.
|'''-- please  choose --''': Specify the source IP address or range. Leave empty if the  rule applies to any source IP.
|-
|
|
|
|
|-
|-
|5
|5
|Local  tunnel IP
|Source Port
|Example: 10.1.1.6
|Example: any
|The IP address of the local tunnel  interface.
|'''any''':  Specify the source port or port range from which the traffic originates.
|-
|-
|6
|6
|Local  tunnel net mask
|Destination Zone
|Example: 255.255.255.0
|Example: lan
|The subnet mask of the local tunnel  interface.
|'''lan''':  Specifies the destination zone to which the traffic is directed.
|-
|-
|7
|7
|Remote IP
|Destination IP Address
|Example: 192.168.10.0/24
|Example: any or a specific IP like 192.168.1.100
|The remote network that is reachable through the IPIP tunnel.
|'''-- please  choose --''': Specify the destination IP address or range. Leave empty if the rule applies to any destination IP.
|-
|-
|8
|8
|Enable  Tunnel Link
|Destination port
|Check to  enable
|Example: any
|Enable or disable the IPIP tunnel link.
|'''any''':  Specify the destination port or port range to which the traffic is directed.
|-
|-
|9
|9
|Interface  type
|SNAT IP Address
|Example: EWAN2
|Example: 203.0.113.5 (an external IP address)
|'''EWAN2''': The type of network interface used for the IPIP tunnel.
|'''-- please  choose --''': Specify the IP address to which the source IP should be translated.
|-
|-
|10
|10
|MTU
|SNAT Port
|Example:  1476
|Example: Leave empty if not needed, or specify a port like ‘12345’
|'''1476''': Maximum Transmission Unit size for the IPIP tunnel.
|Optionally,  rewrite matched traffic to a specific source port. Leave empty to only rewrite the IP address.
|-
|-
|11
|11
|TTL
|Extra Arguments
|Example: 64
|Example: --log-prefix "SNAT_traffic: " (to add a log prefix to log messages for this rule)
|'''64''': Time To Live value for the packets within the IPIP tunnel.
|Pass additional arguments to iptables. Use with care as it can significantly alter rule behaviour.
|-
|12
|Tunnel  key
|Example:  12345678
|Although typically not used in IPIP,  this field might be included for compatibility with certain configurations.
|-
|13
|Enable keep alive
|Check to enable
|Enable or disable the keep-alive  feature to monitor the tunnel's status.
|-
|14
|Keep alive interval
|Example:  10
|'''10''':  Interval in seconds for the keep-alive packets.
|}
|}
Click on save once configured.


= 3.Maintenance =
'''Parental Control:'''
In this module the user can configure/upgrade/modify the settings related to system, password,


firmware and monitoring.
For configuring parental control rules, you want to set restrictions based on time, source, and


It includes 6 submodules.
destination zones, as well as specific devices.


* General
To add parental control in firewall,
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application


[[File:Maintenance System.png|frameless|620x620px]]
Click on “Add and Edit” in “New parental control:” field.  


=== 3.1 General ===
[[File:GRD44B 5R PARENTAL CONTROL.png|1024x1024px]]
Here you can configure the basic aspects of router like its hostname or the timezone.


It is further sub-divided into,
'''EDIT:'''
 
1.) General Settings


2.) Logging
[[File:GRD44B 5R PARENTAL CONTROL CONFIG.png|1024x1024px]]


3.) Language and Style
Specification details are given below:
 
 
'''General Settings:'''
 
[[File:Maintenance General.png|frameless|619x619px]]
 
'''EDIT:'''
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Local  Time
|Name
|2024/07/30  13:25:47
|Example: Parental_Control_Sunday
|The current local date and time set on the device.
|'''Field must  not be empty''': Provide a unique and descriptive name for the parental control rule.
|-
|-
|2
|2
|Hostname
|Proto
|22B25240007
|all
|The hostname of the device, which is  used to identify it on the network.
|'''all''':  This specifies that the rule will apply to all protocols.
|-
|-
|3
|3
|Timezone
|Source Zone
|Asia/Kolkata
|Example: lan
|The timezone setting of the device,  which determines the local time.
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone  names.
|-
|4
|Destination Zone
|Example: wan
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone  names.
|-
|5
|Source MAC Address
|Example: 00:1A:2B:3C:4D:5E
|'''Field''':  Enter the MAC address of the device you want to apply the parental control  rule to. This is useful for restricting specific devices.
|-
|6
|Target
|Example: Reject
|'''Accept''':  This specifies the action to take. For parental controls, you might want to  use ‘Reject’ or ‘Drop’ to block traffic.
|-
|7
|Weekdays
|Example: Sunday
|'''Sunday''':  Specify the days of the week when the rule should be active.
|-
|8
|Month Days
|Example: All
|'''All:''' Specify  the days of the month when the rule should be active.
|-
|9
|Start Time (hh:mm:ss)
|Example: 18:00:00 (6:00 PM)
|'''Field must  not be empty:''' Specify the start time when the rule should begin to apply.
|-
|10
|Stop Time (hh:mm:ss)
|Example: 22:00:00 (10:00 PM)
|'''Field must not be empty:''' Specify the stop time when the rule should end.
|}
|}
Once the user configures the required details then click on the save button to save all the details.
Click on save once configured.


'''Logging:'''


Here the user can configure the basic aspects of your device related to system.


The system log configuration provided specifies how the device handles and stores log information, including buffer size, external log server details, and log verbosity levels.
'''Zone Forwarding:'''


[[File:Maintenance logging.png|frameless|619x619px]]
Zone forwarding in network configuration allows traffic to be directed from one zone to another.


'''EDIT:'''
To ADD new zone,
 
Click on “Add” in “New Zone Forward:” field.
 
[[File:GRD44B 5R ZONE FORWARDING.png|1024x1024px]]'''EDIT:'''
 
[[File:GRD44B 5R ZONE FORWADING EDIT.png|1024x1024px]]
 
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|System log buffer size
|Source Zone
|Example: 32 kiB
|Example options: lan, wan, etc.
|The size of the memory buffer allocated (0-32) for storing system logs before they are either written to a file or  sent to an external server.
|'''--please choose--''': Select the source zone from which the traffic originates.
|-
|-
|2
|2
|External system log server
|Destination Zone
|Example: 0.0.0.0
|Example options: lan, wan, etc.
|The IP address of an external server where logs can be sent.
|'''--please choose--''': Select the destination zone to which the traffic is directed.
|-
|3
|External system log server port
|Example: 514
|The port used to send logs to the external log server. Port 514 is the default port for syslog.
|-
|4
|Log output level
|Example: Debug
|Sets the detail level of the system  logs.
|-
|5
|Cron Log level
|Example: Debug
|The detail level of the logs for cron  jobs.
|}
|}
Once the user configures the required details then click on the save button to save all the details.  
Click on save once configured.


=== 2.7 Loopback Rule ===
In this page the user can configure the port where he wants to forward the traffic to. Here the user can add/edit/delete different ports as per the requirement.


[[File:GRD44B 5R LOOPBACK RULE.png|1024x1024px]]


'''Language and Style:'''
The user should click on ‘add’ and then ‘edit’ to do the required changes in the port and enter the valid information in each section to configure the port for forwarding.


Here the user can configure the basic aspects of your device related to language.
'''EDIT:'''
 
Once the user configures the required details then click on the save button to save all the details.
 
[[File:Maintenance Language and Style.png|frameless|620x620px]]
 
=== 3.2 Password ===
In this module the user can set the password for the admin credentials.
 
Specifies the password for the guest account. If the user enters a plaintext password here, it will get replaced with a crypted password on save. The new password will be effective once the user logs out and log in again.
 
[[File:Admin Password Setup.png|frameless|620x620px]]
 
=== 3.3 Reboot ===
In this module the user can reboot the device remotely.
 
First option is to directly reboot the device without enabling the maintenance reboot tab.
 
Click on “Reboot Now” at the bottom of the screen to start the reboot process.
 
To start maintenance reboot process first the user needs to fill all the required fields.
 
Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.
 
[[File:Maintenance Reboot.png|frameless|620x620px]]


[[File:GRD44B 5R LOOPBACK RULE edit.png|1024x1024px]]


Specification details are given below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Enable  Maintenance Reboot
|Name
|Enable/Disable
|Example: loopback
|Indicates whether the maintenance  reboot feature is enabled or not.
|Provide a  descriptive name for the rule.
|-
|-
|2
|2
|Type
|Protocol
|Maintenance  Reboot
|Example: TCP+UDP
|Specifies the type of reboot being  scheduled.
|'''TCP+UDP''':  Select the protocols that the rule will apply to.
|-
|-
|3
|3
|Reboot  Type
|Source IP Address [Optional]
|Software/Hardware
|Example: any or a specific IP range like 192.168.1.0/24
|'''Hardware''': A hardware reboot involves restarting the entire device as if it were powered off and on again.
|Optionally  specify the source IP address or range. Leave empty if the rule should apply to any source IP.
 
|-
'''Software''': A software reboot involves restarting the  operating system without powering off the hardware.
|-
|4
|4
|Minutes
|Source Port [Optional]
|Example: 59
|Example: any
|The minute at which the reboot should occur (0-59).
|'''any''':  Specify the source port or port range from which the traffic originates. any allows traffic from all ports.
|-
|-
|5
|5
|Hours
|Loopback IP Address
|Example: 22 (10 PM)
|Example: 127.0.0.1
|The hour at which the reboot should occur (0-23, in 24-hour format).
|Specify the  loopback IP address. Typically, this is 127.0.0.1.
|-
|-
|6
|6
|Day Of  Month
|Port
|Example: All
|Example: any
|Specifies which days of the month the  reboot should occur (1-31). "All" means it will occur every day.
|'''any''':  Specify the destination port or port range to which the traffic is directed. any allows traffic to all ports.
|-
|-
|7
|7
|Month
|Action
|Example: All
|Example: DNAT
|Specifies which months the reboot  should occur (1-12). "All" means it will occur every month.
|This  specifies the action to take either DNAT or SNAT.
|-
|-
|8
|8
|Day Of  Week
|Internal IP Address
|Example: All
|Example: 192.168.1.100
|Specifies which days of the week the  reboot should occur (0-6, where 0 is Sunday). "All" means it will occur every day of the week.
|'''Field must  not be empty''': Specify the internal IP address to which the traffic should be redirected.
|-
|9
|Internal Port
|Example: any
|Redirect matched incoming traffic to the given port on the internal host.
|}
|}
Once the user fills all the required given parameters click on the save.
Once the user is done with the required configurations, should click save button and then click on the update to save the changes.


=== 3.4 Import and Export ===
=== 2.8 VRRP ===
In this section, User can Import & Export Configuration files of the Device.
'''VRRP (Virtual Router Redundancy Protocol)''' is used to ensure high availability for IP routing by allowing multiple routers to work together to present the illusion of a single virtual router to the hosts on a network.


[[File:Import and Export Options.png|frameless|601x601px]]
In General Settings, click on ‘Enable VRRP’ and save.


Click “Export Config” to export device configuration & settings to a text file,
[[File:GRD44B 5R VRRP CONFIGURATION.png|1024x1024px]]


Click “Import Config” to import device configuration & settings from a previously exported text file.
In VRRP section,


[[File:Import window.png|frameless|620x620px]]
Give a name and ‘Add’ device.


The user needs to select on the “choose file”, upload the required file and click on apply.
Click on ‘Edit’ to make changes.


=== 3.5 Firmware Upgrade ===
Click on ‘Delete’ if particular instance not required.
The user can upgrade with the latest software for the existing firmware.  


[[File:Firmware Upgrade .png|frameless|620x620px]]
[[File:GRD44B 5R VRRP CONFIGURATION EDIT.png|1024x1024px]]


Click on the '''flash image''' and chose the path where the sys-upgrade file is kept and then click on flash image, it will upgrade to the latest software once the reboot is done.
'''EDIT:'''
 
This option will completely reset the device to default settings.
 
[[File:Flash Image.png|frameless|620x620px]]
 
Click on the '''Retain Config and flash''' and chose the path where the sys-upgrade file is kept and then click on Retain Config and flash, it will upgrade to the latest software once the reboot is done.
 
This refers to updating the firmware (flashing) of a device while preserving the current configuration settings.
 
[[File:Flash Image.png|frameless|620x620px]]
 
Click on the '''Factory Reset''' for the complete retest of the device.
 
=== 3.6 Monitor Application ===
In this section, the monitor application is divided into major 2 configurations which is further sub-divided into 4 editable options,


1.) Modem Monitor Application Configuration:
[[File:GRD44B 5R VRRP CONFIGURATION EDITING.png|1024x1024px]]Specification details are given below:
 
2.) Router Monitor Application Configuration:
 
[[File:Monitor Application Dashboard.png|frameless|620x620px]]
 
 
'''Modem Monitor Application Configuration:'''
 
[[File:Monitor Application.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 2,326: Line 2,468:
|-
|-
|1
|1
|Enable Ping Check Application
|Role
|Enable/Disable
|1.      Master
|Turns on the functionality to perform ping checks on specified IP addresses.
 
2.      Backup
|Choose '''Master'''  for the primary router that should handle the traffic under normal  circumstances.
 
Choose '''Backup''' for a secondary router that will take over if the master fails.
|-
|-
|2
|2
|Time Interval for Check (In minutes)
|Virtual ID
|'''Example:''' 10 minutes
|Ex: 0
|Frequency at which the ping checks are  performed.
|The value can  range from 0 to 255.
 
Ensure all  routers in the same VRRP group share the same '''Virtual ID'''.
|-
|-
|3
|3
|Select No of IP addresses to ping
|Priority
|'''Example:''' 1
|Ex: 100
|Number of IP addresses that will be pinged.
|For the '''Master''' role, use the highest priority, typically above 100.
 
For the '''Backup'''  role, set a lower priority number, usually below the master's priority.
|-
|-
|4
|4
|IP Address 1
|Interface
|'''Example:''' 8.8.8.8
|SW_LAN
|The IP address to ping.
|This is the  network interface on which VRRP operates.
|-
|-
|5
|5
|No. of Retries
|Source IP
|'''Example:''' 5
|Ex: 192.168.10.1
|Number of times to retry pinging an IP address if the initial ping fails.
|This is the  IP address used as the source in VRRP advertisements.
|-
|-
|6
|6
|Failure Criteria in (%)
|Peer IP
|'''Example:''' 80% (If 4 out of 5 pings fail, it’s considered  a failure)
|Ex: 192.168.10.10
|Percentage of failed pings required to consider the ping check a failure.
|This is the  IP address of the other VRRP peer (usually the backup router). It helps the routers identify each other.
|-
|-
|7
|7
|Action On Failure
|Virtual IP  Address
|'''Example:''' Restart Modem
|192.168.10.100/24
|Action to be taken if the ping check fails according to the criteria.
|The virtual  IP should be an unused address within the subnet, such as 192.168.10.100/24, ensuring it's consistent across all VRRP routers.
|-
|-
|8
|8
|Enable Second Level Action
|Enable Authentication
|Enable/Disable
|Enable/Disable
|Option to enable a secondary action if the  primary action fails multiple times.
|Enable this  if you want to secure your VRRP communications.
|-
|-
|9
|9
|Second Level Action Threshold
|Password
|'''Example:''' 2
|*********
|Number of failures required to trigger the  secondary action.
|It ensures that only routers with the correct password can join the VRRP group.
|-
|10
|Second Level Action
|'''Example:''' Restart Board (Reboots the entire hardware board)
|The action to be taken if the second level  action threshold is met.
|}
|}
Save the details once made necessary changes.  
Save and update once changes have been made.
 
=== 2.9 Remote Monitoring ===
In this page the user can select which equipment needs to be monitored remotely.
 
Once the user selects the type of RMS click on save.
 
[[File:GRD44B 5R REMOTE MANAGEMENT SYSTEM.png|1024x1024px]]
 
'''NMS:'''
 
IN this page the user should type the server IP or domain name in the URL then click on save.
 
Click on upload and start (Once key is uploaded and this option is clicked, NMS automatically starts, and this router device gets registered with the NMS server provided).
 
[[File:GRD44B 5R NMS.png|1024x1024px]]
 
'''TR_069:'''


'''Router Monitor Application Configuration:'''
To enable the TR_069 the user needs to click on the enable check box.


[[File:Router Monitor Application Configuration.png|frameless|620x620px]]
[[File:TR_069.png]]Once the user clicks on the check box of enable it will display all the required filed to configured.


Specification details are given below:
[[File:GRD44B 5R TR 069 EDITING.png|1024x1024px]]Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Enable Ping Check Application
|Serving  Interval
|Enable/Disable
|300
|Activates the  ping check functionality to monitor router performance.
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|-
|-
|2
|2
|Time Interval for Check (In minutes)
|Interface
|'''Example:''' 10 minutes
|This can  be something like eth0 or wan.
|How frequently the ping checks are performed.
|This specifies the network interface used for TR-069 communication.
|-
|-
|3
|3
|Select No of IP Addresses to Ping
|Username
|'''Example:''' 1 (Please select the appropriate number  based on your requirements)
|Example: User
|Choose the  number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
|The username used to authenticate with the ACS.
|-
|-
|4
|4
|No. of Retries
|Password
|'''Example:''' 3
|••••
|Number of retries if a ping fails.
|The password used to authenticate with the ACS.
|-
|-
|5
|5
|Failure Criteria in (%)
|URL
|'''Example:''' 80% (If 80% of the pings fail, it’s deemed a failure)
|<nowiki>http://example.com</nowiki>
|Percentage of failed pings required to consider the ping check as failed.
|The URL of the ACS. This is where the CPE (customer-premises equipment) will send its requests and where it will receive configurations and updates from.
|-
|}
|6
 
|Action On Failure
 
|'''Example:''' Restart IPsec
 
|The action  taken if the ping check fails according to the criteria.
The user should fill all the required fields and click on the save button.
|-
 
|7
=== 2.10 Tunnel ===
|Enable Second Level Action
Tunnels are a method of transporting data across a network using protocols which are not supported by that network.
|Enable/Disable
 
|Option to  enable an additional action if the primary action fails.
It is further categorised into 3 sections,
|-
|8
|Second Level Action Threshold
|'''Example:''' Specify the number of failures, such as 2
|Number of  times the primary action must fail before the secondary action is triggered.
|-
|9
|Second Level Action
|'''Example:''' Restart Board
|The action to  be taken if the second level action threshold is met.
|}
Save the details once made necessary changes.


= 4.Status =
1.) General Settings
In this module the user can view the status of the router device with respect to the network, Wan, modem etc.


It has 4 submodules.
2.) GRE Tunnel


* Interfaces
3.) IPIP Tunnel 
* Internet
* Modem
* Routes


[[File:Status Dashboard.png|frameless|620x620px]]
[[File:GRD44B 5R TUNNEL CONFIGURATION .png|1024x1024px]]


=== 4.1 Interfaces ===
'''General Settings:'''
Each network device (interface) is associated with specific traffic statistics, uptime, and status. Active interfaces are operational, while inactive interfaces are not currently transmitting data.


[[File:Status Interfaces.png|frameless|620x620px]]
In this page the user needs to select under which type of tunnel it needs to send the data.


Looking on the network status the user can check if the cellular, wifi, ewan, vpn etc is up.
[[File:GRD44B 5R TUNNEL GENERAL CONFIGURATION.png|1024x1024px]]Once the user selects the type of tunnel then click on the save button.


=== 4.2 Internet ===
In this submodule the user can view the status of the internet connections.


[[File:Internet Status.png|frameless|620x620px]]


  To see the latest status of the internet connection the user needs to click on the refresh button.


=== 4.3 Modem ===
'''GRE Tunnel:'''
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.


[[File:Modem Status.png|frameless|602x602px]]
A GRE (Generic Routing Encapsulation) tunnel configuration involves setting up a virtual point-to-point connection between two endpoints over an IP network.


=== 4.4 Routes ===
Here the user can add/edit/delete the details of the tunnel.
This configuration shows how the router directs traffic between different networks and interfaces, ensuring proper communication within the local network and to external networks via the default gateway.


'''ARP Table:''' Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.
[[File:GRD44B 5R GRE TUNNEL.png|1024x1024px]]


'''IPv4 Routes:''' This shows which network is directly connected on which interface.
Once the required update is done then click on update to save the changes.


Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''


'''IPv6 Routes:''' Similar routes as IPv4, but this time listed under IPv6 routing rules.


Example: Local networks '''192.168.10.0/24''' and '''192.168.100.0/24''' are managed through '''eth0.1''' and '''ra0''', respectively.
'''EDIT:'''


[[File:Route Status.png|frameless|620x620px]]
[[File:GRD44B 5R GRE TUNNEL CONFIGURATION.png|1024x1024px]]


= 5. Features =
Specification details are given below:
In this module the user can see all the features that the router device has.


This module includes 7 features.
{| class="wikitable"
 
* Mac Address Binding
* URL Filtering
* Web Server
* Wi-Fi MacID Filtering
* Routing
* Others
* Connection Diagnostics
 
[[File:Features Dashboard.png|frameless|620x620px]]
 
=== 5.1 Mac Address Binding ===
MAC address binding is a configuration that binds a specific MAC address to a specific IP address. This ensures that a particular device on the network always receives the same IP address from the DHCP server, which can be useful for network management, security, and ensuring consistent network behaviour.
 
Under this submodule the user can configure/update/edit the IP Address for MAC.
 
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.
 
[[File:Mac Addressing Binding.png|frameless|620x620px]]
 
'''EDIT:'''
 
[[File:Mac Address Edit.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Device Name
|Tunnel  name
|Macbinding1
|Example:  GRETunnel
|A user-defined name for the binding  configuration.
|'''GRETunnel''': The name of the GRE tunnel.
|-
|-
|2
|2
|MAC Address
|Local  external IP
|48:9e:bd:da:45:91
|Example: 10.1.1.66
|The unique identifier for the network interface of the device to which the IP address will be bound.
|The IP address of the local endpoint that will initiate the GRE tunnel.
|-
|-
|3
|3
|IP Address
|Remote external  IP
|192.168.10.55
|Example:  10.1.1.40
|The IP address that will be consistently assigned to the device with the specified MAC address.
|The IP address of the remote endpoint that will terminate the GRE tunnel.
|}
 
 
By applying this configuration, the DHCP server will always assign the IP address 192.168.10.55 to the device with the MAC address 48:9e:bd:da:45:91, ensuring consistency and stability in network addressing for that device.
 
* Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
* The user can click on the deleted button to delete an existing configured device.
 
Post all the changes the user needs to click on the update to reflect all the changes in the application.
 
=== 5.2 URL Filtering ===
In this submodule the user should provide the URL which needs to be blocked for the device. By implementing URL filtering with the specified URL, you can control and restrict access to certain websites, thereby improving network security and managing user access.
 
[[File:URL Filtering.png|frameless|620x620px]]
 
To add the new URL for blocking, click on the Add New button.
 
Once the user clicks on the Add New button a new pop will appear in that page write the URL and click on the save.
 
The user can select the status of that URL while defining the URL.
 
[[File:Url Update.png|frameless|620x620px]]
 
To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.
 
Click on “save” after the changes are done as per the need.
 
=== 5.3 Web Server ===
This configuration will allow your device to serve web traffic securely over HTTPS, keep its system time synchronized, and ensure that all HTTP traffic is redirected to HTTPS for better security.
 
[[File:Web server.png|frameless|620x620px]]
 
'''EDIT:'''
 
[[File:Webserver Configuration Editing.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|1
|4
|Enable HTTP
|Peer  tunnel IP
|'''HTTP Port:''' 80
|Example: 10.1.1.4
 
|The IP address of the peer's tunnel interface.
Enable or disable the HTTP server.
|Port 80 is the default port for HTTP traffic. It is used to serve web pages over an unencrypted connection.
|-
|-
|2
|5
|Enable HTTPS
|Local  tunnel IP
|'''HTTPS Port:''' 443
|Example: 10.1.1.6
 
|The IP address of the local tunnel interface.
Enable or disable the HTTPS server.
|Port 443 is the default port for HTTPS traffic. It is used to serve web pages over an encrypted connection.
|-
|-
|3
|6
|Redirect HTTPS
|Local  tunnel net mask
|Option to redirect HTTP traffic to HTTPS.
|Example: 255.255.255.0
|When enabled, all HTTP requests will be automatically redirected to the HTTPS port to ensure secure communication.
|The subnet mask of the local tunnel interface.
|-
|-
|4
|7
|Enable NTP Sync
|Remote IP
|Enable or disable NTP synchronization.
|Example:  192.168.10.0/24
|Synchronizes the device’s system clock with an  external NTP server to maintain accurate time.
|The remote network that is reachable  through the GRE tunnel.
|-
|-
|5
|8
|NTP Server
|Enable  Tunnel Link
|0.openwrt.pool.ntp.org
|Check to  enable
|The address of the NTP server used for time  synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
|Enable or disable the GRE tunnel link.
|-
|-
|6
|9
|NTP Sync Interval (In Minutes)
|Interface  type
|15
|Example:  EWAN2
|The interval at which the device will sync its clock with the NTP server, set to every 15 minutes in this case.
|'''EWAN2''': The type of network interface used for the GRE tunnel.
|-
|10
|MTU
|Example:  1476
|'''1476''': Maximum  Transmission Unit size for the GRE tunnel.
|-
|11
|TTL
|Example:  64
|'''64''': Time To  Live value for the packets within the GRE tunnel.
|-
|12
|Tunnel  key
|Example:  12345678
|'''12345678''': A unique key used to identify the GRE tunnel.
|-
|13
|Enable keep alive
|Check to  enable
|Enable or disable the keep-alive  feature to monitor the tunnel's status.
|-
|14
|Keep  alive interval
|Example:  10
|'''10''':  Interval in seconds for the keep-alive packets.
|}
|}
Once the required update is done then click on update to save the changes.




Click on save once changes are made.


=== 5.4 Wi-Fi MacID Filtering ===
'''IPIP Tunnel:'''
Wireless MAC ID Filtering allows you to control which devices can connect to your wireless network based on their MAC (Media Access Control) addresses. This can help enhance security by allowing only specified devices to access the network.


It is further divided into 2 categories,
An IPIP (IP-in-IP) tunnel is a simple tunnelling protocol used to encapsulate IP packets within IP packets. This is like GRE but without additional features such as keying and type fields.


'''WIFI 2.4G AP'''
Here the user can add/edit/delete the details of the tunnel.


'''WIFI 2.4G AP Guest'''
[[File:GRD44B 5R IPIP TUNNEL CONFIGURATION.png|1024x1024px]]


[[File:Wi-Fi MacID Filtering .png|frameless|620x620px]]


'''EDIT:'''


Before adding the MacIDs the user needs to select the mode from the dropdown menu.
[[File:GRD44B 5R IPIP TUNNEL EDIT.png|1024x1024px]]Once the required update is done then click on update to save the changes.


In ‘Change Mode’ select one option,
Specification details are given below:
 
'''Blacklist'''
 
In blacklist mode, you specify which MAC addresses are not allowed to connect to the wireless network. Devices not on the blacklist will be able to connect.
 
'''Whitelist'''
 
In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.
 
To Add the MacID the user needs to click on Add New option.
 
[[File:WIFI 2.4G AP Guest.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Status
|Tunnel  name
|Enable/Disable
|Example:  IPIPTunnel
|Enable or disable the MAC ID filtering.
|'''IPIPTunnel:''' The name of the IPIP tunnel.
|-
|-
|2
|2
|MAC ID
|Local external  IP
|Example: e8:6f:38:1a:f2:61
|Example: 10.1.1.66
|The MAC address of the device to be whitelisted or blocklisted.
|The IP address of the local endpoint that will initiate the IPIP tunnel.
|-
|-
|3
|3
|Network Name
|Remote  external IP
|Example: WIFI 2.4G AP or Wi-Fi 2.4G AP  Guest.
|Example: 10.1.1.40
|The network to apply the MAC ID filtering.
|The IP address of the remote endpoint  that will terminate the IPIP tunnel.
|}
|-
Once the required MAC ID and Network Name is configured the user needs to click on the save button to add the details.
|4
 
|Peer  tunnel IP
The user needs to click on the edit button to do modifications on the pre-existing configuration.
|Example:  10.1.1.4
 
|The IP address of the peer's tunnel  interface.
Once the required MACID / Network Name is modified the user needs to click on the save button to reflect the changed value in the application.
 
=== 5.5 Routing ===
In this submodule the user can configure the parameters related to routing of the device like Target address, Networks address etc. Routing configurations allow network packets to be directed between different subnets and networks.
 
It is further divided into 2 sections,
 
'''Static IPV4 Routes'''
 
'''Advanced Static IPV4 Routes'''
 
'''Static IPV4 Routes:'''
 
Click on ‘Add’ to add a new interface.
 
[[File:Static IPV4 Routes.png|frameless|620x620px]]
 
 
'''EDIT:'''
 
To edit the existing device the user needs to click on the edit option.
 
Once the changes are done click on the save button to save all the changes.
 
Click on the deleted button to delete the existing device detail.
 
[[File:Static IPV4 Routes Editing.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|1
|5
|Interface
|Local  tunnel IP
|Ex: eth0.1
|Example: 10.1.1.6
|The network interface to be used for this route.  Select the one to use from dropdown.
|The IP address of the local tunnel  interface.
|-
|-
|2
|6
|Target
|Local  tunnel net mask
|Ex: 192.168.20.0
|Example:  255.255.255.0
|The destination subnet to which traffic should be routed.
|The subnet mask of the local tunnel  interface.
|-
|7
|Remote IP
|Example: 192.168.10.0/24
|The remote network that is reachable through the IPIP tunnel.
|-
|-
|3
|8
|IPv4 Netmask
|Enable  Tunnel Link
|255.255.255.0
|Check to  enable
|The subnet mask for the target network.
|Enable or disable the IPIP tunnel link.
|-
|-
|4
|9
|Metric
|Interface  type
|0
|Example:  EWAN2
|The priority of the route.
|'''EWAN2''': The type of network interface used for the IPIP tunnel.
 
Lower values indicate higher priority.
|-
|-
|5
|10
|IPv4 Gateway
|MTU
|Ex: 192.168.10.1
|Example: 1476
|The gateway IP address to be used for routing  traffic to the target subnet.
|'''1476''': Maximum  Transmission Unit size for the IPIP tunnel.
|-
|-
|6
|11
|Route Type
|TTL
|Unicast
|Example:  64
|Standard route for individual destination IP addresses.
|'''64''': Time To  Live value for the packets within the IPIP tunnel.
 
|-
Custom changes can be made.
|12
|Tunnel  key
|Example:  12345678
|Although typically not used in IPIP,  this field might be included for compatibility with certain configurations.
|-
|13
|Enable keep alive
|Check to  enable
|Enable or disable the keep-alive  feature to monitor the tunnel's status.
|-
|14
|Keep  alive interval
|Example:  10
|'''10''':  Interval in seconds for the keep-alive packets.
|}
|}
Click on save once configuration changes have been made.


'''Advanced Static IPV4 Routes:'''
== 3.Maintenance ==
In this module the user can configure/upgrade/modify the settings related to system, password,
 
firmware and monitoring.
 
It includes 6 submodules.


Click on ‘Add’ to add a new interface.
* General
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application


[[File:Advanced Static IPV4 Routes.png|frameless|620x620px]]
[[File:GRD44B 5R MAINTENANCE.png|1024x1024px]]


'''EDIT:'''
''*Below is the detailed explanation of every field*''


To edit the existing device the user needs to click on the edit option.
=== 3.1 General ===
Here you can configure the basic aspects of router like its hostname or the timezone.


Once the changes are done click on the save button to save all the changes.
It is further sub-divided into,


Click on the deleted button to delete the existing device detail.
1.) General Settings


[[File:Advanced Static IPV4 Routes Editing.png|frameless|620x620px]]
2.) Logging


Specification details are given below:
3.) Language and Style
{| class="wikitable"
 
|SN
 
|Field Name
 
|Sample Value
'''General Settings:'''
 
[[File:GRD44B 5R SYS PROPS.png|1024x1024px]] 
 
'''EDIT:'''
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Interface
|Local Time
|Ex: ra0
|2024/07/30  13:25:47
|The network interface through which the traffic  will be routed. Select as per requirement.
|The current local date and time set on  the device.
|-
|-
|2
|2
|To
|Hostname
|Ex: 192.168.10.1
|22B25240007
|This is the target address to which the traffic  is being directed. In this case, all traffic destined for 192.168.10.1 will follow this route.
|The hostname of the device, which is  used to identify it on the network.
|-
|-
|3
|3
|IPv4 Netmask
|Timezone
|255.255.255.192
|Asia/Kolkata
|This defines the subnet of the destination address.
|The timezone setting of the device, which determines the local time.
|-
|}
|4
Once the user configures the required details then click on the save button to save all the details.
|Table
|1.) Local


2.) Main
'''Logging:'''


3.) Default
Here the user can configure the basic aspects of your device related to system.


4.) 220
The system log configuration provided specifies how the device handles and stores log information, including buffer size, external log server details, and log verbosity levels.
 
5.) custom
|1.) This table contains local routes for the addresses assigned to the local interfaces. It's  typically used for host and broadcast addresses.


2.) The  primary routing table used by the system.
[[File:GRD44B 5R LOGGING .png|1024x1024px]]


3.) A  fallback table used when no other table is specified.
'''EDIT:'''
 
4.) Often  used for policy-based routing.
 
5.) A user-defined  routing table.
|-
|5
|From
|Ex: 192.168.100.1
|This source address restricts the route to  traffic originating from 192.168.100.1. Traffic from other sources won't use  this route.
|-
|6
|Priority
|20
|The priority value determines the preference of  this route. A lower number means higher priority; 20 is relatively high, so  this route will be preferred over routes with higher priority values.
|}
Once all the configurations are done click on the update button to reflect the changes made.
 
=== 5.6 Others ===
In this page the user will get to do all the other miscellaneous configuration with respect to the device based on the required parameters. Each utility serves a specific purpose, providing various functionalities for managing and troubleshooting network configurations and statuses.
 
[[File:Miscellaneous configuration v2.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Set Date
|System log buffer size
|Date and time fields (day, month, year,  hour, minute, second)
|Example: 32 kiB
|Sets the system date and time to the specified values.
|The size of the memory buffer allocated  (0-32) for storing system logs before they are either written to a file or sent to an external server.
|-
|-
|2
|2
|Get Date
|External system log server
|System
|Example: 0.0.0.0
|Retrieves and displays the current system date and time.
|The IP address of an external server where logs can be sent.
|-
|-
|3
|3
|ipsec status all
|External system log server port
|Command ‘Get’
|Example: 514
|Displays the status of all IPsec connections.
|The port used to send logs to the external log server. Port 514 is the default port for syslog.
|-
|-
|4
|4
|Wi-Fi Scan
|Log output level
|Command ‘Get’
|Example: Debug
|Initiates a scan for available Wi-Fi networks.
|Sets the detail level of the system  logs.
|-
|-
|5
|5
|iPerf3 Client
|Cron Log level
|IP address (e.g., 192.168.10.100)
|Example: Debug
|Runs an iPerf3 client to measure network  performance.
|The detail level of the logs for cron  jobs.
|-
|}
|6
Once the user configures the required details then click on the save button to save all the details.  
|iPerf3 Server
 
|Command ‘Run’
 
|Runs an iPerf3 server to measure network  performance.
 
|-
'''Language and Style:'''
|7
 
|Ping
Here the user can configure the basic aspects of your device related to language.
|IP address or domain (e.g., 8.8.8.8)
 
|Sends ICMP echo requests to the specified  address to check connectivity.
Once the user configures the required details then click on the save button to save all the details.
|-
 
|8
[[File:GRD44B 5R LANGUAGE AND STYLE.png|1024x1024px]]
|traceroute
 
|IP address or domain (e.g., 8.8.8.8)
=== 3.2 Password ===
|Traces the route packets take to reach the  specified address.
In this module the user can set the password for the admin credentials.
 
Specifies the password for the guest account. If the user enters a plaintext password here, it will get replaced with a crypted password on save. The new password will be effective once the user logs out and log in again.  
 
[[File:GRD44B 5R PASSWORD UPDATE.png|1024x1024px]]
 
=== 3.3 Reboot ===
In this module the user can reboot the device remotely.
 
First option is to directly reboot the device without enabling the maintenance reboot tab.
 
Click on “Reboot Now” at the bottom of the screen to start the reboot process.
 
[[File:GRD44B 5R MAINTENANCE REBOOT .png|1024x1024px]]
 
 
 
To start maintenance reboot process first the user needs to fill all the required fields.
 
Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.
 
[[File:GRD44B 5R MAINTENANCE REBOOT EDIT.png|1024x1024px]]
 
Specification details are given below:
 
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|9
|1
|NTP Sync
|Enable  Maintenance Reboot
|Command ‘Sync’
|Enable/Disable
|Synchronizes the system time with the  configured NTP server.
|Indicates whether the maintenance reboot feature is enabled or not.
|-
|-
|10
|2
|Download Files
|Type
|File or database identifier
|Maintenance  Reboot
|Initiates a download of the specified file or database.
|Specifies the type of reboot being scheduled.
|-
|-
|11
|3
|Restart Power
|Reboot  Type
|Command ‘Restart’
|Software/Hardware
|Restarts the power of the device.
|'''Hardware''': A hardware reboot involves restarting the entire device as if it were powered off and on again.
 
'''Software''': A software reboot involves restarting the operating system without powering off the hardware.
|-
|-
|12
|4
|Restart Modem
|Minutes
|Command ‘Restart’
|Example:  59
|Restarts the modem.
|The minute at which the reboot should  occur (0-59).
|-
|-
|13
|5
|Run AT Command
|Hours
|Enter AT command
|Example:  22 (10 PM)
|Executes the specified AT command on the modem.
|The hour at which the reboot should  occur (0-23, in 24-hour format).
|-
|-
|14
|6
|Show Board Configuration
|Day Of  Month
|Command ‘Show’
|Example:  All
|Displays the current board configuration.
|Specifies which days of the month the  reboot should occur (1-31). "All" means it will occur every day.
|-
|-
|15
|7
|Show VPN Certificate Name
|Month
|Command ‘Show’
|Example:  All
|Displays the name of the VPN certificate in use.
|Specifies which months the reboot should occur (1-12). "All" means it will occur every month.
|-
|-
|16
|8
|Switch SIM to Secondary (Takes >2 mins)
|Day Of Week
|Command ‘Run’
|Example:  All
|Switches the active SIM to the secondary SIM card.
|Specifies which days of the week the  reboot should occur (0-6, where 0 is Sunday). "All" means it will  occur every day of the week.
|-
|}
|17
 
|Send test SMS
Once the user fills all the required given parameters click on the save.
|Phone number (e.g., +911234567890) message text (e.g., "Hello how are you?")
 
|Sends a test SMS to the specified phone number.
=== 3.4 Import and Export ===
|-
In this section, User can Import & Export Configuration files of the Device.
|18
[[File:GRD44B 5R IMPORT EXPORT CONFIGURATION.png|1024x1024px]]
|ReadlatestSMS
 
|Command ‘Read’
Click “Export Config” to export device configuration & settings to a text file,
|Reads the most recent SMS received by the device.
|-
|19
|Data Usage
|'''From:''' Start  date (YYYY-MM-DD)


'''To:''' End date  (YYYY-MM-DD)
Click “Import Config” to import device configuration & settings from a previously exported text file.
|Displays data usage statistics for the  specified date range.
|-
|20
|Monthly Data Usage
|'''Month:''' Month (e.g., 07)


'''Year:''' Year  (e.g., 2024)
[[File:GRD44B 5R IMPORT EXPORT CONFIGURATION UPLOAD.png|1024x1024px]]
|Displays data usage statistics for the specified month and year.
 
|-
The user needs to select on the “choose file”, upload the required file and click on apply.
|
 
|
=== 3.5 Firmware Upgrade ===
|
The user can upgrade with the latest software for the existing firmware.
|
 
[[File:GRD44B 5R FIRMWARE UPGRADE.png|1024x1024px]]
 
Click on the '''flash image''' and chose the path where the sys-upgrade file is kept and then click on flash image, it will upgrade to the latest software once the reboot is done.
 
This option will completely reset the device to default settings.
 
[[File:GRD44B 5R FLASH IMAGE.png|1024x1024px]]Click on the '''Retain Config and flash''' and chose the path where the sys-upgrade file is kept and then click on Retain Config and flash, it will upgrade to the latest software once the reboot is done.
 
This refers to updating the firmware (flashing) of a device while preserving the current configuration settings.
 
[[File:GRD44B 5R RETAIN CONFIG AND FLASH.png|1024x1024px]]
 
Click on the '''Factory Reset''' for the complete retest of the device.
 
[[File:GRD44B 5R FACTORY RESET.png|1024x1024px]]
 
=== 3.6 Monitor Application ===
In this section, the monitor application is divided into major 2 configurations which is further sub-divided into 4 editable options,
 
1.) Modem Monitor Application Configuration:
 
2.) Router Monitor Application Configuration:
 
[[File:GRD44B 5R MONITOR APP.png|1024x1024px]]
 
'''Modem Monitor Application Configuration:'''
 
[[File:GRD44B 5R MODEM MONITOR APP.png|1024x1024px]]Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|21
|1
|Modem Debug Info
|Enable Ping Check Application
|Command ‘Read’
|Enable/Disable
|Displays debug information for the modem.
|Turns on the functionality to perform ping  checks on specified IP addresses.
|-
|-
|22
|2
|Scan Network operators (Takes >3  mins)
|Time Interval for Check (In minutes)
|Command ‘Scan’
|'''Example:''' 10 minutes
|Initiates a scan for available network operators.
|Frequency at which the ping checks are performed.
|-
|-
|23
|3
|Network operator list (First Perform  Scan Network Operators)
|Select No of IP addresses to ping
|Command ‘Show’
|'''Example:''' 1
|Displays the list of network operators detected  in the previous scan.
|Number of IP addresses that will be pinged.
|-
|-
|24
|4
|ReadLogFiles
|IP Address 1
|Log file identifier
|'''Example:''' 8.8.8.8
|Reads and displays the specified log file
|The IP address to ping.
|-
|-
|25
|5
|Enable ssh (Admin)
|No. of Retries
|Command ‘Run’
|'''Example:''' 5
|Enables SSH access for the admin user.
|Number of times to retry pinging an IP address  if the initial ping fails.
|-
|-
|26
|6
|Disable ssh (Admin)
|Failure Criteria in (%)
|Command ‘Run’
|'''Example:''' 80% (If 4 out of 5 pings fail, it’s considered  a failure)
|Disables SSH access for the admin user.
|Percentage of failed pings required to consider  the ping check a failure.
|-
|-
|27
|7
|ClearSIM1Data
|Action On Failure
|Command ‘Clear’
|'''Example:''' Restart Modem
|Clears data usage statistics for SIM1.
|Action to be taken if the ping check fails  according to the criteria.
|-
|-
|28
|8
|ClearSIM2Data
|Enable Second Level Action
|Command ‘Clear’
|Enable/Disable
|Clears data usage statistics for SIM2.
|Option to enable a secondary action if the  primary action fails multiple times.
|-
|-
|29
|9
|Create Bridge with SW_LAN
|Second Level Action Threshold
|Network interface identifier
|'''Example:''' 2
|Creates a network bridge with the specified interface and SW_LAN.
|Number of failures required to trigger the  secondary action.
|-
|-
|30
|10
|Show Bridge
|Second Level Action
|Command ‘Show’
|'''Example:''' Restart Board (Reboots the entire hardware board)
|Displays information about the current network bridges.
|The action to be taken if the second level  action threshold is met.
|-
|31
|Delete Bridge
|Command ‘Delete’
|Deletes the specified network bridge.
|-
|32
|Output
|Any value
|Displays output for all the above actions.
|}
|}
Save the details once made necessary changes.


=== 5.7 Connection Diagnostics ===
'''Router Monitor Application Configuration:'''
This can ensure that your connection diagnostics application effectively monitors and reports the status of your network connections, providing valuable data for troubleshooting and performance optimization.


[[File:Connection Diagnostics.png|frameless|620x620px]]
[[File:GRD44B 5R ROUTER MONITOR APPLICATION CONFIGURATION.png|1024x1024px]]Specification details are given below:
 
{| class="wikitable"
This Application works in 3 parts,
|SN
 
|Field  Name
1.) General settings
 
2.) Connection status and management
 
3.) Application Start/Stop
 
[[File:Connection Diagnostics dashboard.png|frameless|620x620px]]
 
'''General settings:'''
 
First make configuration changes in this section and save.
 
[[File:Connection Diagnostics General Settings.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|Enable Connection Diagnostics
|Enable Ping Check Application
|Enable/Disable
|Enable/Disable
|This option enables or disables the connection diagnostics functionality.
|Activates the ping check functionality to monitor router performance.
|-
|-
|2
|2
|Check Interval (in seconds)
|Time Interval for Check (In minutes)
|'''Value:''' 120
|'''Example:''' 10 minutes
|Specifies how often (in seconds) the diagnostics checks are performed. In this case, every  120 seconds. (min 60 secs)
|How frequently the ping checks are performed.
|-
|-
|3
|3
|Number of Pings
|Select No of IP Addresses to Ping
|'''Value:''' 5
|'''Example:''' 1 (Please select the appropriate number  based on your requirements)
|Determines ping  requests sent during each check.
|Choose the  number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
|-
|-
|4
|4
|Ping Packet Size (in Bytes)
|No. of Retries
|'''Value:''' 56
|'''Example:''' 3
|Defines the size of each ping packet in bytes.
|Number of retries if a ping fails.
|-
|-
|5
|5
|Send to remote MQTT Broker
|Failure Criteria in (%)
|Enable/Disable
|'''Example:''' 80% (If 80% of the pings fail, it’s  deemed a failure)
|This option enables the sending of diagnostic data to a remote MQTT broker.
|Percentage of failed pings required to consider the ping check as failed.
|-
|-
|6
|6
|Publish Data Format
|Action On Failure
|'''CSV''' / '''JSON'''
|'''Example:''' Restart IPsec
|Specifies the format in which the diagnostic data will be published to the MQTT broker. You  can choose either CSV (Comma-Separated Values) or JSON (JavaScript Object  Notation).
|The action taken if the ping check fails according to the criteria.
|-
|-
|7
|7
|MQTT Broker url
|Enable Second Level Action
|'''Value:''' broker.hivemq.com
|Enable/Disable
|The URL of the MQTT broker where the diagnostic data will be sent.
|Option to enable an additional action if the primary action fails.
|-
|-
|8
|8
|TCP port
|Second Level Action Threshold
|'''Value:''' 1883
|'''Example:''' Specify the number of failures, such as 2
|The TCP port used to connect to the MQTT broker. Port 1883 is the default port for MQTT.
|Number of times the primary action must fail before the secondary action is triggered.
|-
|-
|9
|9
|Topic
|Second Level Action
|'''Value:''' 37A26230014/connectionDiagnostics
|'''Example:''' Restart Board
|The MQTT topic under which the diagnostic data will be published. This topic is used  to categorize and identify the data.
|The action to be taken if the second level action threshold is met.
|}
|}
Save the details once made necessary changes.


== 4.Status ==
In this module the user can view the status of the router device with respect to the network, Wan, modem etc.


'''Connection status and management:'''
It has 4 submodules.


To setup a connection,
* Interfaces
* Internet
* Modem
* Routes


Click on ‘Add new target’
=== [[File:GRD44B 5R STATUS.png|1024x1024px]]4.1 Interfaces ===
Each network device (interface) is associated with specific traffic statistics, uptime, and status. Active interfaces are operational, while inactive interfaces are not currently transmitting data.


Enter Target IP (Ex: 8.8.8.8)
[[File:GRD44B 5R INTERFACE.png|1024x1024px]]


Click ‘Add’
Looking on the network status the user can check if the cellular, wifi, ewan, vpn etc is up.


Target has been added successfully.
=== 4.2 Internet ===
In this submodule the user can view the status of the internet connections.


[[File:Connection status and management.png|frameless|620x620px]]
 To see the latest status of the internet connection the user needs to click on the refresh button.


=== [[File:GRD44B 5R WAN STATUS.png|1024x1024px]] 4.3 Modem ===
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.


'''Application Start/Stop:'''
[[File:GRD44B 5R MODEM.png|1024x1024px]]


To check whether the target Ip is sending and receiving packets, you need to start the application to see the desired output.
=== 4.4 Routes ===
This configuration shows how the router directs traffic between different networks and interfaces, ensuring proper communication within the local network and to external networks via the default gateway.


[[File:Application Start-Stop.png|frameless|620x620px]]
'''ARP Table:''' Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.


As shown above, our target Ip is sending packets successfully.
'''IPv4 Routes:''' This shows which network is directly connected on which interface.


You can Add as many target IP’s you need to monitor.
Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''


You can leave the application on for monitoring else ‘Stop’ the application.
'''IPv6 Routes:''' Similar routes as IPv4, but this time listed under IPv6 routing rules.


= 6.Configuration =
Example: Local networks '''192.168.10.0/24''' and '''192.168.100.0/24''' are managed through '''eth0.1''' and '''ra0''', respectively.  
These are gateway features that can be configured as per requirements.


It is divided into 10 sections,
''*Refer the below image*''


1.) Source Configuration
[[File:GRD44B 5R ROUTES.png|1024x1024px]]


2.) Send Configuration
== 5. Features ==
In this module the user can see all the features that the router device has.


3.) Storage Configuration
This module includes 7 features.


4.) Port Configuration
* Mac Address Binding
* URL Filtering
* Web Server
* Wi-Fi MacID Filtering
* Routing
* DMZ
* Others
[[File:GDR44B 5R FEATURES.png|1024x1024px]]


5.) Cloud Configuration
=== 5.1 Mac Address Binding ===
MAC address binding is a configuration that binds a specific MAC address to a specific IP address. This ensures that a particular device on the network always receives the same IP address from the DHCP server, which can be useful for network management, security, and ensuring consistent network behaviour.


6.) Modbus Configuration
Under this submodule the user can configure/update/edit the IP Address for MAC.


7.) RS232 Configuration
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.  


8.) Digital Input Output Configuration
[[File:GRD44B 5R MAC ADDRESS BINDING.png|1024x1024px]]


9.) Analog Input Configuration
'''EDIT:'''
 
10.) Sensor Events
 
[[File:Configuration with Storage Configuration.png|frameless|620x620px]]
 
=== 6.1 Source Configuration ===
These configurations ensure that the system regularly acquires data from various interfaces (RS485, RS232, DIO, and AI) at specified intervals, allowing for efficient monitoring and management of connected devices and sensors.
 
[[File:Source Configuration.png|frameless|620x620px]]


[[File:GRD44B 5R MAC ADDRESS EDITING.png|1024x1024px]]


Specification details are given below:
Specification details are given below:
Line 3,132: Line 3,215:
|-
|-
|1
|1
|Enable  RS485Line1
|Device Name
|Enable/Disable
|Macbinding1
|This option enables the RS485 Line 1 interface for energy meter readings.
|A user-defined name for the binding configuration.
|-
|-
|2
|2
|Overall  Periodicity of RS485 Line 1 Energy meter Readings (In Seconds >= 60)
|MAC Address
|'''Value:'''  60
|48:9e:bd:da:45:91
|Defines the  interval in seconds at which readings are taken from the RS485 Line 1 energy  meter. The minimum allowable interval is 60 seconds.
|The unique identifier for the network interface of the device to which the IP address will be bound.
|-
|-
|3
|3
|Delay between  each Energy meter Readings (in Milliseconds)
|IP Address
|'''Value:'''  1000
|192.168.10.55
|Specifies the  delay in milliseconds between individual readings from the energy meter on  RS485 Line 1.
|The IP address that will be consistently assigned to the device with the specified MAC address.
|-
|4
|Enable RS232
|Enable/Disable
|This option  enables the RS232 interface for device readings.
|-
|5
|Overall  Periodicity of RS232 devices Readings (In Seconds >= 60)
|'''Value:'''  120
|Defines the  interval in seconds at which readings are taken from RS232 devices. The  minimum allowable interval is 60 seconds.
|-
|6
|Delay between  each RS232 device Readings (in Milliseconds)
|'''Value:'''  2000
|Specifies the  delay in milliseconds between individual readings from RS232 devices.
|-
|7
|Enable DIO
|Enable/Disable
|This option  enables the Digital Input/Output (DIO) interface.
|-
|8
|Overall  Periodicity of Digital input/output (In Seconds >= 60)
|'''Value:'''  120
|Defines the  interval in seconds at which readings or updates are taken from the DIO  interface. The minimum allowable interval is 60 seconds.
|-
|9
|Enable AI
|Enable/Disable
|This option enables the Analog Input (AI) interface.
|-
|10
|Overall  Periodicity of Analog Input Readings (In Seconds >= 60)
|'''Value:'''  120
|Defines the  interval in seconds at which readings are taken from the analog inputs. The  minimum allowable interval is 60 seconds.
|}
|}
Click on save once changes have been made.


=== 6.2 Send Configuration ===
By applying this configuration, the DHCP server will always assign the IP address 192.168.10.55 to the device with the MAC address 48:9e:bd:da:45:91, ensuring consistency and stability in network addressing for that device.
Send configuration allows to choose type of string that should be sent to a cloud platform.


SILBO devices do offer 3 different options as shown below.
* Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
* The user can click on the deleted button to delete an existing configured device.


CSV (CSV allows fixed CSV)
Post all the changes the user needs to click on the update to reflect all the changes in the application.


Fixed JSON
=== 5.2 URL Filtering ===
In this submodule the user should provide the URL which needs to be blocked for the device. By implementing URL filtering with the specified URL, you can control and restrict access to certain websites, thereby improving network security and managing user access.


Editable JSON. (JSON option is the editable JSON option)
[[File:GRD44B 5R URL filtering.png|1024x1024px]]


[[File:Send Configuration for Gateway.png|frameless|620x620px]]


To add the new URL for blocking, click on the Add New button.


Data sender Configuration is divided into major 2 parts,
Once the user clicks on the Add New button a new pop will appear in that page write the URL and click on the save.


'''JSON'''
The user can select the status of that URL while defining the URL.


'''CSV'''
[[File:GRD44B 5R URL ENABLE.png|1024x1024px]]


JSON is further divided into 4 categories,
To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.


# '''Modbus Sender'''
[[File:GRD44B 5R URL FILTER DISABLE.png|1024x1024px]]
# '''DIO Sender'''
# '''AI Sender'''
# '''RS232 Sender'''


Click on “save” after the changes are done as per the need.


'''Modbus Sender:'''
=== 5.3 Web Server ===
This configuration will allow your device to serve web traffic securely over HTTPS, keep its system time synchronized, and ensure that all HTTP traffic is redirected to HTTPS for better security.


[[File:Modbus Sender.png|frameless|620x620px]]
[[File:GRD44B 5R Web server.png|1024x1024px]]


Select the field input you wish to add from the ‘Field Content tab’.
'''EDIT:'''


Give a desired JSON Key Name you wish to publish in the ‘Field JSON Key Name’ tab.
[[File:GRD44B 5R Web server edit.png|1024x1024px]]


Once configured, click on Add.
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Enable HTTP
|'''HTTP Port:''' 80


JSON option allows editable JSON in which we can change which parameters should be sent and what name we should use to the tag.
Enable or disable the HTTP server.
|Port 80 is the default port for HTTP traffic.  It is used to serve web pages over an unencrypted connection.
|-
|2
|Enable HTTPS
|'''HTTPS Port:''' 443


[[File:Modbus Sender a1.png|frameless|620x620px]]
Enable or disable the HTTPS server.
 
|Port 443 is the default port for HTTPS traffic.  It is used to serve web pages over an encrypted connection.
 
|-
What changes we can do in JSON edit to the above list.
|3
 
|Redirect HTTPS
Let’s change slave_id to some other name as “Slave number”.
|Option to redirect HTTP traffic to  HTTPS.
 
|When enabled, all HTTP requests will be  automatically redirected to the HTTPS port to ensure secure communication.
[[File:Modbus Sender 1.b.png|frameless|620x620px]]
|-
 
|4
Even custom fields can be added, for example if location name should be sent by router/gateway in JSON packet then it can be configured as shown.
|Session Timeout (in millisecs)
 
|Ex: 60000
[[File:Modbus Sender 1.c.png|frameless|620x620px]]
|In this scenario the webpage will logout after  60secs of inactivity.
|-
|5
|RFC1918 Filter
|Enable/Disable
|When enabled, this filter can block traffic  from private IP ranges (e.g., 192.168.x.x, 10.x.x.x) from being routed  through the public internet, enhancing network security.
|-
|6
|Enable NTP Sync
|Enable or disable NTP synchronization.
|Synchronizes the device’s system clock with an  external NTP server to maintain accurate time.
|-
|7
|NTP Server
|0.openwrt.pool.ntp.org
|The address of the NTP server used for time  synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
|-
|8
|NTP Sync Interval (In Minutes)
|15
|The interval at which the device will sync its  clock with the NTP server, set to every 15 minutes in this case.
|}
Click on save once changes are made.


=== 5.4 Wi-Fi MacID Filtering ===
Wireless MAC ID Filtering allows you to control which devices can connect to your wireless network based on their MAC (Media Access Control) addresses. This can help enhance security by allowing only specified devices to access the network.


'''DIO Sender:'''
It is further divided into 2 categories,


[[File:DIO Sender.png|frameless|620x620px]]
'''WIFI 2.4G AP'''


Select the field input you wish to add from the ‘Field Content tab’.
'''WIFI 2.4G AP Guest'''


Give a desired JSON Key Name you wish to publish in the ‘Field JSON Key Name’ tab.
[[File:GRD44B 5R Wireless mac address.png|1024x1024px]]


Once configured, click on Add.
Before adding the MacIDs the user needs to select the mode from the dropdown menu.


Even custom fields can be added as shown Modbus Sender.
In ‘Change Mode’ select one option,


'''Blacklist'''


'''AI Sender:'''
In blacklist mode, you specify which MAC addresses are not allowed to connect to the wireless network. Devices not on the blacklist will be able to connect.


[[File:AI Sender.png|frameless|650x650px]]
'''Whitelist'''


Select the field input you wish to add from the ‘Field Content tab’.
In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.


Give a desired JSON Key Name you wish to publish in the ‘Field JSON Key Name’ tab.
To Add the MacID the user needs to click on Add New option.


Once configured, click on Add.
[[File:GRD44B 5R MACID ENABLING.png|1024x1024px]]Specification details are given below:
 
{| class="wikitable"
Even custom fields can be added as shown Modbus Sender.
|SN
 
|Field  Name
'''RS232 Sender:'''
|Sample  Value
|Description
|-
|1
|Status
|Enable/Disable
|Enable or disable the MAC ID filtering.
|-
|2
|MAC ID
|Example: e8:6f:38:1a:f2:61
|The MAC address of the device to be whitelisted  or blocklisted.
|-
|3
|Network Name
|Example: WIFI 2.4G AP or Wi-Fi 2.4G AP  Guest.
|The network to apply the MAC ID filtering.
|}
Once the required MAC ID and Network Name is configured the user needs to click on the save button to add the details.


[[File:RS232 Sender.png|frameless|620x620px]]
The user needs to click on the edit button to do modifications on the pre-existing configuration.


Once the required MACID / Network Name is modified the user needs to click on the save button to reflect the changed value in the application.


Select the field input you wish to add from the ‘Field Content tab’.
=== 5.5 Routing ===
In this submodule the user can configure the parameters related to routing of the device like Target address, Networks address etc. Routing configurations allow network packets to be directed between different subnets and networks.
 
It is further divided into 2 sections,
 
'''Static IPV4 Routes'''
 
'''Advanced Static IPV4 Routes'''
 
'''Static IPV4 Routes:'''
 
Click on ‘Add’ to add a new interface.


Give a desired JSON Key Name you wish to publish in the ‘Field JSON Key Name’ tab.
[[File:GRD44B 5R Static routing.png|1024x1024px]]


Once configured, click on Add.


Even custom fields can be added as shown Modbus Sender.
'''EDIT:'''


To edit the existing device the user needs to click on the edit option.


'''CSV:'''
Once the changes are done click on the save button to save all the changes.


This option sends data packets in CSV (Comma-Separated Values) format.
Click on the deleted button to delete the existing device detail.


[[File:RS232 Sender Configuration.png|frameless|620x620px]]
[[File:GRD44B 5R STATIC IPV4 ROUTES EDIT.png|1024x1024px]]




Line 3,291: Line 3,407:
|-
|-
|1
|1
|Device ID
|Interface
|IAB44
|Ex: eth0.1
|A unique identifier for the device.
|The network interface to be used for this route. Select the one to use from dropdown.
|-
|-
|2
|2
|Record Start Mark
|Target
|[
|Ex: 192.168.20.0
|This  character marks the beginning of a data record. It's used to indicate where a new data record starts in the transmitted packet.
|The destination subnet to which traffic should be routed.
|-
|-
|3
|3
|Record End Mark
|IPv4 Netmask
|]
|255.255.255.0
|This  character marks the end of a data record. It signals the end of the data for  one record before a new one starts.
|The subnet mask for the target network.
|-
|-
|4
|4
|Register Start Mark
|Metric
|<
|0
|This  character marks the beginning of a register within a data record. A register  typically represents an individual data field within the record.
|The priority of the route.
 
Lower values indicate higher priority.
|-
|-
|5
|5
|Register End Mark
|IPv4 Gateway
|>
|Ex: 192.168.10.1
|This  character marks the end of a register within a data record. It indicates where the data for a particular field end.
|The gateway IP address to be used for routing traffic to the target subnet.
|-
|-
|6
|6
|Invalid Data Character
|Route Type
|N
|Unicast
|Used to  indicate that the data for a particular register is invalid or could not be collected. This helps in identifying which data points are not usable.
|Standard route for individual destination IP addresses.
|-
 
|7
Custom changes can be made.
|Failure Data Character
|NA
|Used to  indicate that there was a failure in collecting or processing the data for a  particular register. It signifies that an error occurred, and the data point  could not be obtained.
|}
|}
Click on save once changes are made.
Click on save once configuration changes have been made.  


=== 6.3 Storage Configuration ===
'''Advanced Static IPV4 Routes:'''
To enable data storage on eMMC,


Enable the Data storage tab and select the storage size that meets your requirements.
Click on ‘Add’ to add a new interface.  


[[File:Storage Configuration.png|frameless|620x620px]]
[[File:GRD44B 5R Advanced static routing.png|1024x1024px]]


=== 6.4 Port Configuration ===
'''EDIT:'''
Serial port configuration involves setting parameters for serial communication, allowing data exchange between devices via serial ports.


Port Configuration is divided into 4 port mode,
To edit the existing device the user needs to click on the edit option.


'''Transparent Serial to Remote TCP Client'''
Once the changes are done click on the save button to save all the changes.


'''Transparent Serial to Remote TCP Server'''
Click on the deleted button to delete the existing device detail.


'''Modbus TCP Master to Modbus RTU Slave'''
[[File:GRD44B 5R Advanced static routing EDITING.png|1024x1024px]]


'''Modbus RTU Master to Modbus TCP Slave'''
Specification details are given below:
 
[[File:Port Configuration.png|frameless|620x620px]]
 
 
'''Transparent Serial to Remote TCP Client:'''


[[File:Transparent Serial to Remote TCP Client.png|frameless|620x620px]]
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 3,362: Line 3,467:
|-
|-
|1
|1
|Port Mode
|Interface
|Transparent Serial to Remote TCP Client
|Ex: ra0
|Configures  the serial port to send data directly to a remote TCP client without any additional protocol layers, making it "transparent."
|The network interface through which the traffic will be routed. Select as per requirement.
|-
|-
|2
|2
|Transparent Serial Port Mode
|To
|1.) raw
|Ex: 192.168.10.1
|This is the target address to which the traffic  is being directed. In this case, all traffic destined for 192.168.10.1 will  follow this route.
|-
|3
|IPv4 Netmask
|255.255.255.192
|This defines the subnet of the destination  address.
|-
|4
|Table
|1.) Local


2.) rawlp
2.) Main


3.) telnet
3.) Default


4.) off
4.) 220
|1.) It's a straightforward data transfer where the serial data is sent as-is.
 
5.) custom
|1.) This table contains local routes for the  addresses assigned to the local interfaces. It's  typically used for host and broadcast addresses.
 
2.) The  primary routing table used by the system.


2.)  "Rawlp" stands for "raw with local processing". Typically,  it involves some minimal local processing before transmission.
3.) A fallback table used when no other table is specified.


3.) This allows the serial connection to be accessed and managed over a Telnet  session.
4.) Often used for policy-based routing.


4.) The "off" mode disables the transparent serial port functionality.
5.) A user-defined routing table.
|-
|3
|Time Out
|no time out
|Ensures that  the serial port does not time out, meaning it will continuously wait for data  without closing the connection due to inactivity.
|-
|4
|Local Listener TCP Port
|3040
|Sets the TCP  port number to 3040 for the local listener to accept incoming TCP  connections.
|-
|-
|5
|5
|Baud Rate
|From
|9600
|Ex: 192.168.100.1
|This is a common baud rate for serial communication, balancing speed and reliability.
|This source address restricts the route to traffic originating from 192.168.100.1. Traffic from other sources won't use  this route.
|-
|-
|6
|6
|No Of Stopbits
|Priority
|1
|20
|Configures the serial communication to use 1 stop bit, which is a common setting  ensuring the end of each byte is clearly marked.
|The priority value determines the preference of this route. A lower number means higher priority; 20 is relatively high, so  this route will be preferred over routes with higher priority values.
|-
|}
|7
Once all the configurations are done click on the update button to reflect the changes made.
|No Of Databits
 
|8
=== 5.6 DMZ ===
|Sets the  number of bits in each transmitted byte to 8.
A '''DMZ (Demilitarized Zone)''' is a subnetwork that provides an extra layer of security for an organization's internal network.
 
In this case we are configuring several services (HTTP, HTTPS, SSH, FTP, DNS) in a DMZ, and each service requires the correct '''internal port''' (the port used within the network) and '''external port''' (the port used by external clients to access the service) settings.
 
[[File:GRD44B 5R DMZ.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Enable DMZ
|Enable/Disable
|Enable DMZ to configure it further.
|-
|2
|Host IP Address
|Ex: 192.168.10.1
|This is the internal IP address of the device or server that will be in the DMZ.
|-
|-
|8
|3
|Parity
|Protocol
|1.) None
|1.) TCP


2.) Even
2.) UDP


3.) Odd
3.) ICMP


4.) Space
4.) All
|'''TCP''': Used  for reliable services like HTTP, HTTPS, FTP, and SSH.


5.) Mark
'''UDP''': Often used for services like DNS that don't require as much reliability.
|1.) No parity bit is added to the data byte.


2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.
'''ICMP''': Used for sending control messages like "ping."


3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.
'''All''': Select  this if you're unsure which protocol to allow, but it's less secure.
|-
|4
|Allow HTTP
|Internal Port: 80


4.) The parity bit is always set to 0, regardless of the data.
External Port: 80
|Enables web traffic over the unsecured '''HTTP''' protocol.


5.) The  parity bit is always set to 1, regardless of the data.
(Port 80 is the standard port for HTTP traffic  on our internal network).
|-
|-
|9
|5
|Flow Control
|Allow HTTPS
|1.) RTSCTS
|Internal Port: 443


2.) NONE
External Port: 443
|Enables secure web traffic over '''HTTPS.''' (Port  443 is the standard port for HTTPS on our internal network).
|-
|6
|Allow SSH
|Internal Port: 52434


3.) DTRDSR
External Port: 52434
|This is a custom port we’re using for SSH.


4.) XONXOFF
The default is 22.
|1.) Request  to Send / Clear to Send
|-
|7
|Allow FTP
|Internal Port: 21/20


2.) No flow  control is used.
External Port: 21/20
|FTP is used to transfer files between  computers.


3.) Data  Terminal Ready / Data Set Ready
(These are the standard ports for FTP traffic.  Port 21 is used for control commands, and port 20 for the data transfer.)
|-
|8
|Allow DNS
|Internal Port: 53


4.) Software  flow control using specific control characters (XON and XOFF) to manage data  flow.
External Port: 53
|-
|Standard DNS port within our internal network.
|10
|Read Trace
|Enable/Disable
|Enables  logging of data being read from the serial port.
|-
|11
|Write Trace
|Enable/Disable
|Enables  logging of data being written to the serial port.
|}
|}
Click on save once configuration changes are made.


'''Transparent Serial to Remote TCP Server:'''
=== 5.7 Others ===
In this page the user will get to do all the other miscellaneous configuration with respect to the device based on the required parameters. Each utility serves a specific purpose, providing various functionalities for managing and troubleshooting network configurations and statuses.


Configures the port to act as a bridge, converting serial data into TCP packets sent to a remote TCP server.
[[File:GRD44B 5R MISC UTILITIES.png|1024x1024px]]
 
[[File:Transparent Serial to Remote TCP Server-.png|frameless|620x620px]]


Specification details are given below:
Specification details are given below:
Line 3,472: Line 3,610:
|-
|-
|1
|1
|Port Mode
|Set Date
|Transparent Serial to Remote TCP Server
|Date and time fields (day, month, year,  hour, minute, second)
|Defines how  the serial port will operate in relation to the remote server.
|Sets the system date and time to the specified  values.
|-
|-
|2
|2
|Remote Server IP
|Get Date
|Ex: 192.168.10.1
|System
|'''Field must not be empty:''' This is a required field, and you must provide a valid IP  address for proper communication.
|Retrieves and displays the current system date and time.
|-
|-
|3
|3
|Remote Server Port
|ipsec status all
|Ex: 1883
|Command ‘Get’
|'''Field must  not be empty:''' This is a required field, and you must specify the correct  port number used by the server.
|Displays the status of all IPsec connections.
|-
|-
|4
|4
|Transparent Serial Port Mode
|Wi-Fi Scan
|1.) raw
|Command ‘Get’
 
|Initiates a scan for available Wi-Fi networks.
2.) rawlp
|-
 
3.) telnet
 
4.) off
|1.) It's a straightforward data transfer where the serial data is sent as-is.
 
2.)  "Rawlp" stands for "raw with local processing". Typically,  it involves some minimal local processing before transmission.
 
3.) This  allows the serial connection to be accessed and managed over a Telnet  session.
 
4.) The  "off" mode disables the transparent serial port functionality.
|-
|5
|5
|Time Out
|iPerf3 Client
|no time out
|IP address (e.g., 192.168.10.100)
|Ensures that the serial port does not time out, meaning it will continuously wait for data  without closing the connection due to inactivity.
|Runs an iPerf3 client to measure network performance.
|-
|-
|6
|6
|Local Listener Interface IP Address
|iPerf3 Server
|
|Command ‘Run’
|'''Field must  not be empty:''' This is a required field for specifying which local IP  address will be used for listening.
|Runs an iPerf3 server to measure network performance.
|-
|-
|7
|7
|Local Listener TCP Port
|Ping
|3040
|IP address or domain (e.g., 8.8.8.8)
|The TCP port number on the local device that will be used to listen for incoming data.
|Sends ICMP echo requests to the specified address to check connectivity.
|-
|
|
|
|
|-
|-
|8
|8
|Baud Rate
|traceroute
|9600
|IP address or domain (e.g., 8.8.8.8)
|Standard baud rate, common for many serial devices.
|Traces the route packets take to reach the specified address.
|-
|-
|9
|9
|No Of Stopbits
|NTP Sync
|1
|Command ‘Sync’
|Indicates that one stop bit is used, which is standard for most serial communications.
|Synchronizes the system time with the configured NTP server.
|-
|-
|10
|10
|No Of Databits
|Download Files
|8
|File or database identifier
|Indicates that 8 data bits are used per byte, which is a common setting.
|Initiates a download of the specified file or database.
|-
|-
|11
|11
|Parity
|Restart Power
|1.) None
|Command ‘Restart’
 
|Restarts the power of the device.
2.) Even
 
3.) Odd
 
4.) Space
 
5.) Mark
|1.) No parity  bit is added to the data byte.
 
2.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is even.
 
3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.
 
4.) The  parity bit is always set to 0, regardless of the data.
 
5.) The  parity bit is always set to 1, regardless of the data.
|-
|-
|12
|12
|Flow Control
|Restart Modem
|1.) RTSCTS
|Command ‘Restart’
 
|Restarts the modem.
2.) NONE
|-
 
|13
3.) DTRDSR
|Run AT Command
 
|Enter AT command
4.) XONXOFF
|Executes the specified AT command on the modem.
|1.) Request  to Send / Clear to Send
 
2.) No flow  control is used.
 
3.) Data  Terminal Ready / Data Set Ready
 
4.) Software  flow control using specific control characters (XON and XOFF) to manage data  flow.
|-
|13
|Read Trace
|Enable/Disable
|Option to  enable tracing of incoming data from the serial port, useful for debugging.
|-
|-
|14
|14
|Write Trace
|Show Board Configuration
|Enable/Disable
|Command ‘Show’
|Option to  enable tracing of outgoing data from the serial port, useful for debugging.
|Displays the current board configuration.
|}
Click on save once configuration changes are made.
 
 
'''Modbus TCP Master to Modbus RTU Slave:'''
 
Configures the serial port to function as a Modbus TCP Master that communicates with a Modbus RTU Slave over the serial connection.
 
This setup is used to send Modbus TCP commands to a Modbus RTU device via a serial-to-TCP gateway.
 
[[File:Modbus TCP Master to Modbus RTU Slave.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|1
|15
|Port Mode
|Show VPN Certificate Name
|Modbus TCP Master to Modbus RTU Slave
|Command ‘Show’
|This setup is used to send Modbus TCP commands to a Modbus RTU device via a serial-to-TCP  gateway.
|Displays the name of the VPN certificate in use.
|-
|16
|Switch SIM to Secondary (Takes >2  mins)
|Command ‘Run’
|Switches the active SIM to the secondary SIM  card.
|-
|17
|Send test SMS
|Phone number (e.g., +911234567890)  message text (e.g., "Hello how are you?")
|Sends a test SMS to the specified phone number.
|-
|-
|2
|18
|Baud Rate
|ReadlatestSMS
|9600
|Command ‘Read’
|The speed at which data is transmitted over the serial connection.
|Reads the most recent SMS received by the device.
|-
|-
|3
|19
|Parity
|Data Usage
|1.) None
|'''From:''' Start  date (YYYY-MM-DD)


2.) Even
'''To:''' End date  (YYYY-MM-DD)
|Displays data usage statistics for the  specified date range.
|-
|20
|Monthly Data Usage
|'''Month:''' Month (e.g., 07)


3.) Odd
'''Year:''' Year  (e.g., 2024)
|1.) No parity  bit is used, meaning no additional error-checking bits are included.
|Displays data usage statistics for the  specified month and year.
 
2.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is even.
 
3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.
|-
|-
|4
|
|No of Stopbits
|
|1
|
|Indicates  that one stop bit is used, which is standard for most serial communications.
|
|-
|-
|5
|21
|No of Databits
|Modem Debug Info
|8
|Command ‘Read’
|Indicates  that 8 data bits are used per byte, which is a common setting.
|Displays debug information for the modem.
|-
|-
|6
|22
|Local Listener Interface IP Address
|Scan Network operators (Takes >3  mins)
|
|Command ‘Scan’
|'''Field must  not be empty:''' You need to provide a valid IP address where the TCP connections will be received.
|Initiates a scan for available network operators.
|-
|-
|7
|23
|TCP Port
|Network operator list (First Perform  Scan Network Operators)
|502
|Command ‘Show’
|This is the  standard port for Modbus TCP communication.
|Displays the list of network operators detected in the previous scan.
|-
|-
|8
|24
|Max. Number of Retries
|ReadLogFiles
|5
|Log file identifier
|The maximum  number of times to retry sending a request if the initial attempt fails.
|Reads and displays the specified log file
|-
|-
|9
|25
|Delay Between Each Request (In milliseconds)
|Enable ssh (Admin)
|500
|Command ‘Run’
|The delay  between consecutive Modbus requests to avoid overwhelming the system or  device.
|Enables SSH access for the admin user.
|-
|10
|Response Wait Time (In milliseconds)
|500
|The maximum  time to wait for a response from the Modbus RTU Slave before considering the request failed.
|-
|-
|11
|26
|Connection Timeout (In seconds)
|Disable ssh (Admin)
|0
|Command ‘Run’
|A value of 0  typically means no timeout is set, so the system will wait indefinitely.
|Disables SSH access for the admin user.
|-
|-
|12
|27
|Inactivity Timeout (In seconds)
|ClearSIM1Data
|
|Command ‘Clear’
|The time to  wait before closing a connection if no activity is detected.
|Clears data usage statistics for SIM1.
|}
Click on save once configuration changes have been made.
 
'''Modbus RTU Master to Modbus TCP Slave:'''
 
Configures the serial port to function as a Modbus RTU Master that communicates with a Modbus TCP Slave over a network. This setup is used to send Modbus RTU commands from a master device to a Modbus TCP device via a TCP-to-serial gateway.
 
[[File:Modbus RTU Master to Modbus TCP Slave.png|alt=Modbus RTU Master to Modbus TCP Slave|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|1
|28
|Port Mode
|ClearSIM2Data
|Modbus RTU Master to Modbus TCP Slave
|Command ‘Clear’
|This setup is  used to send Modbus RTU commands from a master device to a Modbus TCP device via a TCP-to-serial gateway.
|Clears data usage statistics for SIM2.
|-
|29
|Create Bridge with SW_LAN
|Network interface identifier
|Creates a network bridge with the specified interface and SW_LAN.
|-
|30
|Show Bridge
|Command ‘Show’
|Displays information about the current network  bridges.
|-
|-
|2
|31
|Baud Rate
|Delete Bridge
|9600
|Command ‘Delete’
|The speed at  which data is transmitted over the serial connection.
|Deletes the specified network bridge.
|-
|-
|3
|32
|Parity
|Output
|1.) None
|Any value
|Displays output for all the above actions.
|}


2.) Even
=== 5.8 SNMP Agent Configuration ===
The '''SNMP (Simple Network Management Protocol) Agent Configuration''' is essential for monitoring and managing network devices, such as routers, from a central management system.


3.) Odd
[[File:GRD44B 5R SNMP Agent Configuration.png|1024x1024px]]
|1.) No parity  bit is used, meaning no additional error-checking bits are included.


2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.
Specification details are given below:
 
{| class="wikitable"
3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.
|SN
|Field Name
|Sample  Value
|Description
|-
|-
|4
|No of Stopbits
|1
|1
|Indicates that one stop bit is used, which is standard for most serial communications.
|Enable SNMP Service
|Enable/Disable
|Enable this  if you want the device to be accessible for SNMP-based monitoring and  management.
|-
|2
|IP Family
|IPV4
|Specifies that SNMP service will operate over IPv4.
|-
|3
|Port
|161
|'''161''' is the default and should be used unless there is a specific need to use a  different port.
|-
|4
|System OID
|1.3.6.1.4.1.38151
|This unique  identifier represents the device in the SNMP management system.
|-
|-
|5
|5
|No of Databits
|Name
|8
|Invendis  Router
|Indicates that 8 data bits are used per byte, which is a common setting.
|The name used to identify the device in the SNMP management system.
|-
|-
|6
|6
|TCP Slave Address
|Contact
|Field must not be empty
|Invendis@invendis.co
|The IP address of the Modbus TCP Slave device to which the master will send requests.
|The email address of the person responsible for the device, used for administrative  contact.
|-
|-
|7
|7
|TCP Slave Port
|Location
|Field must not be empty
|Bangalore
|The port number on the Modbus TCP Slave device for receiving Modbus requests.
|The physical location of the device.
|-
|-
|8
|8
|Max. Number of Retries
|SNMP Version
|5
|Version-1,
|The maximum  number of times to retry sending a request if the initial attempt fails.
 
Version-2,
 
Version-3
|'''Version-1''':  Basic and outdated, offering no security.
 
'''Version-2''':  An improvement over Version-1 with better performance and some security  features.
 
'''Version-3''':  The most secure, offering authentication and encryption (AuthPriv).
|-
|-
|9
|9
|Delay Between Each Request (In milliseconds)
|Security       (for SNMP Version-3)
|Field must not be empty
|NoAuthNoPriv
|The delay between consecutive Modbus requests to avoid overwhelming the system.
 
AuthNoPriv
 
AuthPriv
|'''No  Authentication, No Privacy'''
 
'''Authentication,  No Privacy'''
 
'''Authentication and Privacy'''
|-
|-
|10
|10
|Response Wait Time (In milliseconds)
|Username
|500
|Ex: admin
|The maximum time to wait for a response from the Modbus TCP Slave before considering the  request failed.
|The username used for SNMP authentication.
|-
|-
|11
|11
|Connection Timeout (In seconds)
|Authentication  Password
|0
|*******
|A value of 0 typically means no timeout is set, so the system will wait indefinitely.
|This password is used to authenticate the SNMP user.
|-
|-
|12
|12
|Inactivity Timeout (In seconds)
|Privacy  Password
|Field must not be empty
|*******
|The time to  wait before closing a connection if no activity is detected.
|This password  is used to encrypt SNMP messages.
|-
|13
|Download MIB  File
|Download
|Click this to  download the MIB file associated with the device’s SNMP configuration.
|}
|}
Click on save once configuration changes have been made.


=== 6.5 Cloud Configuration ===
In this section you can select the protocol by which you need to send data to cloud.


There are 3 Cloud/Protocol available,
Click on save tab to save changes.
 
=== 5.9 Connection Diagnostics ===
This can ensure that your connection diagnostics application effectively monitors and reports the status of your network connections, providing valuable data for troubleshooting and performance optimization.
 
[[File:GRD44B 5R Connection Diagnostics.png|1024x1024px]]


'''HTTP'''
This Application works in 3 parts,


'''MQTT'''
1.) General settings


'''Azure'''
2.) Connection status and management


[[File:Cloud Configuration.png|frameless|620x620px]]
3.) Application Start/Stop


'''HTTP Cloud/Protocol:'''
[[File:RB44_Application_Start_Stop.png|1024x1024px]]
'''General settings:'''


This configuration sets up communication between your device and cloud service using the HTTP cloud.
First make configuration changes in this section and save.


[[File:HTTP Cloud-Protocol.png|frameless|620x620px]]
[[File:RD44A_Connection_Diagnostics_General_Settings.png|1005x1005px]]


Specification details are given below:
Specification details are given below:
Line 3,784: Line 3,904:
|-
|-
|1
|1
|Site ID
|Enable Connection Diagnostics
|Ex: ‘Site123’ or ‘Device456’.
|Enable/Disable
|A unique identifier for your site or device within the cloud service.
|This option enables or disables the connection diagnostics functionality.
|-
|-
|2
|2
|Cloud / Protocol
|Check Interval (in seconds)
|HTTP
|'''Value:''' 120
|The protocol used for communication with the cloud service.
|Specifies how often (in seconds) the diagnostics checks are performed. In this case, every  120 seconds. (min 60 secs)
|-
|-
|3
|3
|HTTP URL
|Number of Pings
|'''Example:''' www.httpbin.org/post
|'''Value:''' 5
|The endpoint URL of the cloud service where data will be sent.
|Determines ping requests sent during each check.
|-
|-
|4
|4
|HTTP Port (Optional)
|Ping Packet Size (in Bytes)
|Leave it blank for the default port.
|'''Value:''' 56
|The port  number for the HTTP connection. This is optional because the default port for HTTP (80) is used if not specified.
|Defines the  size of each ping packet in bytes.
|-
|-
|5
|5
|Enable Authentication
|Send to remote MQTT Broker
|Enable/Disable
|Enable/Disable
|Enable this if your cloud service requires a username and password.
|This option enables the sending of diagnostic data to a remote MQTT broker.
|-
|-
|6
|6
|Username
|Publish Data Format
|'''Example:''' admin
|'''CSV''' / '''JSON'''
|The username for authentication with the cloud service.
|Specifies the format in which the diagnostic data will be published to the MQTT broker. You  can choose either CSV (Comma-Separated Values) or JSON (JavaScript Object  Notation).
|-
|-
|7
|7
|Password
|MQTT Broker url
|*****
|'''Value:''' broker.hivemq.com
|The password for authentication with the cloud service.
|The URL of the MQTT broker where the diagnostic data will be sent.
|-
|-
|8
|8
|Enable Server Response Validation
|TCP port
|Enable/Disable
|'''Value:''' 1883
|Enable this if you need to verify that the server's response is valid.
|The TCP port used to connect to the MQTT broker. Port 1883 is the default port for MQTT.
|-
|-
|9
|9
|Server Response
|Topic
|Ex: RecordID or custom
|'''Value:''' 37A26230014/connectionDiagnostics
|A unique identifier for the record being sent to the cloud service.
|The MQTT topic under which the diagnostic data will be published. This topic is used  to categorize and identify the data.
|-
|}
|10
 
|Method
|1.) Post


2.) Get
'''Connection status and management:'''
|1.) The HTTP  method used for sending data to the cloud service.


2.) The HTTP  method used for requesting data from the cloud service.
To setup a connection,
|}
'''MQTT Cloud/Protocol:'''


This configuration sets up communication between your device and a cloud service using the MQTT protocol.
Click on ‘Add new target’


[[File:MQTT Cloud-Protocol.png|frameless|620x620px]]
Enter Target IP (Ex: 8.8.8.8)


Specification details are given below:
Click ‘Add’
{| class="wikitable"
 
|SN
Target has been added successfully.
|Field  Name
 
|Sample  Value
[[File:RB44_Connection_status_and_management.png|1024x1024px]]
|Description
|-
|1
|Site ID
|Example:  ‘Site123’ or ‘Device456’.
|A unique  identifier for your site or device within the cloud service.
|-
|2
|Cloud / Protocol
|MQTT
|The protocol  used for communication with the cloud service.
|-
|3
|MQTT Host
|'''Example:''' broker.hivemq.com
|The MQTT  broker's address (hostname or IP address) that the device will connect to for  sending and receiving messages.
|-
|4
|MQTT Port
|'''Example:''' 1883
|This is the  default port for unencrypted MQTT connections.
|-
|5
|Authentication Mode
|1.) No Authentication


2.) Username/Password
'''Application Start/Stop:'''


3.) TLS
To check whether the target Ip is sending and receiving packets, you need to start the application to see the desired output.
|1.) Connect  to the broker without any credentials.


2.) The  Username/Password for authentication with the cloud service.
[[File:RB44_Application_Start_Stop_1.png|980x980px]]


3.) Upload  TLS certificates only if TLS authentication is selected as shown in the above image.
As shown above, our target Ip is sending packets successfully.
|-
|6
|Enable Publish Over LAN
|Enable/Disable
|When enabled, the device will also publish MQTT messages over the local area network (LAN).
|-
|7
|RS485 Topic (Optional)
|'''Example:''' RS485Data1
|The MQTT  topic for publishing RS485 data.
|-
|8
|Command Request Topic (Optional)
|'''Example:''' CommandRequest1
|The topic to  which the device listens for command requests. Leave it blank if not in use.
|-
|9
|Command Response Topic (Optional)
|'''Example:''' CommandResponse1
|The topic on  which the device publishes responses to commands. Leave it blank if not in  use.
|}
Click on save once configuration changes have been made.


You can Add as many target IP’s you need to monitor.


'''Azure:'''
You can leave the application on for monitoring else ‘Stop’ the application.


This configuration sets up the connection to Azure IoT Hub using either MQTT or HTTP protocols with a specified connection string.
=== 5.10 Package Manager ===
A '''Package Manager''' is a tool or interface used to '''manage software packages''' (applications, libraries, tools) on a system.


[[File:Azure Configuration.png|frameless|620x620px]]
The package manager interface you are looking at likely allows you to manage the software installed on your device, such as networking tools, firmware, or other applications relevant to your system.


Specification details are given below:
This section has 3 sub-sections,
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Site ID
|Example:  ‘Site123’ or ‘Device456’.
|A unique  identifier for your site or device within the cloud service.
|-
|2
|Cloud / Protocol
|Azure
|The cloud  service and protocol used for communication.
|-
|3
|Protocol
|1.) MQTT


2.) HTTP
Installed APP
|1.) A  lightweight messaging protocol suitable for IoT devices.
 
Available APP
 
Manual Upgrade
 
[[File:RB44_Package_Manager.png|1024x1024px]]
 
'''Installed APP:'''
 
When you select Installed APP, you will see all the software that is actively running or installed on the device.
 
This could include system utilities, network management tools, monitoring software, or any third-party apps that were previously installed.
 
'''Common Actions''':
 
* '''View Details''': You can check each application's version, source, and    installation date.
* '''Uninstall''': You can remove applications that are no longer needed.
* '''Check for Updates''': You can see if there are updates available for any    installed application.
 
 
'''Available APP''':
 
When you select '''Available APP''', you will see a list of software that can be installed from the system's repositories or sources.
 
These applications are not yet installed but are ready for installation if needed.
 
 
'''Common Actions''':
 
* '''Install''': You can install any of the available applications by selecting them.
* '''View Details''': You can review each application's description, version, and    functionality before installing.
* '''Search''': You can search for specific apps by name or category.
 
 
'''Manual Upgrade''':
 
In contrast to automatic updates, '''Manual Upgrade''' lets you take control over which packages or applications you want to upgrade and when.


2.) A  protocol used for communication over the web, commonly used for RESTful  services.
This can be useful if you need to avoid upgrading certain apps due to compatibility or testing purposes, or if you want to perform updates at a specific time.
|-
|4
|Connection String
|e.g., invendis-iot-hub.azure-devices.net.
|The primary  or secondary key used to authenticate the device with the IoT Hub.
|}
Click on save once configuration changes have been made.


=== 6.6 Modbus Configuration ===
'''Common Actions''':
Modbus Configuration involves setting up communication parameters for Modbus devices, including baud rate, parity, stop bits, data bits, TCP/RTU settings, and timeout/retry settings for reliable data exchange.


Click on “Add Device” to start a new configuration.
* '''Check for Updates''': The system will check for available updates for installed    apps.
* '''Select Updates''': You can select which packages to update manually.
* '''Upgrade Now''': You can start the upgrade process immediately for selected apps.


This Configuration has 2 sections,


1.) Parameter Configuration
== 6.Configuration ==
These are gateway features that can be configured as per requirements.


2.) Register Config
It is divided into 5 sections,


[[File:Modbus Configuration.png|frameless|620x620px]]
1.) Source Configuration


'''Parameter Configuration:'''
2.) Send Configuration


As shown in the image below, there are two types of protocol used in Modbus configuration.
3.) Port Configuration


1.) RTU (Remote Terminal Unit)
4.) Cloud Configuration


2.) TCP (Transmission Control Protocol)
5.) Modbus Configuration


Details of both protocols is mentioned in the specification table.
[[File:GRD44B 5R Configuration.png|1024x1024px]]


[[File:Modbus Parameter Configuration.png|frameless|620x620px]]
=== 6.1 Source Configuration ===
These configurations ensure that the system regularly acquires data from various interfaces at specified intervals, allowing for efficient monitoring and management of connected devices and sensors.


Specification details are given below:
[[File:GRD44B 5R Source config.png|1024x1024px]]Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 3,978: Line 4,059:
|-
|-
|1
|1
|DEVICE NAME
|Enable  RS485Line1
|Ex: Invendis
|Enable/Disable
|This is the name assigned to the Modbus device for identification purposes.
|This option enables the RS485 Line 1 interface for energy meter readings.
|-
|-
|2
|2
|Port number
|Overall  Periodicity of RS485 Line 1 Energy meter Readings (In Seconds >= 60)
|RS485 Port-1
|'''Value:''' 120
|This specifies which RS485 port on the device is being used for communication.
|Defines the interval  in seconds at which readings are taken from the RS485 Line 1 energy meter.  The minimum allowable interval is 60 seconds.
|-
|-
|3
|3
|Meter ID
|Delay between  each Energy meter Readings (in Milliseconds)
|1
|'''Value:'''  2000
|The Meter ID is a unique identifier for the specific meter within the network. Each Modbus device on the network must have a unique ID to differentiate it from others.
|Specifies the delay in milliseconds between individual readings from the energy meter on RS485 Line 1.
|-
|}
|4
Click on save once changes have been made.
|Meter Model
 
|Example: abcd
=== 6.2 Send Configuration ===
|This field  specifies the model of the meter.
Send configuration allows to choose type of string that should be sent to a cloud platform.
|-
 
|5
SILBO devices do offer 3 different options as shown below.
|Function Code
 
|read coils (1)
CSV (CSV allows fixed CSV)
 
Fixed JSON


read input coils (2)
Editable JSON. (JSON option is the editable JSON option)


read holding registers (3)
[[File:GRD44B 5R Data sender config.png|1024x1024px]]


read  input registers (4)
Data sender Configuration is divided into major 2 parts,
|The function  code indicates the operation to be performed. In Modbus, each operation has a  specific function code.
 
|-
'''JSON'''
|6
 
|Slave Address
'''CSV'''
|Example: '''1'''
 
|The slave  address identifies the specific slave device on the Modbus network. Each  slave must have a unique address so that the master can communicate with it  individually.
JSON is further divided into 1 category,
|-
 
|
'''Modbus Sender:'''
|
 
|'''Modbus protocol: RTU'''
[[File:GRD44B 5R Modbus sender.png|1024x1024px]]
|
 
|-
Select the field input you wish to add from the ‘Field Content tab’.
|7
|Baud rate
|<nowiki>300 | 1200 | 1800 | 2400 | 4800 | 19200 |  38400 | default: 9600</nowiki>
|The baud rate determines the  communication speed between devices, measured in bits per second.
|-
|8
|Parity
|1.) NONE


2.) ODD
Give a desired JSON Key Name you wish to publish in the ‘Field JSON Key Name’ tab.


3.) EVEN
Once configured, click on Add.
|1.) No parity  bit is added to the data byte.


2.) Ensures  that the total number of 1-bits in
JSON option allows editable JSON in which we can change which parameters should be sent and what name we should use to the tag.


the data byte  plus the parity bit is even.
[[File:GRD44B 5R Modbus sender 1.png|1024x1024px]]


3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.
What changes we can do in JSON edit to the above list.
|-
 
|9
Let’s change slave_id to some other name as “Slave number”.
|No. of Databits
 
|7/8
[[File:GRD44B 5R Modbus sender 2.png|1024x1024px]]
|Indicates  that 8 data bits are used per byte, which is a common setting.
|-
|10
|No. of Stopbits
|1/2
|Configures  the serial communication to use 1 stop bit, which is a common setting  ensuring the end of each byte is clearly marked.
|-
|
|
|'''Modbus protocol: TCP'''
|
|-
|11
|Modbus Comm IP
|Ex: 192.168.10.147
|IP of the device you  are communicating with.
|-
|12
|Modbus Comm Port
|Ex: 502 (default)


|Give a specified TCP port number
|-
|13
|Modbus Comm Timeout
|Ex: 60
|This refers  to the maximum amount of time the master device will wait for a response from  a slave device before it assumes a communication failure.
|-
|14
|Start Register
|Example: 0
|The start  register indicates the address of the first register to be read in the slave  device.
|-
|15
|No. of Resister
|Example: 10
|This  specifies the number of consecutive registers to read starting from the start  register.
|}
'''Register Config:'''


In this section you can add multiple parameters to read.
Even custom fields can be added, for example if location name should be sent by router/gateway in JSON packet then it can be configured as shown.  


There are 2 different formats,
[[File:Modbus sender 3.png|1024x1024px]]


Default Mapping
'''CSV:'''


Custom Mapping
This option sends data packets in CSV (Comma-Separated Values) format.


[[File:Modbus Register Configuration.png|frameless|620x620px]]
[[File:GRD44B 5R CSV.png|1024x1024px]]


Specification details are given below:
Specification details are given below:
Line 4,099: Line 4,135:
|-
|-
|1
|1
|Default mapping
|Device ID
|1.) Tag Name = (Ex: FQ)
|GRD44B-5R
|A unique  identifier for the device.
|-
|2
|Record Start Mark
|[
|This  character marks the beginning of a data record. It's used to indicate where a  new data record starts in the transmitted packet.
|-
|3
|Record End Mark
|]
|This  character marks the end of a data record. It signals the end of the data for one record before a new one starts.
|-
|4
|Register Start Mark
|<
|This  character marks the beginning of a register within a data record. A register  typically represents an individual data field within the record.
|-
|5
|Register End Mark
|>
|This  character marks the end of a register within a data record. It indicates  where the data for a particular field end.
|-
|6
|Invalid Data Character
|N
|Used to  indicate that the data for a particular register is invalid or could not be  collected. This helps in identifying which data points are not usable.
|-
|7
|Failure Data Character
|NA
|Used to  indicate that there was a failure in collecting or processing the data for a  particular register. It signifies that an error occurred, and the data point  could not be obtained.
|}
Click on save once changes are made.


2.) Data type  = 8bit INT | 8bit UINT | 16bit INT, high byte first | 16bit INT, low byte  first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit  float (various Byte order) | 32bit INT (various Byte order) | 32bit UINT  (various Byte order) | 1 bit; default: Hexadecimal
=== 6.3 Port Configuration ===
|1.) Input value name.


2.) Defines  how read data will be stored.
|-
|2
|Custom mapping
|1.)  Register name:


2.)  Start register:


3.)  Register count:
Serial port configuration involves setting parameters for serial communication, allowing data exchange between devices via serial ports.


4.) Data type = 8bit INT | 8bit UINT | 16bit INT, high byte first | 16bit  INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte  first | 32bit float (various Byte order) | 32bit INT (various Byte order) |  32bit UINT (various Byte order) | 1 bit; Hexadecimal; default: 32-bit  floating point
Port Configuration is divided into 4 port mode,
|1.)  Input value name.


2.)  First register in custom register block.
'''Transparent Serial to Remote TCP Client'''


3.) Path  to file in which the custom register block will be stored.
'''Transparent Serial to Remote TCP Server'''


4.) Defines how read data will be  stored.
'''Modbus TCP Master to Modbus RTU Slave'''
|}
In Register Config,


Click on ‘Add’ to add new parameters.
'''Modbus RTU Master to Modbus TCP Slave'''
 
Click on ‘Show JSON’ to view an example value of how the data will be presented.
 
Click on ‘Update Device’ once configuration changes have been made.
 
=== 6.7 RS232 Configuration ===
This configuration details how to set up communication with a Modbus device over an RS232 serial connection.
 
To add a new device,
 
In ‘Add New Device’ Field, give ‘Device Name’ and ‘Port Number’, then click on ‘Add’.


[[File:Modbus RS232 Configuration.png|frameless|620x620px]]
[[File:GRD44B 5R Port config.png|1024x1024px]]'''Transparent Serial to Remote TCP Client:'''


'''EDIT:'''
[[File:GRD44B 5R Transparent Serial to Remote TCP Client.png|1024x1024px]]
 
[[File:Modbus RS232 Configuration Editing.png|frameless|620x620px]]


Specification details are given below:
Specification details are given below:
Line 4,153: Line 4,199:
|-
|-
|1
|1
|Meter ID
|Port Mode
|In this case,  it's 1
|Transparent Serial to Remote TCP Client
|Identifies the specific meter or device being communicated with.
|Configures the serial port to send data directly to a remote TCP client without any  additional protocol layers, making it "transparent."
|-
|-
|2
|2
|Meter Model
|Transparent Serial Port Mode
|Ex: DeepSea7320
|1.) raw
|Specifies the  model of the meter or device.
 
2.) rawlp
 
3.) telnet
 
4.) off
|1.) It's a  straightforward data transfer where the serial data is sent as-is.
 
2.)  "Rawlp" stands for "raw with local processing". Typically,  it involves some minimal local processing before transmission.
 
3.) This  allows the serial connection to be accessed and managed over a Telnet  session.
 
4.) The "off" mode disables the transparent serial port functionality.
|-
|-
|3
|3
|Slave Address
|Time Out
|Example: 1
|no time out
|The address of the slave device on the RS232 network. This address is used by the master  to address specific slaves.
|Ensures that the serial port does not time out, meaning it will continuously wait for data  without closing the connection due to inactivity.
|-
|-
|4
|4
|Start  Register
|Local Listener TCP Port
|Example: 99
|3040
|The address of the starting register for the data to be read or written.
|Sets the TCP port number to 3040 for the local listener to accept incoming TCP  connections.
|-
|-
|5
|5
|No of  Register
|Baud Rate
|Example: 10
|9600
|The number of registers to be read or written starting from the Start Register.
|This is a common baud rate for serial communication, balancing speed and reliability.
|-
|-
|6
|6
|Baud Rate
|No Of Stopbits
|Example: 9600
|1
|The speed of communication over the serial port, measured in bits per second (bps).
|Configures the serial communication to use 1 stop bit, which is a common setting  ensuring the end of each byte is clearly marked.
|-
|-
|7
|7
|No of  Stopbits
|No Of Databits
|1 or 2
|8
|Indicates the  number of stop bits used in the serial communication.
|Sets the  number of bits in each transmitted byte to 8.
|-
|-
|8
|8
|No of  Databits
|7 or 8
|Specifies the  number of data bits in each character of the serial data.
|-
|9
|Function Code
|read holding registers (3)
read input registers (4)
|The function  code indicates the operation to be performed. In Modbus, each operation has a  specific function code.
|-
|10
|Modbus  Protocol
|RTU or TCP
|Indicates the  type of Modbus protocol used.
|-
|11
|Parity
|Parity
|0 (NONE)
|1.) None


1 (ODD)
2.) Even


2 (EVEN)
3.) Odd
|Error  checking method used in serial communication.
|-
|12
|Port Number
|1
|The serial  port number to which the device is connected.
|-
|13
|Flow Control
|0 – No


1 – hardware
4.) Space


2 – software
5.) Mark
|Specifies the method of flow control used to manage data flow between devices.
|1.) No parity bit is added to the data byte.
|-
|14
|Delay (In  Milliseconds)
|Ex: 500
|Specifies the  delay time in milliseconds between successive communication attempts.
|}
Click on save once configuration changes have been made.  


=== 6.8 Digital Input Output Configuration ===
2.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is even.
The '''Digital Input/Output (DIO) configuration''' sets up the parameters for reading from and writing to digital I/O lines, specifying the timing and behaviour for input signals and output controls.


In Digital IO Configuration, there are 4 Digital IO’s.
3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.


All 4 Digital IO’s have same configuration depending on which I/O is in use.
4.) The  parity bit is always set to 0, regardless of the data.
 
 
[[File:Digital Input Output Configuration.png|frameless|620x620px]]
5.) The  parity bit is always set to 1, regardless of the data.
|-
|9
|Flow Control
|1.) RTSCTS
 
2.) NONE
 
3.) DTRDSR
 
4.) XONXOFF
|1.) Request  to Send / Clear to Send
 
2.) No flow  control is used.
 
3.) Data  Terminal Ready / Data Set Ready
 
4.) Software  flow control using specific control characters (XON and XOFF) to manage data  flow.
|-
|10
|Read Trace
|Enable/Disable
|Enables  logging of data being read from the serial port.
|-
|11
|Write Trace
|Enable/Disable
|Enables  logging of data being written to the serial port.
|}
Click on save once configuration changes are made.
 
 
 
'''Transparent Serial to Remote TCP Server:'''
 
Configures the port to act as a bridge, converting serial data into TCP packets sent to a remote TCP server.  
 
[[File:GRD44B 5R Transparent serial-tcp server.png|1024x1024px]]  


Specification details are given below:
Specification details are given below:
Line 4,251: Line 4,311:
|-
|-
|1
|1
|Enable Digital IO
|Port Mode
 
|Transparent Serial to Remote TCP Server
(1/2/3/4)
|Defines how  the serial port will operate in relation to the remote server.
|Enable/Disable
|Activates the configuration for Digital IO (1/2/3/4).
|-
|-
|2
|2
|Digital IO (1/2/3/4) Mode
|Remote Server IP
|Input/ Output
|Ex: 192.168.10.1
|Determines if Digital IO (1/2/3/4) is set as an input or output.
|'''Field must not be empty:''' This is a required field, and you must provide a valid IP  address for proper communication.
|-
|-
|3
|3
|Digital IO (1/2/3/4) Alarm Active State
|Remote Server Port
|0 for low, 1 for high
|Ex: 1883
|Defines the  active state for alarms.
|'''Field must  not be empty:''' This is a required field, and you must specify the correct port number used by the server.
|-
|-
|4
|4
|Digital IO (1/2/3/4) Alarm Active Filter Time
|Transparent Serial Port Mode
|Example: 20
|1.) raw
|Sets the time (in milliseconds) to filter out noise when the alarm is active.
 
2.) rawlp
 
3.) telnet
 
4.) off
|1.) It's a  straightforward data transfer where the serial data is sent as-is.
 
2.)  "Rawlp" stands for "raw with local processing". Typically,  it involves some minimal local processing before transmission.
 
3.) This  allows the serial connection to be accessed and managed over a Telnet session.
 
4.) The  "off" mode disables the transparent serial port functionality.
|-
|-
|5
|5
|Digital IO (1/2/3/4) Alarm DeActive Filter Time
|Time Out
|Example: 20
|no time out
|Sets the time  (in milliseconds) to filter out noise when the alarm is inactive.
|Ensures that  the serial port does not time out, meaning it will continuously wait for data without closing the connection due to inactivity.
|-
|-
|6
|6
|Digital IO (1/2/3/4) Time Dependency
|Local Listener Interface IP Address
|Enable/Disable
|
|Determines if the alarm is dependent on specific times.
|'''Field must not be empty:''' This is a required field for specifying which local IP  address will be used for listening.
|-
|-
|7
|7
|Digital IO (1/2/3/4) Alarm Start Time
|Local Listener TCP Port
|00:00:00
|3040
|Defines when the alarm starts during the day.
|The TCP port number on the local device that will be used to listen for incoming data.
|-
|
|
|
|
|-
|-
|8
|8
|Digital IO (1/2/3/4) Alarm Stop Time
|Baud Rate
|23:59:59
|9600
|Defines when the alarm stops during the day.
|Standard baud rate, common for many serial devices.
|-
|-
|9
|9
|Digital IO (1/2/3/4) MaskValue
|No Of Stopbits
|0 or 1
|1
|Specifies a value used to filter or mask digital input signals.
|Indicates that one stop bit is used, which is standard for most serial communications.
|-
|-
|10
|10
|Digital IO (1/2/3/4) Alarm Set Notify Value
|No Of Databits
|0 or 1
|8
|Value that triggers an alarm notification.
|Indicates  that 8 data bits are used per byte, which is a common setting.
|-
|-
|11
|11
|Digital IO (1/2/3/4) Alarm Reset Notify Value
|Parity
|0 or 1
|1.) None
|Value that  resets an alarm notification.
 
|}
2.) Even
Click on save once configuration changes have been made.
 
3.) Odd
 
4.) Space


=== 6.9 Analog Input Configuration ===
5.) Mark
'''Analog Input Configuration''' involves setting parameters for analog input lines, such as enabling the input, defining measurement ranges, setting thresholds, and configuring alarm conditions and filtering times.
|1.) No parity  bit is added to the data byte.


In Analog Input Configuration, there are 2 Analog Input’s.
2.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is even.


Both Analog Input’s have same configuration depending on which AI is in use.
3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.


[[File:Analog Input Configuration.png|frameless|620x620px]]
4.) The  parity bit is always set to 0, regardless of the data.


Specification details are given below:
5.) The parity bit is always set to 1, regardless of the data.
{| class="wikitable"
|SN
|Field Name
|Sample  Value
|Description
|-
|-
|1
|12
|Enable Analog Input/output (1,2)
|Flow Control
|1.) RTSCTS
 
2.) NONE
 
3.) DTRDSR
 
4.) XONXOFF
|1.) Request  to Send / Clear to Send
 
2.) No flow  control is used.
 
3.) Data  Terminal Ready / Data Set Ready


|Enable/Disable
4.) Software flow control using specific control characters (XON and XOFF) to manage data flow.
|This option enables the first and second analog input channel for monitoring and  configuration.
|-
|-
|2
|13
|Analog Input (1,2) Alarm Enable
|Read Trace
|Enable/Disable
|Enable/Disable
|When enabled, the system will monitor the input levels against the defined thresholds and  trigger alarms accordingly.
|Option to enable tracing of incoming data from the serial port, useful for debugging.
|-
|-
|3
|14
|Analog Input (1,2) Upper Threshold Level
|Write Trace
|Example: 16
|When the  input level exceeds this value, an alarm can be triggered.
|-
|4
|Analog Input (1,2) Upper Hysteresis
|Example: 0.5
|Defines the  hysteresis (buffer) for the upper threshold level. This helps to prevent  frequent triggering of the alarm due to small fluctuations around the  threshold level.
|-
|5
|Analog Input (1,2) Lower Threshold Level
|Example: 4
|When the  input level falls below this value, an alarm can be triggered.
|-
|6
|Analog Input (1,2) Lower Hysteresis
|Example: 0.5
|This helps to  prevent frequent triggering of the alarm due to small fluctuations around the  threshold level.
|-
|7
|Analog Input (1,2) Time Dependency
|Enable/Disable
|This setting  allows configuring the time period during which the alarm monitoring is  active.
|-
|8
|Analog Input (1,2) Alarm Start Time
|Do no leave it empty
|Specifies the  start time for the alarm monitoring period.
|-
|9
|Analog Input (1,2) Alarm Stop Time
|Do no leave it empty
|Specifies the  stop time for the alarm monitoring period.
|-
|10
|Day Dependency
|Enable/Disable
|Enable/Disable
|Allows  configuring the monitoring to be active only on certain days.
|Option to enable tracing of outgoing data from the serial port, useful for debugging.
|-
|11
|Weekly Holidays
|Example: Sunday
|Specifies the days of the week when the monitoring and alarms should be disabled.
|}
|}
Click on save once configuration changes have been made.
Click on save once configuration changes are made.  


=== 6.10 Sensor Events ===
A '''sensor event''' refers to a specific occurrence or condition detected by a sensor that triggers a predefined response or action within a system.


In ‘Add New Event’,


Enter an ‘Event Name’ and click on ‘Add’.
'''Modbus TCP Master to Modbus RTU Slave:'''


This section is divided into 3 parts,
Configures the serial port to function as a Modbus TCP Master that communicates with a Modbus RTU Slave over the serial connection.
 
Event
 
Action 1
 
Action 2


[[File:Sensor Events.png|frameless|620x620px]]
This setup is used to send Modbus TCP commands to a Modbus RTU device via a serial-to-TCP gateway.  


'''Event:'''
[[File:GRD44B 5R Modbus tcp master.png|1024x1024px]]  
 
[[File:Sensor Events 1.a.png|frameless|620x620px]]


Specification details are given below:
Specification details are given below:
Line 4,412: Line 4,445:
|-
|-
|1
|1
|Enable
|Port Mode
|Enable/Disable
|Modbus TCP Master to Modbus RTU Slave
|This option allows you to enable or disable the sensor event configuration.
|This setup is used to send Modbus TCP commands to a Modbus RTU device via a serial-to-TCP  gateway.
|-
|-
|2
|2
|Sensor Type
|Baud Rate
|1.) Digital  Input
|9600
|The speed at  which data is transmitted over the serial connection.
|-
|3
|Parity
|1.) None


2.) Relay
2.) Even


3.) Analog Input
3.) Odd
|1.) No parity bit is used, meaning no additional error-checking bits are included.


4.)  Temperature sensor
2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.
|'''Digital  Input:''' Configures events for digital input sensors.


'''Relay:'''  Configures events for relay sensors.
3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.
 
'''Analog  Input:''' Configures events for analog input sensors.
 
'''Temperature Sensor:''' Configures events for temperature sensors.
|-
|-
|3
|4
|Digital Input  no
|No of Stopbits
 
|1
Relay Input  no
|Indicates that one stop bit is used, which is standard for most serial communications.
 
Analog Input  no
 
Temperature  sensor no
|This field must not be empty when either of the sensor type is selected.
|Specifies the  number or identifier.
|-
|-
|4
|5
|Alarm Active  State
|No of Databits
|0 or 1
|8
|Defines the state that triggers the alarm for the selected sensor type.
|Indicates that 8 data bits are used per byte, which is a common setting.
|}
Click on save once configuration changes have been made.
 
'''Action 1/ Action 2:'''
 
Sensor Type selected is '''DIGITAL INPUT''' or '''RELAY.'''
 
[[File:Sensor Events Action configuration.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|                                                          '''Alarm Active Status'''
|-
|-
|6
|Local Listener Interface IP Address
|
|
{| class="wikitable"
|'''Field must  not be empty:''' You need to provide a valid IP address where the TCP  connections will be received.
|SN
|Field   Name
|Sample    Value
|Description
|-
|-
|1
|7
|Type
|TCP Port
|1.) None
|502
 
|This is the standard port for Modbus TCP communication.
2.) Relay    Control
|1.) No    action will be defined.
 
2.) Specifies    that the action taken will involve controlling a relay.
 
|-
|-
|2
|8
|Relay No
|Max. Number of Retries
|1.) Relay 1
|5
 
|The maximum  number of times to retry sending a request if the initial attempt fails.
2.) Relay 2
|-
 
|9
3.) Relay 3
|Delay Between Each Request (In milliseconds)
 
|500
4.) Relay 4
|The delay  between consecutive Modbus requests to avoid overwhelming the system or  device.
|Select the   specific relay that will be controlled when the alarm is active.
|-
|10
|Response Wait Time (In milliseconds)
|500
|The maximum  time to wait for a response from the Modbus RTU Slave before considering the  request failed.
|-
|11
|Connection Timeout (In seconds)
|0
|A value of 0  typically means no timeout is set, so the system will wait indefinitely.
|-
|-
|3
|12
|Relay    Action
|Inactivity Timeout (In seconds)
|1.)    Continuous On
|
|The time to  wait before closing a connection if no activity is detected.
|}
Click on save once configuration changes have been made.  


2.)    Continuous Off
'''Modbus RTU Master to Modbus TCP Slave:'''


3.) Off    with Timeout
Configures the serial port to function as a Modbus RTU Master that communicates with a Modbus TCP Slave over a network. This setup is used to send Modbus RTU commands from a master device to a Modbus TCP device via a TCP-to-serial gateway.  


4.) Off    without Timeout
[[File:GRD44B 5R Modbus rtu master.png|1024x1024px]]


5.) On    & off
Specification details are given below:
|1.) The    relay will be turned on and will remain on indefinitely if the alarm    condition is active or until manually turned off.
 
2.) The    relay will be turned off and will remain off indefinitely regardless of the    alarm condition.
 
3.) The    relay will be turned off, but only for a specified timeout period.
 
4.) The    relay will be turned off immediately and will remain off without any time    constraints.
 
5.) This    could be useful for signalling or for specific control requirements where    intermittent activation is needed.
 
|}
|-
|'''Alarm Inactive Status'''
|-
|
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field   Name
|Field Name
|Sample   Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Type
|Port Mode
|1.) None
|Modbus RTU Master to Modbus TCP Slave
 
|This setup is  used to send Modbus RTU commands from a master device to a Modbus TCP device  via a TCP-to-serial gateway.
2.) Relay Control
|1.) No    action will be defined.
 
2.) This   indicates that the system will perform an action related to relay control    when the alarm condition is active.
|-
|-
|2
|2
|Relay No
|Baud Rate
|1.) Relay 1
|9600
 
|The speed at  which data is transmitted over the serial connection.
2.) Relay 2
 
3.) Relay 3
 
4.) Relay 4
|The   specific relay that should be deactivated or controlled when the alarm is    cleared.
|-
|-
|3
|3
|Relay    Action
|Parity
|1.)   Continuous On
|1.) None


2.)   Continuous Off
2.) Even


3.) Off    with Timeout
3.) Odd
|1.) No parity  bit is used, meaning no additional error-checking bits are included.


4.) Off    without Timeout
2.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is even.


5.) On    & off
3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.
|1.) The    relay will be turned on and will remain on indefinitely when the alarm is    inactive.
 
2.) The    relay will be turned off and will remain off indefinitely when the alarm is    inactive.
 
3.) The    relay will be turned off for a specified timeout period when the alarm    becomes inactive.
 
4.) The    relay will be turned off immediately and will remain off without any time    constraints when the alarm is inactive.
 
5.) The    relay will cycle between on and off states when the alarm is inactive.
|}
|}
 
 
Click on save once configuration changes have been made.
 
'''Action 1/ Action 2:'''
 
Sensor Type selected is '''ANALOG INPUT''' or '''TEMPERATURE SENSOR.'''
[[File:Anolog Input Temperature Sensor.png|frameless|620x620px]]Specification details are given below:
{| class="wikitable"
| colspan="4" |'''Above Maximum Threshold Level'''
|-
|SN
|Field Name
|Sample Value
|Description
|-
|-
|4
|No of Stopbits
|1
|1
|Type
|Indicates  that one stop bit is used, which is standard for most serial communications.
|1.) None
 
2.) Relay Control
|'''Relay Control:''' This specifies that the action  to be taken involves controlling a relay.
|-
|-
|2
|5
|Relay Number
|No of Databits
|1.) Relay 1
|8
 
|Indicates that 8 data bits are used per byte, which is a common setting.
2.) Relay 2
 
3.) Relay 3
 
4.) Relay 4
|The specific relay number to be controlled needs to be selected from a list of available relays. This allows you to target a  specific relay for the action.
|-
|-
|3
|6
|Relay Action
|TCP Slave Address
|1.) Continuous On
|Field must not be empty
 
|The IP address of the Modbus TCP Slave device to which the master will send requests.
2.) Continuous Off
 
3.) Off with Timeout
 
4.) Off without Timeout
 
5.) On & off
|1.) This is typically used to trigger an alert or  activate a device that should remain on until the condition is resolved.
 
2.) The relay remains continuously off when the  threshold is exceeded.
 
3.) The relay will turn off for a specified duration (timeout) when the threshold is exceeded and then return to its previous  state.
 
4.) The relay turns off and stays off until manually  reset or until the condition causing the threshold breach is resolved.
 
5.) The relay toggles between on and off states.
|}
{| class="wikitable"
| colspan="4" |'''Between Threshold Level'''
|-
|-
|SN
|7
|Field Name
|TCP Slave Port
|Sample Value
|Field must not be empty
|Description
|The port  number on the Modbus TCP Slave device for receiving Modbus requests.
|-
|-
|1
|8
|Type
|Max. Number of Retries
|1.) None
|5
 
|The maximum number of times to retry sending a request if the initial attempt fails.
2.) Relay Control
|'''Relay Control:''' This specifies that the action to be taken is related to controlling a relay.
|-
|-
|2
|9
|Relay Number
|Delay Between Each Request (In milliseconds)
|1.) Relay 1
|Field must not be empty
 
|The delay between consecutive Modbus requests to avoid overwhelming the system.
2.) Relay 2
 
3.) Relay 3
 
4.) Relay 4
|This field requires you to choose the specific relay that will be controlled when the parameter value is between the threshold  levels.
|-
|-
|3
|10
|Relay Action
|Response Wait Time (In milliseconds)
|1.) Continuous On
|500
|The maximum  time to wait for a response from the Modbus TCP Slave before considering the  request failed.
|-
|11
|Connection Timeout (In seconds)
|0
|A value of 0  typically means no timeout is set, so the system will wait indefinitely.
|-
|12
|Inactivity Timeout (In seconds)
|Field must not be empty
|The time to  wait before closing a connection if no activity is detected.
|}
Click on save once configuration changes have been made.


2.) Continuous Off
=== 6.4 Cloud Configuration ===
In this section you can select the protocol by which you need to send data to cloud.


3.) Off with Timeout
There are 3 Cloud/Protocol available,


4.) Off without Timeout
'''HTTP'''


5.) On & off
'''MQTT'''
|1.) The relay will remain continuously on as long as  the parameter value stays within the specified threshold range.


2.) The relay will remain continuously off if the  parameter value stays within the specified threshold range.
'''Azure'''


3.) The relay will turn off for a specified timeout  period when the parameter value enters the threshold range.
[[File:GRD44B 5R Cloud config.png|1024x1024px]]'''HTTP Cloud/Protocol:'''


4.) The relay will turn off immediately without any  timeout when the parameter value enters the threshold range.
This configuration sets up communication between your device and cloud service using the HTTP cloud.


5.) The relay will alternate between on and off  states when the parameter value stays within the threshold range.
[[File:GRD44B 5R Http CLOUD-PROTOCOL.png|1024x1024px]]Specification details are given below:
|}
{| class="wikitable"
{| class="wikitable"
| colspan="4" | '''   Below Minimum Threshold Level'''
|-
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Type
|Site ID
|1.) None
|Ex: ‘Site123’ or ‘Device456’.
 
|A unique  identifier for your site or device within the cloud service.
2.) Relay Control
|'''Relay Control:''' This specifies that the action  to be taken is related to controlling a relay.
|-
|-
|2
|2
|Relay Number
|Cloud / Protocol
|1.) Relay 1
|HTTP
 
|The protocol used for communication with the cloud service.
2.) Relay 2
 
3.) Relay 3
 
4.) Relay 4
|This field requires you to choose the specific relay that will be controlled when the parameter value is between the threshold  levels.
|-
|-
|3
|3
|Relay Action
|HTTP URL
|1.) Continuous On
|'''Example:''' www.httpbin.org/post
 
|The endpoint  URL of the cloud service where data will be sent.
2.) Continuous Off
|-
|4
|HTTP Port (Optional)
|Leave it blank for the default port.
|The port  number for the HTTP connection. This is optional because the default port for  HTTP (80) is used if not specified.
|-
|5
|Enable Authentication
|Enable/Disable
|Enable this  if your cloud service requires a username and password.
|-
|6
|Username
|'''Example:''' admin
|The username  for authentication with the cloud service.
|-
|7
|Password
|*****
|The password  for authentication with the cloud service.
|-
|8
|Enable Server Response Validation
|Enable/Disable
|Enable this  if you need to verify that the server's response is valid.
|-
|9
|Server Response
|Ex: RecordID or custom
|A unique  identifier for the record being sent to the cloud service.
|-
|10
|Method
|1.) Post


3.) Off with Timeout
2.) Get
|1.) The HTTP  method used for sending data to the cloud service.


4.) Off without Timeout
2.) The HTTP  method used for requesting data from the cloud service.
|}


5.) On & off
'''MQTT Cloud/Protocol:'''
|1.) The relay will remain continuously on as long as  the parameter value stays below the minimum threshold level.


2.) The relay will remain continuously off as long  as the parameter value stays below the minimum threshold level.
This configuration sets up communication between your device and a cloud service using the MQTT protocol.  


3.) The relay will turn off for a specified timeout  period when the parameter value falls below the minimum threshold level.
[[File:GRD44B 5R MQTT.png|1024x1024px]]Specification details are given below:


4.) The relay will turn off immediately without any  timeout when the parameter value falls below the minimum threshold level.
{| class="wikitable"
 
5.) The relay will alternate between on and off  states when the parameter value stays below the minimum threshold level.
|}
 
= 7. Appmanager =
'''Appmanager''' is a system utility that manages the installation, configuration, and execution of software applications on a device.
 
This section is divided into 8 categories,
 
* Application Start/Stop
* Application Software Upgrade
* ADC Utility Configuration
* Modbus Utility Configuration
* Import/Export Application Configurations
* App Health Status
* RS232 Utility Configuration
* IO Utilities
 
[[File:App Manager.png|frameless|620x620px]]
 
== 7.1 Application Start/Stop ==
All changes made in ‘'''Configuration’''' section should be saved into backend and to do that navigate to Appmanager>> Application Start/Stop.
 
Click on update to save all the changes made in configuration section.
 
Once updated click on start.
 
[[File:Application Start-Stop Configuration.png|frameless|620x620px]]
 
Make sure application is started to send data to cloud, once started it can be seen start option is replaced by Stop as shown above.
 
=== 7.2 Application Software Upgrade ===
In this section you can upgrade software manually or automatically.
 
For auto upgrade, enable auto upgrade tab,
 
This is further divided into 2 sections,
 
Client and server settings
 
Auto Upgrade Interval
 
[[File:Application Software Upgrade.png|frameless|620x620px]]
 
 
Specification details are given below:
{| class="wikitable"
| colspan="4" |Client and Server Settings
|-
|SN
|SN
|Field  Name
|Field  Name
Line 4,764: Line 4,687:
|-
|-
|1
|1
|Authentication
|Site ID
|Enable/Disable
|Example:  ‘Site123’ or ‘Device456’.
|Enable if username/password is required.
|A unique identifier for your site or device within the cloud service.
|-
|-
|2
|2
|Username
|Cloud / Protocol
|XXXX
|MQTT
|The username required to authenticate with the server.
|The protocol used for communication with the cloud service.
|-
|-
|3
|3
|Password
|MQTT Host
|XXXX
|'''Example:''' broker.hivemq.com
|The password required to authenticate with the server.
|The MQTT broker's address (hostname or IP address) that the device will connect to for  sending and receiving messages.
|-
|-
|4
|4
|Server  address
|MQTT Port
|<nowiki>ftp://XXXX</nowiki>
|'''Example:''' 1883
|The URL or IP address of the server where the upgrade files are located.
|This is the default port for unencrypted MQTT connections.
|-
|-
|5
|5
|Connection  timeout
|Authentication Mode
|Ex: 180
|1.) No Authentication
|The maximum time (in seconds) the system will wait to establish a connection with the  server before timing out.
 
2.) Username/Password
 
3.) TLS
|1.) Connect  to the broker without any credentials.
 
2.) The  Username/Password for authentication with the cloud service.
 
3.) Upload  TLS certificates only if TLS authentication is selected as shown in the above image.
|-
|-
|6
|6
|Operation  timeout
|Enable Publish Over LAN
|Ex: 240
|Enable/Disable
|The maximum time (in seconds) the system will wait for the upgrade operation to complete  before timing out.
|When enabled, the device will also publish MQTT messages over the local area network (LAN).
|-
|-
| colspan="4" |'''Auto Upgrade Interval'''
|7
|RS485 Topic (Optional)
|'''Example:''' RS485Data1
|The MQTT  topic for publishing RS485 data.
|-
|-
|SN
|8
|Field  Name
|Command Request Topic (Optional)
|Sample  Value
|'''Example:''' CommandRequest1
|Description
|The topic to  which the device listens for command requests. Leave it blank if not in use.
|-
|-
|1
|9
|Minutes
|Command Response Topic (Optional)
|Example: 56
|'''Example:''' CommandResponse1
|Set the minute part of the interval when the auto-upgrade check will occur
|The topic on which the device publishes responses to commands. Leave it blank if not in use.
|-
|2
|Day Of Month
|Example: all
|Specifies the  days of the month when the auto-upgrade check should occur.
|-
|3
|Month
|Example: all
|Specifies the months during which the auto-upgrade check should occur
|-
|4
|Day Of Week
|Example: all
|Specifies the  days of the week when the auto-upgrade check should occur.
|}
|}
You can also check the current software version and manually upgrade software as shown below.
Click on save once configuration changes have been made.


To Manually upgrade Application,


Enter the correct ‘Checksum’ and ‘Size’ and upgrade the page.


'''(Please stop the applications before upgrading)'''
'''Azure:'''


[[File:Manual Upgrade Application.png|frameless|620x620px]]
This configuration sets up the connection to Azure IoT Hub using either MQTT or HTTP protocols with a specified connection string.


=== 7.3 ADC Utility Configuration ===
[[File:GRD44B 5R Azure.png|1024x1024px]]Specification details are given below:
The following settings allow you to configure how the Analog-to-Digital Converter (ADC) operates, including how frequently it samples data, the mode of conversion, how many samples to take, and the specific address for communication.
 
[[File:ADC Utility Configuration.png|frameless|620x620px]]  
 
 
'''Specification details are given below:'''
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 4,844: Line 4,755:
|-
|-
|1
|1
|Sampling Rate
|Site ID
|Example: 1
|Example: ‘Site123’ or ‘Device456’.
|This value specifies the rate at which the Analog-to-Digital Converter (ADC) samples the input signal.
|A unique identifier for your site or device within the cloud service.
|-
|-
|2
|2
|Conversion Mode
|Cloud / Protocol
|1.) 0-Continuous
|Azure
 
|The cloud  service and protocol used for communication.
2.) 1-single shot
|-
|1.) In continuous mode, the ADC continuously converts the input signal at the  defined sampling rate.
|3
 
|Protocol
2.) In single-shot mode, the ADC performs a single conversion of the input signal when triggered, and then it stops.
|1.) MQTT
|-
 
|3
2.) HTTP
|No Of Samples
|1.) A  lightweight messaging protocol suitable for IoT devices.
|Example: 20
 
|This  specifies the number of samples the ADC will take. In single-shot mode, this might indicate the total samples to be taken in a session, while in continuous mode, it could refer to a batch size for processing or averaging.
2.) A  protocol used for communication over the web, commonly used for RESTful  services.
|-
|-
|4
|4
|Address
|Connection String
|0x49
|e.g., invendis-iot-hub.azure-devices.net.
|The address  is used to communicate with the specific ADC chip in systems that support multiple devices.
|The primary  or secondary key used to authenticate the device with the IoT Hub.
|}
|}
Click on save once configuration changes have been made.
Click on save once configuration changes have been made.
 
 
=== 7.4 Modbus Utility Configuration ===
=== 6.5 Modbus Configuration ===
Any changes to be made in Modbus Configuration to test can be made in Modbus Utility Configuration without disturbing the actual Modbus Configuration.
Modbus Configuration involves setting up communication parameters for Modbus devices, including baud rate, parity, stop bits, data bits, TCP/RTU settings, and timeout/retry settings for reliable data exchange.
 
 
The working process of ‘Modbus Configuration’ and ‘Modbus Utility Configuration’ are same.
Click on “Add Device” to start a new configuration.
 
 
Refer (6.5 Modbus Configuration) for specification details.
This Configuration has 4 sections,
 
 
[[File:Modbus Utility Configuration.png|frameless|620x620px]]
1.) Parameter Configuration
 
 
Click on save once configuration changes have been made.
2.) Block Config
 
 
=== 7.5 Import / Export Gateway Configuration ===
3.) Register Config
This functionality ensures that you can easily manage, back up, and restore device gateway
 
 
4.) Alarm/Event Config
configurations, as well as reset the device to default settings when needed.
 
 
[[File:GRD44B 5R Modbus config.png|1024x1024px]]
[[File:Import - Export Gateway Configuration.png|frameless|620x620px]]
 
 
'''Parameter Configuration:'''
 
 
'''Export Config:'''
As shown in the image below, there are two types of protocol used in Modbus configuration.
 
 
'''Usage:''' Click the "Export Config" button to save the current configuration to a file.
1.) RTU (Remote Terminal Unit)
 
 
 
2.) TCP (Transmission Control Protocol)
'''Import Config:'''
 
 
Details of both protocols is mentioned in the specification table.
'''Usage:''' Click the "Import Config" button and select the text file containing the configuration you want to import.
 
 
 
 
 
'''Reset Config''':
'''Modbus Protocol: RTU'''
 
 
'''Usage''': Click the "Reset Config" button to revert the device to its default configuration settings.
[[File:GRD44B 5R Parameter config.png|1024x1024px]]
 
 
=== 7.6 App Health Status ===
Specification details are given below:
This section provides utilities to check the health and status of various applications and data inputs
{| class="wikitable"
 
|
within the system. It allows monitoring of the last data produced and sent times for different utilities, as
|
 
|'''Modbus protocol: RTU'''
well as the running status of applications.
|
 
|-
[[File:App Health Status.png|frameless|620x620px]]
|1
 
|DEVICE NAME
 
|Ex: Invendis
Specification details are given below:
|This is the  name assigned to the Modbus device for identification purposes.
{| class="wikitable"
|-
|SN
|2
|Field  Name
|Baud rate
|Sample  Value
|<nowiki>300 | 1200 | 1800 | 2400 | 4800 | 19200 |  38400 | default: 9600</nowiki>
|Description
|The baud rate determines the communication  speed between devices, measured in bits per second.
|-
|-
|1
|3
|Energymeter  Last Data Produced Time
|Parity
|1.) NONE
 
2.) ODD
 
3.) EVEN
|1.) No parity  bit is added to the data byte.
 
2.) Ensures  that the total number of 1-bits in
 
the data byte  plus the parity bit is even.
 
3.) Ensures  that the total number of 1-bits in the data byte plus the parity bit is odd.
|-
|4
|Meter ID
|1
|The Meter ID  is a unique identifier for the specific meter within the network. Each Modbus  device on the network must have a unique ID to differentiate it from others.
|-
|5
|Meter Model
|Example: abcd
|This field  specifies the model of the meter.
|-
|6
|Port number
|RS485 Port-1
|This  specifies which RS485 port on the device is being used for communication.
|-
|7
|Slave Address
|Example: '''1'''
|The slave  address identifies the specific slave device on the Modbus network. Each  slave must have a unique address so that the master can communicate with it  individually.
|-
|8
|No. of Databits
|7/8
|Indicates that 8 data bits are used per byte, which is a common setting.
|-
|9
|No. of Stopbits
|1/2
|Configures  the serial communication to use 1 stop bit, which is a common setting  ensuring the end of each byte is clearly marked.
|}
 
'''Modbus Protocol: TCP'''
 
[[File:GRD44B 5R Parameter config 1.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|
|
|'''Modbus protocol: TCP'''
|
|-
|1
|DEVICE NAME
|Ex: Invendis
|This is the  name assigned to the Modbus device for identification purposes.
|-
|2
|Modbus Comm IP
|Ex: 192.168.10.147
|IP of the device you  are communicating with.
|-
|3
|Modbus Comm Port
|Ex: 502 (default)
 
|Give a specified TCP port number
|-
|4
|Modbus Comm Timeout
|Ex: 60
|This refers  to the maximum amount of time the master device will wait for a response from a slave device before it assumes a communication failure.
|-
|5
|Meter ID
|1
|The Meter ID  is a unique identifier for the specific meter within the network. Each Modbus  device on the network must have a unique ID to differentiate it from others.
|-
|6
|Meter Model
|Example: abcd
|This field  specifies the model of the meter.
|-
|7
|Slave Address
|Example: '''1'''
|The slave  address identifies the specific slave device on the Modbus network. Each  slave must have a unique address so that the master can communicate with it  individually.
|}
 
 
 
'''Block Config:'''
 
[[File:GRD44B 5R Block config.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Funtion Code
|read coils (1)
 
read input coils (2)
 
read holding registers (3)
 
read  input registers (4)
|The function code indicates the operation to be performed. In Modbus, each operation has a  specific function code.
|-
|2
|Start  Register
|Example: 0
|The start  register indicates the address of the first register to be read in the slave  device.
|-
|3
|Register  Count
|Example: 10
|This  specifies the number of consecutive registers to read starting from the start  register.
|}
Click on “Add Block” below to add another set of parameters.
 
 
 
'''Register Config:'''
 
In this section you can add multiple parameters to read in ‘Default Mapping’ & ‘Custom Mapping’ field.
 
 
 
''*Refer the image below*''
 
[[File:GRD44B 5R Register config.png|1024x1024px]]
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Default  mapping
|1.) Tag Name = (Ex: FQ)
 
2.) Data type  = Hexadecimal; Floating point | Floating point (Swapped Byte) | 16bit INT,  high byte first | 16bit INT, low byte first | 16bit UINT, high byte first |  16bit UINT, low byte first | 32bit UINT (byte order 1,2,3,4) | 32bit UINT  (byte order 4,3,2,1) | 32bit INT (byte order 1,2,3,4) | 32bit INT (byte order  4,3,2,1)
|1.) Input value name.
 
2.) Defines  how read data will be stored.
|-
|2
|Custom mapping
|1.)  Register name:
 
2.)  Start register:
 
3.)  Register count:
 
4.) Data type = Hexadecimal;  Floating point | Floating point (Swapped Byte) | 16bit INT, high byte first |  16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low  byte first | 32bit UINT (byte order 1,2,3,4) | 32bit UINT (byte order 4,3,2,1)  | 32bit INT (byte order 1,2,3,4) | 32bit INT (byte order 4,3,2,1); 1 bit
|1.)  Input value name.
 
2.)  First register in custom register block.
 
3.) Path  to file in which the custom register block will be stored.
 
4.) Defines how read data will be  stored.
|}
 
 
 
In Register Config,
 
Click on ‘Add’ to add new parameters.
 
Click on ‘Show JSON’ to view an example value of how the data will be presented.
 
Click on ‘Add Device’ once configuration changes have been made.
 
'''Alarm/Event Config:'''
 
[[File:GRD44B 5R Alarm-event config.png|1024x1024px]]Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Category
|1.) Alarm
 
2.) Event
|'''Alarm''':  Specifies that the configuration is for an alarm, which typically triggers  when certain conditions are met.
 
'''Event''': Specifies that the configuration is for an event, which might log information  or trigger actions without necessarily being an alarm.
|-
|2
|Status
|1.) Enabled
 
2.) Disabled
|'''Enabled''':  Activates the alarm or event, making it operational.
 
'''Disabled''': Deactivates the alarm or event, making it non-operational.
|-
|3
|Name
|Ex: vtg
|The name or  identifier for the alarm/event.
|-
|4
|Function code
|read coils (1)
 
read input coils (2)
 
read holding registers (3)
 
read  input registers (4)
|These  function codes are typically based on the Modbus protocol, indicating what  type of data is being monitored.
|-
|5
|Start Register
|Ex: 0
|The address  of the first register to monitor.
|-
|6
|No_of Reg
|Ex: 10
|The number of  consecutive registers to monitor from the starting register.
|-
|7
|Data Type
|<nowiki>Hexadecimal; Floating point | Floating point (Swapped  Byte) | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT,  high byte first | 16bit UINT, low byte first | 32bit UINT (byte order 1,2,3,4)  | 32bit UINT (byte order 4,3,2,1) | 32bit INT (byte order 1,2,3,4) | 32bit  INT (byte order 4,3,2,1); Boolean</nowiki>
|Provides  options for the type of data being monitored, such as integer, float,  Boolean, etc.
|-
|8
|Upper Thresh/
 
Alarm Value
|Ex: 2
|The value at  which the alarm is triggered if the monitored parameter exceeds this upper  threshold.
|-
|9
|Upper Hys
|Ex: 2
|This value is  subtracted from the upper threshold to set the point at which the alarm  resets, preventing rapid toggling.
|-
|10
|Lower Thresh
|Ex: 2
|The value at  which the alarm is triggered if the monitored parameter falls below this  lower threshold.
|-
|11
|Lower Hys
|Ex: 1
|This value is added to the lower threshold to set the point at which the alarm resets, preventing rapid toggling.
|}
Click on “Add Alarm” to add another Alarm/Event.
 
Click on ‘Show JSON’ to view an example value of how the data will be presented.
 
Click on ‘Add Device’ once configuration changes have been made.
 
== 7. Appmanager ==
'''Appmanager''' is a system utility that manages the installation, configuration, and execution of software applications on a device.
 
This section is divided into 6 categories,
 
* Application Start/Stop
* Application Software Upgrade
* Modbus Utility Configuration
* Import/Export Application Configurations
* App Health Status
* IO Utilities
 
[[File:GRD44B 5R Appmanager.png|1024x1024px]]
=== 7.1 Application Start/Stop ===
All changes made in ‘'''Configuration’''' section should be saved into backend and to do that navigate to Appmanager >> Application Start/Stop.
 
Click on update to save all the changes made in configuration section.
 
Once updated click on start.
 
[[File:GRD44B 5R App start-stop.png|1024x1024px]]
 
Make sure application is started to send data to cloud, once started it can be seen start option is replaced by Stop as shown above.
 
=== 7.2 Application Software Upgrade ===
In this section you can upgrade software manually or automatically.
 
For auto upgrade, enable auto upgrade tab,
 
This is further divided into 2 sections,
 
'''Client and server settings'''
 
'''Auto Upgrade Interval'''
 
[[File:GRD44B 5R Software upgrade.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
| colspan="4" |'''Client  and server settings'''
|-
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Authentication
|Enable/Disable
|Enable if  username/password is required.
|-
|2
|Username
|XXXX
|The username  required to authenticate with the server.
|-
|3
|Password
|XXXX
|The password  required to authenticate with the server.
|-
|4
|Server  address
|<nowiki>ftp://XXXX</nowiki>
|The URL or IP  address of the server where the upgrade files are located.
|-
|5
|Connection  timeout
|Ex: 180
|The maximum  time (in seconds) the system will wait to establish a connection with the  server before timing out.
|-
|6
|Operation  timeout
|Ex: 240
|The maximum  time (in seconds) the system will wait for the upgrade operation to complete before  timing out.
|-
| colspan="4" |'''Auto Upgrade Interval'''
|-
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Minutes
|Example: 56
|Set the  minute part of the interval when the auto-upgrade check will occur
|-
|2
|Day Of Month
|Example: all
|Specifies the  days of the month when the auto-upgrade check should occur.
|-
|3
|Month
|Example: all
|Specifies the  months during which the auto-upgrade check should occur
|-
|4
|Day Of Week
|Example: all
|Specifies the  days of the week when the auto-upgrade check should occur.
|}
You can also check the current software version and manually upgrade software as shown below.
 
 
 
To Manually upgrade Application,
 
Enter the correct ‘Checksum’ and ‘Size’ and upgrade the page.
 
'''(Please stop the applications before upgrading)'''
 
[[File:GRD44B 5R Software upgrade 1.png|1024x1024px]]
 
=== 7.3 Modbus Utility Configuration ===
Any changes to be made in Modbus Configuration to test can be made in Modbus Utility Configuration without disturbing the actual Modbus Configuration.
 
The working process of ‘Modbus Configuration’ and ‘Modbus Utility Configuration’ are same.
 
Refer (6.5 Modbus Configuration) for specification details.
 
[[File:GRD44B 5R Modbus utility config.png|1024x1024px]]Click on save once configuration changes have been made.
 
=== 7.4 Import / Export Gateway Configuration ===
This functionality ensures that you can easily manage, back up, and restore device gateway
 
configurations, as well as reset the device to default settings when needed.  
 
[[File:GRD44B 5R Gateway import-export.png|1024x1024px]]
 
'''Export Config:'''
 
'''Usage:''' Click the "Export Config" button to save the current configuration to a file.
 
 
 
'''Import Config:'''
 
'''Usage:''' Click the "Import Config" button and select the text file containing the configuration you want to import.
 
 
 
'''Reset Config''':
 
'''Usage''': Click the "Reset Config" button to revert the device to its default configuration settings.
 
=== 7.5 App Health Status ===
This section provides utilities to check the health and status of various applications and data inputs
 
within the system. It allows monitoring of the last data produced and sent times for different utilities, as
 
well as the running status of applications.  
 
''*Refer the image below*''
 
[[File:GRD44B 5R App health status.png|1024x1024px]]Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Energymeter  Last Data Produced Time
|Command  ‘Read’
|Command  ‘Read’
|Displays the  last time data was produced by the energymeter.
|Displays the  last time data was produced by the energymeter.
Line 4,930: Line 5,274:
|-
|-
|3
|3
|AI (Analog Input) Last Data Produced Time
|Energymeter Last Data Sent Time
|Command  ‘Read’
|Command  ‘Read’
|Displays the  last time data was produced by the analog input system.
|Displays the  last time data from the energymeter was sent.
|-
|-
|4
|4
|RS232 Last Data Produced Time
|App Running Status
|Command  ‘Read’
|Command  ‘Read’
|Displays the  last time data was produced by the RS232 interface.
|Displays the  current running status of applications.
|-
|-
|5
|5
|Energymeter Last Data Sent Time
|Download Files
|Command  ‘Read’
|Command  ‘Download’
|Displays the  last time data from the energymeter was sent.
|Choose the  desired option from the dropdown menu.
 
Download data or logs related to the options available.
|-
|-
|6
|6
|DIO Last Data  Sent Time
|Output
|Command  ‘Read’
|Display Value
|Displays the last time data from the digital input/output system was sent.
|Provides output or feedback based on selected utilities.
|-
|}
|7
 
|AI Last Data  Sent Time
 
|Command  ‘Read’
 
|Displays the  last time data from the analog input system was sent.
=== 7.6 IO Utilities ===
|-
This section provides output of various utilities connected to the device.
|8
 
|RS232 Last  Data Sent Time
This section exactly shows whether the connection made is successful or not.
|Command  ‘Read’
|Displays the  last time data from the RS232 interface was sent.
|-
|9
|App Running  Status
|Command  ‘Read’
|Displays the  current running status of applications.
|-
|10
|Download  Files
|Command  ‘Download’
|Choose the  desired option from the dropdown menu.


Download data  or logs related to the options available.
|-
|11
|Output
|Display Value
|Provides  output or feedback based on selected utilities.
|}


=== 7.7 RS232 Utility Configuration ===
Any changes to be made in RS232 Configuration to test can be made in RS232 Utility Configuration without disturbing the actual RS232 Configuration.


The working process of ‘RS232 Configuration’ and ‘RS232 Utility Configuration’ are same.
''*Refer the image below*''


Refer (6.7 RS232 Configuration) for specification details.
[[File:GRD44B 5R IO Utilities.png|1024x1024px]]Specification details are given below:
 
[[File:RS232 Utility Configuration.png|frameless|620x620px]]
 
Click on save once configuration changes have been made.
 
=== 7.8 IO Utilities ===
This section provides output of various utilities connected to the device.
 
This section exactly shows whether the connection made is successful or not.
 
[[File:IO Utilities.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 5,003: Line 5,315:
|-
|-
|1
|1
|RS485 EnergyMeter
|Modbus Utility
|'''Input''':  Slave ID
|'''Input''':  Slave ID
|'''Action''':  Manage RS485 energy meters by specifying the slave ID.
|'''Action''':  Manage RS485 energy meters by specifying the slave ID. (Read/Write)
|-
|-
|2
|2
|RS232 Device
|'''Input''':  Slave ID
|'''Action''':  Manage RS232 devices by specifying the slave ID.
|-
|3
|Analog Input  (AIO)
|'''Input''':  Select from 1, 2 (default: 2)
|'''Action''':  Manage analog input settings.
|-
|4
|Digital Input  (DIO)
|'''Input''':  Select from 1, 2, 3, 4
|'''Action''':  Manage digital input settings.
|-
|5
|Digital  Output (DO)
|'''Input''':  Select from 1, 2, 3, 4 and specify the value (0 or 1)
|'''Action''':  Manage digital output settings.
|-
|6
|Copy Database  to USB
|1.) Database/File
2.)  Energymeter RS485
3.) DIO
4.) AIO
5.) Energymeter  RS232
|'''Action''':  Copy the selected database/file to a USB device.
|-
|7
|Output
|Output
|Print any  values
|Print any  values
Line 5,046: Line 5,325:
|}
|}


= 8.Logout =
== 8.Logout ==
The user should click on log out option to logged out from the router application.
The user should click on log out option to logged out from the router application.


[[File:Logout.png|frameless|620x620px]]
[[File:GRD44_3_Logout.png|1024x1024px]]

Latest revision as of 10:58, 7 January 2025


Connecting with the device to the System (Laptop/Desktop)       

To log in to SILBO_GRD44B-5R by connecting the router to your laptop or desktop via LAN or using Wi-Fi, please follow the steps below.

Connecting via LAN:

Connect your laptop's LAN port to one of the router's LAN interfaces. Ensure that you select any LAN interface (there are 4 available) while making sure the WAN interface is not used.

                                                                                                                                     

How to connect with the SILBO_ GRD44B-5R application

Once the LAN connection is established between the device and the laptop or the desktop

Please open the command prompt and ping to get the IP config of that device.

Type the command Ipconfig

It will provide the Ip address/url of that device through which the application can be accessed.

Log In

Open the web browser and type the IP address in the URL.

It will show the log in page of the application.

Give the valid credentials for the username and password to login to the application page.

Once the user credentials are provided it will direct to the landing page of the application.

       

The “Status” landing page shows all the detailed specification of the device like system, memory storage and connection tracking etc.

The application is divided in to 8 Modules.

  • Info
  • Settings
  • Maintenance
  • Status
  • Features
  • Configuration
  • Appmanager
  • Logout

1. Info

The “Info” module provides the information about the devices to the user.

It provides all the specification related to the hardware, firmware, Networks and the Connection uptimes.

It has 3 submodules.

  • Overview
  • System Log
  • Kernel Log

1.1 Overview

In overview module it displays all the specification categorically of a device like System, Memory, storage, Connection tracking, DHCP Lease.

System:

In this section it displays the hardware configured specification of the device.

The specifications details are as follows,

SN Field name Sample value Description
1 Hostname 45A27240005 This field displays the router serial number of the device
2 Model Silbo_GRD44B-5R_GW-EC200A This field displays the model number of the device
3 Firmware Version and IPK Version 1.17_1.15 This field displays the firmware version and IPK version
4 Application Firmware version and IPK version 1.03_1.13 This field displays the software version of the device.
5 Kernel Version 4.14.180 This field displays the kernel version of the device
6 Local Time Wednesday, December 18, 2024 at 12:56:00 PM This field displays the local time
7 Uptime 5h 27m 5s This field displays the uptime of the device
8 Load Average 0.31 0.27 0.19 This field displays the average load

Memory:

In this section it displays the memory configured specification of the device.

The specifications details are as follows.

SN Field name Sample value Description
1 Total Available 57716 kB / 124188 kB (46%) This field displays the total availability of memory space in the device
2 Free 46424 kB / 124188 kB (37%) This field displays the Free memory space in the device
3 Cached 444 kB / 124188 kB (0%) This field displays the Cached memory space in the device
4 Buffered 11224 kB / 124188 kB (9%) This field displays the Buffered memory space in the device


Storage:

In this section it displays the status of storage as root and temporary usage specification of the device.


The specifications details are as follows.

SN Field name Sample value Description
1 Root Usage 1580 kB / 12800 kB (12%) This field displays the total root usage of the device
2 Temporary Usage 444 kB / 62092 kB (0%) This field displays the total temporary usage of the device

Network:

In this section you can monitor IPv4 WAN status.

The specifications details are as follows.

SN Field Name Sample value Description
1 Type DHCP client A DHCP client is a device or software that requests and receives configuration information from a DHCP server, such as an IP address, gateway, and DNS servers.
2 Connected 1h 49m 8s This indicates the duration for which the device has been connected to the network.
3 Address 10.62.35.111 This is the IP address assigned to the DHCP client by the DHCP server. It uniquely identifies the device on the network.
4 Gateway 10.62.35.144 The gateway (or default gateway) is the IP address of the network device that routes traffic from the local network to other networks.
5 DNS 8.8.8.8, 10.103.81.232 The first DNS server "8.8.8.8" is a public DNS server provided by Google.

The second DNS server "10.103.81.232" is a private DNS server.

Active SIM Information:

This section displays SIM details only when the SIM card is active.

Connection Tracking:

In this section it displays the status of connection tracking for the device.

The specifications details are as follows.

SN Field Value Sample Value Description
1 Active Connections 48/16384 (0%) This field displays the active connection of the device.

DHCP Leases:

In this section it displays the DHCP lease of the temporary assignment of an IP address to a device on the network.

The specifications details are below.

SN Field name Sample value Description
1 Host Name KermaniK-LT This field displays the configured Host Name/Username for that device.
2 IPv4-Address 192.168.10.147 This field displays the IP address of the device.
3 MAC-Address 34:73:5a:bb: ab:7a This field displays the MAC-Address of the device.
4 Lease time remaining 11h 53m 49s This field displays the lease time remaining for the device.

1.2 System Log

This page provides on screen System logging information. In this page the user gets to view the system logs.

1.3 Kernel Log

This page provides on screen Kernel logging information.

In this page the user gets to view the Kernel logs.


2. Setting

In this “Setting” module the user can Configure/update all the required parameters related to Network, SIM Switch, Internet, VPN, Firewall, Loopback Rule, Remote monitoring, Tunnel as per requirement.

IT consist of 8 submodules.

  • Network
  • VLAN
  • Sim Switch
  • Multi-WAN
  • VPN
  • Firewall
  • Loopback Rule
  • VRRP
  • Remote Monitoring
  • Tunnel

2.1 Network

In this section the user does all the setting related configuration with reference to network like Ethernet Setting, Cellular Setting, Band lock and Operator Lock, Wi-Fi, Guest Wi-Fi, Wireless Schedule, SMS Setting, Loopback IP.

Ethernet Setting:

In this page it will display all the configured port that is attached with the device.

For this device 5 ports are configured.

Ethernet mode can be configured as WAN and as LAN as well.

Ethernet WAN Connection settings can be configured as DHCP, Static and PPOE.

EDIT:

To add a new Interface, click on ‘Add’.

To edit the existing device the user needs to click on the edit option.

Once the changes are done click on the update button to save all the changes.

Click on the deleted button to delete the existing device detail.

Specification details are given below:  Type: WAN

SN Field Name Sample Value Description
1 Physical Device Ex: eth0.5 This indicates a network interface on which our network is connected. This setting is by default (Editable).
2 Type WAN/LAN This designates whether the interface is part of the WAN or LAN.

WAN: Connects the device to the internet.

LAN: Connects the device to the internal network.

                                                                    Protocol: Static
3 Static IP Address Ex: 192.168.1.10 The manually assigned IP address for the interface.
4 Static Netmask Ex: 255.255.255.0 Subnet mask corresponding to the IP address.
5 Static Gateway Ex: 192.168.1.1 The IP address of the gateway (router) that the interface will use to send traffic outside its own subnet.
                                                                    Protocol: DHCP
6 DHCP Gateway Ex: 10.1.1.1 The IP address of the DHCP server (often the same as the router or gateway).
                                                                    Protocol: PPPoE
7 Username Any Name The username provided by your ISP for PPPoE authentication.
8 Password ***** The password provided by your ISP for PPPoE authentication.
9 Access Concentrator Typically, the name of the ISP's PPPoE server.
10 Service Name Sometimes required by ISPs, this field specifies a particular service offered by the ISP.
11 Gateway Ex: 0.0.0.0 The IP address used as the default route.
12 MAC Address Ex: D0:93:95:B0:98:6B The hardware (MAC) address of the network interface. This is unique to every network device.
13 Override MAC Address Ex: D0:93:95:B0:98:6B This field allows you to manually set a different MAC address if needed.

If left blank, the default MAC address is used.

14 Create Firewall Zone Enable/Disable You can assign this interface to a particular firewall zone, which determines its access rules (e.g., WAN zone for internet traffic, LAN zone for internal traffic).
Advanced Settings: Enable/Disable
15 Broadcast Ex: 192.168.123.34 Broadcast address for the network, typically calculated based on the IP and subnet mask.
16 Override MTU Ex: 1500 MTU size controls the maximum packet size that can be sent over the network.

Default is usually 1500 bytes.

17 Delegate Enable/Disable If checked, it allows delegation of prefixes for IPv6, often left unchecked unless needed.
18 Force Link Enable/Disable Forces the interface to be up even if no physical link is detected.
19 IPv4 Route Table Enable/Disable This field is used to specify static routes for IPv4.
20 Table No. 254: Default main routing table.

100: Custom routing table for specific purposes.

Default Table (Main Table): Usually, there is a default routing table (often Table No. 254 or 255) where all the routes are stored by default.

Custom Table: You can specify a different table number if you are managing multiple routing policies (e.g., VoIP traffic, VPN traffic).


Type: LAN


Specification details are given below:

SN Field Name Sample Value Description
1 Physical Device Ex: eth0.1 This is the network interface identifier.
2 Type WAN/LAN This designates whether the interface is part of the WAN or LAN.

WAN: Connects the device to the internet.

LAN: Connects the device to the internal network.

3 Protocol Static This means that the IP address, netmask, and other network settings are manually configured rather than being automatically assigned by a DHCP server.
4 IP Address Ex: 192.168.10.1 This is the static IP address assigned to the interface. It acts as the gateway IP address for devices connected to this LAN.
5 Static Netmask Ex: 255.255.255.0 This is the subnet mask for the network.
6 MAC Address Ex: D0:93:95:B0:98:6C This is the hardware (MAC) address of the network interface, which uniquely identifies this device on the network.
7 Override MAC Address This allows you to manually enter a different MAC address if needed.
8 Enable DNS Enable/Disable If this option is enabled, the interface will act as a DNS resolver for the devices on the LAN, using the specified DNS server.
9 DNS Server Address Ex: 8.8.8.8 This is the IP address of the DNS server that will be used by devices on the LAN to resolve domain names to IP addresses.

More than one DNS Address can be added.

10 Enable DHCP Server Enable/Disable If enabled, this setting allows the interface to function as a DHCP server, automatically assigning IP addresses to devices connected to the LAN.
11 DHCP Start Address 70 The DHCP server will begin assigning IP addresses starting from 192.168.10.70
12 DHCP Limit 100 This specifies the number of IP addresses the DHCP server can assign. Starting at 192.168.10.70 and with a limit of 100, the server can assign addresses up to 192.168.10.169.
13 Lease Time Duration Hours-(H)

Minutes-(M)

Seconds-(S)

Hours-(H): This indicates that the lease time for each IP address assignment is measured in hours.

Minutes-(M): This indicates that the lease time for each IP address assignment is measured in minutes.

Seconds-(S): This indicates that the lease time for each IP address assignment is measured in seconds.

14 Lease Time 12 The DHCP lease time is set to 12 hours. After this period, a device must renew its IP address lease with the DHCP server to continue using the assigned IP address.
15 Create Firewall Zone Enable/Disable You can assign this interface to a particular firewall zone, which determines its access rules (e.g., WAN zone for internet traffic, LAN zone for internal traffic).
16 Internet Over SW_LAN Enable/Disable Allow all outbound traffic from the LAN to the internet.
Advanced Settings: Enable/Disable
17 Broadcast Ex: 192.168.123.34 Broadcast address for the network, typically calculated based on the IP and subnet mask.
18 Override MTU Ex: 1500 MTU size controls the maximum packet size that can be sent over the network.

Default is usually 1500 bytes.

19 Delegate Enable/Disable If checked, it allows delegation of prefixes for IPv6, often left unchecked unless needed.
20 Force Link Enable/Disable Forces the interface to be up even if no physical link is detected.
21 IPv4 Route Table Enable/Disable This field is used to specify static routes for IPv4.

Save and Update once configuration changes have been made.

Relay Server:

A relay server typically functions in a network to forward requests (usually DHCP or DNS) from clients to

a designated server when the server is on a different network segment.


EDIT:

To edit the existing device the user needs to click on the edit option.

Once the changes are done click on the save button to save all the changes.

Click on the deleted button to delete the existing device detail.


Specification details are given below:

SN Field Name Sample Value Description
1 Interface 1.)   eth0.1

2.)   ra0

1) eth0.1 typically represents a VLAN where the relay will listen for client requests.

2) If your device is broadcasting a Wi-Fi network on the ra0 interface, any DHCP or DNS relay settings will apply to devices connected via this wireless interface.

2 Start IP Address Ex: 192.168.10.100 This is the beginning IP address of the range that will be leased out to clients.
3 End IP Address Ex: 192.168.10.150 An IP address that is in the same subnet as the Start IP Address and allows sufficient addresses to be leased.
4 Netmask Ex: 255.255.255.0 A valid subnet mask such as 255.255.255.0 (for a /24 network), or 255.255.0.0 (for a /16 network).
5 Lease Time For a 24-hour lease time, set this value to 86400. This is the amount of time that an IP address is assigned to a client before it needs to request a renewal from the DHCP server.

Save and update.


Cellular Setting:

In this page, the user needs to configure the various details with respect to the SIM.

Select single cellular single sim where the user must configure the APN details of the sim used for the router device. The Configurations can be done based on the SIM usage, with respect to IPV4 or IPV6.

Specification details are given below:

SN Field name Sample value Description
1 Cellular Enable Checkbox Check this box to enable cellular functionality.
2 Cellular Operation Mode 1.) Single Cellular with Dual Sim

2.) Single Cellular with Single SIM

1.) This mode allows you to use one cellular modem with two SIM cards.

2.) This mode allows you to use one cellular modem with single SIM card.

3 Cellular Modem 1 QuectelEC200A This field displays the modem name.
4 Choose SIM 1 APN Mode 1.) Auto

2.) Manual

1.) Choose Auto for regular SIM to detect APN name automatically.

2.) Choose manual to enter the APN settings manually in case of M2M SIM cards.

5 SIM 1 Access Point Name airtelgprs.com Enter the APN provided by your cellular service provider in case of M2M sim. For regular sim cards APN name will be displayed automatically.
6 SIM 1 PDP Type IPV4 Choose the PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
7 SIM 1 Username Enter the username if required by the APN. Leave blank if not required.
8 SIM 1 Password Enter the password if required by the APN. Leave blank if not required.
9 SIM 1 Authentication Protocol None Choose the authentication protocol. Options typically include None, PAP, or CHAP.
10 SIM 1 MTU Ex: 1500 (a common MTU size) MTU (Maximum Transmission Unit) defines the largest size of a data packet that can be transmitted over the network.
11 Choose SIM 2 APN Mode 1.) Auto

2.) Manual

1.) Choose Auto for regular SIM to detect APN name automatically.

2.) Choose manual to enter the APN settings manually in case of M2M SIM cards.

12 SIM 2 Access Point Name airtelgprs.com Enter the APN provided by your cellular service provider in case of M2M sim. For regular sim cards APN name will be displayed automatically.
13 SIM 2 PDP Type IPV4 Choose the PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
14 SIM 2 Username Enter the username if required by the APN. Leave blank if not required.
15 SIM 2 Password Enter the password if required by the APN. Leave blank if not required.
16 SIM 2 Authentication Protocol None Choose the authentication protocol. Options typically include None, PAP, or CHAP.
17 SIM 2 MTU Ex: 1500 (a common MTU size) MTU (Maximum Transmission Unit) defines the largest size of a data packet that can be transmitted over the network.
18 Primary SIM Switchback Enable Enable/Disable When enabled, the device will automatically switch back to the primary SIM (SIM 1) after switching to SIM 2, under certain conditions (e.g., SIM 1 regains network availability).
19 Primary SIM Switchback Time (In Minutes) 10 Enter the time in minutes after which the system should switch back to the primary SIM if it becomes available.


After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.


Band lock and Operator Lock:

In this page, the user needs to configure the lock band and operator based on the service provider.

Bands available in the drop-down list.

2G/3G option:

2G/3G: - 3G allows additional features such as mobile internet access, video calls and mobile TV.

While the main function of 2G technology is the transmission of information through voice calls.


*Refer the image below*

The user should select the band check box available for 2g/3g from the given list. Bands available for selection under LTE for the bands available in that area.

Operator Selection Mode:

The user needs to click on the check box of the “operator select enable” to select the operator.

Once the check box is clicked there will be a dropdown list of the operator modes from which the user needs to select the mode. The user needs to select the operator mode from the given dropdown list.


If the user selects the mode “Manual” or “Manual-Automatic” then one more text box will appear where the user must provide the operator code.

After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.


Wi-Fi Setting:

In this, router has the general setting and change country code, channel, radio mode, radio passphrase as per the requirement after clicking on enable Radio button.

The user needs to select the respective radio mode based on its need.

It has 3 radio modes.

Access point

Client only

Access point and client


Access Point mode:

In Access Point mode, a configuration in which a router, allows wireless devices to connect to a wired network by creating a Wi-Fi hotspot.


Client point:

In client mode, the access point connects your wired devices to a wireless network. This mode is suitable when you have a wired device with an Ethernet port and no wireless capability, for example, a smart TV, Media Player, or Game console and you want to connect it to the internet wirelessly, select the Client Mode and give the Radio SSID & client passphrase.


Access point and client point:

Select this option for both type of connection, give both SSID and passphrase.

After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.

The specifications details are below.

SN Field name Sample value Description
1 Radio 0 Protocol IEEE 802.11 b/g/n This section shows the radio protocol which is by default.
2 Country Code INDIA Select the country accordingly.

(INDIA by default)

3 Channel Auto In this dropdown the user should select the proper channel to be used. (Auto by default)
4 TX Power 100 In this text box the user should specify the power.
5 Channel Width 20 MHz In this dropdown the user should select the channel width
6 Radio Mode 1.) Access point

2.) Client only

3.) Access point and client

In this drop down the user should select the mode.

(Access point by default)

7 Radio SSID AP_37A26230014 In this text box the user should specify the SSID number which usually comes with the router.
8 Radio Authentication WPA2 Personal (PSK) In this dropdown the user should select the type of authentication.

(WPA2 Personal (PSK) by default)

9 Radio Encryption AES In this dropdown the user should select the type of encryption required.

(AES by default)

10 Radio Passphrase ********* In this text box the user should specify the password. Password will be given with the router which can be changed later.
11 Radio DHCP server IP 192.168.100.1 In this text box the user should specify the IP address of DHCP server.

(192.168.100.1 will be default which can be changed accordingly)

12 Radio DHCP start address 100 In this text box the user should specify the start address of the DHCP.

(100 value is default)

13 Radio DHCP limit 50 In this text box the user should specify the limit for the DHCP.

(50 value is default)

Click on save once changes have been made.


Guest Wifi:

This option enables a separate Wi-Fi network for guests, isolated from the main network to enhance security and privacy. Guest Wi-Fi allows visitors or temporary users to connect to your network without accessing the main LAN resources.

Wireless Schedule:

Wi-Fi can be automatically withdrawn based on the configuration done in this section.

The user can schedule the Wi-Fi’s accessibility time during a particular period.

Note: This section is turned off by default, tick the box to activate it.

After configuring all the required information, the user should click on save and then click on update to update all the required information.

The user can select more than one “day of the week” for scheduling the Wi-Fi working hours.

SMS Settings:

User needs to enable SMS option in SMS settings page.

This option is to validate the mobile numbers using which controlling commands could be sent to the

router device.

1 to 5 mobile numbers can be authenticated by choosing from “Select Valid SMS user numbers” and

adding the mobile numbers below respectively.

API key is the pass key used in the commands while sending SMS.

Displayed in the below screen is the default API key which can be edited and changed as per choice.

After addition of the mobile number’s user needs to click on save button for changes to take place.

*Refer the image below*


1.) Select valid user number max. 5 and add authorized phone number in the tab where you want to find the alert and click on ‘SMS Response Enable’, ‘save’ and ‘update’ button.

2.) Now send SMS commands from the configured mobile number.

3.) Once the commands are received from the user phone number the board will send acknowledgement as per the commands.

4.) After that it will send the router’s status once it has rebooted and is operational again.

Mentioned below are a few commands which can be sent from the configured mobile number to the router device. Below two commands are One for rebooting the router device and another to get the uptime.

1) {"device”: ["passkey”, “API key"],"command":"reboot","arguments":"hardware"}

2) {"device”: ["passkey ","API key"],"command”: “uptime"}

Loop back IP settings:

The loopback IP address, often referred to as “localhost.” it is used to establish network connections within the same device for testing and troubleshooting purpose.

The loopback IP address, commonly represented as 127.0.0.1, is a special address used for testing network connectivity on a local machine.

It allows a device to send network messages to itself without involving external networks, making it useful for troubleshooting and diagnostics.


However, this IP can be changed as per requirement and to do that, Navigating to Setting>>Network configuration>> Loopback IP settings can be changed/updated.

After configuring all the required information, the user should click on the save and then click on the update to update the all the required information.

2.2 VLAN

VLAN (Virtual Local Area Network) is a network within a network that segregates traffic into different logical networks on the same physical hardware. VLANs help in managing traffic more effectively and securely.

It is further divided into 2 sections,

Port-Based VLAN

Tagged Port Configuration


Port-Based VLAN:

A VLAN configuration method where network ports are assigned to specific VLANs.

EDIT:

To add a new VLAN ID, click on ‘Add Device’.

To edit the existing device the user needs to click on the edit option.

Once the changes are done click on the save button to save all the changes.

Click on the deleted button to delete the existing device detail.

Specification details are given below:

SN Field Name Sample Value Description
1 VLAN ID 1 This is a unique identifier for a VLAN within a network.
2 Port 0 Untagged When a port is set as untagged for a VLAN, it means that traffic entering or exiting this port is automatically associated with that VLAN without any VLAN tags being added to the frames.
3 Port 1 Untagged
4 Port 2 tagged When a port is set as tagged for a VLAN, it means that traffic on this port will include VLAN tags in the Ethernet frames. These tags carry the VLAN ID, allowing switches and other devices to know which VLAN the traffic belongs to.
5 Port 3 Untagged
6 Port 4 OFF When a port is marked as off for a VLAN, it means that the port is not participating in that VLAN at all. It will neither send nor receive traffic associated with that VLAN.

Save and update the page.


Tagged Port Configuration:

EDIT:

To add a new VLAN ID, click on ‘Add Device’.

To edit the existing device the user needs to click on the edit option.

Once the changes are done click on the save button to save all the changes.

Click on the deleted button to delete the existing device detail.

Specification details are given below:

SN Field Name Sample Value Description
1 Type 802.1Q IEEE 802.1Q is the standard protocol for VLAN tagging in Ethernet networks.
2 Parent Interface Port 2 It is the underlying physical interface like port 2 that carries the VLAN-tagged traffic.

Save and update the page.

2.3 SIM Switch

In this page the user needs to configure the Sim for the given device.

The user needs to select from the drop-down menu on which basis the sim needs to be switched.


Once the user selects on “signal strength” then the parameters related to signal strength will pop up and the user needs to configure the parameters based on the requirement.

Threshold RSRP:

This Needs to be set appropriately. Incorrect setting may cause unnecessary SIM switching. (In General, a BAD RSRP value range is -140 to -115 and FAIR RSRP value range is -115 to -105).

Threshold SINR:

This Needs to be set appropriately. Incorrect setting may cause unnecessary SIM switching. (In General, a BAD SNR value range is -20 to 0 and FAIR SNR value range is 0 to 13)

Once the user selects on “Data Limit” then the parameters related to Data Limit will pop up and the user needs to configure the parameters based on the requirement.

SN Field name Sample value Description
1 SIM Switch Based on Data Limit The user needs to select from the drop-down menu on what basis the sim needs to be switched.
2 SIM 1 Data Usage Limit (In MB) 1000 The user needs to set the limit for the data usage for SIM 1.
3 SIM 2 Data Usage Limit (In MB) 1000 The user needs to set the limit for the data usage for SIM 2.
4 Periodicity Daily The user needs to set the pattern/frequency to switch the sims.
5 Day Of Month For Ex: 16 The user needs to set the day for switching the sim.

After configuring all the required information, the user should click on the save.

2.4 Multi-WAN

As shown below, this section has 4 categories,

Status

General settings

Failover

Load Balancing


In ‘Status’ tab user can see the active network connections on the device as shown above.

General Settings:

In general settings, select any one option from the drop-down menu which you wish to imply and click on save and update.


Click on save and update.

Failover:

NOTE: Please verify that the name to be added is in the interface section of the status tab.

EDIT:


The specifications details are below.

SN Field name Sample value Description
1 Priority Ex: 5 Setting a priority of 1 means this connection has the highest priority and will be used before any others with a higher priority number.
2 Select Track IP Numbers 2 In this dropdown the user needs to select the track number for the Ips. This specifies the number of IP addresses that will be used for tracking the status of the connection.
3 TrackIP1 8.8.8.8 The system will ping this IPV4 IP address to check if the connection is up and working. You can even add any whitelisted IP.
4 TrackIP2 8.8.4.4 The system will ping this IPV4 IP address to check if the connection is up and working. You can even add any whitelisted IP.
5 Reliability 1 If reliability is set to 1, it might mean the connection is considered reliable if it successfully pings at least one of the tracked IP addresses.
6 Count 1 Setting Count to 1 means the device will send one ping to each IP address to check for connectivity.
7 Up 3 If set to 3, the connection will be considered "up" only if all three pings are successful.
8 Down 3 If set to 3, the connection will be considered "down" if all three pings fail.

Click on save and update tab.

Load Balancing:

Load balancing is a network management technique used to distribute traffic across multiple network connections or servers to optimize resource use, maximize throughput, minimize response time, and ensure reliability.

Task: Distributes network traffic evenly across multiple connections (e.g., multiple WAN links) or servers.

Purpose: This ensures that no single connection or server is overwhelmed with too much traffic, which could lead to congestion and slower performance.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Traffic Distribution Ratio Ex: 60% If you have two connections and set one to 60% and the other to 40%, traffic will be distributed accordingly.

The ratio must be the same for CWAN1_0 and CWAN1_1.

2 Select Track IP Numbers 2 The system will track two IP addresses to determine if the network connection is active and reliable.
3 TrackIP1 8.8.8.8 The system will ping this IPV4 IP address to check if the connection is up and working. You can even add any whitelisted IP.
4 TrackIP2 8.8.4.4 The system will ping this IPV4 IP address to check if the connection is up and working. You can even add any whitelisted IP.
5 Reliability 1 With a reliability setting of 1, the connection might be considered reliable if at least one ping is successful.
6 Count 1 The system will send one ping to each tracked IP to check the connection's status.
7 Up 3 The system requires 3 successful pings for the connection to be marked as "up."
8 Down 3 If 3 pings fail, the system will mark the connection as "down," and it may switch to an alternate connection if available.

Click on save and update tab.

2.5 VPN

VPN stands for Virtual Private Network, it establishes a connection between the system and a remote server, which is owned by a VPN provider.

Creating a point-to-point tunnel that encrypts the personal data, masks the IP address, and allows to block the required website to blocks via firewalls on the internet.

Navigate to settings >= VPN, general settings and you will see all VPN options you wish to use.

Refer the below figure.

There are 7 types of setting available under VPN configuration.

  • General Settings
  • IPSEC
  • Open VPN
  • Wireguard
  • Zerotier
  • PPTP
  • L2TP


General Settings:

In this page the user must choose which type of VPN connection is required for the device. The user must select from the above VPN based on its requirement. If required, the user can select all the options. The user needs to click on the save after selecting the option based on its use.

IPSEC:

IPSEC VPN is used to create a VPN connection between local and remote networks.

To use IPSEC VPN, the user should check that both local and remote routers support IPSEC VPN feature.

In this page the user can add/edit/delete the IPSEC VPN connection for the device.

The user needs to click on the update button once the required configuration is completed.

In IPSEC the user needs to click on edit button to edit the configuration of an existing VPN connection.

Click on update once done with configurations.

The tunnel will show established, showing the connection has been made.

IPSEC VPN has been Eshtablished.

Detailed specifications are below:

SN Field name Sample value Description
1 IPSEC Site to Site VPN In this dropdown the user should select the IPSEC connection type.
2 IPSEC Role Client/Server In this dropdown box the user needs to select the IPSEC role. The device is acting as a client in the VPN setup (in this example).
3 Connection Type Tunnel In this dropdown the user needs to select the connection type. The user should select on the connection enable check box.
4 Connection mode Route/add/start/trap In this drop down list the user should select the mode for the connection. In this example start is selected which means the VPN connection is initiated automatically.
5 Remote Server IP ******** The IP address of the remote VPN server.
6 Local ID 3.3.3.3 The user needs to set the local id. It is the identification for the local VPN client.
7 No. of local subnets 1 In this dropdown the user needs to select how many subnets will be connected.
8 Local Subnet 1 172.16.31.25/32 In this text box the user needs to put the specific local subnet included in the VPN.
9 Remote id 1.1.1.1 In this text box the user needs to put the id of the remote connection. It is the identification for the remote VPN server.
10 No of remote subnet 1 In this dropdown the user needs to select how many subnets it will be connected remotely.
11 Remote subnet 10.1.1.0/24 In this text box the user needs to put the address of the remote subnet. The specific remote subnet included in the VPN.
12 Key exchange Ikev1 In this dropdown the user should select the which key exchange version to be selected.
13 Aggressive Yes/No In this dropdown the user should select either yes or no.
14 IKE Lifetime (In Seconds) 86400 The lifetime of the IKE phase in seconds (1 day).
15 Lifetime (in seconds) 28800 The lifetime of the IPsec SA (Security Association) in seconds (8 hours).
16 Enable DPD Detection 1

0

Indicates whether Dead Peer Detection is enabled to detect a lost connection. Enable this option as per server-side settings.
17 Time Interval (In Seconds) 60 This option is available only if DPD Detection is enabled. The time interval is the interval for DPD checks.
18 Action Restart/clear/hold/

trap/start

Restart: Action to take when DPD detects a lost connection (restart the connection). Select as per server-side setting.
19 Authentication Method PSK PSK: Pre-shared key is used for authentication. Select this option for authentication as per sever side setting.
20 Multiple Secrets 1/0 Indicates whether multiple PSK secrets are used. Enable only if required.
21 PSK Value ****** Pre-shared key value (masked for security).
Proposal settings Phase I
22 Encryption Algorithm AES 128

AES 192

AES 256

3DES

AES 256: Encryption algorithm for Phase I. Select as per server-side configuration. Both server and client should have same configuration.
23 Authentication Phase I SHA1

MD5

SHA 256

SHA 384

SHA 512

SHA 512: Authentication algorithm for Phase I.

Select as per server-side configuration. Both server and client should have same configuration.

24 DH Group MODP768(group1)

MODP1024(group2)

MODP1536(group5)

MODP2048(group14)

MODP3072(group15)

MODP4096(group16)

MODP2048 (group14): Diffie-Hellman group for key exchange.

Select as per server-side configuration. Both server and client should have same configuration.

Proposal settings Phase II
25 Hash Algorithm AES 128

AES 192

AES 256

3DES

AES 256: Encryption algorithm for Phase II. Select as per server-side configuration. Both server and client should have same configuration.
26 Authentication Phase II SHA1

MD5

SHA 256

SHA 384

SHA 512

SHA 512: Authentication algorithm for Phase II.

Select as per server-side configuration. Both server and client should have same configuration.

27 PFS Group MODP768(group1)

MODP1024(group2)

MODP1536(group5)

MODP2048(group14)

MODP3072(group15)

MODP4096(group16)

MODP2048 (group14): Perfect Forward Secrecy group.

Select as per server-side configuration. Both server and client should have same configuration.

Click on save and then update the page for changes to reflect.

Open VPN:

To use the VPN feature, the user should enable OpenVPN Server on the router and install and run VPN client software on the remote device.

The user needs to “upload” the respective certificate from a valid path and then click on the “Update.”

Only the TAP connection needs a bridge. The tun connection does not require a bridge. Here we have established a TUN connection.

By clicking on the enable/disable button, the user can start/stop the VPN connection.

VPN TUN has been established.

Same way VPN TAP can also be established with the help of bridging.

WireGuard:

WireGuard is simple, fast, lean, and modern VPN that utilizes secure and trusted cryptography.

Click on “Edit” to start configurations as needed.

EDIT:

Click on the save button after the required configuration.

Specifications details are given below:

SN Field name Sample value Description
1 Wireguard Role Client/Server In this dropdown box the user needs to select the wireguard role.
2 WireGuard Tunnel Over IPV4/IPV6 IPV4: Use this if your network and endpoint (WireGuard server) support only IPv4.

IPV6: Use this if your network and endpoint support IPv6.

3 Enable Failover Enable/Disable This option allows the VPN connection to automatically switch to a backup connection if the primary connection fails.
4 Enable IPV4 Enable/Disable This enables IPv4 traffic to be routed through the WireGuard tunnel.
5 Enable IPV6 Enable/Disable Enable this if your network and the destination support IPv6.
6 Listen Port 51820 This is the default port that WireGuard uses to listen for incoming connections.
7 Endpoint Host port 51820 This is the port on the WireGuard server that the client will connect to.
8 Peer Publickey ***** This is the public key of the WireGuard server that the client uses to establish a secure connection.
9 Enable Default Route Enable/Disable Enable this if you want all network traffic (not just specific routes) to be routed through the WireGuard VPN.

Save and update the page after configuration has been done.


Zerotier:

ZeroTier is a tool that lets you create your own private network over the internet.

Go to ZeroTier Central and sign up for a free account.

In ZeroTier Central, click on "Create a Network". This will generate a unique 16-digit network ID for your new network.

Go to settings => VPN, in general settings, enable ZeroTier and save.


Copy and paste the unique 16-digit network ID in the edit section.

Click on the save button after the required configuration.

SN Field name Sample value Description
1 NetworkID Ad2769hfkw2345f4 In this dropdown box the user needs to paste the unique 16-digit network id.
2 Listen Port 9993 Default


PPTP:

This configuration is for setting up a PPTP (Point-to-Point Tunnelling Protocol) VPN connection.

PPTP is a protocol that enables secure data transmission across public networks like the internet, often used to connect to remote networks or access resources securely.

*Refer the image below*

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 PPTP Role Client/Server Client: meaning it will initiate the connection to the remote PPTP server.

Server: means this device will accept incoming PPTP connections from clients, which can be users or devices that need remote access to the local network or internet via this server.

PPTP Role: CLIENT
2 Default Route Enable/Disable Enabling the default route means that all network traffic will be routed through the VPN tunnel once the connection is established.
3 Metric Ex: 0 The metric is a value that defines the priority of this route among other available routes. Lower metrics indicate higher priority.
4 Server IP Ex: 192.168.10.1 This is the IP address of the PPTP server the client will connect to.
5 Interface Any

EWAN5

Selecting the correct interface is essential because it tells the system which network adapter should be used to establish the VPN connection.
6 Username ****** This field is the login username for the PPTP server.
7 Password **** This is the password associated with the username.
PPTP Role: SERVER
8 Local IP Ex: 192.168.0.1 This IP address (192.168.0.1) is the local IP of the PPTP server on its network. Clients connecting to the VPN will see this address as their gateway or endpoint within the VPN.
9 Remote IP Range Ex: 192.168.0.20-30 This range defines the pool of IP addresses that the server will assign to connected VPN clients. Here, any client connecting to the server will receive an IP address between 192.168.0.20 and 192.168.0.30, which provides up to 11 possible addresses for simultaneous connections.
10 Username Ex: User1 This is a username that the client will use to authenticate with the PPTP server. In this case, User1 is designated as an authorized user.
11 Password ***** The password associated with User1 is required to complete the authentication.

Once Configured, click on save and update.

L2TP:

L2TP (Layer 2 Tunnelling Protocol) is a network protocol used to establish secure tunnels for transferring data between remote devices or networks, often in VPNs, by encapsulating data for encryption and routing.

*Refer the image below*

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 L2TP Role Client/Server Client: connecting to an L2TP server to establish a secure tunnel for communication.

Server: the server listens for incoming client connections.

L2TP Role: CLIENT
2 Default Route Enable/Disable If enabled, all outbound traffic will be routed through the L2TP connection.

If disabled, only specific traffic destined for the L2TP network will use the tunnel.

3 Metric Ex: 1 The system uses this metric to decide which route to prioritize if multiple routes exist.

L2TP connection with Metric 1 will take precedence over a LAN or WAN route with Metric 10.

4 Server IP Ex: 192.168.10.1 This is the IP address of the L2TP server to which the client will connect.

Local Networks: If connecting within a LAN, the server might have an IP like 192.168.x.x.

Remote Connections: The server IP might be a public address like 203.0.113. x.

5 Checkup Interval Time (in sec) Ex: 30/60 secs Setting 30 seconds ensures the client checks the connection every half-minute. If the tunnel drops, the client can quickly reconnect.
6 Interface Any Example interfaces might include eth0, usb0, or ra0.
7 Username Ex: User The server verifies the username to grant or deny access.

Must match credentials configured on the L2TP server.

8 Password ****** Should be kept secure and match the configuration on the server.

Masked for privacy during configuration.

9 MPPE Encryption Enable/Disable Enabled: Encrypts traffic using MPPE, enhancing security (recommended).

Disabled: Transmits data unencrypted, reducing overhead but exposing traffic to potential risks.

L2TP Role: SERVER
10 Local IP Ex: 192.168.0.1 This is the local IP address of the L2TP server. It serves as the gateway for clients connected via the L2TP tunnel.
11 Start Ex: 192.168.0.20 Specifies the first IP address that can be assigned to connected clients.
12 Limit Ex: 192.168.0.30 Creates an IP pool for clients (from 192.168.0.20 to 192.168.0.30 in this case).
13 Username Ex: User1 Ensures that only authorized users can connect.

The server verifies this username against its authentication database.

14 Password ****** The server verifies the password along with the username.

The password must match the one configured on the server for successful authentication.

2.6 Firewall

A firewall is a layer of security between the network and the Internet.

Since a router is the main connection from a network to the Internet, the firewall function is merged into this device.

Every network should have a firewall to protect its privacy.

To configure a Firewall, navigate to settings <= firewall,

There are 6 types of setting available under firewall.

  • General Settings
  • Port forwards
  • Traffic Rules
  • SNAT traffic Rules
  • Parental Control
  • Zone Forwarding

General Settings:

General settings are subdivided into 2 parts,

1.) General settings

In general settings, the settings that are made are default settings and can be changed according to user’s preference.

SN Field Name Sample Value Description
1 Enable SYN-flood protection Enabled This is enabled by default; setting can be changed if required.
2 Disable IPV6 Disabled This is enabled by default; setting can be changed if required.
3 Drop invalid packets Disabled This is enabled by default; setting can be changed if required.
4 TCP SYN Cookies Disabled This is enabled by default; setting can be changed if required.
5 Input Reject/Accept By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
6 Output Reject/Accept By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
7 Forward Reject/Accept By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.


2.) Zone settings

In zone settings, there’s an option to add “New Zone”, according to user’s requirement.


Port Forwards:

Port forwarding is a feature in a router or gateway that allows external devices to access services on a private network.

It maps an external port on the router to an internal IP address and port on the local network, enabling applications such as gaming servers, web servers, or remote desktop connections to be accessed from outside the network.

This helps in directing incoming traffic to the correct device within a local network based on the port number, enhancing connectivity and accessibility.

EDIT:


Click on the save button after the required configuration.

SN Field name Sample value Description
1 Name Example: Web_Server_Forward Field must not be empty. Provide a name for the rule to easily identify it.
2 Protocol Example: TCP+UDP Select the protocol for the rule.

Options typically include TCP+UDP, TCP, UDP, ICMP, Custom.

3 Source zone Example: SW_LAN Select the source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
4 Source MAC address [optional] Example: any any: Leave as any if you don't want to specify a MAC address.
5 Source IP address[optional] Example: Leave blank if not needed. Optionally specify an IP address or range.
6 Source port Example: 80, 443 (if matching traffic for web server ports) Specify the source port or port range.
7 Destination zone Example: SW_LAN Select the destination zone where the traffic is heading to.
8 Destination IP address Leave blank if not needed. Optionally specify the destination IP address or range.
9 Destination port Example: 80 (if redirecting to a web server port) Specify the destination port or port range.

Traffic Rule:

"Traffic rules" refer to the policies and regulations that govern the flow of data packets within a network.

To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.

EDIT:

SN Field name Sample value Description
1 Name Example: Allow_HTTP_and_HTTPS Field must not be empty: Provide a descriptive name for the traffic rule.
2 Restrict to Address Family 1.     Options: IPv4, IPv6

Example: IPv4 if dealing with typical internet traffic.

Select the address family to generate iptables rules for.
3 Protocol Example: TCP+UDP TCP+UDP: Match incoming traffic using the given protocol.
4 Match ICMP Type Example: any Match all ICMP types if set to any. Specific types can be chosen if needed.
5 Source Zone Example: LAN Specifies the traffic source zone.
6 Enable DDoS Prevention Example: ‘Checked’ if you want to enable DDoS prevention measures Enable or disable Distributed Denial of Service (DDoS) prevention.
7 Source MAC Address Example: any any: Match traffic from any MAC address or specify a particular MAC address.
8 Source Address Example: 192.168.1.0/24 Match incoming traffic from the specified source IP address or range.
9 Source Port Example: any if all source ports should be matched any: Match incoming traffic from the specified source port or port range.
10 Destination Zone Example: WAN Specifies the traffic destination zone.
11 Action Example: ACCEPT Options: ACCEPT, DROP, REJECT. Specify the action to take for matched traffic.
12 Limit Example: 10/minute to limit matches to 10 times per minute. Maximum average matching rate; specified as a number, with an optional /second, /minute, /hour, or /day suffix.
13 Extra arguments Example: --log-prefix "Blocked: " to add a log prefix to log messages for this rule. Passes additional arguments to iptables. Use with care as it can significantly alter rule behaviour.

Click on save once configured.

SNAT Traffic Rule:

For configuring SNAT (Source Network Address Translation) traffic rules, you can control how outbound traffic from your local network is translated to a different IP address as it exits the network.

To add new source NAT,

Click on “ADD” in “New Source NAT:”

EDIT:


Specification details are below:

SN Field name Sample value Description
1 Name Example: SNAT_WAN_to_LAN Field must not be empty: Provide a unique and descriptive name for the SNAT rule.
2 Protocol Example: TCP+UDP TCP+UDP: Select the protocols that the SNAT rule will apply to.
3 Source Zone Example: wan wan: Specifies the source zone from which the traffic originates.
4 Source IP Address Example: any or a specific range like 192.168.1.0/24 -- please choose --: Specify the source IP address or range. Leave empty if the rule applies to any source IP.
5 Source Port Example: any any: Specify the source port or port range from which the traffic originates.
6 Destination Zone Example: lan lan: Specifies the destination zone to which the traffic is directed.
7 Destination IP Address Example: any or a specific IP like 192.168.1.100 -- please choose --: Specify the destination IP address or range. Leave empty if the rule applies to any destination IP.
8 Destination port Example: any any: Specify the destination port or port range to which the traffic is directed.
9 SNAT IP Address Example: 203.0.113.5 (an external IP address) -- please choose --: Specify the IP address to which the source IP should be translated.
10 SNAT Port Example: Leave empty if not needed, or specify a port like ‘12345’ Optionally, rewrite matched traffic to a specific source port. Leave empty to only rewrite the IP address.
11 Extra Arguments Example: --log-prefix "SNAT_traffic: " (to add a log prefix to log messages for this rule) Pass additional arguments to iptables. Use with care as it can significantly alter rule behaviour.

Click on save once configured.

Parental Control:

For configuring parental control rules, you want to set restrictions based on time, source, and

destination zones, as well as specific devices.

To add parental control in firewall,

Click on “Add and Edit” in “New parental control:” field.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Name Example: Parental_Control_Sunday Field must not be empty: Provide a unique and descriptive name for the parental control rule.
2 Proto all all: This specifies that the rule will apply to all protocols.
3 Source Zone Example: lan Field must not be empty: Please look at Firewall->Zone Settings to find zone names.
4 Destination Zone Example: wan Field must not be empty: Please look at Firewall->Zone Settings to find zone names.
5 Source MAC Address Example: 00:1A:2B:3C:4D:5E Field: Enter the MAC address of the device you want to apply the parental control rule to. This is useful for restricting specific devices.
6 Target Example: Reject Accept: This specifies the action to take. For parental controls, you might want to use ‘Reject’ or ‘Drop’ to block traffic.
7 Weekdays Example: Sunday Sunday: Specify the days of the week when the rule should be active.
8 Month Days Example: All All: Specify the days of the month when the rule should be active.
9 Start Time (hh:mm:ss) Example: 18:00:00 (6:00 PM) Field must not be empty: Specify the start time when the rule should begin to apply.
10 Stop Time (hh:mm:ss) Example: 22:00:00 (10:00 PM) Field must not be empty: Specify the stop time when the rule should end.

Click on save once configured.


Zone Forwarding:

Zone forwarding in network configuration allows traffic to be directed from one zone to another.

To ADD new zone,

Click on “Add” in “New Zone Forward:” field.

EDIT:

Specification details are below:

SN Field Name Sample Value Description
1 Source Zone Example options: lan, wan, etc. --please choose--: Select the source zone from which the traffic originates.
2 Destination Zone Example options: lan, wan, etc. --please choose--: Select the destination zone to which the traffic is directed.

Click on save once configured.

2.7 Loopback Rule

In this page the user can configure the port where he wants to forward the traffic to. Here the user can add/edit/delete different ports as per the requirement.

The user should click on ‘add’ and then ‘edit’ to do the required changes in the port and enter the valid information in each section to configure the port for forwarding.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Name Example: loopback Provide a descriptive name for the rule.
2 Protocol Example: TCP+UDP TCP+UDP: Select the protocols that the rule will apply to.
3 Source IP Address [Optional] Example: any or a specific IP range like 192.168.1.0/24 Optionally specify the source IP address or range. Leave empty if the rule should apply to any source IP.
4 Source Port [Optional] Example: any any: Specify the source port or port range from which the traffic originates. any allows traffic from all ports.
5 Loopback IP Address Example: 127.0.0.1 Specify the loopback IP address. Typically, this is 127.0.0.1.
6 Port Example: any any: Specify the destination port or port range to which the traffic is directed. any allows traffic to all ports.
7 Action Example: DNAT This specifies the action to take either DNAT or SNAT.
8 Internal IP Address Example: 192.168.1.100 Field must not be empty: Specify the internal IP address to which the traffic should be redirected.
9 Internal Port Example: any Redirect matched incoming traffic to the given port on the internal host.

Once the user is done with the required configurations, should click save button and then click on the update to save the changes.

2.8 VRRP

VRRP (Virtual Router Redundancy Protocol) is used to ensure high availability for IP routing by allowing multiple routers to work together to present the illusion of a single virtual router to the hosts on a network.

In General Settings, click on ‘Enable VRRP’ and save.

In VRRP section,

Give a name and ‘Add’ device.

Click on ‘Edit’ to make changes.

Click on ‘Delete’ if particular instance not required.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Role 1.      Master

2.      Backup

Choose Master for the primary router that should handle the traffic under normal circumstances.

Choose Backup for a secondary router that will take over if the master fails.

2 Virtual ID Ex: 0 The value can range from 0 to 255.

Ensure all routers in the same VRRP group share the same Virtual ID.

3 Priority Ex: 100 For the Master role, use the highest priority, typically above 100.

For the Backup role, set a lower priority number, usually below the master's priority.

4 Interface SW_LAN This is the network interface on which VRRP operates.
5 Source IP Ex: 192.168.10.1 This is the IP address used as the source in VRRP advertisements.
6 Peer IP Ex: 192.168.10.10 This is the IP address of the other VRRP peer (usually the backup router). It helps the routers identify each other.
7 Virtual IP Address 192.168.10.100/24 The virtual IP should be an unused address within the subnet, such as 192.168.10.100/24, ensuring it's consistent across all VRRP routers.
8 Enable Authentication Enable/Disable Enable this if you want to secure your VRRP communications.
9 Password ********* It ensures that only routers with the correct password can join the VRRP group.

Save and update once changes have been made.

2.9 Remote Monitoring

In this page the user can select which equipment needs to be monitored remotely.

Once the user selects the type of RMS click on save.

NMS:

IN this page the user should type the server IP or domain name in the URL then click on save.

Click on upload and start (Once key is uploaded and this option is clicked, NMS automatically starts, and this router device gets registered with the NMS server provided).

TR_069:

To enable the TR_069 the user needs to click on the enable check box.

Once the user clicks on the check box of enable it will display all the required filed to configured.

Specification details are given below:

SN Field Name Sample Value Description
1 Serving Interval 300 A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
2 Interface This can be something like eth0 or wan. This specifies the network interface used for TR-069 communication.
3 Username Example: User The username used to authenticate with the ACS.
4 Password •••• The password used to authenticate with the ACS.
5 URL http://example.com The URL of the ACS. This is where the CPE (customer-premises equipment) will send its requests and where it will receive configurations and updates from.


The user should fill all the required fields and click on the save button.

2.10 Tunnel

Tunnels are a method of transporting data across a network using protocols which are not supported by that network.

It is further categorised into 3 sections,

1.) General Settings

2.) GRE Tunnel

3.) IPIP Tunnel

General Settings:

In this page the user needs to select under which type of tunnel it needs to send the data.

Once the user selects the type of tunnel then click on the save button.



GRE Tunnel:

A GRE (Generic Routing Encapsulation) tunnel configuration involves setting up a virtual point-to-point connection between two endpoints over an IP network.

Here the user can add/edit/delete the details of the tunnel.

Once the required update is done then click on update to save the changes.


EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Tunnel name Example: GRETunnel GRETunnel: The name of the GRE tunnel.
2 Local external IP Example: 10.1.1.66 The IP address of the local endpoint that will initiate the GRE tunnel.
3 Remote external IP Example: 10.1.1.40 The IP address of the remote endpoint that will terminate the GRE tunnel.
4 Peer tunnel IP Example: 10.1.1.4 The IP address of the peer's tunnel interface.
5 Local tunnel IP Example: 10.1.1.6 The IP address of the local tunnel interface.
6 Local tunnel net mask Example: 255.255.255.0 The subnet mask of the local tunnel interface.
7 Remote IP Example: 192.168.10.0/24 The remote network that is reachable through the GRE tunnel.
8 Enable Tunnel Link Check to enable Enable or disable the GRE tunnel link.
9 Interface type Example: EWAN2 EWAN2: The type of network interface used for the GRE tunnel.
10 MTU Example: 1476 1476: Maximum Transmission Unit size for the GRE tunnel.
11 TTL Example: 64 64: Time To Live value for the packets within the GRE tunnel.
12 Tunnel key Example: 12345678 12345678: A unique key used to identify the GRE tunnel.
13 Enable keep alive Check to enable Enable or disable the keep-alive feature to monitor the tunnel's status.
14 Keep alive interval Example: 10 10: Interval in seconds for the keep-alive packets.

Once the required update is done then click on update to save the changes.


IPIP Tunnel:

An IPIP (IP-in-IP) tunnel is a simple tunnelling protocol used to encapsulate IP packets within IP packets. This is like GRE but without additional features such as keying and type fields.

Here the user can add/edit/delete the details of the tunnel.


EDIT:

Once the required update is done then click on update to save the changes.

Specification details are given below:

SN Field Name Sample Value Description
1 Tunnel name Example: IPIPTunnel IPIPTunnel: The name of the IPIP tunnel.
2 Local external IP Example: 10.1.1.66 The IP address of the local endpoint that will initiate the IPIP tunnel.
3 Remote external IP Example: 10.1.1.40 The IP address of the remote endpoint that will terminate the IPIP tunnel.
4 Peer tunnel IP Example: 10.1.1.4 The IP address of the peer's tunnel interface.
5 Local tunnel IP Example: 10.1.1.6 The IP address of the local tunnel interface.
6 Local tunnel net mask Example: 255.255.255.0 The subnet mask of the local tunnel interface.
7 Remote IP Example: 192.168.10.0/24 The remote network that is reachable through the IPIP tunnel.
8 Enable Tunnel Link Check to enable Enable or disable the IPIP tunnel link.
9 Interface type Example: EWAN2 EWAN2: The type of network interface used for the IPIP tunnel.
10 MTU Example: 1476 1476: Maximum Transmission Unit size for the IPIP tunnel.
11 TTL Example: 64 64: Time To Live value for the packets within the IPIP tunnel.
12 Tunnel key Example: 12345678 Although typically not used in IPIP, this field might be included for compatibility with certain configurations.
13 Enable keep alive Check to enable Enable or disable the keep-alive feature to monitor the tunnel's status.
14 Keep alive interval Example: 10 10: Interval in seconds for the keep-alive packets.

3.Maintenance

In this module the user can configure/upgrade/modify the settings related to system, password,

firmware and monitoring.

It includes 6 submodules.

  • General
  • Password
  • Reboot
  • Import and Export config
  • Firmware upgrade
  • Monitor Application

*Below is the detailed explanation of every field*

3.1 General

Here you can configure the basic aspects of router like its hostname or the timezone.

It is further sub-divided into,

1.) General Settings

2.) Logging

3.) Language and Style


General Settings:

EDIT:

SN Field Name Sample Value Description
1 Local Time 2024/07/30 13:25:47 The current local date and time set on the device.
2 Hostname 22B25240007 The hostname of the device, which is used to identify it on the network.
3 Timezone Asia/Kolkata The timezone setting of the device, which determines the local time.

Once the user configures the required details then click on the save button to save all the details.

Logging:

Here the user can configure the basic aspects of your device related to system.

The system log configuration provided specifies how the device handles and stores log information, including buffer size, external log server details, and log verbosity levels.

EDIT:

SN Field Name Sample Value Description
1 System log buffer size Example: 32 kiB The size of the memory buffer allocated (0-32) for storing system logs before they are either written to a file or sent to an external server.
2 External system log server Example: 0.0.0.0 The IP address of an external server where logs can be sent.
3 External system log server port Example: 514 The port used to send logs to the external log server. Port 514 is the default port for syslog.
4 Log output level Example: Debug Sets the detail level of the system logs.
5 Cron Log level Example: Debug The detail level of the logs for cron jobs.

Once the user configures the required details then click on the save button to save all the details.


Language and Style:

Here the user can configure the basic aspects of your device related to language.

Once the user configures the required details then click on the save button to save all the details.

3.2 Password

In this module the user can set the password for the admin credentials.

Specifies the password for the guest account. If the user enters a plaintext password here, it will get replaced with a crypted password on save. The new password will be effective once the user logs out and log in again.

3.3 Reboot

In this module the user can reboot the device remotely.

First option is to directly reboot the device without enabling the maintenance reboot tab.

Click on “Reboot Now” at the bottom of the screen to start the reboot process.


To start maintenance reboot process first the user needs to fill all the required fields.

Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Maintenance Reboot Enable/Disable Indicates whether the maintenance reboot feature is enabled or not.
2 Type Maintenance Reboot Specifies the type of reboot being scheduled.
3 Reboot Type Software/Hardware Hardware: A hardware reboot involves restarting the entire device as if it were powered off and on again.

Software: A software reboot involves restarting the operating system without powering off the hardware.

4 Minutes Example: 59 The minute at which the reboot should occur (0-59).
5 Hours Example: 22 (10 PM) The hour at which the reboot should occur (0-23, in 24-hour format).
6 Day Of Month Example: All Specifies which days of the month the reboot should occur (1-31). "All" means it will occur every day.
7 Month Example: All Specifies which months the reboot should occur (1-12). "All" means it will occur every month.
8 Day Of Week Example: All Specifies which days of the week the reboot should occur (0-6, where 0 is Sunday). "All" means it will occur every day of the week.

Once the user fills all the required given parameters click on the save.

3.4 Import and Export

In this section, User can Import & Export Configuration files of the Device.

Click “Export Config” to export device configuration & settings to a text file,

Click “Import Config” to import device configuration & settings from a previously exported text file.

The user needs to select on the “choose file”, upload the required file and click on apply.

3.5 Firmware Upgrade

The user can upgrade with the latest software for the existing firmware.

Click on the flash image and chose the path where the sys-upgrade file is kept and then click on flash image, it will upgrade to the latest software once the reboot is done.

This option will completely reset the device to default settings.

Click on the Retain Config and flash and chose the path where the sys-upgrade file is kept and then click on Retain Config and flash, it will upgrade to the latest software once the reboot is done.

This refers to updating the firmware (flashing) of a device while preserving the current configuration settings.

Click on the Factory Reset for the complete retest of the device.

3.6 Monitor Application

In this section, the monitor application is divided into major 2 configurations which is further sub-divided into 4 editable options,

1.) Modem Monitor Application Configuration:

2.) Router Monitor Application Configuration:

Modem Monitor Application Configuration:

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Ping Check Application Enable/Disable Turns on the functionality to perform ping checks on specified IP addresses.
2 Time Interval for Check (In minutes) Example: 10 minutes Frequency at which the ping checks are performed.
3 Select No of IP addresses to ping Example: 1 Number of IP addresses that will be pinged.
4 IP Address 1 Example: 8.8.8.8 The IP address to ping.
5 No. of Retries Example: 5 Number of times to retry pinging an IP address if the initial ping fails.
6 Failure Criteria in (%) Example: 80% (If 4 out of 5 pings fail, it’s considered a failure) Percentage of failed pings required to consider the ping check a failure.
7 Action On Failure Example: Restart Modem Action to be taken if the ping check fails according to the criteria.
8 Enable Second Level Action Enable/Disable Option to enable a secondary action if the primary action fails multiple times.
9 Second Level Action Threshold Example: 2 Number of failures required to trigger the secondary action.
10 Second Level Action Example: Restart Board (Reboots the entire hardware board) The action to be taken if the second level action threshold is met.

Save the details once made necessary changes.

Router Monitor Application Configuration:

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Ping Check Application Enable/Disable Activates the ping check functionality to monitor router performance.
2 Time Interval for Check (In minutes) Example: 10 minutes How frequently the ping checks are performed.
3 Select No of IP Addresses to Ping Example: 1 (Please select the appropriate number based on your requirements) Choose the number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
4 No. of Retries Example: 3 Number of retries if a ping fails.
5 Failure Criteria in (%) Example: 80% (If 80% of the pings fail, it’s deemed a failure) Percentage of failed pings required to consider the ping check as failed.
6 Action On Failure Example: Restart IPsec The action taken if the ping check fails according to the criteria.
7 Enable Second Level Action Enable/Disable Option to enable an additional action if the primary action fails.
8 Second Level Action Threshold Example: Specify the number of failures, such as 2 Number of times the primary action must fail before the secondary action is triggered.
9 Second Level Action Example: Restart Board The action to be taken if the second level action threshold is met.

Save the details once made necessary changes.

4.Status

In this module the user can view the status of the router device with respect to the network, Wan, modem etc.

It has 4 submodules.

  • Interfaces
  • Internet
  • Modem
  • Routes

4.1 Interfaces

Each network device (interface) is associated with specific traffic statistics, uptime, and status. Active interfaces are operational, while inactive interfaces are not currently transmitting data.

Looking on the network status the user can check if the cellular, wifi, ewan, vpn etc is up.

4.2 Internet

In this submodule the user can view the status of the internet connections.

 To see the latest status of the internet connection the user needs to click on the refresh button.

4.3 Modem

This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.

4.4 Routes

This configuration shows how the router directs traffic between different networks and interfaces, ensuring proper communication within the local network and to external networks via the default gateway.

ARP Table: Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.

IPv4 Routes: This shows which network is directly connected on which interface.

Example: Network 192.168.10.0/24 is directly connected on interface eth0.1.

IPv6 Routes: Similar routes as IPv4, but this time listed under IPv6 routing rules.

Example: Local networks 192.168.10.0/24 and 192.168.100.0/24 are managed through eth0.1 and ra0, respectively.

*Refer the below image*

5. Features

In this module the user can see all the features that the router device has.

This module includes 7 features.

  • Mac Address Binding
  • URL Filtering
  • Web Server
  • Wi-Fi MacID Filtering
  • Routing
  • DMZ
  • Others

5.1 Mac Address Binding

MAC address binding is a configuration that binds a specific MAC address to a specific IP address. This ensures that a particular device on the network always receives the same IP address from the DHCP server, which can be useful for network management, security, and ensuring consistent network behaviour.

Under this submodule the user can configure/update/edit the IP Address for MAC.

You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Device Name Macbinding1 A user-defined name for the binding configuration.
2 MAC Address 48:9e:bd:da:45:91 The unique identifier for the network interface of the device to which the IP address will be bound.
3 IP Address 192.168.10.55 The IP address that will be consistently assigned to the device with the specified MAC address.

By applying this configuration, the DHCP server will always assign the IP address 192.168.10.55 to the device with the MAC address 48:9e:bd:da:45:91, ensuring consistency and stability in network addressing for that device.

  • Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
  • The user can click on the deleted button to delete an existing configured device.

Post all the changes the user needs to click on the update to reflect all the changes in the application.

5.2 URL Filtering

In this submodule the user should provide the URL which needs to be blocked for the device. By implementing URL filtering with the specified URL, you can control and restrict access to certain websites, thereby improving network security and managing user access.


To add the new URL for blocking, click on the Add New button.

Once the user clicks on the Add New button a new pop will appear in that page write the URL and click on the save.

The user can select the status of that URL while defining the URL.

To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.

Click on “save” after the changes are done as per the need.

5.3 Web Server

This configuration will allow your device to serve web traffic securely over HTTPS, keep its system time synchronized, and ensure that all HTTP traffic is redirected to HTTPS for better security.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Enable HTTP HTTP Port: 80

Enable or disable the HTTP server.

Port 80 is the default port for HTTP traffic. It is used to serve web pages over an unencrypted connection.
2 Enable HTTPS HTTPS Port: 443

Enable or disable the HTTPS server.

Port 443 is the default port for HTTPS traffic. It is used to serve web pages over an encrypted connection.
3 Redirect HTTPS Option to redirect HTTP traffic to HTTPS. When enabled, all HTTP requests will be automatically redirected to the HTTPS port to ensure secure communication.
4 Session Timeout (in millisecs) Ex: 60000 In this scenario the webpage will logout after 60secs of inactivity.
5 RFC1918 Filter Enable/Disable When enabled, this filter can block traffic from private IP ranges (e.g., 192.168.x.x, 10.x.x.x) from being routed through the public internet, enhancing network security.
6 Enable NTP Sync Enable or disable NTP synchronization. Synchronizes the device’s system clock with an external NTP server to maintain accurate time.
7 NTP Server 0.openwrt.pool.ntp.org The address of the NTP server used for time synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
8 NTP Sync Interval (In Minutes) 15 The interval at which the device will sync its clock with the NTP server, set to every 15 minutes in this case.

Click on save once changes are made.

5.4 Wi-Fi MacID Filtering

Wireless MAC ID Filtering allows you to control which devices can connect to your wireless network based on their MAC (Media Access Control) addresses. This can help enhance security by allowing only specified devices to access the network.

It is further divided into 2 categories,

WIFI 2.4G AP

WIFI 2.4G AP Guest

Before adding the MacIDs the user needs to select the mode from the dropdown menu.

In ‘Change Mode’ select one option,

Blacklist

In blacklist mode, you specify which MAC addresses are not allowed to connect to the wireless network. Devices not on the blacklist will be able to connect.

Whitelist

In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.

To Add the MacID the user needs to click on Add New option.

Specification details are given below:

SN Field Name Sample Value Description
1 Status Enable/Disable Enable or disable the MAC ID filtering.
2 MAC ID Example: e8:6f:38:1a:f2:61 The MAC address of the device to be whitelisted or blocklisted.
3 Network Name Example: WIFI 2.4G AP or Wi-Fi 2.4G AP Guest. The network to apply the MAC ID filtering.

Once the required MAC ID and Network Name is configured the user needs to click on the save button to add the details.

The user needs to click on the edit button to do modifications on the pre-existing configuration.

Once the required MACID / Network Name is modified the user needs to click on the save button to reflect the changed value in the application.

5.5 Routing

In this submodule the user can configure the parameters related to routing of the device like Target address, Networks address etc. Routing configurations allow network packets to be directed between different subnets and networks.

It is further divided into 2 sections,

Static IPV4 Routes

Advanced Static IPV4 Routes

Static IPV4 Routes:

Click on ‘Add’ to add a new interface.


EDIT:

To edit the existing device the user needs to click on the edit option.

Once the changes are done click on the save button to save all the changes.

Click on the deleted button to delete the existing device detail.


Specification details are given below:

SN Field Name Sample Value Description
1 Interface Ex: eth0.1 The network interface to be used for this route. Select the one to use from dropdown.
2 Target Ex: 192.168.20.0 The destination subnet to which traffic should be routed.
3 IPv4 Netmask 255.255.255.0 The subnet mask for the target network.
4 Metric 0 The priority of the route.

Lower values indicate higher priority.

5 IPv4 Gateway Ex: 192.168.10.1 The gateway IP address to be used for routing traffic to the target subnet.
6 Route Type Unicast Standard route for individual destination IP addresses.

Custom changes can be made.

Click on save once configuration changes have been made.

Advanced Static IPV4 Routes:

Click on ‘Add’ to add a new interface.

EDIT:

To edit the existing device the user needs to click on the edit option.

Once the changes are done click on the save button to save all the changes.

Click on the deleted button to delete the existing device detail.

Specification details are given below:

SN Field Name Sample Value Description
1 Interface Ex: ra0 The network interface through which the traffic will be routed. Select as per requirement.
2 To Ex: 192.168.10.1 This is the target address to which the traffic is being directed. In this case, all traffic destined for 192.168.10.1 will follow this route.
3 IPv4 Netmask 255.255.255.192 This defines the subnet of the destination address.
4 Table 1.) Local

2.) Main

3.) Default

4.) 220

5.) custom

1.) This table contains local routes for the addresses assigned to the local interfaces. It's typically used for host and broadcast addresses.

2.) The primary routing table used by the system.

3.) A fallback table used when no other table is specified.

4.) Often used for policy-based routing.

5.) A user-defined routing table.

5 From Ex: 192.168.100.1 This source address restricts the route to traffic originating from 192.168.100.1. Traffic from other sources won't use this route.
6 Priority 20 The priority value determines the preference of this route. A lower number means higher priority; 20 is relatively high, so this route will be preferred over routes with higher priority values.

Once all the configurations are done click on the update button to reflect the changes made.

5.6 DMZ

A DMZ (Demilitarized Zone) is a subnetwork that provides an extra layer of security for an organization's internal network.

In this case we are configuring several services (HTTP, HTTPS, SSH, FTP, DNS) in a DMZ, and each service requires the correct internal port (the port used within the network) and external port (the port used by external clients to access the service) settings.

Specification details are given below:

SN Field Name Sample Value Description
1 Enable DMZ Enable/Disable Enable DMZ to configure it further.
2 Host IP Address Ex: 192.168.10.1 This is the internal IP address of the device or server that will be in the DMZ.
3 Protocol 1.) TCP

2.) UDP

3.) ICMP

4.) All

TCP: Used for reliable services like HTTP, HTTPS, FTP, and SSH.

UDP: Often used for services like DNS that don't require as much reliability.

ICMP: Used for sending control messages like "ping."

All: Select this if you're unsure which protocol to allow, but it's less secure.

4 Allow HTTP Internal Port: 80

External Port: 80

Enables web traffic over the unsecured HTTP protocol.

(Port 80 is the standard port for HTTP traffic on our internal network).

5 Allow HTTPS Internal Port: 443

External Port: 443

Enables secure web traffic over HTTPS. (Port 443 is the standard port for HTTPS on our internal network).
6 Allow SSH Internal Port: 52434

External Port: 52434

This is a custom port we’re using for SSH.

The default is 22.

7 Allow FTP Internal Port: 21/20

External Port: 21/20

FTP is used to transfer files between computers.

(These are the standard ports for FTP traffic. Port 21 is used for control commands, and port 20 for the data transfer.)

8 Allow DNS Internal Port: 53

External Port: 53

Standard DNS port within our internal network.

5.7 Others

In this page the user will get to do all the other miscellaneous configuration with respect to the device based on the required parameters. Each utility serves a specific purpose, providing various functionalities for managing and troubleshooting network configurations and statuses.

Specification details are given below:

SN Field Name Sample Value Description
1 Set Date Date and time fields (day, month, year, hour, minute, second) Sets the system date and time to the specified values.
2 Get Date System Retrieves and displays the current system date and time.
3 ipsec status all Command ‘Get’ Displays the status of all IPsec connections.
4 Wi-Fi Scan Command ‘Get’ Initiates a scan for available Wi-Fi networks.
5 iPerf3 Client IP address (e.g., 192.168.10.100) Runs an iPerf3 client to measure network performance.
6 iPerf3 Server Command ‘Run’ Runs an iPerf3 server to measure network performance.
7 Ping IP address or domain (e.g., 8.8.8.8) Sends ICMP echo requests to the specified address to check connectivity.
8 traceroute IP address or domain (e.g., 8.8.8.8) Traces the route packets take to reach the specified address.
9 NTP Sync Command ‘Sync’ Synchronizes the system time with the configured NTP server.
10 Download Files File or database identifier Initiates a download of the specified file or database.
11 Restart Power Command ‘Restart’ Restarts the power of the device.
12 Restart Modem Command ‘Restart’ Restarts the modem.
13 Run AT Command Enter AT command Executes the specified AT command on the modem.
14 Show Board Configuration Command ‘Show’ Displays the current board configuration.
15 Show VPN Certificate Name Command ‘Show’ Displays the name of the VPN certificate in use.
16 Switch SIM to Secondary (Takes >2 mins) Command ‘Run’ Switches the active SIM to the secondary SIM card.
17 Send test SMS Phone number (e.g., +911234567890) message text (e.g., "Hello how are you?") Sends a test SMS to the specified phone number.
18 ReadlatestSMS Command ‘Read’ Reads the most recent SMS received by the device.
19 Data Usage From: Start date (YYYY-MM-DD)

To: End date (YYYY-MM-DD)

Displays data usage statistics for the specified date range.
20 Monthly Data Usage Month: Month (e.g., 07)

Year: Year (e.g., 2024)

Displays data usage statistics for the specified month and year.
21 Modem Debug Info Command ‘Read’ Displays debug information for the modem.
22 Scan Network operators (Takes >3 mins) Command ‘Scan’ Initiates a scan for available network operators.
23 Network operator list (First Perform Scan Network Operators) Command ‘Show’ Displays the list of network operators detected in the previous scan.
24 ReadLogFiles Log file identifier Reads and displays the specified log file
25 Enable ssh (Admin) Command ‘Run’ Enables SSH access for the admin user.
26 Disable ssh (Admin) Command ‘Run’ Disables SSH access for the admin user.
27 ClearSIM1Data Command ‘Clear’ Clears data usage statistics for SIM1.
28 ClearSIM2Data Command ‘Clear’ Clears data usage statistics for SIM2.
29 Create Bridge with SW_LAN Network interface identifier Creates a network bridge with the specified interface and SW_LAN.
30 Show Bridge Command ‘Show’ Displays information about the current network bridges.
31 Delete Bridge Command ‘Delete’ Deletes the specified network bridge.
32 Output Any value Displays output for all the above actions.

5.8 SNMP Agent Configuration

The SNMP (Simple Network Management Protocol) Agent Configuration is essential for monitoring and managing network devices, such as routers, from a central management system.

Specification details are given below:

SN Field Name Sample Value Description
1 Enable SNMP Service Enable/Disable Enable this if you want the device to be accessible for SNMP-based monitoring and management.
2 IP Family IPV4 Specifies that SNMP service will operate over IPv4.
3 Port 161 161 is the default and should be used unless there is a specific need to use a different port.
4 System OID 1.3.6.1.4.1.38151 This unique identifier represents the device in the SNMP management system.
5 Name Invendis Router The name used to identify the device in the SNMP management system.
6 Contact Invendis@invendis.co The email address of the person responsible for the device, used for administrative contact.
7 Location Bangalore The physical location of the device.
8 SNMP Version Version-1,

Version-2,

Version-3

Version-1: Basic and outdated, offering no security.

Version-2: An improvement over Version-1 with better performance and some security features.

Version-3: The most secure, offering authentication and encryption (AuthPriv).

9 Security       (for SNMP Version-3) NoAuthNoPriv

AuthNoPriv

AuthPriv

No Authentication, No Privacy

Authentication, No Privacy

Authentication and Privacy

10 Username Ex: admin The username used for SNMP authentication.
11 Authentication Password ******* This password is used to authenticate the SNMP user.
12 Privacy Password ******* This password is used to encrypt SNMP messages.
13 Download MIB File Download Click this to download the MIB file associated with the device’s SNMP configuration.


Click on save tab to save changes.

5.9 Connection Diagnostics

This can ensure that your connection diagnostics application effectively monitors and reports the status of your network connections, providing valuable data for troubleshooting and performance optimization.

This Application works in 3 parts,

1.) General settings

2.) Connection status and management

3.) Application Start/Stop

General settings:

First make configuration changes in this section and save.

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Connection Diagnostics Enable/Disable This option enables or disables the connection diagnostics functionality.
2 Check Interval (in seconds) Value: 120 Specifies how often (in seconds) the diagnostics checks are performed. In this case, every 120 seconds. (min 60 secs)
3 Number of Pings Value: 5 Determines ping requests sent during each check.
4 Ping Packet Size (in Bytes) Value: 56 Defines the size of each ping packet in bytes.
5 Send to remote MQTT Broker Enable/Disable This option enables the sending of diagnostic data to a remote MQTT broker.
6 Publish Data Format CSV / JSON Specifies the format in which the diagnostic data will be published to the MQTT broker. You can choose either CSV (Comma-Separated Values) or JSON (JavaScript Object Notation).
7 MQTT Broker url Value: broker.hivemq.com The URL of the MQTT broker where the diagnostic data will be sent.
8 TCP port Value: 1883 The TCP port used to connect to the MQTT broker. Port 1883 is the default port for MQTT.
9 Topic Value: 37A26230014/connectionDiagnostics The MQTT topic under which the diagnostic data will be published. This topic is used to categorize and identify the data.


Connection status and management:

To setup a connection,

Click on ‘Add new target’

Enter Target IP (Ex: 8.8.8.8)

Click ‘Add’

Target has been added successfully.

Application Start/Stop:

To check whether the target Ip is sending and receiving packets, you need to start the application to see the desired output.

As shown above, our target Ip is sending packets successfully.

You can Add as many target IP’s you need to monitor.

You can leave the application on for monitoring else ‘Stop’ the application.

5.10 Package Manager

A Package Manager is a tool or interface used to manage software packages (applications, libraries, tools) on a system.

The package manager interface you are looking at likely allows you to manage the software installed on your device, such as networking tools, firmware, or other applications relevant to your system.

This section has 3 sub-sections,

Installed APP

Available APP

Manual Upgrade

Installed APP:

When you select Installed APP, you will see all the software that is actively running or installed on the device.

This could include system utilities, network management tools, monitoring software, or any third-party apps that were previously installed.

Common Actions:

  • View Details: You can check each application's version, source, and installation date.
  • Uninstall: You can remove applications that are no longer needed.
  • Check for Updates: You can see if there are updates available for any installed application.


Available APP:

When you select Available APP, you will see a list of software that can be installed from the system's repositories or sources.

These applications are not yet installed but are ready for installation if needed.


Common Actions:

  • Install: You can install any of the available applications by selecting them.
  • View Details: You can review each application's description, version, and functionality before installing.
  • Search: You can search for specific apps by name or category.


Manual Upgrade:

In contrast to automatic updates, Manual Upgrade lets you take control over which packages or applications you want to upgrade and when.

This can be useful if you need to avoid upgrading certain apps due to compatibility or testing purposes, or if you want to perform updates at a specific time.

Common Actions:

  • Check for Updates: The system will check for available updates for installed apps.
  • Select Updates: You can select which packages to update manually.
  • Upgrade Now: You can start the upgrade process immediately for selected apps.


6.Configuration

These are gateway features that can be configured as per requirements.

It is divided into 5 sections,

1.) Source Configuration

2.) Send Configuration

3.) Port Configuration

4.) Cloud Configuration

5.) Modbus Configuration

6.1 Source Configuration

These configurations ensure that the system regularly acquires data from various interfaces at specified intervals, allowing for efficient monitoring and management of connected devices and sensors.

Specification details are given below:

SN Field Name Sample Value Description
1 Enable RS485Line1 Enable/Disable This option enables the RS485 Line 1 interface for energy meter readings.
2 Overall Periodicity of RS485 Line 1 Energy meter Readings (In Seconds >= 60) Value: 120 Defines the interval in seconds at which readings are taken from the RS485 Line 1 energy meter. The minimum allowable interval is 60 seconds.
3 Delay between each Energy meter Readings (in Milliseconds) Value: 2000 Specifies the delay in milliseconds between individual readings from the energy meter on RS485 Line 1.

Click on save once changes have been made.

6.2 Send Configuration

Send configuration allows to choose type of string that should be sent to a cloud platform.

SILBO devices do offer 3 different options as shown below.

CSV (CSV allows fixed CSV)

Fixed JSON

Editable JSON. (JSON option is the editable JSON option)

Data sender Configuration is divided into major 2 parts,

JSON

CSV

JSON is further divided into 1 category,

Modbus Sender:

Select the field input you wish to add from the ‘Field Content tab’.

Give a desired JSON Key Name you wish to publish in the ‘Field JSON Key Name’ tab.

Once configured, click on Add.

JSON option allows editable JSON in which we can change which parameters should be sent and what name we should use to the tag.

What changes we can do in JSON edit to the above list.

Let’s change slave_id to some other name as “Slave number”.


Even custom fields can be added, for example if location name should be sent by router/gateway in JSON packet then it can be configured as shown.

CSV:

This option sends data packets in CSV (Comma-Separated Values) format.

Specification details are given below:

SN Field Name Sample Value Description
1 Device ID GRD44B-5R A unique identifier for the device.
2 Record Start Mark [ This character marks the beginning of a data record. It's used to indicate where a new data record starts in the transmitted packet.
3 Record End Mark ] This character marks the end of a data record. It signals the end of the data for one record before a new one starts.
4 Register Start Mark < This character marks the beginning of a register within a data record. A register typically represents an individual data field within the record.
5 Register End Mark > This character marks the end of a register within a data record. It indicates where the data for a particular field end.
6 Invalid Data Character N Used to indicate that the data for a particular register is invalid or could not be collected. This helps in identifying which data points are not usable.
7 Failure Data Character NA Used to indicate that there was a failure in collecting or processing the data for a particular register. It signifies that an error occurred, and the data point could not be obtained.

Click on save once changes are made.

6.3 Port Configuration

Serial port configuration involves setting parameters for serial communication, allowing data exchange between devices via serial ports.

Port Configuration is divided into 4 port mode,

Transparent Serial to Remote TCP Client

Transparent Serial to Remote TCP Server

Modbus TCP Master to Modbus RTU Slave

Modbus RTU Master to Modbus TCP Slave

Transparent Serial to Remote TCP Client:

Specification details are given below:

SN Field Name Sample Value Description
1 Port Mode Transparent Serial to Remote TCP Client Configures the serial port to send data directly to a remote TCP client without any additional protocol layers, making it "transparent."
2 Transparent Serial Port Mode 1.) raw

2.) rawlp

3.) telnet

4.) off

1.) It's a straightforward data transfer where the serial data is sent as-is.

2.) "Rawlp" stands for "raw with local processing". Typically, it involves some minimal local processing before transmission.

3.) This allows the serial connection to be accessed and managed over a Telnet session.

4.) The "off" mode disables the transparent serial port functionality.

3 Time Out no time out Ensures that the serial port does not time out, meaning it will continuously wait for data without closing the connection due to inactivity.
4 Local Listener TCP Port 3040 Sets the TCP port number to 3040 for the local listener to accept incoming TCP connections.
5 Baud Rate 9600 This is a common baud rate for serial communication, balancing speed and reliability.
6 No Of Stopbits 1 Configures the serial communication to use 1 stop bit, which is a common setting ensuring the end of each byte is clearly marked.
7 No Of Databits 8 Sets the number of bits in each transmitted byte to 8.
8 Parity 1.) None

2.) Even

3.) Odd

4.) Space

5.) Mark

1.) No parity bit is added to the data byte.

2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.

3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.

4.) The parity bit is always set to 0, regardless of the data.

5.) The parity bit is always set to 1, regardless of the data.

9 Flow Control 1.) RTSCTS

2.) NONE

3.) DTRDSR

4.) XONXOFF

1.) Request to Send / Clear to Send

2.) No flow control is used.

3.) Data Terminal Ready / Data Set Ready

4.) Software flow control using specific control characters (XON and XOFF) to manage data flow.

10 Read Trace Enable/Disable Enables logging of data being read from the serial port.
11 Write Trace Enable/Disable Enables logging of data being written to the serial port.

Click on save once configuration changes are made.


Transparent Serial to Remote TCP Server:

Configures the port to act as a bridge, converting serial data into TCP packets sent to a remote TCP server.

Specification details are given below:

SN Field Name Sample Value Description
1 Port Mode Transparent Serial to Remote TCP Server Defines how the serial port will operate in relation to the remote server.
2 Remote Server IP Ex: 192.168.10.1 Field must not be empty: This is a required field, and you must provide a valid IP address for proper communication.
3 Remote Server Port Ex: 1883 Field must not be empty: This is a required field, and you must specify the correct port number used by the server.
4 Transparent Serial Port Mode 1.) raw

2.) rawlp

3.) telnet

4.) off

1.) It's a straightforward data transfer where the serial data is sent as-is.

2.) "Rawlp" stands for "raw with local processing". Typically, it involves some minimal local processing before transmission.

3.) This allows the serial connection to be accessed and managed over a Telnet session.

4.) The "off" mode disables the transparent serial port functionality.

5 Time Out no time out Ensures that the serial port does not time out, meaning it will continuously wait for data without closing the connection due to inactivity.
6 Local Listener Interface IP Address Field must not be empty: This is a required field for specifying which local IP address will be used for listening.
7 Local Listener TCP Port 3040 The TCP port number on the local device that will be used to listen for incoming data.
8 Baud Rate 9600 Standard baud rate, common for many serial devices.
9 No Of Stopbits 1 Indicates that one stop bit is used, which is standard for most serial communications.
10 No Of Databits 8 Indicates that 8 data bits are used per byte, which is a common setting.
11 Parity 1.) None

2.) Even

3.) Odd

4.) Space

5.) Mark

1.) No parity bit is added to the data byte.

2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.

3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.

4.) The parity bit is always set to 0, regardless of the data.

5.) The parity bit is always set to 1, regardless of the data.

12 Flow Control 1.) RTSCTS

2.) NONE

3.) DTRDSR

4.) XONXOFF

1.) Request to Send / Clear to Send

2.) No flow control is used.

3.) Data Terminal Ready / Data Set Ready

4.) Software flow control using specific control characters (XON and XOFF) to manage data flow.

13 Read Trace Enable/Disable Option to enable tracing of incoming data from the serial port, useful for debugging.
14 Write Trace Enable/Disable Option to enable tracing of outgoing data from the serial port, useful for debugging.

Click on save once configuration changes are made.


Modbus TCP Master to Modbus RTU Slave:

Configures the serial port to function as a Modbus TCP Master that communicates with a Modbus RTU Slave over the serial connection.

This setup is used to send Modbus TCP commands to a Modbus RTU device via a serial-to-TCP gateway.

Specification details are given below:

SN Field Name Sample Value Description
1 Port Mode Modbus TCP Master to Modbus RTU Slave This setup is used to send Modbus TCP commands to a Modbus RTU device via a serial-to-TCP gateway.
2 Baud Rate 9600 The speed at which data is transmitted over the serial connection.
3 Parity 1.) None

2.) Even

3.) Odd

1.) No parity bit is used, meaning no additional error-checking bits are included.

2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.

3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.

4 No of Stopbits 1 Indicates that one stop bit is used, which is standard for most serial communications.
5 No of Databits 8 Indicates that 8 data bits are used per byte, which is a common setting.
6 Local Listener Interface IP Address Field must not be empty: You need to provide a valid IP address where the TCP connections will be received.
7 TCP Port 502 This is the standard port for Modbus TCP communication.
8 Max. Number of Retries 5 The maximum number of times to retry sending a request if the initial attempt fails.
9 Delay Between Each Request (In milliseconds) 500 The delay between consecutive Modbus requests to avoid overwhelming the system or device.
10 Response Wait Time (In milliseconds) 500 The maximum time to wait for a response from the Modbus RTU Slave before considering the request failed.
11 Connection Timeout (In seconds) 0 A value of 0 typically means no timeout is set, so the system will wait indefinitely.
12 Inactivity Timeout (In seconds) The time to wait before closing a connection if no activity is detected.

Click on save once configuration changes have been made.

Modbus RTU Master to Modbus TCP Slave:

Configures the serial port to function as a Modbus RTU Master that communicates with a Modbus TCP Slave over a network. This setup is used to send Modbus RTU commands from a master device to a Modbus TCP device via a TCP-to-serial gateway.

Specification details are given below:

SN Field Name Sample Value Description
1 Port Mode Modbus RTU Master to Modbus TCP Slave This setup is used to send Modbus RTU commands from a master device to a Modbus TCP device via a TCP-to-serial gateway.
2 Baud Rate 9600 The speed at which data is transmitted over the serial connection.
3 Parity 1.) None

2.) Even

3.) Odd

1.) No parity bit is used, meaning no additional error-checking bits are included.

2.) Ensures that the total number of 1-bits in the data byte plus the parity bit is even.

3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.

4 No of Stopbits 1 Indicates that one stop bit is used, which is standard for most serial communications.
5 No of Databits 8 Indicates that 8 data bits are used per byte, which is a common setting.
6 TCP Slave Address Field must not be empty The IP address of the Modbus TCP Slave device to which the master will send requests.
7 TCP Slave Port Field must not be empty The port number on the Modbus TCP Slave device for receiving Modbus requests.
8 Max. Number of Retries 5 The maximum number of times to retry sending a request if the initial attempt fails.
9 Delay Between Each Request (In milliseconds) Field must not be empty The delay between consecutive Modbus requests to avoid overwhelming the system.
10 Response Wait Time (In milliseconds) 500 The maximum time to wait for a response from the Modbus TCP Slave before considering the request failed.
11 Connection Timeout (In seconds) 0 A value of 0 typically means no timeout is set, so the system will wait indefinitely.
12 Inactivity Timeout (In seconds) Field must not be empty The time to wait before closing a connection if no activity is detected.

Click on save once configuration changes have been made.

6.4 Cloud Configuration

In this section you can select the protocol by which you need to send data to cloud.

There are 3 Cloud/Protocol available,

HTTP

MQTT

Azure

HTTP Cloud/Protocol:

This configuration sets up communication between your device and cloud service using the HTTP cloud.

Specification details are given below:

SN Field Name Sample Value Description
1 Site ID Ex: ‘Site123’ or ‘Device456’. A unique identifier for your site or device within the cloud service.
2 Cloud / Protocol HTTP The protocol used for communication with the cloud service.
3 HTTP URL Example: www.httpbin.org/post The endpoint URL of the cloud service where data will be sent.
4 HTTP Port (Optional) Leave it blank for the default port. The port number for the HTTP connection. This is optional because the default port for HTTP (80) is used if not specified.
5 Enable Authentication Enable/Disable Enable this if your cloud service requires a username and password.
6 Username Example: admin The username for authentication with the cloud service.
7 Password ***** The password for authentication with the cloud service.
8 Enable Server Response Validation Enable/Disable Enable this if you need to verify that the server's response is valid.
9 Server Response Ex: RecordID or custom A unique identifier for the record being sent to the cloud service.
10 Method 1.) Post

2.) Get

1.) The HTTP method used for sending data to the cloud service.

2.) The HTTP method used for requesting data from the cloud service.

MQTT Cloud/Protocol:

This configuration sets up communication between your device and a cloud service using the MQTT protocol.

Specification details are given below:

SN Field Name Sample Value Description
1 Site ID Example: ‘Site123’ or ‘Device456’. A unique identifier for your site or device within the cloud service.
2 Cloud / Protocol MQTT The protocol used for communication with the cloud service.
3 MQTT Host Example: broker.hivemq.com The MQTT broker's address (hostname or IP address) that the device will connect to for sending and receiving messages.
4 MQTT Port Example: 1883 This is the default port for unencrypted MQTT connections.
5 Authentication Mode 1.) No Authentication

2.) Username/Password

3.) TLS

1.) Connect to the broker without any credentials.

2.) The Username/Password for authentication with the cloud service.

3.) Upload TLS certificates only if TLS authentication is selected as shown in the above image.

6 Enable Publish Over LAN Enable/Disable When enabled, the device will also publish MQTT messages over the local area network (LAN).
7 RS485 Topic (Optional) Example: RS485Data1 The MQTT topic for publishing RS485 data.
8 Command Request Topic (Optional) Example: CommandRequest1 The topic to which the device listens for command requests. Leave it blank if not in use.
9 Command Response Topic (Optional) Example: CommandResponse1 The topic on which the device publishes responses to commands. Leave it blank if not in use.

Click on save once configuration changes have been made.


Azure:

This configuration sets up the connection to Azure IoT Hub using either MQTT or HTTP protocols with a specified connection string.

Specification details are given below:

SN Field Name Sample Value Description
1 Site ID Example: ‘Site123’ or ‘Device456’. A unique identifier for your site or device within the cloud service.
2 Cloud / Protocol Azure The cloud service and protocol used for communication.
3 Protocol 1.) MQTT

2.) HTTP

1.) A lightweight messaging protocol suitable for IoT devices.

2.) A protocol used for communication over the web, commonly used for RESTful services.

4 Connection String e.g., invendis-iot-hub.azure-devices.net. The primary or secondary key used to authenticate the device with the IoT Hub.

Click on save once configuration changes have been made.

6.5 Modbus Configuration

Modbus Configuration involves setting up communication parameters for Modbus devices, including baud rate, parity, stop bits, data bits, TCP/RTU settings, and timeout/retry settings for reliable data exchange.

Click on “Add Device” to start a new configuration.

This Configuration has 4 sections,

1.) Parameter Configuration

2.) Block Config

3.) Register Config

4.) Alarm/Event Config

Parameter Configuration:

As shown in the image below, there are two types of protocol used in Modbus configuration.

1.) RTU (Remote Terminal Unit)

2.) TCP (Transmission Control Protocol)

Details of both protocols is mentioned in the specification table.


Modbus Protocol: RTU

Specification details are given below:

Modbus protocol: RTU
1 DEVICE NAME Ex: Invendis This is the name assigned to the Modbus device for identification purposes.
2 Baud rate 300 | 1200 | 1800 | 2400 | 4800 | 19200 | 38400 | default: 9600 The baud rate determines the communication speed between devices, measured in bits per second.
3 Parity 1.) NONE

2.) ODD

3.) EVEN

1.) No parity bit is added to the data byte.

2.) Ensures that the total number of 1-bits in

the data byte plus the parity bit is even.

3.) Ensures that the total number of 1-bits in the data byte plus the parity bit is odd.

4 Meter ID 1 The Meter ID is a unique identifier for the specific meter within the network. Each Modbus device on the network must have a unique ID to differentiate it from others.
5 Meter Model Example: abcd This field specifies the model of the meter.
6 Port number RS485 Port-1 This specifies which RS485 port on the device is being used for communication.
7 Slave Address Example: 1 The slave address identifies the specific slave device on the Modbus network. Each slave must have a unique address so that the master can communicate with it individually.
8 No. of Databits 7/8 Indicates that 8 data bits are used per byte, which is a common setting.
9 No. of Stopbits 1/2 Configures the serial communication to use 1 stop bit, which is a common setting ensuring the end of each byte is clearly marked.

Modbus Protocol: TCP

Specification details are given below:

Modbus protocol: TCP
1 DEVICE NAME Ex: Invendis This is the name assigned to the Modbus device for identification purposes.
2 Modbus Comm IP Ex: 192.168.10.147 IP of the device you are communicating with.
3 Modbus Comm Port Ex: 502 (default) Give a specified TCP port number
4 Modbus Comm Timeout Ex: 60 This refers to the maximum amount of time the master device will wait for a response from a slave device before it assumes a communication failure.
5 Meter ID 1 The Meter ID is a unique identifier for the specific meter within the network. Each Modbus device on the network must have a unique ID to differentiate it from others.
6 Meter Model Example: abcd This field specifies the model of the meter.
7 Slave Address Example: 1 The slave address identifies the specific slave device on the Modbus network. Each slave must have a unique address so that the master can communicate with it individually.


Block Config:

Specification details are given below:

SN Field Name Sample Value Description
1 Funtion Code read coils (1)

read input coils (2)

read holding registers (3)

read input registers (4)

The function code indicates the operation to be performed. In Modbus, each operation has a specific function code.
2 Start Register Example: 0 The start register indicates the address of the first register to be read in the slave device.
3 Register Count Example: 10 This specifies the number of consecutive registers to read starting from the start register.

Click on “Add Block” below to add another set of parameters.


Register Config:

In this section you can add multiple parameters to read in ‘Default Mapping’ & ‘Custom Mapping’ field.


*Refer the image below*

SN Field Name Sample Value Description
1 Default mapping 1.) Tag Name = (Ex: FQ)

2.) Data type = Hexadecimal; Floating point | Floating point (Swapped Byte) | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit UINT (byte order 1,2,3,4) | 32bit UINT (byte order 4,3,2,1) | 32bit INT (byte order 1,2,3,4) | 32bit INT (byte order 4,3,2,1)

1.) Input value name.

2.) Defines how read data will be stored.

2 Custom mapping 1.) Register name:

2.) Start register:

3.) Register count:

4.) Data type = Hexadecimal; Floating point | Floating point (Swapped Byte) | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit UINT (byte order 1,2,3,4) | 32bit UINT (byte order 4,3,2,1) | 32bit INT (byte order 1,2,3,4) | 32bit INT (byte order 4,3,2,1); 1 bit

1.) Input value name.

2.) First register in custom register block.

3.) Path to file in which the custom register block will be stored.

4.) Defines how read data will be stored.


In Register Config,

Click on ‘Add’ to add new parameters.

Click on ‘Show JSON’ to view an example value of how the data will be presented.

Click on ‘Add Device’ once configuration changes have been made.

Alarm/Event Config:

Specification details are given below:

SN Field Name Sample Value Description
1 Category 1.) Alarm

2.) Event

Alarm: Specifies that the configuration is for an alarm, which typically triggers when certain conditions are met.

Event: Specifies that the configuration is for an event, which might log information or trigger actions without necessarily being an alarm.

2 Status 1.) Enabled

2.) Disabled

Enabled: Activates the alarm or event, making it operational.

Disabled: Deactivates the alarm or event, making it non-operational.

3 Name Ex: vtg The name or identifier for the alarm/event.
4 Function code read coils (1)

read input coils (2)

read holding registers (3)

read input registers (4)

These function codes are typically based on the Modbus protocol, indicating what type of data is being monitored.
5 Start Register Ex: 0 The address of the first register to monitor.
6 No_of Reg Ex: 10 The number of consecutive registers to monitor from the starting register.
7 Data Type Hexadecimal; Floating point | Floating point (Swapped Byte) | 16bit INT, high byte first | 16bit INT, low byte first | 16bit UINT, high byte first | 16bit UINT, low byte first | 32bit UINT (byte order 1,2,3,4) | 32bit UINT (byte order 4,3,2,1) | 32bit INT (byte order 1,2,3,4) | 32bit INT (byte order 4,3,2,1); Boolean Provides options for the type of data being monitored, such as integer, float, Boolean, etc.
8 Upper Thresh/

Alarm Value

Ex: 2 The value at which the alarm is triggered if the monitored parameter exceeds this upper threshold.
9 Upper Hys Ex: 2 This value is subtracted from the upper threshold to set the point at which the alarm resets, preventing rapid toggling.
10 Lower Thresh Ex: 2 The value at which the alarm is triggered if the monitored parameter falls below this lower threshold.
11 Lower Hys Ex: 1 This value is added to the lower threshold to set the point at which the alarm resets, preventing rapid toggling.

Click on “Add Alarm” to add another Alarm/Event.

Click on ‘Show JSON’ to view an example value of how the data will be presented.

Click on ‘Add Device’ once configuration changes have been made.

7. Appmanager

Appmanager is a system utility that manages the installation, configuration, and execution of software applications on a device.

This section is divided into 6 categories,

  • Application Start/Stop
  • Application Software Upgrade
  • Modbus Utility Configuration
  • Import/Export Application Configurations
  • App Health Status
  • IO Utilities

7.1 Application Start/Stop

All changes made in ‘Configuration’ section should be saved into backend and to do that navigate to Appmanager >> Application Start/Stop.

Click on update to save all the changes made in configuration section.

Once updated click on start.

Make sure application is started to send data to cloud, once started it can be seen start option is replaced by Stop as shown above.

7.2 Application Software Upgrade

In this section you can upgrade software manually or automatically.

For auto upgrade, enable auto upgrade tab,

This is further divided into 2 sections,

Client and server settings

Auto Upgrade Interval

Specification details are given below:

Client and server settings
SN Field Name Sample Value Description
1 Authentication Enable/Disable Enable if username/password is required.
2 Username XXXX The username required to authenticate with the server.
3 Password XXXX The password required to authenticate with the server.
4 Server address ftp://XXXX The URL or IP address of the server where the upgrade files are located.
5 Connection timeout Ex: 180 The maximum time (in seconds) the system will wait to establish a connection with the server before timing out.
6 Operation timeout Ex: 240 The maximum time (in seconds) the system will wait for the upgrade operation to complete before timing out.
Auto Upgrade Interval
SN Field Name Sample Value Description
1 Minutes Example: 56 Set the minute part of the interval when the auto-upgrade check will occur
2 Day Of Month Example: all Specifies the days of the month when the auto-upgrade check should occur.
3 Month Example: all Specifies the months during which the auto-upgrade check should occur
4 Day Of Week Example: all Specifies the days of the week when the auto-upgrade check should occur.

You can also check the current software version and manually upgrade software as shown below.


To Manually upgrade Application,

Enter the correct ‘Checksum’ and ‘Size’ and upgrade the page.

(Please stop the applications before upgrading)

7.3 Modbus Utility Configuration

Any changes to be made in Modbus Configuration to test can be made in Modbus Utility Configuration without disturbing the actual Modbus Configuration.

The working process of ‘Modbus Configuration’ and ‘Modbus Utility Configuration’ are same.

Refer (6.5 Modbus Configuration) for specification details.

Click on save once configuration changes have been made.

7.4 Import / Export Gateway Configuration

This functionality ensures that you can easily manage, back up, and restore device gateway

configurations, as well as reset the device to default settings when needed.

Export Config:

Usage: Click the "Export Config" button to save the current configuration to a file.


Import Config:

Usage: Click the "Import Config" button and select the text file containing the configuration you want to import.


Reset Config:

Usage: Click the "Reset Config" button to revert the device to its default configuration settings.

7.5 App Health Status

This section provides utilities to check the health and status of various applications and data inputs

within the system. It allows monitoring of the last data produced and sent times for different utilities, as

well as the running status of applications.

*Refer the image below*

Specification details are given below:

SN Field Name Sample Value Description
1 Energymeter Last Data Produced Time Command ‘Read’ Displays the last time data was produced by the energymeter.
2 DIO Last Data Produced Time Command ‘Read’ Displays the last time data was produced by the digital input/output system.
3 Energymeter Last Data Sent Time Command ‘Read’ Displays the last time data from the energymeter was sent.
4 App Running Status Command ‘Read’ Displays the current running status of applications.
5 Download Files Command ‘Download’ Choose the desired option from the dropdown menu.

Download data or logs related to the options available.

6 Output Display Value Provides output or feedback based on selected utilities.


7.6 IO Utilities

This section provides output of various utilities connected to the device.

This section exactly shows whether the connection made is successful or not.


*Refer the image below*

Specification details are given below:

SN Field Name Sample Value Description
1 Modbus Utility Input: Slave ID Action: Manage RS485 energy meters by specifying the slave ID. (Read/Write)
2 Output Print any values Action: Will display the results or status messages based on the actions performed using the utilities.

8.Logout

The user should click on log out option to logged out from the router application.