RD44 A Manual: Difference between revisions

From Silbo Networks
VisualWikitext
No edit summary
No edit summary
 
(14 intermediate revisions by the same user not shown)
Line 35: Line 35:
Once the user credentials are provided it will direct to the landing page of the application.
Once the user credentials are provided it will direct to the landing page of the application.


[[File:RB44 Dashboard.png|1024x1024px]]
[[File:RD44A Dashboard.png|1024x1024px]]
 
 
 
 


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.
Line 63: Line 59:
* Kernel Log
* Kernel Log


[[File:RB44 Info.png|1024x1024px]]
[[File:RD44 Info.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:RB44 Dashboard.png|1024x1024px]]
[[File:RD44A Dashboard.png|1024x1024px]]


'''System'''
'''System'''
Line 74: Line 70:
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:RB44 System Section.png|1024x1024px]]
[[File:RD44A System.png|1024x1024px]]
 




Line 86: Line 83:
|1
|1
|Hostname
|Hostname
|31B30241002
|45A27240002
|This field  displays the router serial number of the device
|This field  displays the router serial number of the device
|-
|-
|2
|2
|Model
|Model
|Silbo_RB44- EC200A
|Silbo_RD44-A- EC200A
|This field  displays the model number of the device
|This field  displays the model number of the device
|-
|-
Line 106: Line 103:
|5
|5
|Local Time
|Local Time
|Tuesday, December 3, 2024 at 11:26:32 AM
|Thursday, December 5, 2024 at 04:05:24 PM
|This field  displays the local time
|This field displays the local time
|-
|-
|6
|6
|Uptime
|Uptime
|0h 3m 10s
|0h 3m 58s
|This field  displays the uptime of the device
|This field  displays the uptime of the device
|-
|-
|7
|7
|Load Average
|Load Average
|2.47 2.24 2.06
|1.03 0.98 0.44
|This field  displays the average load
|This field  displays the average load
|}
|}
Line 272: Line 269:
[[File:RB44 Network Settings.png|1020x1020px]]
[[File:RB44 Network Settings.png|1020x1020px]]


'''Ethernet Setting:'''
'''Relay Server:'''


In this page it will display all the configured port that is attached with the device.
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.


For this device 5 ports are configured.  
[[File:RD44A Relay Server.png|1024x1024px]]


Ethernet mode can be configured as WAN and as LAN as well.
'''EDIT:'''


Ethernet WAN Connection settings can be configured as DHCP, Static and PPOE.  
To edit the existing device the user needs to click on the edit option.


[[File:RB44 Ethernet Settings.png|1020x1020px]]
Once the changes are done click on the save button to save all the changes.


'''EDIT:'''
Click on the deleted button to delete the existing device detail.


To add a new Interface, click on ‘Add’.  
[[File:RB44 Relay Server Edit.png|1024x1024px]]


To edit the existing device the user needs to click on the edit option.  
Specification details are given below:
 
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.
 
'''Note: If required, add an interface in Settings-->Multi-WAN-->Failover'''
 
[[File:RB44 EWAN Network Config.png|1020x1020px]]
 
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
|Physical Device
|Interface
|Ex: eth0.5
|1.)    eth0.1
|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.  
2.)    ra0
|1) eth0.1  typically represents a VLAN where the relay will listen for client requests.


LAN: Connects the device to the internal network.  
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.
|-
|-
| colspan="4" |                                                                          '''Protocol: Static'''
|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  
|3
|Static IP Address  
|End IP Address
|Ex: 192.168.1.10
|Ex: 192.168.10.150
|The manually assigned IP address for the interface.
|An IP address that is in the same subnet as the Start IP Address and allows sufficient  addresses to be leased.
|-
|4
|Static Netmask
|Ex: 255.255.255.0
|Subnet mask corresponding to the IP address.  
|-
|-
|5
|4
|Static Gateway
|Netmask
|Ex: 192.168.1.1
|Ex: 255.255.255.0
|The IP address of the gateway (router) that the interface will use to send traffic outside its own subnet.  
|A valid  subnet mask such as 255.255.255.0 (for a /24 network), or 255.255.0.0 (for a  /16 network).
|-
|-
| colspan="4" |                                                                          '''Protocol: DHCP'''
|5
|-
|Lease Time
|6
|For a 24-hour  lease time, set this value to 86400.
|DHCP Gateway
|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.
|Ex: 10.1.1.1
|}
|The IP address of the DHCP server (often the same as the router or gateway).
Save and update.
|-
| colspan="4" |                                                                            '''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
|Override MAC Address
|Ex: D0:93:95:B0:CF:7A
|The MAC address for this interface is set to a custom value, replacing the default hardware address.  
|-
|13
|Enable Bridge
|
# CWAN1_0


# SW_LAN


# VPN
'''Ethernet Setting:'''


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


|Since this is a WAN interface, it is not typically bridged with others. Bridges are more common for LAN interfaces to combine multiple connections.
For this device 5 ports are configured.
|-
|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
|IPv4 Route Table
|Enable/Disable
|This field is used to specify static routes for IPv4.
|-
|16
|Table No.
|'''254''': Default main routing table.  


'''100''': Custom routing table for specific purposes.
Ethernet mode can be configured as WAN and as LAN as well.
|'''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).
Ethernet WAN Connection settings can be configured as DHCP, Static, PPOE, PPTP and L2TP.
|-
|17
|Gateway Metric
|Ex: 1
|A numeric value used to prioritize gateways when multiple are available.  


Lower metrics indicate higher priority. For example, if two gateways exist, the one with the smaller metric is used.
[[File:RD44A Ethernet settings.png|1024x1024px]]
|-
|18
|Broadcast
|Ex: 192.168.123.34
|Broadcast address for the network, typically calculated based on the IP and subnet mask.  
|-
|19
|Override MTU
|Ex: 1500
|MTU size controls the maximum packet size that can be sent over the network.  


Default is usually 1500 bytes.
'''For port 5 setting,'''
|-
|20
|Force Link
|Enable/Disable
|Forces the interface to be up even if no physical link is detected.
|}


'''Type: LAN'''
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:RB44 SW LAN Configuration.png|1024x1024px]]Specification details are given below:


[[File:RD44A Port 5 Settings.png|1024x1024px]]
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample Value
|Sample value
|Description
|Description
|-
|-
|1
|1
|Physical Device
|Port 5 mode LAN/WAN
|Ex: eth0.1
|LAN
|This is the network interface identifier.
|This field displays the port mode selection
|-
|-
|2
|2
|Type
|Port 5 Ethernet Protocol [LAN Eth0.1]
|WAN/'''LAN'''
|DHCP Server
|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.
Static
|This field  displays the  Ethernet mode selection
|-
|-
|3
|3
|Protocol
|Port 5 DHCP Server IP
|Static
 
|This means that the IP address, netmask, and other  network settings are manually configured rather than being automatically  assigned by a DHCP server.
Port 5 Static IP
|192.168.10.1
 
5.6.7.8
|This field displays DHCP server and static IP configured.
|-
|-
|4
|4
|IP Address
|Port 5 DHCP and Static  Netmask
|Ex: 192.168.10.1
|255.255.255.0
|This is the static IP address assigned to the  interface. It acts as the gateway IP address for devices connected to this  LAN.
|This field displays DHCP server and static Netmask address configured
|-
|-
|5
|5
|Static Netmask
|Port 5 DHCP Start Address
|Ex: 255.255.255.0
|100
|This is the subnet mask for the network.
|This field displays DHCP server start address configured
|-
|-
|7
|6
|Override MAC Address
|Port 5 DHCP Limit
|D0:93:95:B0:CF:7B
|50
|This allows you to manually enter a different  MAC address if needed.
|This field displays DHCP server limit
|}
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:RD44A DHCP Settings.png|1024x1024px]]
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|8
|1
|Enable DNS
|Port 5 mode WAN
|Enable/Disable
|EWAN2
|If this option is enabled, the interface will act as a DNS resolver for the devices on the LAN, using the specified DNS  server.
|This field displays the port mode selection
|-
|-
|9
|2
|DNS Server Address
|Ethernet Protocol Port 5  WAN
|Ex: 8.8.8.8
|1.) DHCP client
|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.
 
2.) Static
 
3.) PPPoE


More than one DNS Address can be added.
4.) PPTP
|-
 
|10
5.) L2TP
|Enable DHCP Server
|1.) Automatically obtains IP  address and network configuration from a 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
|50
|The DHCP server will begin assigning IP  addresses starting from 192.168.10.50
|-
|12
|DHCP Limit
|100
|This specifies the number of IP addresses the DHCP server can assign. Starting at 192.168.10.50 and with a limit of 100,  the server can assign addresses up to 192.168.10.149.
|-
|13
|Lease Time Duration
|Hours-(H)


Minutes-(M)
2.) Manually set a fixed IP  address and network configuration.


Seconds-(S)
3.) Point-to-Point Protocol over Ethernet, used for connecting to DSL services.
|'''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.
4.) Point-to-Point Tunnelling Protocol, used for establishing VPN connections.


'''Seconds-(S):''' This indicates that the lease time for each IP address assignment is measured in seconds.
5.) Layer 2 Tunnelling Protocol, another VPN protocol option.
|-
|-
|14
|3
|Lease Time
|Gateway
|12
|192.168.1.1
|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.
|This field displays gateway address  configured
|-
 
|15
|}
|Enable Bridge
Click on the save once all the configuration is done and click on the update button to update all the information.
|1.      CWAN1_0


2.      SW_LAN


3.      VPN
'''SW_LAN settings,'''


4.      ra0
In this part the user can configure the setting for SW_LAN


|Since this is a WAN interface, it is not  typically bridged with others. Bridges are more common for LAN interfaces to  combine multiple connections.
[[File:RD44A SW LAN Settings.png|1024x1024px]]
|-
|16
|Enable DHCP Relay
|Enter Relay Server IP
|Forwards DHCP requests from devices in this  subnet to an external DHCP server instead of using the built-in DHCP server.


The specifications details are below.
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|17
|1
|Create Firewall Zone
|SW_LAN  Ethernet Protocol
|Enable/Disable
|DHCP Server
|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).
|This field displays the Ethernet mode selection
|-
|-
|18
|2
|Internet Over SW_LAN
|SW_LAN DHCP Server IP
|Enable/Disable
|192.168.10.1
|Allow all outbound traffic from the LAN to the internet.
|This field displays DHCP server IP configured.
|-
|-
| colspan="4" |'''Advanced Settings: Enable/Disable'''
|3
|SW_LAN DHCP Netmask
|255.255.255.0
|This field displays DHCP server  Netmask address configured
|-
|-
|19
|4
|IPv4 Route Table
|SW_LAN DHCP Start Address
|Enable/Disable
|100
|This field is used to specify static routes for IPv4.
|This field displays DHCP server start address configured
|-
|-
|20
|5
|Table No.
|SW_LAN DHCP Limit
|'''254''': Default  main routing table.
|50
 
|This field displays DHCP server limit
'''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).
|-
|-
|21
|6
|Gateway Metric
|DNS Server
|Ex: 1
|1
|A numeric value used to prioritize gateways when multiple are available.
|This filed display number of DSN server availability
 
Lower metrics indicate higher priority. For  example, if two gateways exist, the one with the smaller metric is used.
|-
|-
|22
|7
|Broadcast
|DNS Server Address
|Ex: 192.168.123.34
|8.8.8.8
|Broadcast address for the network, typically calculated based on the IP and subnet mask.
|This filed display the DSN server address.
|-
|23
|Override MTU
|Ex: 1500
|MTU size controls the maximum packet size that  can be sent over the network.
 
Default is usually 1500 bytes.
|}
|}
Save and Update once configuration changes have been made.
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.
 


'''Relay Server:'''


A relay server typically functions in a network to forward requests (usually DHCP or DNS) from clients to
'''Static option for SW_LAN Ethernet Protocol:'''


a designated server when the server is on a different network segment.
[[File:RD44A Ethernet Protocol.png|1024x1024px]]
 
[[File:RB44 Relay Server Settings.png|1020x1020px]]
 
'''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:RB44 Relay Server 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
|Interface
|SW_LAN  Ethernet Protocol
|1.)    eth0.1
|Static
 
|This field displays the Ethernet mode selection
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
|Start IP Address
|SW_LAN  static IP
|Ex: 192.168.10.100
|192.168.5.1
|This is the beginning IP address of the range that will be leased out to clients.
|This field displays static server IP configured.
|-
|-
|3
|3
|End IP  Address
|SW_LAN Netmask
|Ex: 192.168.10.150
|255.255.255.0
|An IP address that is in the same subnet as the Start IP Address and allows sufficient  addresses to be leased.
|This field displays static server  Netmask address configured
|-
|-
|4
|4
|Netmask
|DNS Server
|Ex: 255.255.255.0
|1
|A valid subnet mask such as 255.255.255.0 (for a /24 network), or 255.255.0.0 (for a  /16 network).
|This filed display number of DSN server availability
|-
|-
|5
|5
|Lease Time
|DNS Server Address
|For a 24-hour  lease time, set this value to 86400.
|8.8.8.8
|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.
|This  filed display the DNS server address.
|}
|}
Save and update.
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.


'''Cellular Setting:'''
'''Cellular Setting:'''
Line 651: Line 520:
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.
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:RB44 Cellular Setting.png|1020x1020px]]
[[File:RD44A Cellular Settings.png|1024x1024px]]


The specifications details are below.
The specifications details are below.
Line 775: Line 644:
Bands available in the drop-down list.
Bands available in the drop-down list.


[[File:RB44 Band lock and Operator Lock.png|1020x1020px]]
[[File:RD44A Band lock and Operator Lock.png|1024x1024px]]


'''2G/3G option:'''
'''2G/3G option:'''
Line 781: Line 650:
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. While the main function of 2G technology is the transmission of information through voice calls.


[[File:RB44 2G-3G Option.png|1020x1020px]]
[[File:RD44A 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.  
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.  
Line 791: Line 660:
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:RB44 Operator Selection Mode.png|1020x1020px]]
[[File:RD44A 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:RB44 Operator Selection Mode Manual or Manual Automatic Settings.png|1020x1020px]]
[[File:RD44A 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.




Line 986: Line 856:
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, often referred to as “localhost.” it is used to establish network connections within the same device for testing and troubleshooting purpose.


[[File:RB44 Lookback IP Settings.png|1020x1020px]]
[[File:RD44A 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.
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.
Line 994: Line 864:
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.
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.


=== 2.2 VLAN ===
=== 2.2 SIM Switch ===
'''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.
In this page the user needs to configure the Sim for the given device.


It is further divided into 2 sections,
[[File:RB44 SIM Switch Configuration.png|1020x1020px]]


Port-Based VLAN


Tagged Port Configuration


'''Port-Based VLAN:'''
The user needs to select from the drop-down menu on which basis the sim needs to be switched.


A VLAN configuration method where network ports are assigned to specific VLANs.
[[File:RB44 SIM Switch Update.png|1020x1020px]]


[[File:RB44 VLAN Configuration.png|1020x1020px]]
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.


'''EDIT:'''
[[File:RB44 SIM Switch based on Signal Strength.png|1020x1020px]]


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


To edit the existing device the user needs to click on the edit option.
'''Threshold RSRP:'''


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 RSRP value range is -140 to -115 and FAIR RSRP value range is -115 to -105).
 
'''Threshold SINR:'''


Click on the deleted button to delete the existing device detail.
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)


[[File:RB44 VLAN Configuration Editing.png|1020x1020px]]
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.


Specification details are given below:
[[File:RB44 Threshold SINR.png|1020x1020px]]
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample  Value
|Sample  value
|Description
|Description
|-
|-
|1
|1
|'''VLAN ID'''
|SIM Switch Based on
|1
|Data Limit
|This is a unique identifier for a VLAN within a network.
|The user needs to select from the drop-down menu on what basis the sim needs to be switched.
 
|-
|-
|2
|2
|'''Port 0'''
|SIM 1 Data Usage Limit (In MB)
|Untagged
|1000
|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.
|The user needs to  set the limit for the data usage for SIM 1.
|-
|-
|3
|3
|'''Port 1'''
|SIM 2 Data Usage Limit (In MB)
|Untagged
|1000
|
|The user needs to  set the limit for the data usage for SIM 2.
|-
|-
|4
|4
|'''Port 2'''
|Periodicity
|tagged
|Daily
|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.
|The user needs to  set the pattern/frequency to switch the sims.
|-
|-
|5
|5
|'''Port 3'''
|Day Of Month
|Untagged
|16
|
|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.
After configuring all the required information, the user should click on the save.


'''Tagged Port Configuration:'''
=== 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:RB44 Tagged based VLAN.png|1020x1020px]]
[[File:RD44A Internet Settings.png|1024x1024px]]


'''EDIT:'''
If the user needs to edit on the existing configuration, then the user should click on the “EDIT” button.


To add a new VLAN ID, click on ‘Add Device’.
[[File:RD44A Ewan Priority Settings.png|1024x1024px]]


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:RB44 VLAN ID.png|1020x1020px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample  Value
|Sample  value
|Description
|Description
|-
|-
|1
|1
|Type
|Name
|802.1Q
|EWAN2
|'''IEEE 802.1Q''' is the  standard protocol for VLAN tagging in Ethernet networks.
|This field displays the name of the WAN connection
|-
|-
|2
|2
|Parent Interface
|Priority
|Port 2
|1
|It is the underlying physical interface like port 2 that carries the VLAN-tagged traffic.
|In this dropdown box the user needs to select the priority.
|}
|-
Save and update the page.
|3
 
|Select Track IP Numbers
=== 2.2 SIM Switch ===
|2
In this page the user needs to configure the Sim for the given device.
|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.
 
|-
[[File:RB44 SIM Switch Configuration.png|1020x1020px]]
|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.
The user needs to select from the drop-down menu on which basis the sim needs to be switched.
|-
 
|5
[[File:RB44 SIM Switch Update.png|1020x1020px]]
|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.


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.
=== 2.4 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.


[[File:RB44 SIM Switch based on Signal Strength.png|1020x1020px]]
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.


'''Threshold RSRP:'''
Refer the below figure.


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).
[[File:RD44 A VPN Configuration.png|1024x1024px]]


'''Threshold SINR:'''
There are 5 types of setting available under VPN configuration.


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)
* General Settings
* IPSEC
* Open VPN
* Wireguard
* Zerotier
 
'''General Settings:'''
 
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.
 
Click on the save after selecting the option based on its requirement.
 
[[File:RD44A VPN General Settings.png|1024x1024px]]
 
'''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.
 
[[File:RD44A IPsec Dashboard.png|1024x1024px]]
 
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:RB44 Ipsec Edit Options.png|1020x1020px]]
 
Click on update once done with configurations.
 
The tunnel will show established, showing the connection has been made.
 
[[File:VPN Configurtaion IPSEC .png]]


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:RB44 Threshold SINR.png|1020x1020px]]
Detailed specifications are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 1,129: Line 1,050:
|-
|-
|1
|1
|SIM Switch Based on
|IPSEC
|Data Limit
|Site to Site VPN
|The user needs to select from the drop-down menu on what basis the sim needs to be switched.
|In this dropdown the user should select the  IPSEC connection type.
 
|-
|-
|2
|2
|SIM 1 Data Usage Limit (In MB)
|IPSEC Role
|1000
|Client/Server
|The user needs to  set the limit for the data usage for SIM 1.
|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
|3
|SIM 2 Data Usage Limit (In MB)
|Connection Type
|1000
|Tunnel
|The user needs to set the limit for the data usage for SIM 2.
|In this dropdown  the user needs to select the connection type. The user should select on the connection enable check box.
|-
|-
|4
|4
|Periodicity
|Connection mode
|Daily
|Route/add/'''start'''/trap
|The user needs to set the pattern/frequency to switch the sims.
|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
|Day Of Month
|Remote Server IP
|16
|********
|The user needs to  set the day for switching the sim.
|The IP address of the remote VPN server.
|}
|-
After configuring all the required information, the user should click on the save.
|6
 
|Local ID
=== 2.3 Multi-WAN ===
|3.3.3.3
As shown below, this section has 4 categories,
|The user needs to  set the local id. It is the identification for the local VPN client.
 
|-
'''Status'''
|7
 
|No. of local subnets
'''General settings'''
 
'''Failover'''
 
'''Load Balancing'''
 
[[File:RB44 Multi-WAN Configuration.png|1020x1020px]]
 
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:RB44 Failover.png|1020x1020px]]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:RB44 Multi Wan Failover Configuration.png|1020x1020px]]'''EDIT:'''
 
[[File:RB44 WAN Priority settings.png|1020x1020px]]
 
The specifications details are below.
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|1
|1
|Priority
|In this dropdown the user needs to select how many subnets will be connected.
|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
|8
|Select Track IP Numbers
|Local Subnet 1
|2
|172.16.31.25/32
|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 text box  the user needs to put the specific local subnet included in the VPN.
|-
|-
|3
|9
|TrackIP1
|Remote id
|8.8.8.8
|1.1.1.1
|The system will ping this IPV4 IP address to check if the connection is up and working. You can even add any whitelisted IP.
|In this text box the user needs to put the id of the remote connection. It is the identification for the remote VPN server.
|-
|-
|4
|10
|TrackIP2
|No of remote subnet
|8.8.4.4
|1
|The system will ping this IPV4 IP address to check if the connection is up and working.  You can even add any whitelisted IP.
|In this dropdown the user needs to select how many subnets it will be connected remotely.
|-
|-
|5
|11
|Reliability
|Remote subnet
|1
|10.1.1.0/24
|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.
|In this text box the user needs to put the address of the remote subnet. The specific remote subnet included in the VPN.
|-
|-
|6
|12
|Count
|Key exchange
|1
|Ikev1
|Setting Count to 1 means the device will send one ping to each IP address to check for  connectivity.
|In this dropdown the user should select the which key exchange version to be selected.
|-
|-
|7
|13
|Up
|Aggressive
|3
|Yes/No
|If set to 3, the connection will be considered "up" only if all three pings are  successful.
|In this dropdown the user should select either yes or no.
|-
|-
|8
|14
|Down
|IKE Lifetime (In Seconds)
|3
|86400
|If set to 3, the connection will be considered "down" if all three pings fail.
|The lifetime of the IKE phase in seconds (1 day).
|}
|-
Click on save and update tab.
|15
 
|Lifetime (in seconds)
'''Load Balancing:'''
|28800
 
|The lifetime of the IPsec SA (Security Association) in seconds (8 hours).
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:RB44 Multi WAN Load Balancing.png|1020x1020px]]'''EDIT:'''
 
 
[[File:RB44 Multi WAN Load Balancing Editing.png|1020x1020px]]
 
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample  Value
|Description
|-
|-
|1
|16
|Traffic Distribution Ratio
|Enable DPD Detection
|Ex: 60%
|'''1'''
|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.
0
|Indicates whether Dead Peer Detection is  enabled to detect a lost connection. Enable this option as per server-side  settings.
|-
|-
|2
|17
|Select Track IP Numbers
|Time Interval (In Seconds)
|2
|60
|The system  will track two IP addresses to determine if the network connection is active  and reliable.
|This option is available only if DPD  Detection is enabled. The time interval is the interval for DPD checks.
|-
|-
|3
|18
|TrackIP1
|Action
|8.8.8.8
|'''Restart'''/clear/hold/
|The system will ping this IPV4 IP address to check if the connection is up and working.  You can even add any whitelisted IP.
 
trap/start
|'''Restart''': Action to take when DPD detects a lost connection (restart the connection).  Select as per server-side setting.
|-
|-
|4
|19
|TrackIP2
|Authentication Method
|8.8.4.4
|'''PSK'''
|The system will ping this IPV4 IP address to check if the connection is up and working.  You can even add any whitelisted IP.
|'''PSK''': Pre-shared key is used for authentication. Select this option for authentication as per sever side setting.
|-
|-
|5
|20
|Reliability
|Multiple Secrets
|1
|1/'''0'''
|With a reliability setting of 1, the connection might be considered reliable if at  least one ping is successful.
|Indicates whether multiple PSK secrets are used. Enable only if required.
|-
|-
|6
|21
|Count
|PSK Value
|1
|******
|The system will send one ping to each tracked IP to check the connection's status.
|Pre-shared key value (masked for security).
|}
{| class="wikitable"
| colspan="7" |'''Proposal settings Phase I'''
|-
|-
|7
|22
|Up
| colspan="2" |'''Encryption Algorithm'''
|3
| colspan="3" |AES 128
|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.


AES 192


=== 2.4 VPN ===
'''AES 256'''
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.
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


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


Refer the below figure.
SHA 256


[[File:VPN Configuration Dashboard.png|1020x1020px]]
SHA 384


There are 5 types of setting available under VPN configuration.
'''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.
* IPSEC
|-
* Open VPN
|24
* Wireguard
| colspan="2" |DH Group
* Zerotier
| colspan="3" |MODP768(group1)
* PPTP
* L2TP


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


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.
MODP1536(group5)


[[File:RB44 VPN General Settings.png|1020x1020px]]
'''MODP2048(group14)'''


'''IPSEC:'''
MODP3072(group15)


IPSEC VPN is used to create a VPN connection between local and remote networks.
MODP4096(group16)
|'''MODP2048 (group14)''':  Diffie-Hellman group for key exchange.


To use IPSEC VPN, the user should check that both local and remote routers support IPSEC VPN feature.
Select as per  server-side configuration. Both server and client should have same  configuration.
|-
| colspan="7" |'''Proposal settings Phase II'''
|-
| colspan="2" |25
| colspan="2" |Hash Algorithm
|AES 128


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


[[File:IPSec Config.png|1020x1020px]]
'''AES 256'''


The user needs to click on the update button once the required configuration is completed.
3DES
| 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


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


[[File:RB44 Ipsec Edit Options.png|1020x1020px]]
SHA 256


Click on update once done with configurations.
SHA 384


The tunnel will show established, showing the connection has been made.
'''SHA 512'''
| colspan="2" |'''SHA 512''': Authentication  algorithm for Phase II.


[[File:VPN Configurtaion IPSEC .png]]
Select as per  server-side configuration. Both server and client should have same  configuration.
|-
| colspan="2" |27
| colspan="2" |PFS Group
|MODP768(group1)


MODP1024(group2)


Detailed specifications are below:
MODP1536(group5)
{| class="wikitable"
 
|SN
'''MODP2048(group14)'''
|Field name
 
|Sample value
MODP3072(group15)
|Description
 
|-
MODP4096(group16)
|1
| colspan="2" |'''MODP2048 (group14)''': Perfect  Forward Secrecy group.
|IPSEC
 
|Site to Site VPN
Select as per  server-side configuration. Both server and client should have same configuration.
|In this dropdown the user should select the IPSEC connection type.
|}
|-
'''Open VPN:'''
|2
 
|IPSEC Role
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.
|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).
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.
|-
 
|3
[[File:RD44A Open VPN Dashboard.png|1024x1024px]]
|Connection Type
 
|Tunnel
The user needs to “upload” the respective certificate from a valid path and then click on the “Update.”
|In this dropdown  the user needs to select the connection type. The user should select on the connection enable check box.
 
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.
 
[[File:RD44A Open VPN Status.png|alt=RD44A Open VPN Status|1024x1024px]]
 
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:RD44A Wireguard.png|1024x1024px]]
 
EDIT:
 
[[File:RD44 A Wirguard Config.png|1024x1024px]]
 
Click on the save button after the required configuration.
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|4
|1
|Connection mode
|Wireguard Role
|Route/add/'''start'''/trap
|Client/Server
|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.
|In this dropdown box the user needs to select  the wireguard role.
|-
|-
|5
|2
|Remote Server IP
|Listen Port
|********
|51820
|The IP address of the remote VPN server.
|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
|Allowed PeerIPs
|10.1.1.1
|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.
|-
|5
|Endpoint HostIP
|10.1.1.1
|The IP address of the WireGuard server (the endpoint to which the client connects).
|-
|-
|6
|6
|Local ID
|Endpoint HostPort
|3.3.3.3
|51820
|The user needs to set the local id. It is the identification for the local VPN client.
|The port on the WireGuard server to which the client connects.
|-
|-
|7
|7
|No. of local subnets
|PeerPublicKey
|1
|*****
|In this dropdown the user needs to select how many subnets will be connected.
|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.
|-
|-
|8
|8
|Local Subnet 1
|Enable Preshared key
|172.16.31.25/32
|Yes/No
|In this text box the user needs to put the specific local subnet included in the VPN.
|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.
|-
|-
|9
|9
|Remote id
|Preshared key
|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.
|The actual pre-shared key value shared between the client and the server. This option  appears only if you have enabled preshared key.
|-
|}
|10
Save and update the page after configuration has been done.
|No of remote subnet
 
|1
 
|In this dropdown the user needs to select how many subnets it will be connected remotely.
'''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.
 
[[File:RD44A Zero Tier .png|1024x1024px]]
 
Copy and paste the unique 16-digit network ID in the edit section.
 
[[File:RD44A 16 digit network ID Update.png|1024x1024px]]
 
[[File:RD44 A Zerotier Unique ID.png|1024x1024px]]
 
 
Click on the save button after the required configuration.
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|11
|1
|Remote subnet
|NetworkID
|10.1.1.0/24
|Ad2769hfkw2345f4
|In this text box the user needs to put the address of the remote subnet. The specific  remote subnet included in the VPN.
|In this dropdown  box the user needs to paste the unique 16-digit network id.
|-
|-
|12
|2
|Key exchange
|Listen Port
|Ikev1
|9993
|In this dropdown  the user should select the which key exchange version to be selected.
|Default
|-
 
|13
|}
|Aggressive
=== 2.5 Firewall ===
|Yes/No
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.
|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
[[File:RB44 Firewall Config.png|1024x1024px]]
|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
There are 6 types of setting available under firewall.
|'''Restart''':  Action to take when DPD detects a lost connection (restart the connection).  Select as per server-side setting.
 
|-
* General Settings
|19
* Port forwards
|Authentication Method
* Traffic Rules
|'''PSK'''
* SNAT traffic Rules
|'''PSK''': Pre-shared  key is used for authentication. Select this option for authentication as per  sever side setting.
* Parental Control
|-
* Zone Forwarding
|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="7" |'''Proposal settings Phase I'''
|-
|22
| colspan="2" |'''Encryption Algorithm'''
| colspan="3" |AES 128


AES 192
'''General Settings:'''


'''AES 256'''
General settings are subdivided into 2 parts,


3DES
'''1.) General settings'''
|'''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
In general settings, the settings that are made are default settings and can be changed according to user’s preference.


SHA 256
[[File:RB44 Firewall General Settings.png|1024x1024px]]


SHA 384
Specification details are below:
 
{| class="wikitable"
'''SHA 512'''
|'''SN'''
|'''SHA 512''': Authentication algorithm for Phase I.
|'''Field  Name'''
 
|'''Sample Value'''
Select as per server-side configuration. Both server and client should have same configuration.
|'''Description'''
|-
|1
|Enable SYN-flood protection
|Enabled
|This is enabled by default; setting can be changed if required.
|-
|-
|24
|2
| colspan="2" |DH Group
|Disable IPV6
| colspan="3" |MODP768(group1)
|Disabled
 
|This is  enabled by default; setting can be changed if required.
MODP1024(group2)
|-
 
|3
MODP1536(group5)
|Drop invalid packets
 
|Disabled
'''MODP2048(group14)'''
|This is  enabled by default; setting can be changed if required.
 
|-
MODP3072(group15)
|4
 
|TCP SYN Cookies
MODP4096(group16)
|Disabled
|'''MODP2048 (group14)''':  Diffie-Hellman group for key exchange.
|This is  enabled by default; setting can be changed if required.
 
|-
Select as per server-side configuration. Both server and client should have same configuration.
|5
|Input
|Reject/Accept
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|-
|-
| colspan="7" |'''Proposal settings Phase II'''
|6
|Output
|Reject/Accept
|By  default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’  compulsory.
|-
|-
| colspan="2" |25
|7
| colspan="2" |Hash Algorithm
|Forward
|AES 128
|Reject/Accept
|By  default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’  compulsory.
|}


AES 192


'''AES 256'''
'''2.) Zone settings'''


3DES
In zone settings, there’s an option to add “New Zone”, according to user’s requirement.
| 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
[[File:RB44 Zone Settings.png|1024x1024px]]


SHA 256
'''Port Forwards:'''


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


'''SHA 512'''
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.
| colspan="2" |'''SHA 512''': Authentication  algorithm for Phase II.


Select as per  server-side configuration. Both server and client should have same  configuration.
This helps in directing incoming traffic to the correct device within a local network based on the port number, enhancing connectivity and accessibility.
|-
| colspan="2" |27
| colspan="2" |PFS Group
|MODP768(group1)


MODP1024(group2)
[[File:RB44 Port Forward.png|1024x1024px]]


MODP1536(group5)
'''EDIT:'''


'''MODP2048(group14)'''
[[File:RB44 Port Forwarding Settings.png|1024x1024px]]


MODP3072(group15)
Click on the save button after the required configuration.
 
{| class="wikitable"
MODP4096(group16)
|SN
| colspan="2" |'''MODP2048 (group14)''': Perfect  Forward Secrecy group.
|Field name
 
Select as per  server-side configuration. Both server and client should have same  configuration.
|}
'''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.
 
[[File:Open VPN Settings .png|975x975px]]
 
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.
 
[[File:Open VPN Dashboard.png|972x972px]]
 
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:Wire Guard RC44.png|1024x1024px]]
 
EDIT:
 
[[File:Wire Guard RC44 Setttings.png|1024x1024px]]
{| class="wikitable"
|SN
|Field name
|Sample  value
|Sample  value
|Description
|Description
|-
|-
|1
|1
|Wireguard Role
|Name
|Client/Server
|Example: <code>Web_Server_Forward</code>
|In this dropdown box the user needs to select  the wireguard role.
|Field must  not be empty. Provide a name for the rule to easily identify it.
|-
|-
|2
|2
|WireGuard Tunnel Over
|Protocol
|IPV4/IPV6
|Example: <code>TCP+UDP</code>
|'''IPV4''': Use this if your network and endpoint (WireGuard server) support only IPv4.
|Select the protocol for the rule.


'''IPV6''': Use this if your network and endpoint support IPv6.
Options typically include TCP+UDP, TCP, UDP, ICMP, Custom.
|-
|-
|3
|3
|Enable Failover
|Source zone
|Enable/Disable
|Example: <code>SW_LAN</code>
|This option allows the VPN connection to automatically switch to a backup connection if the primary connection fails.
|Select the  source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
|-
|-
|4
|4
|Enable IPV4
|Source MAC address [optional]
|Enable/Disable
|Example: <code>any</code>
|This enables IPv4 traffic to be routed through  the WireGuard tunnel.
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|-
|-
|5
|5
|Enable IPV6
|Source IP address[optional]
|Enable/Disable
|Example: Leave blank if not needed.
|Enable this if your network and the destination support IPv6.
|Optionally specify an IP address or range.
|-
|-
|6
|6
|Listen Port
|Source port
|51820
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|This is the default port that WireGuard uses  to listen for incoming connections.
|Specify the source port or port range.
|-
|-
|7
|7
|Endpoint Host port
|Destination zone
|51820
|Example: <code>SW_LAN</code>
|This is the  port on the WireGuard server that the client will connect to.
|Select the  destination zone where the traffic is heading to.
|-
|-
|8
|8
|Peer Publickey
|Destination IP address
|*****
|Leave blank if not needed.
|This is the public key of the WireGuard server that the client uses to establish a secure  connection.
|Optionally specify the destination IP address or range.
|-
|-
|9
|9
|Enable Default Route
|Destination port
|Enable/Disable
|Example: <code>80</code> (if redirecting to a web server port)
|Enable this if you want all network traffic (not just specific routes) to be routed through the WireGuard VPN.
|Specify the destination port or port range.
|}
|}
Save and update the page after configuration has been done.
'''Traffic Rule:'''


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


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


ZeroTier is a tool that lets you create your own private network over the internet.
[[File:RB44 Traffic Rule.png|1024x1024px]]


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


In ZeroTier Central, click on "Create a Network". This will generate a unique 16-digit network ID for your new network.
[[File:RB44 Traffic Rule Edit.png|1024x1024px]]


Go to settings => VPN, in general settings, enable ZeroTier and save.
Specification details are below:
 
[[File:RB44 Zerotier Enable.png|1024x1024px]]
 
Copy and paste the unique 16-digit network ID in the edit section.
 
[[File:RB44 Zerotier Editing .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
|NetworkID
|Name
|Ad2769hfkw2345f4
|Example: Allow_HTTP_and_HTTPS
|In this dropdown box the user needs to paste the unique 16-digit network id.
|Field must not be empty: Provide a descriptive name for the traffic rule.
|-
|-
|2
|2
|Listen Port
|Restrict to Address Family
|9993
|Default


|}
|1.      Options: IPv4, IPv6
'''PPTP:'''


This configuration is for setting up a PPTP (Point-to-Point Tunnelling Protocol) VPN connection.
2.      Example:  IPv4 if dealing with typical internet traffic.
 
|Select the  address family to generate iptables rules for.
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.
|-
 
|3
 
|Protocol
''*Refer the image below*''
|Example: TCP+UDP
 
|TCP+UDP: Match incoming traffic using the given protocol.
[[File:RB44 PPTP Config.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:PPTP Connection Settings.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|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.
|-
| 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
|4
|Server  IP
|Match ICMP Type
|Ex: 192.168.10.1
|Example: any
|This is the IP address of the PPTP server the client will connect to.
|Match all ICMP types if set to any. Specific types can be chosen if needed.
|-
|-
|5
|5
|Interface
|Source Zone
|Any
|Example: LAN
 
|Specifies the  traffic source zone.
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
|Username
|Enable DDoS Prevention
|******
|Example: ‘Checked’ if you want to enable DDoS prevention  measures
|This field is the login username for the PPTP server.
|Enable or disable Distributed Denial of Service (DDoS) prevention.
|-
|-
|7
|7
|Password
|Source MAC Address
|****
|Example: any
|This is the password associated with the username.
|any: Match traffic from any MAC address or specify a particular MAC address.
|-
| colspan="4" |'''PPTP Role: SERVER'''
|-
|-
|8
|8
|Local  IP
|Source Address
|Ex: 192.168.0.1
|Example: 192.168.1.0/24
|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.
|Match incoming traffic from the specified source IP address or range.
|-
|-
|9
|9
|Remote  IP Range
|Source Port
|Ex: 192.168.0.20-30
|Example: any if all source ports should be matched
|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.
|any: Match incoming traffic from the specified source port or port range.
|-
|-
|10
|10
|Username
|Destination Zone
|Ex: User1
|Example: WAN
|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.
|Specifies the  traffic destination zone.
|-
|-
|11
|11
|Password
|Action
|*****
|Example: ACCEPT
|The password associated with User1 is required to complete the authentication.
|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.
|}
|}
Once Configured, click on save and update.
Click on save once configured.  


'''SNAT Traffic Rule:'''


'''L2TP:'''
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.


L2TP (Layer 2 Tunneling 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.
To add new source NAT,


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


''*Refer the image below*''
[[File:RB44 SNAT Traffic Rules.png|1024x1024px]]
 
[[File:L2TP Configuration.png|1024x1024px]]  


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


[[File:RB44 L2TP Connection Settings.png|1024x1024px]]
[[File:RB44 SNAT Editing.png|1024x1024px]]


Specification details are given below:
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample Value
|Sample value
|Description
|Description
|-
|-
|1
|1
|L2TP Role
|Name
|Client/Server
|Example: SNAT_WAN_to_LAN
|'''Client''': connecting to an L2TP server to establish a secure tunnel for communication.
|'''Field must  not be empty''': Provide a unique and descriptive name for the SNAT rule.
 
'''Server''': the server listens for incoming client connections.
|-
| colspan="4" |'''L2TP Role: CLIENT'''
|-
|-
|2
|2
|Default Route
|Protocol
|Enable/Disable
|Example: TCP+UDP
|If enabled, all outbound traffic will be routed through the L2TP connection.
|'''TCP+UDP''': Select the protocols that the SNAT rule will apply to.
 
If disabled,  only specific traffic destined for the L2TP network will use the tunnel.
|-
|-
|3
|3
|Metric
|Source Zone
|Ex: 1
|Example: wan
|The system uses this metric to decide which route to prioritize if multiple routes exist.
|'''wan''': Specifies the source zone from which the traffic originates.
 
L2TP connection  with Metric 1 will take precedence over a LAN or WAN route with Metric 10.
|-
|-
|4
|4
|Server IP
|Source IP Address
|Ex: 192.168.10.1
|Example: any or a specific range like 192.168.1.0/24
|This is the '''IP address of the L2TP server''' to which the client will connect.
|'''-- please choose --''': Specify the source IP address or range. Leave empty if the rule applies to any source IP.
 
'''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
|Checkup  Interval Time (in sec)
|Source Port
|Ex: 30/60 secs
|Example: any
|Setting 30 seconds ensures the client checks the connection every half-minute. If the  tunnel drops, the client can quickly reconnect.
|'''any''': Specify the source port or port range from which the traffic originates.
|-
|-
|6
|6
|Interface
|Destination Zone
|Any
|Example: lan
|Example interfaces might include eth0, usb0, or ra0.
|'''lan''': Specifies the destination zone to which the traffic is directed.
|-
|-
|7
|7
|Username
|Destination IP Address
|Ex: User
|Example: any or a specific IP like 192.168.1.100
|The server verifies the username to grant or deny access.
|'''-- please choose --''': Specify the destination IP address or range. Leave empty if the rule applies to any destination IP.
 
Must match credentials configured on the L2TP server.
|-
|-
|8
|8
|Password
|Destination port
|******
|Example: any
|Should be kept secure and match the configuration on the server.
|'''any''': Specify the destination port or port range to which the traffic is directed.
 
Masked for  privacy during configuration.
|-
|-
|9
|9
|MPPE Encryption
|SNAT IP Address
|Enable/Disable
|Example: 203.0.113.5 (an external IP address)
|'''Enabled''': Encrypts  traffic using MPPE, enhancing security (recommended).
|'''-- please  choose --''': Specify the IP address to which the source IP should be translated.
 
'''Disabled''': Transmits data unencrypted, reducing overhead but exposing traffic to potential risks.
|-
| colspan="4" |'''L2TP Role: SERVER'''
|-
|-
|10
|10
|Local IP
|SNAT Port
|Ex: 192.168.0.1
|Example: Leave empty if not needed, or specify a port  like ‘12345’
|This is the '''local IP address of the L2TP server'''. It serves as the gateway for clients connected via the L2TP tunnel.
|Optionally, rewrite matched traffic to a specific source port. Leave empty to only rewrite the IP address.
|-
|-
|11
|11
|Start
|Extra Arguments
|Ex: 192.168.0.20
|Example: --log-prefix "SNAT_traffic: " (to add a log prefix to log messages for this rule)
|Specifies the first IP address that can be assigned to connected clients.
|Pass additional arguments to iptables. Use with care as it can significantly alter  rule behaviour.
|-
|}
|12
Click on save once configured.
|Limit
 
|Ex: 192.168.0.30
'''Parental Control:'''
|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.
For configuring parental control rules, you want to set restrictions based on time, source, and destination zones, as well as specific devices.
|-
|14
|Password
|******
|The server  verifies the password along with the username.


The password  must match the one configured on the server for successful authentication.
To add parental control in firewall,
|}


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


=== 2.5 Firewall ===
[[File:RB44 Parental Control.png|1024x1024px]]
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:RB44 Firewall Config.png|1024x1024px]]
'''EDIT:'''


There are 6 types of setting available under firewall.
[[File:RB44 Parental Control Editing .png|1024x1024px]]


* General Settings
Specification details are given below:
* 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.
 
[[File:RB44 Firewall General Settings.png|1024x1024px]]
 
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|'''SN'''
|SN
|'''Field  Name'''
|Field  Name
|'''Sample  Value'''
|Sample  Value
|'''Description'''
|Description
|-
|-
|1
|1
|Enable SYN-flood  protection
|Name
|Enabled
|Example: Parental_Control_Sunday
|This is enabled by default; setting can be changed if required.
|'''Field must not be empty''': Provide a unique and descriptive name for the parental  control rule.
|-
|-
|2
|2
|Disable IPV6
|Proto
|Disabled
|all
|This is  enabled by default; setting can be changed if required.
|'''all''':  This specifies that the rule will apply to all protocols.
|-
|-
|3
|3
|Drop invalid packets
|Source Zone
|Disabled
|Example: lan
|This is enabled by default; setting can be changed if required.
|'''Field must not be empty''': Please look at Firewall->Zone Settings to find zone  names.
|-
|-
|4
|4
|TCP SYN Cookies
|Destination  Zone
|Disabled
|Example: wan
|This is enabled by default; setting can be changed if required.
|'''Field must not be empty''': Please look at Firewall->Zone Settings to find zone  names.
|-
|-
|5
|5
|Input
|Source MAC  Address
|Reject/Accept
|Example:  00:1A:2B:3C:4D:5E
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’  compulsory.
|'''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
|6
|Output
|Target
|Reject/Accept
|Example:  Reject
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|'''Accept''': This specifies the action to take. For parental controls, you might want to  use ‘Reject’ or ‘Drop’ to block traffic.
|-
|-
|7
|7
|Forward
|Weekdays
|Reject/Accept
|Example:  Sunday
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|'''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.




'''2.) Zone settings'''
'''Zone Forwarding:'''


In zone settings, there’s an option to add “New Zone”, according to user’s requirement.
Zone forwarding in network configuration allows traffic to be directed from one zone to another.


[[File:RB44 Zone Settings.png|1024x1024px]]
To ADD new zone,


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


Port forwarding is a feature in a router or gateway that allows external devices to access services on a private network.
''*Refer the image below*''


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.
[[File:RB44 Zone Forwarding.png|1024x1024px]]
 
This helps in directing incoming traffic to the correct device within a local network based on the port number, enhancing connectivity and accessibility.
 
[[File:RB44 Port Forward.png|1024x1024px]]


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


[[File:RB44 Port Forwarding Settings.png|1024x1024px]]
[[File:RB44 Zone Forwarding Edit.png|1024x1024px]]


Click on the save button after the required configuration.
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field Name
|Sample  value
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|Name
|Source Zone
|Example: <code>Web_Server_Forward</code>
|Example options: lan, wan, etc.
|Field must not be empty. Provide a name for the rule to easily identify it.
|'''--please choose--''': Select the source zone from which the traffic originates.
|-
|-
|2
|2
|Protocol
|Destination Zone
|Example: <code>TCP+UDP</code>
|Example options: lan, wan, etc.
|Select the protocol  for the rule.
|'''--please  choose--''': Select the destination zone to which the traffic is directed.
|}
Click on save once configured.
 
 
=== 2.6 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 port ports as per the requirement.
 
[[File:RB44 Loopback Rule.png|1024x1024px]]


Options typically include TCP+UDP, TCP, UDP, ICMP, Custom.
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.
|-
 
|3
'''EDIT:'''
|Source zone
 
|Example: <code>SW_LAN</code>
[[File:RB44 Loopback Rule Edit.png|1024x1024px]]
|Select the  source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
 
Specification details are given below:
{| class="wikitable"
|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
|4
|Source MAC address [optional]
|Source Port [Optional]
|Example: <code>any</code>
|Example: any
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|'''any''': Specify the source port or port range from which the traffic originates. any allows traffic from all ports.
|-
|-
|5
|5
|Source IP address[optional]
|Loopback IP Address
|Example: Leave blank if not needed.
|Example: 1.1.1.1
|Optionally specify an IP address or range.
|Specify the loopback IP address.
|-
|-
|6
|6
|Source port
|Port
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|Example: 81
|Specify the source port or port range.
|'''any''':  Specify the destination port or port range to which the traffic is directed.  any allows traffic to all ports.
|-
|-
|7
|7
|Destination zone
|Action
|Example: <code>SW_LAN</code>
|Example: DNAT
|Select the destination zone where the traffic is heading to.
|This specifies the action to take either DNAT or SNAT.
|-
|-
|8
|8
|Destination IP address
|Internal IP Address
|Leave blank if not needed.
|Example: 2.2.2.2
|Optionally specify the destination IP address or range.
|'''Field must not be empty''': Specify the internal IP address to which the traffic should  be redirected.
|-
|-
|9
|9
|Destination port
|Internal Port
|Example: <code>80</code> (if redirecting to a web server port)
|Example: 81
|Specify the destination port or port range.
|Redirect matched incoming traffic to the given port on the internal host.
|}
|}
'''Traffic Rule:'''
Once the user is done with the required configurations, user should click save button and then click on the update to save the changes.


"Traffic rules" refer to the policies and regulations that govern the flow of data packets within a network.
=== 2.7 Remote Monitoring ===
In this page the user can select which equipment needs to be monitored remotely.


To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.
Once the user selects the type of RMS click on save.


[[File:RB44 Traffic Rule.png|1024x1024px]]
[[File:RB44 Remote Managment System.png|1024x1024px]]


'''EDIT:'''
'''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:RB44 NMS Dashboard.png|1024x1024px]]
 
'''TR_069:'''
 
To enable the TR_069 the user needs to click on the enable check box.
 
[[File:RB44 TR 069 Config.png|1024x1024px]]
 
Once the user clicks on the check box of enable it will display all the required filed to configured.
 
[[File:RB44 TR 069 Edit.png|1024x1024px]]


[[File:RB44 Traffic Rule Edit.png|1024x1024px]]


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
|Name
|Serving  Interval
|Example: Allow_HTTP_and_HTTPS
|300
|Field must not be empty: Provide a descriptive name for the traffic rule.
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|-
|-
|2
|2
|Restrict to Address Family
|Interface
 
|This can be something like eth0 or wan.
|1.      Options:  IPv4, IPv6
|This specifies the network interface used for TR-069 communication.
 
2.      Example: IPv4 if dealing with typical internet traffic.
|Select the  address family to generate iptables rules for.
|-
|-
|3
|3
|Protocol
|Username
|Example: TCP+UDP
|Example: User
|TCP+UDP: Match incoming traffic using the given protocol.
|The username used to authenticate with the ACS.
|-
|-
|4
|4
|Match ICMP Type
|Password
|Example: any
|••••
|Match all ICMP types if set to any. Specific types can be chosen if needed.
|The password used to authenticate with the ACS.
|-
|-
|5
|5
|Source Zone
|URL
|Example: LAN
|<nowiki>http://example.com</nowiki>
|Specifies the traffic source zone.
|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
The user should fill all the required fields and click on the save button.
|Enable DDoS Prevention
 
|Example: ‘Checked’ if you want to enable DDoS prevention measures
=== 2.8 Tunnel ===
|Enable or  disable Distributed Denial of Service (DDoS) prevention.
Tunnels are a method of transporting data across a network using protocols which are not supported by that network.
|-
 
|7
It is further categorised into 3 sections,
|Source MAC Address
 
|Example: any
1.) General Settings
|any: Match traffic from any MAC address or specify a particular MAC address.
 
|-
2.) GRE Tunnel
|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:'''
3.) IPIP Tunnel
 
[[File:RB44 Tunnel Configuration.png|1024x1024px]]
 
 
'''General Settings:'''  
 
In this page the user needs to select under which type of tunnel it needs to send the data.
 
[[File:RB44 Tunnel General Settings.png|1024x1024px]]
 
 
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:RB44 GRE Tunnel Config.png|1024x1024px]]


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:”
Once the required update is done then click on update to save the changes.


[[File:RB44 SNAT Traffic Rules.png|1024x1024px]]


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


[[File:RB44 SNAT Editing.png|1024x1024px]]
[[File:RB44 GRE Tunnel Configuration .png|1024x1024px]]
 
 
Specification details are given below:


Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field Name
|Sample value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Name
|Tunnel  name
|Example: SNAT_WAN_to_LAN
|Example: GRETunnel
|'''Field must  not be empty''': Provide a unique and descriptive name for the SNAT rule.
|'''GRETunnel''': The name of the GRE tunnel.
|-
|-
|2
|2
|Protocol
|Local external  IP
|Example: TCP+UDP
|Example: 10.1.1.66
|'''TCP+UDP''': Select the protocols that the SNAT rule will apply to.
|The IP address of the local endpoint that will initiate the GRE tunnel.
|-
|-
|3
|3
|Source Zone
|Remote  external IP
|Example: wan
|Example: 10.1.1.40
|'''wan''': Specifies the source zone from which the traffic originates.
|The IP address of the remote endpoint that will terminate the GRE tunnel.
|-
|-
|4
|4
|Source IP Address
|Peer  tunnel IP
|Example: any or a specific range like 192.168.1.0/24
|Example: 10.1.1.4
|'''-- please  choose --''': Specify the source IP address or range. Leave empty if the  rule applies to any source IP.
|The IP address of the peer's tunnel interface.
|-
|-
|5
|5
|Source Port
|Local  tunnel IP
|Example: any
|Example: 10.1.1.6
|'''any''': Specify the source port or port range from which the traffic originates.
|The IP address of the local tunnel interface.
|-
|-
|6
|6
|Destination Zone
|Local  tunnel net mask
|Example: lan
|Example: 255.255.255.0
|'''lan''': Specifies the destination zone to which the traffic is directed.
|The subnet mask of the local tunnel interface.
|-
|-
|7
|7
|Destination IP Address
|Remote IP
|Example: any or a specific IP like 192.168.1.100
|Example: 192.168.10.0/24
|'''-- please choose --''': Specify the destination IP address or range. Leave empty if  the rule applies to any destination IP.
|The remote network that is reachable through the GRE tunnel.
|-
|-
|8
|8
|Destination port
|Enable  Tunnel Link
|Example: any
|Check to  enable
|'''any''':  Specify the destination port or port range to which the traffic is directed.
|Enable or disable the GRE tunnel link.
|-
|-
|9
|9
|SNAT IP Address
|Interface  type
|Example: 203.0.113.5 (an external IP address)
|Example: EWAN2
|'''-- please  choose --''': Specify the IP address to which the source IP should be  translated.
|'''EWAN2''': The  type of network interface used for the GRE tunnel.
|-
|-
|10
|10
|SNAT Port
|MTU
|Example: Leave empty if not needed, or specify a port like ‘12345’
|Example:  1476
|Optionally,  rewrite matched traffic to a specific source port. Leave empty to only rewrite the IP address.
|'''1476''': Maximum Transmission Unit size for the GRE tunnel.
|-
|-
|11
|11
|Extra Arguments
|TTL
|Example: --log-prefix "SNAT_traffic: " (to add a log prefix to log messages for this rule)
|Example: 64
|Pass additional arguments to iptables. Use with care as it can significantly alter  rule behaviour.
|'''64''': Time To  Live value for the packets within the GRE tunnel.
|}
|-
Click on save once configured.
|12
 
|Tunnel  key
'''Parental Control:'''
|Example:  12345678
 
|'''12345678''': A unique key used to identify the GRE tunnel.
For configuring parental control rules, you want to set restrictions based on time, source, and destination zones, as well as specific devices.
|-
|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.  


To add parental control in firewall,
'''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.


Click on “Add and Edit” in “New parental control:” field.
Here the user can add/edit/delete the details of the tunnel.


[[File:RB44 Parental Control.png|1024x1024px]]
[[File:RB44 IPIP Tunnel Configuration.png|1024x1024px]]  


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


[[File:RB44 Parental Control Editing .png|1024x1024px]]
[[File:RB44 IPIP Tunnel Edit.png|1024x1024px]]
 
Once the required update is done then click on update to save the changes.
 


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
|Tunnel  name
|Example: Parental_Control_Sunday
|Example: IPIPTunnel
|'''Field must  not be empty''': Provide a unique and descriptive name for the parental  control rule.
|'''IPIPTunnel:''' The name of the IPIP tunnel.
|-
|-
|2
|2
|Proto
|Local  external IP
|all
|Example:  10.1.1.66
|'''all''': This specifies that the rule will apply to all protocols.
|The IP address of the local endpoint that will initiate the IPIP tunnel.
|-
|-
|3
|3
|Source Zone
|Remote  external IP
|Example: lan
|Example: 10.1.1.40
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone names.
|The IP address of the remote endpoint that will terminate the IPIP tunnel.
|-
|-
|4
|4
|Destination Zone
|Peer tunnel IP
|Example: wan
|Example: 10.1.1.4
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone names.
|The IP address of the peer's tunnel interface.
|-
|-
|5
|5
|Source MAC Address
|Local tunnel IP
|Example:  00:1A:2B:3C:4D:5E
|Example:  10.1.1.6
|'''Field''':  Enter the MAC address of the device you want to apply the parental control rule to. This is useful for restricting specific devices.
|The IP address of the local tunnel interface.
|-
|-
|6
|6
|Target
|Local  tunnel net mask
|Example:  Reject
|Example:  255.255.255.0
|'''Accept''':  This specifies the action to take. For parental controls, you might want to use ‘Reject’ or ‘Drop’ to block traffic.
|The subnet mask of the local tunnel interface.
|-
|-
|7
|7
|Weekdays
|Remote IP
|Example:  Sunday
|Example:  192.168.10.0/24
|'''Sunday''': Specify the days of the week when the rule should be active.
|The remote network that is reachable through the IPIP tunnel.
|-
|-
|8
|8
|Month Days
|Enable  Tunnel Link
|Example: All
|Check to  enable
|'''All:''' Specify  the days of the month when the rule should be active.
|Enable or disable the IPIP tunnel link.
|-
|-
|9
|9
|Start Time (hh:mm:ss)
|Interface  type
|Example:  18:00:00 (6:00 PM)
|Example:  EWAN2
|'''Field must  not be empty:''' Specify the start time when the rule should begin to apply.
|'''EWAN2''': The  type of network interface used for the IPIP tunnel.
|-
|-
|10
|10
|Stop Time (hh:mm:ss)
|MTU
|Example:  22:00:00 (10:00 PM)
|Example: 1476
|'''Field must not be empty:''' Specify the stop time when the rule should end.
|'''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.
|}
|}
Click on save once configured.


== 3.Maintenance ==
In this module the user can configure/upgrade/modify the settings related to system, password, firmware and monitoring.


'''Zone Forwarding:'''
It includes below submodules.
 
* General
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application
 
[[File:RB44 Maintenance Dashboard.png|1024x1024px]]
 
''*Below is the detailed explanation of every field*''
 
=== 3.1 General/ System ===
Here you can configure the basic aspects of router like its hostname or the time zone.


Zone forwarding in network configuration allows traffic to be directed from one zone to another.
It is further sub-divided into,


To ADD new zone,
1.) General Settings


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


''*Refer the image below*''
3.) Language and Style


[[File:RB44 Zone Forwarding.png|1024x1024px]]


'''EDIT:'''
'''General Settings:'''


[[File:RB44 Zone Forwarding Edit.png|1024x1024px]]
[[File:RB44 Maintenance General Settings.png|1024x1024px]]  


Specification details are below:
'''EDIT:'''
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Source Zone
|Local Time
|Example options: lan, wan, etc.
|2024/07/30  13:25:47
|'''--please choose--''': Select the source zone from which the traffic originates.
|The current local date and time set on the device.
|-
|-
|2
|2
|Destination Zone
|Hostname
|Example options: lan, wan, etc.
|22B25240007
|'''--please choose--''': Select the destination zone to which the traffic is directed.
|The hostname of the device, which is  used to identify it on the network.
|-
|3
|Time zone
|Asia/Kolkata
|The time zone setting of the device, which determines the local time.
|}
|}
Click on save once configured.
Once the user configures the required details then click on the save button to save all the details.  


'''Logging:'''


=== 2.7 Loopback Rule ===
Here the user can configure the basic aspects of your device related to system.
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 port ports as per the requirement.


[[File:RB44 Loopback Rule.png|1024x1024px]]
The system log configuration provided specifies how the device handles and stores log information, including buffer size, external log server details, and log detail levels.


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.
[[File:RB44 Logging .png|1024x1024px]]


'''EDIT:'''
'''EDIT:'''
[[File:RB44 Loopback Rule 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
|Name
|System  log buffer size
|Example: loopback
|Example: 32 kiB
|Provide a  descriptive name for the rule.
|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
|Protocol
|External  system log server
|Example: TCP+UDP
|Example: 0.0.0.0
|'''TCP+UDP''': Select the protocols that the rule will apply to.
|The IP address of an external server where logs can be sent.
|-
|-
|3
|3
|Source IP Address [Optional]
|External  system log server port
|Example: any or a specific IP range like 192.168.1.0/24
|Example: 514
|Optionally specify the source IP address or range. Leave empty if the rule should apply  to any source IP.
|The port used to send logs to the external log server. Port 514 is the default port for syslog.
|-
|-
|4
|4
|Source Port [Optional]
|Log  output level
|Example: any
|Example: Debug
|'''any''':  Specify the source port or port range from which the traffic originates. any allows traffic from all ports.
|Sets the detail level of the system logs.
|-
|-
|5
|5
|Loopback IP Address
|Cron Log  level
|Example: 1.1.1.1
|Example: Debug
|Specify the  loopback IP address.
|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.
|Port
 
|Example: 81
 
|'''any''':  Specify the destination port or port range to which the traffic is directed.  any allows traffic to all ports.
'''Language and Style:'''
|-
 
|7
Here the user can configure the basic aspects of your device related to language.
|Action
 
|Example: DNAT
Once the user configures the required details then click on the save button to save all the details.
|This  specifies the action to take either DNAT or SNAT.
 
|-
[[File:RB44 Language and Style.png|1024x1024px]]
|8
 
|Internal IP Address
=== 3.2 Password ===
|Example: 2.2.2.2
In this module the user can set the password for the admin credentials.
|'''Field must  not be empty''': Specify the internal IP address to which the traffic should  be redirected.
 
|-
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.
|9
|Internal Port
|Example: 81
|Redirect  matched incoming traffic to the given port on the internal host.
|}
Once the user is done with the required configurations, user should click save button and then click on the update to save the changes.


=== 2.8 VRRP ===
[[File:RB44 Password Setting.png|1024x1024px]]
'''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.
=== 3.3 Reboot ===
In this module the user can reboot the device remotely.


[[File:RB44 VRRP Configuration.png|1024x1024px]]
First option is to directly reboot the device without enabling the maintenance reboot tab.


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


Give a name and ‘Add’ device.
[[File:RB44 Maintenance Reboot.png|1024x1024px]]


Click on ‘Edit’ to make changes.


Click on ‘Delete’ if particular instance not required.
To start maintenance reboot process first the user needs to fill all the required fields.


[[File:RB44 VRRP Configuration Edit.png|1024x1024px]]
Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.


'''EDIT:'''
[[File:RB44 Reboot settings.png|1024x1024px]]


[[File:RB44 VRRP Configuration Settings.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
|Role
|Enable Maintenance  Reboot
|1.      Master
|Enable/Disable
 
|Indicates whether the maintenance reboot feature is enabled or not.
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
|Virtual ID
|Type
|Ex: 0
|Maintenance  Reboot
|The value can range from 0 to 255.
|Specifies the type of reboot being scheduled.
 
Ensure all  routers in the same VRRP group share the same '''Virtual ID'''.
|-
|-
|3
|3
|Priority
|Reboot  Type
|Ex: 100
|Software/Hardware
|For the '''Master'''  role, use the highest priority, typically above 100.
|'''Hardware''': A hardware reboot involves restarting the entire device as if it were powered off and on again.


For the '''Backup'''  role, set a lower priority number, usually below the master's priority.
'''Software''': A software reboot involves restarting the operating system without powering off the hardware.
|-
|-
|4
|4
|Interface
|Minutes
|SW_LAN
|Example:  59
|This is the  network interface on which VRRP operates.
|The minute at which the reboot should occur (0-59).
|-
|-
|5
|5
|Source IP
|Hours
|Ex: 192.168.10.1
|Example: 22 (10 PM)
|This is the  IP address used as the source in VRRP advertisements.
|The hour at which the reboot should occur (0-23, in 24-hour format).
|-
|-
|6
|6
|Peer IP
|Day Of  Month
|Ex: 192.168.10.10
|Example: All
|This is the  IP address of the other VRRP peer (usually the backup router). It helps the  routers identify each other.
|Specifies which days of the month the  reboot should occur (1-31). "All" means it will occur every day.
|-
|-
|7
|7
|Virtual IP  Address
|Month
|192.168.10.100/24
|Example:  All
|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.
|Specifies which months the reboot should occur (1-12). "All" means it will occur every month.
|-
|-
|8
|8
|Enable Authentication
|Day Of Week
|Enable/Disable
|Example:  All
|Enable this if you want to secure your VRRP communications.
|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.
|-
|9
|Password
|*********
|It ensures that only routers with the correct password can join the VRRP group.
|}
|}
Save and update once changes have been made.
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.


=== 2.9 Remote Monitoring ===
[[File:RB44 Import and Export.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.
Click “Export Config” to export device configuration & settings to a text file,


[[File:RB44 Remote Managment System.png|1024x1024px]]
Click “Import Config” to import device configuration & settings from a previously exported text file.


'''NMS:'''
[[File:RB44 Import Config.png|1024x1024px]]


IN this page the user should type the server IP or domain name in the URL then click on save.
The user needs to select on the “choose file”, upload the required file and click on apply.


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).
=== 3.5 Firmware Upgrade ===
The user can upgrade with the latest software for the existing firmware.


[[File:RB44 NMS Dashboard.png|1024x1024px]]  
[[File:RB44 Firmware Upgrade.png|1024x1024px]]


'''TR_069:'''
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.


To enable the TR_069 the user needs to click on the enable check box.
This option will completely reset the device to default settings.


[[File:RB44 TR 069 Config.png|1024x1024px]]  
[[File:RB44 Flash Image.png|1024x1024px]]


Once the user clicks on the check box of enable it will display all the required filed to configured.
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.


[[File:RB44 TR 069 Edit.png|1024x1024px]]
This refers to updating the firmware (flashing) of a device while preserving the current configuration settings.


[[File:RB44 Retain and Flash.png|1024x1024px]]


Specification details are given below:
Click on the '''Factory Reset''' for the complete reset of the device.
{| class="wikitable"
 
|SN
[[File:RB44 Factory Reset.png|1024x1024px]]
|Field Name
 
|Sample Value
=== 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:RB44 Monitor Application.png|1024x1024px]]
 
'''Modem Monitor Application Configuration:'''
 
[[File:RB44 Modem Monitor Application.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Serving  Interval
|Enable Ping Check Application
|300
|Enable/Disable
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|Turns on the functionality to perform ping checks on specified IP addresses.
|-
|-
|2
|2
|Interface
|Time Interval for Check (In minutes)
|This can  be something like eth0 or wan.
|'''Example:''' 10 minutes
|This specifies the network interface  used for TR-069 communication.
|Frequency at which the ping checks are performed.
|-
|-
|3
|3
|Username
|Select No of IP addresses to ping
|Example: User
|'''Example:''' 1
|The username used to authenticate with  the ACS.
|Number of IP addresses that will be pinged.
|-
|-
|4
|4
|Password
|IP Address 1
|••••
|'''Example:''' 8.8.8.8
|The password used to authenticate with  the ACS.
|The IP address to ping.
|-
|-
|5
|5
|URL
|No. of Retries
|<nowiki>http://example.com</nowiki>
|'''Example:''' 5
|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.
|Number of times to retry pinging an IP address  if the initial ping fails.
|}
|-
The user should fill all the required fields and click on the save button.
|6
 
|Failure Criteria in (%)
=== 2.10 Tunnel ===
|'''Example:''' 80% (If 4 out of 5 pings fail, it’s considered a failure)
Tunnels are a method of transporting data across a network using protocols which are not supported by that network.
|Percentage of failed pings required to consider the ping check a failure.
 
|-
It is further categorised into 3 sections,
|7
 
|Action On Failure
1.) General Settings
|'''Example:''' Restart Modem
 
|Action to be taken if the ping check fails  according to the criteria.
2.) GRE Tunnel
|-
|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.  


3.) IPIP Tunnel
'''Router Monitor Application Configuration:'''


[[File:RB44 Tunnel Configuration.png|1024x1024px]]
[[File:RB44 Monitor Application Configuration.png|1024x1024px]]


 
Specification details are given below:
'''General Settings:'''
{| class="wikitable"
 
|SN
In this page the user needs to select under which type of tunnel it needs to send the data.
|Field Name
 
|Sample Value
[[File:RB44 Tunnel General Settings.png|1024x1024px]]
|Description
 
|-
 
|1
Once the user selects the type of tunnel then click on the save button.
|Enable Ping Check Application
 
|Enable/Disable
'''GRE Tunnel:'''
|Activates the ping check functionality to monitor router performance.
 
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:RB44 GRE Tunnel Config.png|1024x1024px]]
 
 
 
Once the required update is done then click on update to save the changes.
 
 
'''EDIT:'''
 
[[File:RB44 GRE Tunnel Configuration .png|1024x1024px]]
 
 
Specification details are given below:
 
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|1
|Tunnel  name
|Example:  GRETunnel
|'''GRETunnel''': The name of the GRE tunnel.
|-
|-
|2
|2
|Local external  IP
|Time Interval for Check (In minutes)
|Example: 10.1.1.66
|'''Example:''' 10 minutes
|The IP address of the local endpoint that will initiate the GRE tunnel.
|How frequently the ping checks are performed.
|-
|-
|3
|3
|Remote  external IP
|Select No of IP Addresses to Ping
|Example:  10.1.1.40
|'''Example:''' 1 (Please select the appropriate number based on your requirements)
|The IP address of the remote endpoint that will terminate the GRE tunnel.
|Choose the  number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
|-
|-
|4
|4
|Peer  tunnel IP
|No. of Retries
|Example: 10.1.1.4
|'''Example:''' 3
|The IP address of the peer's tunnel interface.
|Number of  retries if a ping fails.
|-
|-
|5
|5
|Local  tunnel IP
|Failure Criteria in (%)
|Example:  10.1.1.6
|'''Example:''' 80% (If 80% of the pings fail, it’s deemed a failure)
|The IP address of the local tunnel  interface.
|Percentage of failed pings required to consider the ping check as failed.
|-
|-
|6
|6
|Local  tunnel net mask
|Action On Failure
|Example: 255.255.255.0
|'''Example:''' Restart IPsec
|The subnet mask of the local tunnel  interface.
|The action  taken if the ping check fails according to the criteria.
|-
|-
|7
|7
|Remote IP
|Enable Second Level Action
|Example: 192.168.10.0/24
|Enable/Disable
|The remote network that is reachable through the GRE tunnel.
|Option to enable an additional action if the primary action fails.
|-
|-
|8
|8
|Enable  Tunnel Link
|Second Level Action Threshold
|Check to  enable
|'''Example:''' Specify the number of failures, such as 2
|Enable or disable the GRE tunnel link.
|Number of  times the primary action must fail before the secondary action is triggered.
|-
|-
|9
|9
|Interface  type
|Second Level Action
|Example:  EWAN2
|'''Example:''' Restart Board
|'''EWAN2''': The  type of network interface used for the GRE tunnel.
|The action to  be taken if the second level action threshold is met.
|-
|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.  
Save the details once made necessary changes.


'''IPIP Tunnel:'''
== 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
[[File:RD44A Status.png|1024x1024px]]


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.
=== 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.
 
[[File:RB44 Interfaces.png|1024x1024px]]


Here the user can add/edit/delete the details of the tunnel.
Looking on the network status the user can check if the cellular, Wi-Fi, Ewan, VPN etc is up.


[[File:RB44 IPIP Tunnel Configuration.png|1024x1024px]]
=== 4.2 Internet ===
In this submodule the user can view the status of the internet connections.


'''EDIT:'''
[[File:RB44 Internet.png|1024x1024px]]


[[File:RB44 IPIP Tunnel Edit.png|1024x1024px]]
To see the latest status of the internet connection the user needs to click on the refresh button.


Once the required update is done then click on update to save the changes.
=== 4.3 Modem ===
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.


[[File:RB44 Modem Status.png|1024x1024px]]


Specification details are given below:
=== 4.4 Routes ===
{| class="wikitable"
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.
|SN
 
|Field Name
'''ARP Table:''' Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.
|Sample Value
 
|Description
'''IPv4 Routes:''' This shows which network is directly connected on which interface.
|-
 
|1
Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''
|Tunnel  name
 
|Example: IPIPTunnel
'''IPv6 Routes:''' Similar routes as IPv4, but this time listed under IPv6 routing rules.
|'''IPIPTunnel:''' The name of the IPIP tunnel.
 
|-
Example: Local networks '''192.168.10.0/24''' and '''192.168.100.0/24''' are managed through '''eth0.1''' and '''ra0''', respectively.
|2
 
|Local  external IP
''*Refer the below image*''
|Example: 10.1.1.66
 
|The IP address of the local endpoint  that will initiate the IPIP tunnel.
[[File:RB44 Routes.png|1024x1024px]]
|-
 
|3
== 5. Features ==
|Remote  external IP
In this module the user can see all the features that the router has.
|Example:  10.1.1.40
 
|The IP address of the remote endpoint  that will terminate the IPIP tunnel.
This module includes 9 features.
|-
 
|4
* Mac Address Binding
|Peer  tunnel IP
* URL Filtering
|Example: 10.1.1.4
* Web Server
|The IP address of the peer's tunnel  interface.
* Wi-Fi MacID Filtering
|-
* Routing
|5
* DMZ
|Local  tunnel IP
* Others
|Example:  10.1.1.6
* Connection Diagnostics
|The IP address of the local tunnel  interface.
* Package Manager
|-
 
|6
[[File:RD44A Features.png|1024x1024px]]
|Local  tunnel net mask
 
|Example: 255.255.255.0
=== 5.1 Mac Address Binding ===
|The subnet mask of the local tunnel  interface.
MAC address binding is a configuration that binds a specific MAC address to a specific IP address.
|-
 
|7
This ensures that a particular device on the network always receives the same IP address from the DHCP
|Remote IP
 
|Example: 192.168.10.0/24
server, which can be useful for network management, security, and ensuring consistent network
|The remote network that is reachable  through the IPIP tunnel.
 
|-
behaviour.
|8
 
|Enable Tunnel Link
Under this submodule the user can configure/update/edit the IP Address for MAC.
|Check to enable
 
|Enable or disable the IPIP tunnel link.
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.
 
[[File:RB44 MAC Address Binding.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:RB44 Mac Address Edit.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|9
|1
|Interface  type
|Device Name
|Example:  EWAN2
|mac1
|'''EWAN2''': The  type of network interface used for the IPIP tunnel.
|A user-defined name for the binding  configuration.
|-
|-
|10
|2
|MTU
|MAC Address
|Example: 1476
|48:9e:bd:da:45:91
|'''1476''': Maximum Transmission Unit size for the IPIP tunnel.
|The unique identifier for the network interface of the device to which the IP address will be bound.
|-
|-
|11
|3
|TTL
|IP Address
|Example:  64
|192.168.10.55
|'''64''': Time To  Live value for the packets within the IPIP tunnel.
|The IP address that will be consistently assigned to the device with the specified MAC address.
|-
|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 ==
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.
In this module the user can configure/upgrade/modify the settings related to system, password, firmware and monitoring.


It includes below submodules.
* 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.


* General
Post all the changes the user needs to click on the update to reflect all the changes in the application.
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application


[[File:RB44 Maintenance Dashboard.png|1024x1024px]]
=== 5.2 URL Filtering ===
In this submodule the user should provide the URL which needs to be blocked for the device.


''*Below is the detailed explanation of every field*''
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:RB44 URL Filtering.png|1024x1024px]]To add the new URL for blocking, click on the Add New button.


=== 3.1 General/ System ===
Once the user clicks on the Add New button a new pop will appear in that page write the URL and click
Here you can configure the basic aspects of router like its hostname or the time zone.


It is further sub-divided into,
on the save.


1.) General Settings
The user can select the status of that URL while defining the URL.


2.) Logging
[[File:RB44 URL Filter Edit.png|1024x1024px]]To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.


3.) Language and Style
[[File:RB44 URL Filter OFF.png|1024x1024px]]


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


'''General Settings:'''
=== 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:RB44 Maintenance General Settings.png|1024x1024px]]  
[[File:Rd44A Webserver .png|1024x1024px]]


'''EDIT:'''
'''EDIT:'''
[[File:RD44A Webserver 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
|Local Time
|Enable HTTP
|2024/07/30  13:25:47
|'''HTTP Port:''' 80
|The current local date and time set on the device.
 
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
|2
|Hostname
|Enable HTTPS
|22B25240007
|'''HTTPS Port:''' 443
|The hostname of the device, which is used to identify it on the network.
 
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
|3
|Time zone
|Redirect HTTPS
|Asia/Kolkata
|Option to redirect HTTP traffic to  HTTPS.
|The time zone setting of the device,  which determines the local time.
|When enabled, all HTTP requests will be automatically redirected to the HTTPS port to ensure secure communication.
|}
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 detail levels.
 
[[File:RB44 Logging .png|1024x1024px]]
 
'''EDIT:'''
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|1
|4
|System  log buffer size
|Session Timeout (in millisecs)
|Example: 32 kiB
|Ex: 60000
|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.
|In this scenario the webpage will logout after 60secs of inactivity.
|-
|-
|2
|5
|External  system log server
|RFC1918 Filter
|Example: 0.0.0.0
|Enable/Disable
|The IP address of an external server where logs can be sent.
|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.
|-
|-
|3
|6
|External  system log server port
|Enable NTP Sync
|Example:  514
|Enable or disable NTP synchronization.
|The port used to send logs to the  external log server. Port 514 is the default port for syslog.
|Synchronizes the device’s system clock with an external NTP server to maintain accurate time.
|-
|-
|4
|7
|Log  output level
|NTP Server
|Example:  Debug
|0.openwrt.pool.ntp.org
|Sets the detail level of the system logs.
|The address of the NTP server used for time synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
|-
|-
|5
|8
|Cron Log  level
|NTP Sync Interval (In Minutes)
|Example:  Debug
|15
|The detail level of the logs for cron jobs.
|The interval at which the device will sync its clock with the NTP server, set to every 15 minutes in this case.
|}
|}
Once the user configures the required details then click on the save button to save all the details.
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.


'''Language and Style:'''
It is further divided into 2 categories,


Here the user can configure the basic aspects of your device related to language.
'''WIFI 2.4G AP'''


Once the user configures the required details then click on the save button to save all the details.
'''WIFI 2.4G AP Guest'''


[[File:RB44 Language and Style.png|1024x1024px]]
[[File:RB44 WIFI 2.4G AP Guest.png|1024x1024px]]


=== 3.2 Password ===
Before adding the MacIDs the user needs to select the mode from the dropdown menu.
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.
In ‘Change Mode’ select one option,


[[File:RB44 Password Setting.png|1024x1024px]]
'''Blacklist'''


=== 3.3 Reboot ===
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.
In this module the user can reboot the device remotely.


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


Click on “Reboot Now” at the bottom of the screen to start the reboot process.
In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.


[[File:RB44 Maintenance Reboot.png|1024x1024px]]
To Add the MacID the user needs to click on Add New option.
 
 
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:RB44 Reboot settings.png|1024x1024px]]


[[File:RB44 Whitelist.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
|Status
|Enable/Disable
|Enable/Disable
|Indicates whether the maintenance  reboot feature is enabled or not.
|Enable or disable the MAC ID filtering.
|-
|-
|2
|2
|Type
|MAC ID
|Maintenance  Reboot
|Example: e8:6f:38:1a:f2:61
|Specifies the type of reboot being scheduled.
|The MAC address of the device to be whitelisted or blocklisted.
|-
|-
|3
|3
|Reboot Type
|Network Name
|Software/Hardware
|Example: WIFI 2.4G AP or Wi-Fi 2.4G AP Guest.
|'''Hardware''': A hardware reboot involves restarting the entire device as if it were powered off and on again.
|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,


'''Software''': A software reboot involves restarting the  operating system without powering off the hardware.
'''Static IPV4 Routes'''
|-
|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 ===
'''Advanced Static IPV4 Routes'''
In this section, User can Import & Export Configuration files of the Device.


[[File:RB44 Import and Export.png|1024x1024px]]
'''Static IPV4 Routes:'''


Click “Export Config” to export device configuration & settings to a text file,
Click on ‘Add’ to add a new interface. 


Click “Import Config” to import device configuration & settings from a previously exported text file.
[[File:RB44 Routing .png|1024x1024px]] 


[[File:RB44 Import Config.png|1024x1024px]]
'''EDIT:'''


The user needs to select on the “choose file”, upload the required file and click on apply.
To edit the existing device the user needs to click on the edit option.


=== 3.5 Firmware Upgrade ===
Once the changes are done click on the save button to save all the changes.
The user can upgrade with the latest software for the existing firmware.


[[File:RB44 Firmware Upgrade.png|1024x1024px]]
Click on the deleted button to delete the existing device detail.
 
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:RB44 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:RB44 Retain and Flash.png|1024x1024px]]
 
Click on the '''Factory Reset''' for the complete reset of the device.
 
[[File:RB44 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:RB44 Monitor Application.png|1024x1024px]]
 
'''Modem Monitor Application Configuration:'''
 
[[File:RB44 Modem Monitor Application.png|1024x1024px]]


[[File:RB44 Static IPV4 Routes.png|1023x1023px]]
Specification details are given below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
Line 2,958: Line 2,760:
|-
|-
|1
|1
|Enable Ping Check Application
|Interface
|Enable/Disable
|Ex: eth0.1
|Turns on the functionality to perform ping  checks on specified IP addresses.
|The network interface to be used for this route.  Select the one to use from dropdown.
|-
|-
|2
|2
|Time Interval for Check (In minutes)
|Target
|'''Example:''' 10 minutes
|Ex: 192.168.20.0
|Frequency at which the ping checks are performed.
|The destination subnet to which traffic should  be routed.
|-
|-
|3
|3
|Select No of IP addresses to ping
|IPv4 Netmask
|'''Example:''' 1
|255.255.255.0
|Number of IP addresses that will be pinged.
|The subnet mask for the target network.
|-
|-
|4
|4
|IP Address 1
|Metric
|'''Example:''' 8.8.8.8
|0
|The IP address to ping.
|The priority of the route.
 
Lower values indicate higher priority.
|-
|-
|5
|5
|No. of Retries
|IPv4 Gateway
|'''Example:''' 5
|Ex: 192.168.10.1
|Number of times to retry pinging an IP address  if the initial ping fails.
|The gateway IP address to be used for routing traffic to the target subnet.
|-
|-
|6
|6
|Failure Criteria in (%)
|Route Type
|'''Example:''' 80% (If 4 out of 5 pings fail, it’s considered  a failure)
|Unicast
|Percentage of failed pings required to consider the ping check a failure.
|Standard route for individual destination IP addresses.
|-
 
|7
Custom changes can be made.
|Action On Failure
|}
|'''Example:''' Restart Modem
Click on save once configuration changes have been made.  
|Action to be taken if the ping check fails  according to the criteria.
 
|-
'''Advanced Static IPV4 Routes:'''
|8
 
|Enable Second Level Action
This is further divided into 2 sections,
|Enable/Disable
 
|Option to enable a secondary action if the  primary action fails multiple times.
Routing Tables
|-
|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:'''
Routing Rules for IPV4


[[File:RB44 Monitor Application Configuration.png|1024x1024px]]
'''Routing Tables:'''


Specification details are given below:
Adding a new table in static routing allows you to define specific routes for traffic within a network.
{| class="wikitable"
 
|SN
Click on ‘Add’ to add a new Table.
|Field  Name
 
|Sample  Value
[[File:RB44 Advanced Static IPV4 Routes-.png|1024x1024px]]
|Description
 
|-
'''EDIT:'''
 
[[File:RB44 Advanced Static IPV4 Routes Editing.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|1
|Enable Ping Check Application
|ID of Table
|Enable/Disable
|Ex: 1
|Activates the  ping check functionality to monitor router performance.
|A unique identifier for the routing table. Multiple tables can be used to define different sets of routing rules,  providing flexibility in how traffic is managed.
|-
|-
|2
|2
|Time Interval for Check (In minutes)
|Name of Table
|'''Example:''' 10 minutes
|Ex: Route
|How frequently the ping checks are performed.
|A descriptive name for the routing table, making it easier to manage and identify different tables.
|-
|-
|3
|3
|Select No of IP Addresses to Ping
|Target
|'''Example:''' 1 (Please select the appropriate number  based on your requirements)
|Ex: 192.168.10.0
|Choose the number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
|Specifies the destination network or IP address that the route is intended for.
|-
|-
|4
|4
|No. of Retries
|IPv4 Netmask
|'''Example:''' 3
|255.255.255.0
|Number of  retries if a ping fails.
|Defines the subnet mask for the target network.
|-
|-
|5
|5
|Failure Criteria in (%)
|Metric
|'''Example:''' 80% (If 80% of the pings fail, it’s deemed a failure)
|Ex: 0
|Percentage of failed pings required to consider the ping check as failed.
|Indicates the priority of the route. A lower metric value means a higher priority. Routes with lower metrics are preferred over those with higher metrics.
|-
|-
|6
|6
|Action On Failure
|IPv4 Gateway
|'''Example:''' Restart IPsec
|Ex: 10.1.1.1
|The action taken if the ping check fails according to the criteria.
|Specifies the next hop or gateway IP address through which the traffic to the target network should be routed.
|-
|-
|7
|7
|Enable Second Level Action
|Route Type
|Enable/Disable
|1.) Unicast
|Option to  enable an additional action if the primary action fails.
 
|-
2.) Custom
|8
|'''Unicast''': Standard route where packets are sent to a single destination IP address.
|Second Level Action Threshold
 
|'''Example:''' Specify the number of failures, such as 2
'''Custom''': Enables advanced routing configurations or specific protocols that might not be covered by default.
|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
'''Routing Rules for IPV4:'''
* Internet
* Modem
* Routes
[[File:RB44 Status .png|1024x1024px]]


=== 4.1 Interfaces ===
Click on ‘Add’ to add a new interface.  
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:RB44 Interfaces.png|1024x1024px]]
[[File:RB44 Routing Rules for IPV4.png|1024x1024px]]  


Looking on the network status the user can check if the cellular, Wi-Fi, Ewan, VPN etc is up.
'''EDIT:'''


=== 4.2 Internet ===
To edit the existing device the user needs to click on the edit option.
In this submodule the user can view the status of the internet connections.


[[File:RB44 Internet.png|1024x1024px]]
Once the changes are done click on the save button to save all the changes.


To see the latest status of the internet connection the user needs to click on the refresh button.
Click on the deleted button to delete the existing device detail.


=== 4.3 Modem ===
[[File:RB44 Routing Rules for IPV4 Editing.png|1024x1024px]]
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.


[[File:RB44 Modem Status.png|1024x1024px]]
Specification details are given below:
 
{| class="wikitable"
=== 4.4 Routes ===
|SN
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.
|Field  Name
 
|Sample  Value
'''ARP Table:''' Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.
|Description
|-
|1
|Interface
|Ex: ra0
|Select the specific network interface on the  router through which traffic enters or exits.
|-
|2
|To
|Ex: 192.168.10.1
|The destination IP address or network. In this  case, 192.168.10.1 is the target IP address for routing traffic.
|-
|3
|IPv4 Netmask
|Ex: 255.255.255.192
|Defines the subnet mask, which helps determine  the size of the network.
|-
|4
|Table ID
|Ex: 1
|Identifies which routing table this rule  applies to.
|-
|5
|From
|Ex: 192.168.100.1
|Specifies the source IP address or network from  which the traffic originates. In this case, the traffic is coming from  192.168.100.1.
|-
|6
|Priority
|Ex:20
|Determines the order in which routing rules are  evaluated. Lower numbers have higher priority. If two rules conflict, the one  with the lower priority number will be applied first.
|-
|7
|Outgoing Interface
|1.) fwmark


'''IPv4 Routes:''' This shows which network is directly connected on which interface.
2.) iif (Incoming Interface)


Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''
3.) oif (Outgoing Interface)


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


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


''*Refer the below image*''
6.) prohibited


[[File:RB44 Routes.png|1024x1024px]]
7.) unreachable
|1.) This  allows you to create rules that apply only to traffic that has been marked in  a specific way by the firewall.


== 5. Features ==
2.) This is  often used to create rules based on the interface through which traffic is  received.
In this module the user can see all the features that the router has.


This module includes 9 features.
3.) This allows you to control the flow of traffic based on the desired outgoing  interface.


* Mac Address Binding
4.) It tells the router to check the specific  routing table ID mentioned to determine how to route the traffic.
* URL Filtering
* Web Server
* Wi-Fi MacID Filtering
* Routing
* DMZ
* Others
* Connection Diagnostics
* Package Manager


[[File:RB44 Features.png|1024x1024px]]
5.) This is  used when you want to block traffic without notifying the sender.


=== 5.1 Mac Address Binding ===
6.) Like  blackhole but sends an ICMP unreachable message to the sender, indicating  that the route is prohibited.
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
7.) Causes  the router to send an ICMP unreachable message to the source IP, notifying  that the destination is unreachable.
|}


server, which can be useful for network management, security, and ensuring consistent network
=== 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.


behaviour.
[[File:RB44 Others .png|1024x1024px]]


Under this submodule the user can configure/update/edit the IP Address for MAC.
Specification details are given below:
 
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.
 
[[File:RB44 MAC Address Binding.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:RB44 Mac Address Edit.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 3,158: Line 2,960:
|-
|-
|1
|1
|Device Name
|Set Date
|mac1
|Date and time fields (day, month, year,  hour, minute, second)
|A user-defined name for the binding configuration.
|Sets the system date and time to the specified values.
|-
|-
|2
|2
|MAC Address
|Get Date
|48:9e:bd:da:45:91
|System
|The unique identifier for the network interface of the device to which the IP address will be bound.
|Retrieves and displays the current system date and time.
|-
|-
|3
|3
|IP Address
|ipsec status all
|192.168.10.55
|Command ‘Get’
|The IP address that will be consistently  assigned to the device with the specified MAC address.
|Displays the status of all IPsec connections.
|}
|-
 
|4
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.
|Wi-Fi Scan
 
|Command ‘Get’
* Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
|Initiates a scan for available Wi-Fi networks.
* The user can click on the deleted button to delete an existing configured device.
|-
 
|5
Post all the changes the user needs to click on the update to reflect all the changes in the application.
|iPerf3 Client
 
|IP address (e.g., 192.168.10.100)
=== 5.2 URL Filtering ===
|Runs an iPerf3 client to measure network performance.
In this submodule the user should provide the URL which needs to be blocked for the device.
|-
 
|6
By implementing URL filtering with the specified URL, you can control and restrict access to certain
|iPerf3 Server
 
|Command ‘Run’
websites, thereby improving network security and managing user access.
|Runs an iPerf3 server to measure network  performance.
 
|-
[[File:RB44 URL Filtering.png|1024x1024px]]To add the new URL for blocking, click on the Add New button.
|7
 
|Ping
Once the user clicks on the Add New button a new pop will appear in that page write the URL and click
|IP address or domain (e.g., 8.8.8.8)
 
|Sends ICMP echo requests to the specified  address to check connectivity.
on the save.
|-
 
|8
The user can select the status of that URL while defining the URL.
|traceroute
 
|IP address or domain (e.g., 8.8.8.8)
[[File:RB44 URL Filter Edit.png|1024x1024px]]To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.
|Traces the route packets take to reach the specified address.
 
[[File:RB44 URL Filter OFF.png|1024x1024px]]
 
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:RB44 Web Server.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:RB44 Webserver Config.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample  Value
|Description
|-
|-
|1
|9
|Enable HTTP
|NTP Sync
|'''HTTP Port:''' 80
|Command ‘Sync’
 
|Synchronizes the system time with the  configured NTP server.
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
|10
|Enable HTTPS
|Download Files
|'''HTTPS Port:''' 443
|File or database identifier
 
|Initiates a download of the specified file or database.
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
|11
|Redirect HTTPS
|Restart Power
|Option to redirect HTTP traffic to  HTTPS.
|Command ‘Restart’
|When enabled, all HTTP requests will be  automatically redirected to the HTTPS port to ensure secure communication.
|Restarts the power of the device.
|-
|-
|4
|12
|Session Timeout (in millisecs)
|Restart Modem
|Ex: 60000
|Command ‘Restart’
|In this scenario the webpage will logout after  60secs of inactivity.
|Restarts the modem.
|-
|-
|5
|13
|RFC1918 Filter
|Run AT Command
|Enable/Disable
|Enter AT command
|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.
|Executes the specified AT command on the modem.
|-
|-
|6
|14
|Enable NTP Sync
|Show Board Configuration
|Enable or disable NTP synchronization.
|Command ‘Show’
|Synchronizes the device’s system clock with an  external NTP server to maintain accurate time.
|Displays the current board configuration.
|-
|-
|7
|15
|NTP Server
|Show VPN Certificate Name
|0.openwrt.pool.ntp.org
|Command ‘Show’
|The address of the NTP server used for time synchronization.  The openwrt.pool.ntp.org server is a public NTP server pool.
|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.
|-
|-
|8
|19
|NTP Sync Interval (In Minutes)
|Data Usage
|15
|'''From:''' Start date (YYYY-MM-DD)
|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
'''To:''' End date  (YYYY-MM-DD)
 
|Displays data usage statistics for the  specified date range.
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.
|-
|20
|Monthly Data Usage
|'''Month:''' Month (e.g., 07)


It is further divided into 2 categories,
'''Year:''' Year  (e.g., 2024)
 
|Displays data usage statistics for the specified month and year.
'''WIFI 2.4G AP'''
 
'''WIFI 2.4G AP Guest'''
 
[[File:RB44 WIFI 2.4G AP Guest.png|1024x1024px]]
 
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.
 
[[File:RB44 Whitelist.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|1
|
|Status
|
|Enable/Disable
|
|Enable or disable the MAC ID filtering.
|
|-
|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.
|-
|-
|2
|23
|MAC ID
|Network operator list (First Perform  Scan Network Operators)
|Example: e8:6f:38:1a:f2:61
|Command ‘Show’
|The MAC address of the device to be whitelisted  or blocklisted.
|Displays the list of network operators detected  in the previous scan.
|-
|-
|3
|24
|Network Name
|ReadLogFiles
|Example: WIFI 2.4G AP or Wi-Fi 2.4G AP  Guest.
|Log file identifier
|The network to apply the MAC ID filtering.
|Reads and displays the specified log file
|}
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. 
 
[[File:RB44 Routing .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.
 
[[File:RB44 Static IPV4 Routes.png|1023x1023px]]
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|-
|1
|25
|Interface
|Enable ssh (Admin)
|Ex: eth0.1
|Command ‘Run’
|The network interface to be used for this route.  Select the one to use from dropdown.
|Enables SSH access for the admin user.
|-
|-
|2
|26
|Target
|Disable ssh (Admin)
|Ex: 192.168.20.0
|Command ‘Run’
|The destination subnet to which traffic should  be routed.
|Disables SSH access for the admin user.
|-
|-
|3
|27
|IPv4 Netmask
|ClearSIM1Data
|255.255.255.0
|Command ‘Clear’
|The subnet mask for the target network.
|Clears data usage statistics for SIM1.
|-
|-
|4
|28
|Metric
|ClearSIM2Data
|0
|Command ‘Clear’
|The priority of the route.
|Clears data usage statistics for SIM2.
 
Lower values indicate higher priority.
|-
|-
|5
|29
|IPv4 Gateway
|Create Bridge with SW_LAN
|Ex: 192.168.10.1
|Network interface identifier
|The gateway IP address to be used for routing traffic to the target subnet.
|Creates a network bridge with the specified interface and SW_LAN.
|-
|-
|6
|30
|Route Type
|Show Bridge
|Unicast
|Command ‘Show’
|Standard route for individual destination IP addresses.
|Displays information about the current network bridges.
 
|-
Custom changes can be made.
|31
|Delete Bridge
|Command ‘Delete’
|Deletes the specified network bridge.
|-
|32
|Output
|Any value
|Displays output for all the above actions.
|}
|}
Click on save once configuration changes have been made.


'''Advanced Static IPV4 Routes:'''
=== 5.7 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 is further divided into 2 sections,
[[File:RD44A Connection Diagnostics.png|1024x1024px]]


Routing Tables
This Application works in 3 parts,


Routing Rules for IPV4
1.) General settings


'''Routing Tables:'''
2.) Connection status and management


Adding a new table in static routing allows you to define specific routes for traffic within a network.
3.) Application Start/Stop


Click on ‘Add’ to add a new Table.
[[File:RB44 Application Start Stop.png|1024x1024px]]


[[File:RB44 Advanced Static IPV4 Routes-.png|1024x1024px]]
'''General settings:'''


'''EDIT:'''
First make configuration changes in this section and save.
 
[[File:RB44 Advanced Static IPV4 Routes Editing.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|ID of Table
|Ex: 1
|A unique identifier for the routing table.  Multiple tables can be used to define different sets of routing rules,  providing flexibility in how traffic is managed.
|-
|2
|Name of Table
|Ex: Route
|A descriptive name for the routing table,  making it easier to manage and identify different tables.
|-
|3
|Target
|Ex: 192.168.10.0
|Specifies the destination network or IP address  that the route is intended for.
|-
|4
|IPv4 Netmask
|255.255.255.0
|Defines the subnet mask for the target network.
|-
|5
|Metric
|Ex: 0
|Indicates the priority of the route. A lower  metric value means a higher priority. Routes with lower metrics are preferred  over those with higher metrics.
|-
|6
|IPv4 Gateway
|Ex: 10.1.1.1
|Specifies the next hop or gateway IP address through  which the traffic to the target network should be routed.
|-
|7
|Route Type
|1.) Unicast
 
2.) Custom
|'''Unicast''':  Standard route where packets are sent to a single destination IP address.
 
'''Custom''': Enables  advanced routing configurations or specific protocols that might not be  covered by default.
|}
 
 
 
'''Routing Rules for IPV4:'''
 
Click on ‘Add’ to add a new interface.
 
[[File:RB44 Routing Rules for IPV4.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.
 
[[File:RB44 Routing Rules for IPV4 Editing.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Interface
|Ex: ra0
|Select the specific network interface on the  router through which traffic enters or exits.
|-
|2
|To
|Ex: 192.168.10.1
|The destination IP address or network. In this  case, 192.168.10.1 is the target IP address for routing traffic.
|-
|3
|IPv4 Netmask
|Ex: 255.255.255.192
|Defines the subnet mask, which helps determine  the size of the network.
|-
|4
|Table ID
|Ex: 1
|Identifies which routing table this rule  applies to.
|-
|5
|From
|Ex: 192.168.100.1
|Specifies the source IP address or network from  which the traffic originates. In this case, the traffic is coming from  192.168.100.1.
|-
|6
|Priority
|Ex:20
|Determines the order in which routing rules are  evaluated. Lower numbers have higher priority. If two rules conflict, the one  with the lower priority number will be applied first.
|-
|7
|Outgoing Interface
|1.) fwmark
 
2.) iif (Incoming Interface)
 
3.) oif (Outgoing Interface)
 
4.) lookup
 
5.) blackhole
 
6.) prohibited
 
7.) unreachable
|1.) This  allows you to create rules that apply only to traffic that has been marked in  a specific way by the firewall.
 
2.) This is  often used to create rules based on the interface through which traffic is  received.
 
3.) This  allows you to control the flow of traffic based on the desired outgoing  interface.
 
4.) It tells the router to check the specific  routing table ID mentioned to determine how to route the traffic.
 
5.) This is  used when you want to block traffic without notifying the sender.
 
6.) Like  blackhole but sends an ICMP unreachable message to the sender, indicating  that the route is prohibited.
 
7.) Causes  the router to send an ICMP unreachable message to the source IP, notifying  that the destination is unreachable.
|}
 
=== 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) setting
 
[[File:RB44 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.
|-
|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.
 
[[File:RB44 Others .png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|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 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:RB44 Connection Diagnostics.png|1024x1024px]]
 
This Application works in 3 parts,
 
1.) General settings
 
2.) Connection status and management


3.) Application Start/Stop
[[File:RD44A Connection Diagnostics General Settings.png|1005x1005px]]
 
[[File:RB44 Application Start Stop.png|1024x1024px]]
 
'''General settings:'''
 
First make configuration changes in this section and save.


Specification details are given below:
Specification details are given below:
Line 3,904: Line 3,231:
You can leave the application on for monitoring else ‘Stop’ the application.
You can leave the application on for monitoring else ‘Stop’ the application.


=== 5.9 Package Manager ===
=== 5.8 Package Manager ===
A '''Package Manager''' is a tool or interface used to '''manage software packages''' (applications, libraries, tools) on a system.
A '''Package Manager''' is a tool or interface used to '''manage software packages''' (applications, libraries, tools) on a system.


Latest revision as of 12:24, 6 January 2025

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

To log in to SILBO_RD44-A 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_RD44-A 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

How to connect with the SILBO RB44 application

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 6 Modules.

  • Info
  • Settings
  • Maintenance
  • Status
  • Features
  • 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 45A27240002 This field displays the router serial number of the device
2 Model Silbo_RD44-A- 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 Kernel Version 4.14.180 This field displays the kernel version of the device
5 Local Time Thursday, December 5, 2024 at 04:05:24 PM This field displays the local time
6 Uptime 0h 3m 58s This field displays the uptime of the device
7 Load Average 1.03 0.98 0.44 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 68676 kB / 124208 kB (55%) This field displays the total availability of memory space in the device
2 Free 59344 kB / 124208 kB (47%) This field displays the Free memory space in the device
3 Cached 312 kB / 124208 kB (0%) This field displays the Cached memory space in the device
4 Buffered 9332 kB / 124208 kB (7%) 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


796 kB / 15488 kB (5%)

This field displays the total root usage of the device
2 Temporary Usage


312 kB / 62104 kB (0%)

This field displays the total temporary usage of the device

Connection Tracking

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


The specifications details are as follows.

SN Field name Sample value Description
1 Active Connection 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
  • Sim Switch
  • Internet
  • VPN
  • Firewall
  • Loopback Rule
  • 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.

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.


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, PPOE, PPTP and L2TP.

For port 5 setting,

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.

SN Field name Sample value Description
1 Port 5 mode LAN/WAN LAN This field displays the port mode selection
2 Port 5 Ethernet Protocol [LAN Eth0.1] DHCP Server

Static

This field displays the Ethernet mode selection
3 Port 5 DHCP Server IP

Port 5 Static IP

192.168.10.1

5.6.7.8

This field displays DHCP server and static IP configured.
4 Port 5 DHCP and Static Netmask 255.255.255.0 This field displays DHCP server and static Netmask address configured
5 Port 5 DHCP Start Address 100 This field displays DHCP server start address configured
6 Port 5 DHCP Limit 50 This field displays DHCP server limit

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.

SN Field name Sample value Description
1 Port 5 mode WAN EWAN2 This field displays the port mode selection
2 Ethernet Protocol Port 5 WAN 1.) DHCP client

2.) Static

3.) PPPoE

4.) PPTP

5.) L2TP

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

2.) Manually set a fixed IP address and network configuration.

3.) Point-to-Point Protocol over Ethernet, used for connecting to DSL services.

4.) Point-to-Point Tunnelling Protocol, used for establishing VPN connections.

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

The specifications details are below.

SN Field name Sample value Description
1 SW_LAN Ethernet Protocol DHCP Server This field displays the Ethernet mode selection
2 SW_LAN DHCP Server IP 192.168.10.1 This field displays DHCP server IP configured.
3 SW_LAN DHCP Netmask 255.255.255.0 This field displays DHCP server Netmask address configured
4 SW_LAN DHCP Start Address 100 This field displays DHCP server start address configured
5 SW_LAN DHCP Limit 50 This field displays DHCP server limit
6 DNS Server 1 This filed display number of DSN server availability
7 DNS Server Address 8.8.8.8 This filed display the DSN server address.

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.


Static option for SW_LAN Ethernet Protocol:

SN Field name Sample value Description
1 SW_LAN Ethernet Protocol Static This field displays the Ethernet mode selection
2 SW_LAN static IP 192.168.5.1 This field displays static server IP configured.
3 SW_LAN Netmask 255.255.255.0 This field displays static server Netmask address configured
4 DNS Server 1 This filed display number of DSN server availability
5 DNS Server Address 8.8.8.8 This filed display the DNS server address.

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.

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.

The specifications details are 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.

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’ and ‘Access point and client’

Refer the below picture.

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 only:

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)

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.

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.

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"}


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


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.

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 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.

2.2 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 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.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.

If the user needs to edit on the existing configuration, then the user should click on the “EDIT” button.

The specifications details are below.

SN Field name Sample value Description
1 Name EWAN2 This field displays the name of the WAN connection
2 Priority 1 In this dropdown box the user needs to select the priority.
3 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.
4 TrackIP1 8.8.8.8 This is the first IP address used for tracking the connection. 8.8.8.8 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. 8.8.4.4 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 1 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

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 5 types of setting available under VPN configuration.

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

General Settings:

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.

Click on the save after selecting the option based on its requirement.

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.


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.

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.

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.

RD44A Open VPN Status

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.

SN Field name Sample value Description
1 Wireguard Role Client/Server In this dropdown box the user needs to select the wireguard role.
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 Allowed PeerIPs 10.1.1.1 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.
5 Endpoint HostIP 10.1.1.1 The IP address of the WireGuard server (the endpoint to which the client connects).
6 Endpoint HostPort 51820 The port on the WireGuard server to which the client connects.
7 PeerPublicKey ***** 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.
8 Enable Preshared key Yes/No 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.
9 Preshared key ***** The actual pre-shared key value shared between the client and the server. This option appears only if you have enabled preshared key.

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

2.5 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.

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.

Specification details are below:

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:

Specification details are below:

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

2.      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.

*Refer the image below*

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.6 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 port 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: 1.1.1.1 Specify the loopback IP address.
6 Port Example: 81 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: 2.2.2.2 Field must not be empty: Specify the internal IP address to which the traffic should be redirected.
9 Internal Port Example: 81 Redirect matched incoming traffic to the given port on the internal host.

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

2.7 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.8 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 below submodules.

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

*Below is the detailed explanation of every field*

3.1 General/ System

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

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 Time zone Asia/Kolkata The time zone 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 detail 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 reset 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, Wi-Fi, 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 has.

This module includes 9 features.

  • Mac Address Binding
  • URL Filtering
  • Web Server
  • Wi-Fi MacID Filtering
  • Routing
  • DMZ
  • Others
  • Connection Diagnostics
  • Package Manager

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 mac1 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:

This is further divided into 2 sections,

Routing Tables

Routing Rules for IPV4

Routing Tables:

Adding a new table in static routing allows you to define specific routes for traffic within a network.

Click on ‘Add’ to add a new Table.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 ID of Table Ex: 1 A unique identifier for the routing table. Multiple tables can be used to define different sets of routing rules, providing flexibility in how traffic is managed.
2 Name of Table Ex: Route A descriptive name for the routing table, making it easier to manage and identify different tables.
3 Target Ex: 192.168.10.0 Specifies the destination network or IP address that the route is intended for.
4 IPv4 Netmask 255.255.255.0 Defines the subnet mask for the target network.
5 Metric Ex: 0 Indicates the priority of the route. A lower metric value means a higher priority. Routes with lower metrics are preferred over those with higher metrics.
6 IPv4 Gateway Ex: 10.1.1.1 Specifies the next hop or gateway IP address through which the traffic to the target network should be routed.
7 Route Type 1.) Unicast

2.) Custom

Unicast: Standard route where packets are sent to a single destination IP address.

Custom: Enables advanced routing configurations or specific protocols that might not be covered by default.


Routing Rules for IPV4:

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 Select the specific network interface on the router through which traffic enters or exits.
2 To Ex: 192.168.10.1 The destination IP address or network. In this case, 192.168.10.1 is the target IP address for routing traffic.
3 IPv4 Netmask Ex: 255.255.255.192 Defines the subnet mask, which helps determine the size of the network.
4 Table ID Ex: 1 Identifies which routing table this rule applies to.
5 From Ex: 192.168.100.1 Specifies the source IP address or network from which the traffic originates. In this case, the traffic is coming from 192.168.100.1.
6 Priority Ex:20 Determines the order in which routing rules are evaluated. Lower numbers have higher priority. If two rules conflict, the one with the lower priority number will be applied first.
7 Outgoing Interface 1.) fwmark

2.) iif (Incoming Interface)

3.) oif (Outgoing Interface)

4.) lookup

5.) blackhole

6.) prohibited

7.) unreachable

1.) This allows you to create rules that apply only to traffic that has been marked in a specific way by the firewall.

2.) This is often used to create rules based on the interface through which traffic is received.

3.) This allows you to control the flow of traffic based on the desired outgoing interface.

4.) It tells the router to check the specific routing table ID mentioned to determine how to route the traffic.

5.) This is used when you want to block traffic without notifying the sender.

6.) Like blackhole but sends an ICMP unreachable message to the sender, indicating that the route is prohibited.

7.) Causes the router to send an ICMP unreachable message to the source IP, notifying that the destination is unreachable.

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.

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.7 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.8 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.Logout

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

Retrieved from "https://wiki.silbonetworks.com/index.php?title=RD44_A_Manual&oldid=2604"