RB44 Manual: Difference between revisions

From Silbo Networks
VisualWikitext
No edit summary
 
(29 intermediate revisions by the same user not shown)
Line 252: Line 252:
[[File:Kernel Log.png|1020x1020px]]
[[File:Kernel Log.png|1020x1020px]]


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


Line 299: Line 299:
[[File:RB44 EWAN Network Config.png|1020x1020px]]
[[File:RB44 EWAN Network Config.png|1020x1020px]]


'''For port 5 setting,'''
Specification details are given below:  '''Type: WAN'''
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|1
|Physical Device
|Ex: eth0.5  
|This indicates a network interface on which our network is connected. This setting is by default (Editable).
|-
|2
|Type
|'''WAN'''/LAN
|This designates whether the interface is part of the WAN or LAN.


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.
WAN: Connects the device to the internet.  


[[File:RB44 five port Settings.png|frameless|620x620px]]
LAN: Connects the device to the internal network.  
 
|-
{| class="wikitable"
| colspan="4" |                                                                          '''Protocol: Static'''
|SN
|-
|Field name
|3
|Sample value
|Static IP Address
|Description
|Ex: 192.168.1.10
|The manually assigned IP address for the interface.
|-
|4
|Static Netmask
|Ex: 255.255.255.0
|Subnet mask corresponding to the IP address.
|-
|5
|Static Gateway
|Ex: 192.168.1.1
|The IP address of the gateway (router) that the interface will use to send traffic outside its own subnet.
|-
| colspan="4" |                                                                          '''Protocol: DHCP'''
|-
|6
|DHCP Gateway
|Ex: 10.1.1.1
|The IP address of the DHCP server (often the same as the router or gateway).
|-
| colspan="4" |                                                                            '''Protocol: PPPoE'''
|-
|7
|Username
|Any Name
|The username provided by your ISP for PPPoE authentication.
|-
|-
|1
|8
|Port 5 mode LAN/WAN
|Password
|LAN
|*****
|This field displays the port mode selection
|The password provided by your ISP for PPPoE authentication.
|-
|-
|2
|9
|Port 5 Ethernet Protocol  [LAN Eth0.1]
|Access Concentrator
|DHCP Server
|
 
|Typically, the name of the ISP's PPPoE server.
Static
|This field  displays the Ethernet mode selection
|-
|-
|3
|10
|Port 5 DHCP Server IP
|Service Name
 
|
Port 5 Static IP
|Sometimes required by ISPs, this field specifies a particular service offered by the ISP.  
|192.168.10.1
 
5.6.7.8
|This field displays DHCP server and static IP configured.
|-
|-
|4
|11
|Port 5 DHCP and Static  Netmask
|Gateway
|255.255.255.0
|Ex: 0.0.0.0  
|This field displays DHCP server and static Netmask address configured
|The IP address used as the default route.
|-
|-
|5
|12
|Port 5 DHCP Start Address
|Override MAC Address  
|100
|Ex: D0:93:95:B0:CF:7A
|This field displays DHCP server start address configured
|The MAC address for this interface is set to a custom value, replacing the default hardware address.
|-
|-
|6
|13
|Port 5 DHCP Limit
|Enable Bridge
|50
|
|This field displays DHCP server limit
# CWAN1_0
|}
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:RB44 Ewan2 5 port Configuration.png|frameless|620x620px]]
# SW_LAN


# VPN


# ra0 


The specifications details are below.
|Since this is a WAN interface, it is not typically bridged with others. Bridges are more common for LAN interfaces to combine multiple connections.  
{| class="wikitable"
|-
|SN
|14
|Field name
|Create Firewall Zone
|Sample value
|Enable/Disable
|Description
|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'''
|-
|-
|1
|15
|Port 5 mode WAN
|IPv4 Route Table
|EWAN2
|Enable/Disable
|This field displays the port mode selection
|This field is used to specify static routes for IPv4.
|-
|-
|2
|16
|Table No.
|'''254''': Default main routing table.


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


'''Custom Table''': You can specify a different table number if you are managing multiple routing policies (e.g., VoIP traffic, VPN traffic).
|-
|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.
|-
|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.  
|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
|20
|Gateway
|Force Link
|192.168.1.1
|Enable/Disable
|This field displays gateway address  configured
|Forces the interface to be up even if no physical link is detected.
|}
|}


'''Type: LAN'''
[[File:RB44 SW LAN Configuration.png|1024x1024px]]Specification details are given below:


Click on the save once all the configuration is done and click on the update button to update all the information.
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Physical Device
|Ex: eth0.1
|This is the network interface identifier.
|-
|2
|Type
|WAN/'''LAN'''
|This designates whether the interface is part  of the WAN or LAN.


WAN: Connects the device to the internet.


'''SW_LAN settings,'''
LAN: Connects the device to the internal network.
 
|-
In this part the user can configure the setting for SW_LAN.
 
'''Note:''' After any changes made, save and update the page below.
 
[[File:RB44 SW LAN Settings.png|frameless|620x620px]]
 
 
 
The specifications details are below.
{| class="wikitable"
|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 which can be changed accordingly.
|-
|3
|3
|SW_LAN  DHCP Netmask
|Protocol
|255.255.255.0
|Static
|This field displays DHCP server Netmask  address configured.
|This means that the IP address, netmask, and other  network settings are manually configured rather than being automatically  assigned by a DHCP server.
|-
|-
|4
|4
|SW_LAN  DHCP Start Address
|IP Address
|100
|Ex: 192.168.10.1
|This field displays DHCP server start address configured.
|This is the static IP address assigned to the interface. It acts as the gateway IP address for devices connected to this  LAN.
|-
|-
|5
|5
|SW_LAN  DHCP Limit
|Static Netmask
|50
|Ex: 255.255.255.0
|This field displays DHCP server limit.
|This is the subnet mask for the network.
|-
|7
|Override MAC Address
|D0:93:95:B0:CF:7B
|This allows you to manually enter a different  MAC address if needed.
|-
|-
|6
|8
|DNS Server
|Enable DNS
|1
|Enable/Disable
|This filed display number of DNS server availability.
|If this option is enabled, the interface will  act as a DNS resolver for the devices on the LAN, using the specified DNS  server.
|-
|-
|7
|9
|DNS Server Address
|DNS Server Address
|8.8.8.8
|Ex: 8.8.8.8
|This filed display the DNS  server address.
|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.
|}
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:'''
More than one DNS Address can be added.
|-
|10
|Enable DHCP Server
|Enable/Disable
|If enabled, this setting allows the interface  to function as a DHCP server, automatically assigning IP addresses to devices  connected to the LAN.
|-
|11
|DHCP Start Address
|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)


Select the option of static from the drop-down menu for SW_LAN Ethernet Protocol.
Minutes-(M)


'''Note:''' After any changes made, save and update the page below.
Seconds-(S)
|'''Hours-(H)''': This  indicates that the lease time for each IP address assignment is measured in  hours.


[[File:RB44 Static option for SW LAN Ethernet Protocol.png|frameless|620x620px]]
'''Minutes-(M):''' This  indicates that the lease time for each IP address assignment is measured in minutes.


The specifications details are below.
'''Seconds-(S):''' This  indicates that the lease time for each IP address assignment is measured in seconds.
{| class="wikitable"
|SN
|Field name
|Sample value
|Description
|-
|-
|1
|14
|SW_LAN Ethernet Protocol
|Lease Time
|Static
|12
|This field displays the Ethernet mode selection
|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.
|-
|-
|2
|15
|SW_LAN static IP
|Enable Bridge
|192.168.5.1
|1.      CWAN1_0
|This field displays static server IP configured.
 
2.      SW_LAN
 
3.      VPN
 
4.      ra0
 
|Since this is a WAN interface, it is not  typically bridged with others. Bridges are more common for LAN interfaces to combine multiple connections.
|-
|-
|3
|16
|SW_LAN  Netmask
|Enable DHCP Relay
|255.255.255.0
|Enter Relay Server IP
|This field displays static server Netmask  address configured
|Forwards DHCP requests from devices in this  subnet to an external DHCP server instead of using the built-in DHCP server.
 
|-
|-
|4
|17
|DNS Server
|Create Firewall Zone
|1
|Enable/Disable
|This filed display number of DSN server availability
|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).
|-
|18
|Internet Over SW_LAN
|Enable/Disable
|Allow all outbound traffic from the LAN to the  internet.
|-
| colspan="4" |'''Advanced Settings: Enable/Disable'''
|-
|19
|IPv4 Route Table
|Enable/Disable
|This field is used to specify static routes for IPv4.
|-
|20
|Table No.
|'''254''': Default  main routing table.
 
'''100''': Custom  routing table for specific purposes.
|'''Default Table (Main Table)''': Usually, there is a default routing table  (often Table No. 254 or 255) where all the routes are stored by default.
 
'''Custom Table''': You can  specify a different table number if you are managing multiple routing  policies (e.g., VoIP traffic, VPN traffic).
|-
|21
|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.
|-
|22
|Broadcast
|Ex: 192.168.123.34
|Broadcast address for the network, typically calculated based on the IP and subnet mask.
|-
|-
|5
|23
|DSN  Server Address
|Override MTU
|8.8.8.8
|Ex: 1500
|This filed display the DSN server address.
|MTU size controls the maximum packet size that can be sent over the network.
 
Default is usually 1500 bytes.
|}
|}
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.
Save and Update once configuration changes have been made.
 
 
'''Relay Server:'''


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


In this page, the user needs to configure the various details with respect to the SIM.
a designated server when the server is on a different network segment.


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 Relay Server Settings.png|1020x1020px]]


[[File:RB44 Cellular Setting.png|frameless|800x800px]]
'''EDIT:'''


The specifications details are below.
To edit the existing device the user needs to click on the edit option.
{| class="wikitable"
 
|SN
Once the changes are done click on the save button to save all the changes.
|Field name
 
|Sample  value
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"
|SN
|Field Name
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|Cellular Enable
|Interface
|Checkbox
|1.)    eth0.1
|Check this box to  enable cellular functionality.
 
2.)    ra0
|1) eth0.1  typically represents a VLAN where the relay will listen for client requests.
 
2) If your  device is broadcasting a Wi-Fi network on the ra0 interface, any DHCP or DNS  relay settings will apply to devices connected via this wireless interface.
|-
|-
|2
|2
|Cellular Operation Mode
|Start IP Address
|1.) Single Cellular with Dual Sim
|Ex: 192.168.10.100
 
|This is the beginning IP address of the range that will be leased out to clients.
2.) Single Cellular with Single  SIM
|1.) This mode allows you to use one cellular modem with two SIM cards.
 
2.) This mode allows you to use one cellular modem with single SIM card.
|-
|-
|3
|3
|Cellular Modem 1
|End IP Address
|QuectelEC200A
|Ex: 192.168.10.150
|This field displays the modem name.
|An IP address that is in the same subnet as the Start IP Address and allows sufficient  addresses to be leased.
|-
|-
|4
|4
|Choose SIM 1 APN Mode
|Netmask
|1.) Auto
|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).
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
|5
|SIM 1 Access Point Name
|Lease Time
|airtelgprs.com
|For a 24-hour  lease time, set this value to 86400.
|Enter the APN provided by your cellular service provider in case of M2M sim. For regular  sim cards APN name will be displayed automatically.
|This is the  amount of time that an IP address is assigned to a client before it needs to  request a renewal from the DHCP server.
|}
Save and update.
 
'''Cellular Setting:'''
 
In this page, the user needs to configure the various details with respect to the SIM.
 
Select single cellular single sim where the user must configure the APN details of the sim used for the router device. The Configurations can be done based on the SIM usage, with respect to IPV4 or IPV6.
 
[[File:RB44 Cellular Setting.png|1020x1020px]]
 
The specifications details are below.
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|-
|6
|1
|SIM 1 PDP Type
|Cellular Enable
|IPV4
|Checkbox
|Choose the PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
|Check this box to enable cellular functionality.
|-
|-
|7
|2
|SIM 1 Username
|Cellular  Operation Mode
|
|1.) Single Cellular with Dual Sim
|Enter the username if required by the APN.  Leave blank if not required.
 
|-
2.) Single Cellular with Single SIM
|8
|1.) This mode  allows you to use one cellular modem with two SIM cards.
|SIM 1 Password
 
|
2.) This mode allows you to use one cellular modem with single SIM card.
|Enter the password if required by the APN. Leave blank if not required.
|-
|-
|9
|3
|SIM 1 Authentication Protocol
|Cellular  Modem 1
|None
|QuectelEC200A
|Choose the authentication protocol. Options typically include None, PAP, or CHAP.
|This  field displays the modem name.
|-
|-
|10
|4
|Choose SIM 2 APN Mode
|Choose SIM 1 APN Mode
|1.) Auto
|1.) Auto


2.) Manual
2.) Manual
|1.) Choose  Auto for regular SIM to detect APN name automatically.
|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.
2.) Choose manual to enter the APN settings manually in case of  M2M SIM cards.
|-
|-
|11
|5
|SIM 2 Access Point Name
|SIM 1 Access Point Name
|airtelgprs.com
|airtelgprs.com
|Enter the APN  provided by your cellular service provider in case of M2M sim. For regular sim cards APN name will be displayed automatically.
|Enter the APN provided by your cellular service provider in case of M2M sim. For regular sim cards APN name will be displayed automatically.
|-
|-
|12
|6
|SIM 2 PDP Type
|SIM 1 PDP Type
|IPV4
|IPV4
|Choose the  PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
|Choose the PDP type, which is typically either IPv4 or IPv6 depending on the sim card.
|-
|-
|13
|7
|SIM 2 Username
|SIM 1 Username
|
|
|Enter the username if required by the APN. Leave blank if not required.
|Enter the username if required by the APN. Leave blank if not required.
|-
|-
|14
|8
|SIM 2 Password
|SIM 1 Password
|
|
|Enter the password if required by the APN. Leave blank if not required.
|Enter the password if required by the APN. Leave blank if not required.
|-
|-
|15
|9
|SIM 2 Authentication Protocol
|SIM 1 Authentication Protocol
|None
|None
|Choose the  authentication protocol. Options typically include None, PAP, or CHAP.
|Choose the  authentication protocol. Options typically include None, PAP, or CHAP.
|-
|-
|16
|Primary SIM Switchback Time (In Minutes)
|10
|10
|Enter the  time in minutes after which the system should switch back to the primary SIM  if it becomes available.
|SIM 1 MTU
|}
|Ex: 1500 (a common MTU size)
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.
|'''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


'''Band lock and Operator Lock:'''
2.) Manual
|1.) Choose  Auto for regular SIM to detect APN name automatically.


In this page, the user needs to configure the lock band and operator based on the service provider'''.'''
2.) Choose manual to enter the APN settings manually in case of  M2M SIM cards.
 
|-
Bands available in the drop-down list.
|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.


[[File:RB44 Band lock and Operator Lock.png|frameless|620x620px]]
'''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.
 
[[File:RB44 Band lock and Operator Lock.png|1020x1020px]]


'''2G/3G option:'''
'''2G/3G option:'''
Line 618: Line 782:
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|frameless|620x620px]]
[[File:RB44 2G-3G Option.png|1020x1020px]]


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 628: Line 792:
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|frameless|620x620px]]
[[File:RB44 Operator Selection Mode.png|1020x1020px]]


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|frameless|620x620px]]
[[File:RB44 Operator Selection Mode Manual or Manual Automatic Settings.png|1020x1020px]]


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 643: Line 807:
The user needs to select the respective radio mode based on its need.  
The user needs to select the respective radio mode based on its need.  


[[File:RB44 Wifi General Setting.png|frameless|620x620px]]
[[File:RB44 Wifi General Setting.png|1020x1020px]]


It has 3 radio modes.
It has 3 radio modes.
Line 651: Line 815:
Refer the below picture.
Refer the below picture.


[[File:RB44 Access point update.png|frameless|620x620px]]
[[File:RB44 Access point update.png|1020x1020px]]


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


[[File:RB44 Access point mode.png|frameless|620x620px]]
[[File:RB44 Access point mode.png|1020x1020px]]


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


[[File:RB44 Client Mode.png|frameless|620x620px]]
[[File:RB44 Client Mode.png|1020x1020px]]


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


[[File:RB44 Access point and Client Point.png|frameless|620x620px]]
[[File:RB44 Access point and Client Point.png|1020x1020px]]


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 764: Line 928:
(50 value is default)
(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.
[[File:RB44 Guest Wifi.png|1024x1024px]]
'''Wireless Schedule:'''
'''Wireless Schedule:'''


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


[[File:RB44 Wireless Schedule.png|frameless|620x620px]]
[[File:RB44 Wireless Schedule.png|1020x1020px]]


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


[[File:RB44 wireless Schedule Editing.png|frameless|620x620px]]
[[File:RB44 wireless Schedule Editing.png|1020x1020px]]
 
'''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.
 
[[File:RB44 Lookback IP Settings.png|frameless|620x620px]]
 
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.


'''SMS Settings:'''
'''SMS Settings:'''
Line 802: Line 961:
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.
Displayed in the below screen is the default API key which can be edited and changed as per choice. After addition of the mobile number’s user needs to click on save button for changes to take place.


[[File:RB44 SMS Settings.png|frameless|620x620px]]
[[File:RB44 SMS Settings.png|1020x1020px]]


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.  
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.  
Line 822: Line 981:
After configuring all the required information, the user should click on save and then click on update to update all the required information.
After configuring all the required information, the user should click on save and then click on update to update all the required information.


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


[[File:RB44 SIM Switch Configuration.png|frameless|620x620px]]


'''Loop back IP settings:'''


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


The user needs to select from the drop-down menu on which basis the sim needs to be switched.
[[File:RB44 Lookback IP Settings.png|1020x1020px]]


[[File:RB44 SIM Switch Update.png|frameless|620x620px]]
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.


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


[[File:RB44 SIM Switch based on Signal Strength.png|frameless|620x620px]]
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 ===
'''VLAN (Virtual Local Area Network)''' is a network within a network that segregates traffic into different logical networks on the same physical hardware. VLANs help in managing traffic more effectively and securely.


It is further divided into 2 sections,


Port-Based VLAN


'''Threshold RSRP:'''
Tagged Port Configuration


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).
'''Port-Based VLAN:'''


'''Threshold SINR:'''
A VLAN configuration method where network ports are assigned to specific VLANs.


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.png|1020x1020px]]
 
'''EDIT:'''
 
To add a new VLAN ID, click on ‘Add Device’.
 
To edit the existing device the user needs to click on the edit option.
 
Once the changes are done click on the save button to save all the changes.
 
Click on the deleted button to delete the existing device detail.


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


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


=== 2.3 Internet ===
'''EDIT:'''
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 Internet Connection Configuration.png|frameless|620x620px]]
To add a new VLAN ID, click on ‘Add Device’.


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


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


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


=== 2.4 VPN ===
The user needs to select from the drop-down menu on which basis the sim needs to be switched.
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.
[[File:RB44 SIM Switch Update.png|1020x1020px]]


Navigate to settings >= VPN, general settings and you will see all VPN options you wish to use.
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.


Refer the below figure.
[[File:RB44 SIM Switch based on Signal Strength.png|1020x1020px]]


[[File:VPN Configuration Dashboard.png|frameless|620x620px]]


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


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


'''General Settings:'''
'''Threshold SINR:'''


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


AES 192


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


3DES
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.
|'''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
Navigate to settings >= VPN, general settings and you will see all VPN options you wish to use.


SHA 256
Refer the below figure.


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


'''SHA 512'''
There are 5 types of setting available under VPN configuration.
|'''SHA 512''': Authentication  algorithm for Phase I.


Select as per  server-side configuration. Both server and client should have same  configuration.
* General Settings
|-
* IPSEC
|24
* Open VPN
| colspan="2" |DH Group
* Wireguard
| colspan="3" |MODP768(group1)
* Zerotier
* PPTP
* L2TP


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


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


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


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


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


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


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


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


3DES
The user needs to click on the update button once the required configuration is completed.
| 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
In IPSEC the user needs to click on edit button to edit the configuration of an existing VPN connection.


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


SHA 384
Click on update once done with configurations.


'''SHA 512'''
The tunnel will show established, showing the connection has been made.
| colspan="2" |'''SHA 512''': Authentication  algorithm for Phase II.
 
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)
[[File:VPN Configurtaion IPSEC .png]]


MODP1536(group5)


'''MODP2048(group14)'''
Detailed specifications are below:
 
{| class="wikitable"
MODP3072(group15)
|SN
 
|Field name
MODP4096(group16)
|Sample value
| colspan="2" |'''MODP2048 (group14)''': Perfect  Forward Secrecy group.
|Description
 
|-
Select as per server-side configuration. Both server and client should have same  configuration.
|1
|}'''Open VPN:'''
|IPSEC
 
|Site to Site 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.
|In this dropdown the user should select the IPSEC connection type.
 
To use the VPN feature, the user should enable OpenVPN Server on the router, and install and run VPN client software on the remote device.
 
[[File:Open VPN Settings .png|frameless|620x620px]]
 
The user needs to “upload” the respective certificate from a valid path and then click on the “Update.”
 
Once the OpenVPN connection starts the user will get an option to enable/disable the VPN connection as and when required.
 
By clicking on the enable/disable button, the user can start/stop the VPN connection.
 
[[File:Open VPN Dashboard.png|frameless|620x620px]]
 
VPN has been established.
 
'''WireGuard:'''
 
'''WireGuard''' is simple, fast, lean, and modern VPN that utilizes secure and trusted cryptography.
 
Click on “Edit” to start configurations as needed.
 
[[File:Wire Guard RC44.png|frameless|620x620px]]
 
EDIT:
 
[[File:Wire Guard RC44 Setttings.png|frameless|620x620px]]
 
Click on the save button after the required configuration.
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|-
|1
|2
|Wireguard Role
|IPSEC Role
|Client/Server
|Client/Server
|In this dropdown box the user needs to select the wireguard role.
|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).
|-
|2
|Listen Port
|51820
|The UDP port on which the WireGuard client  listens for incoming connections.
|-
|-
|3
|3
|IP Addresses
|Connection Type
|10.0.0.1/24
|Tunnel
|The IP address and subnet mask assigned to the WireGuard client's interface. This address is used within the VPN.
|In this dropdown the user needs to select the connection type. The user should select on the connection enable check box.
|-
|-
|4
|4
|Allowed PeerIPs
|Connection mode
|10.1.1.1
|Route/add/'''start'''/trap
|The IP address of the allowed peer(s) that can connect to this WireGuard client. This might need adjustment based on the actual peer IPs used in the network.
|In this drop down list the user should select the mode for the connection. In this example '''start''' is selected which means the VPN connection is initiated automatically.
|-
|-
|5
|5
|Endpoint HostIP
|Remote Server IP
|10.1.1.1
|********
|The IP address of the WireGuard server (the endpoint to which the client connects).
|The IP address of the remote VPN server.
|-
|-
|6
|6
|Endpoint HostPort
|Local ID
|51820
|3.3.3.3
|The port on the WireGuard server to which the client connects.
|The user needs to set the local id. It is the identification for the local VPN client.
|-
|-
|7
|7
|PeerPublicKey
|No. of local subnets
|*****
|1
|The public key of the peer (the server) the client is connecting to. This key is part of  the public-private key pair used in WireGuard for encryption and  authentication.
|In this dropdown the user needs to select how many subnets will be connected.
|-
|-
|8
|8
|Enable Preshared key
|Local Subnet 1
|Yes/No
|172.16.31.25/32
|This option indicates that a pre-shared key (PSK) is used in addition to the public-private key pair for an extra layer of security.
|In this text box the user needs to put the specific local subnet included in the VPN.
|-
|-
|9
|9
|Preshared key
|Remote id
|*****
|1.1.1.1
|The actual  pre-shared key value shared between the client and the server. This option  appears only if you have enabled preshared key.
|In this text box  the user needs to put the id of the remote connection. It is the identification for the remote VPN server.
|}
'''Zerotier:'''
 
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:Zero Tier Enabling.png|frameless|620x620px]]
 
Copy and paste the unique 16-digit network ID in the edit section.
 
[[File:Zero tier Unique ID.png|frameless|620x620px]]
 
[[File:Zerotier Connection.png|frameless|620x620px]]
 
Click on the save button after the required configuration.
{| class="wikitable"
|SN
|Field name
|Sample  value
|Description
|-
|-
|10
|No of remote subnet
|1
|1
|NetworkID
|In this dropdown  the user needs to select how many subnets it will be connected remotely.
|Ad2769hfkw2345f4
|-
|In this dropdown box the user needs to paste the unique 16-digit network id.
|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.
|-
|-
|2
|12
|Listen Port
|Key exchange
|9993
|Ikev1
|Default
|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.
=== 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.
|17
 
|Time Interval (In Seconds)
[[File:Firewall General Settings.png|frameless|620x620px]]
|60
 
|This option is available only if DPD  Detection is enabled. The time interval is the interval for DPD checks.
There are 6 types of setting available under firewall.
|-
|18
|Action
|'''Restart'''/clear/hold/


* General Settings
trap/start
* Port forwards
|'''Restart''':  Action to take when DPD detects a lost connection (restart the connection). Select as per server-side setting.
* 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:Firewall Configuration 1.png|frameless|620x620px]]
 
{| class="wikitable"
|'''SN'''
|'''Field Name'''
|'''Sample Value'''
|'''Description'''
|-
|-
|1
|19
|Enable SYN-flood protection
|Authentication Method
|Enabled
|'''PSK'''
|This is enabled by default; setting can be changed  if required.
|'''PSK''': Pre-shared  key is used for authentication. Select this option for authentication as per  sever side setting.
|-
|-
|2
|20
|Disable IPV6
|Multiple Secrets
|Disabled
|1/'''0'''
|This is enabled by default; setting can be changed if required.
|Indicates whether multiple PSK secrets are used. Enable only if required.
|-
|-
|3
|21
|Drop invalid packets
|PSK Value
|Disabled
|******
|This is enabled by default; setting can be changed if required.
|Pre-shared key value (masked for security).
|}
{| class="wikitable"
| colspan="7" |'''Proposal settings Phase I'''
|-
|-
|4
|22
|TCP SYN Cookies
| colspan="2" |'''Encryption Algorithm'''
|Disabled
| colspan="3" |AES 128
|This is enabled by default; setting can be changed if required.
 
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.
|-
|-
|5
|23
|Input
| colspan="2" |Authentication Phase I
|Reject/Accept
| colspan="3" |SHA1
|By default, the setting is ‘Reject’ but this needs  to be changed to ‘Accept’ compulsory.
 
|-
MD5
|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.
SHA 256


[[File:Firewall Zone Settings.png|frameless|620x620px]]
SHA 384


'''Port Forwards:'''
'''SHA 512'''
|'''SHA 512''': Authentication  algorithm for Phase I.


Port forwarding is a feature in a router or gateway that allows external devices to access services on a private network.
Select as per  server-side configuration. Both server and client should have same  configuration.
|-
|24
| colspan="2" |DH Group
| colspan="3" |MODP768(group1)


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.
MODP1024(group2)


This helps in directing incoming traffic to the correct device within a local network based on the port number, enhancing connectivity and accessibility.
MODP1536(group5)
[[File:Firewall Enabled.png|frameless|620x620px]]


EDIT:
'''MODP2048(group14)'''


[[File:Firewall Configuration 2.png|frameless|620x620px]]
MODP3072(group15)


Click on the save button after the required configuration.
MODP4096(group16)
{| class="wikitable"
|'''MODP2048 (group14)''':  Diffie-Hellman group for key exchange.
|SN
 
|Field name
Select as per  server-side configuration. Both server and client should have same configuration.
|Sample value
|Description
|-
|-
|1
| colspan="7" |'''Proposal settings Phase II'''
|Name
|Example: <code>Web_Server_Forward</code>
|Field must  not be empty. Provide a name for the rule to easily identify it.
|-
|-
|2
| colspan="2" |25
|Protocol
| colspan="2" |Hash Algorithm
|Example: <code>TCP+UDP</code>
|AES 128
|Select the protocol  for the rule.
 
AES 192
 
'''AES 256'''


Options typically include TCP+UDP, TCP, UDP, ICMP, Custom.
3DES
| colspan="2" |'''AES 256''': Encryption algorithm for Phase II. Select as per server-side configuration. Both server and client  should have same configuration.
|-
|-
|3
| colspan="2" |26
|Source zone
| colspan="2" |Authentication Phase II
|Example: <code>SW_LAN</code>
|SHA1
|Select the source zone where the traffic is originating  from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
 
|-
MD5
|4
|Source MAC address [optional]
|Example: <code>any</code>
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|-
|5
|Source IP address[optional]
|Example: Leave blank if not needed.
|Optionally  specify an IP address or range.
|-
|6
|Source port
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|Specify the  source port or port range.
|-
|7
|Destination zone
|Example: <code>SW_LAN</code>
|Select the  destination zone where the traffic is heading to.
|-
|8
|Destination IP address
|Leave blank if not needed.
|Optionally specify  the destination IP address or range.
|-
|9
|Destination port
|Example: <code>80</code>  (if redirecting to a web server port)
|Specify the  destination port or port range.
|}
'''Traffic Rule:'''


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


To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.
SHA 384
 
'''SHA 512'''
| colspan="2" |'''SHA 512''': Authentication  algorithm for Phase II.
 
Select as per  server-side configuration. Both server and client should have same  configuration.
|-
| colspan="2" |27
| colspan="2" |PFS Group
|MODP768(group1)


[[File:Firewall Traffic Rule Dashboard.png|frameless|620x620px]]
MODP1024(group2)


EDIT:
MODP1536(group5)


[[File:Firewall Edit Options .png|frameless|620x620px]]
'''MODP2048(group14)'''
{| class="wikitable"
|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
MODP3072(group15)


Example: IPv4 if dealing with typical internet traffic.
MODP4096(group16)
|Select the address family to generate iptables rules for.
| colspan="2" |'''MODP2048 (group14)''': Perfect Forward Secrecy group.
|-
 
|3
Select as per  server-side configuration. Both server and client should have same configuration.
|Protocol
|}
|Example: TCP+UDP
'''Open VPN:'''
|TCP+UDP: Match incoming traffic using the  given protocol.
 
|-
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.
|4
 
|Match ICMP Type
[[File:Open VPN Settings .png|975x975px]]
|Example: any
 
|Match all ICMP types if set to any.  Specific types can be chosen if needed.
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
|Description
|-
|-
|5
|1
|Source Zone
|Wireguard Role
|Example: LAN
|Client/Server
|Specifies the traffic source zone.
|In this dropdown box the user needs to select  the wireguard role.
|-
|2
|WireGuard Tunnel Over
|IPV4/IPV6
|'''IPV4''': Use this  if your network and endpoint (WireGuard server) support only IPv4.
 
'''IPV6''': Use  this if your network and endpoint support IPv6.
|-
|3
|Enable Failover
|Enable/Disable
|This option allows the VPN connection to  automatically switch to a backup connection if the primary connection fails.
|-
|4
|Enable IPV4
|Enable/Disable
|This enables IPv4 traffic to be routed through  the WireGuard tunnel.
|-
|5
|Enable IPV6
|Enable/Disable
|Enable this if your network and the destination  support IPv6.
|-
|-
|6
|6
|Enable DDoS  Prevention
|Listen Port
|Example:  ‘Checked’ if you want to enable DDoS prevention measures
|51820
|Enable or disable Distributed Denial of Service (DDoS) prevention.
|This is the default port that WireGuard uses to listen for incoming connections.
|-
|-
|7
|7
|Source MAC  Address
|Endpoint Host port
|Example: any
|51820
|any: Match traffic from any MAC address or specify a particular MAC address.
|This is the port on the WireGuard server that the client will connect to.
|-
|-
|8
|8
|Source Address
|Peer Publickey
|Example:  192.168.1.0/24
|*****
|Match incoming traffic from the specified source IP address or range.
|This is the  public key of the WireGuard server that the client uses to establish a secure connection.
|-
|-
|9
|9
|Source Port
|Enable Default Route
|Example: any if all source ports should be matched
|Enable/Disable
|any: Match incoming traffic from the specified source port or port range.
|Enable this  if you want all network traffic (not just specific routes) to be routed through the WireGuard VPN.
|-
|}
|10
Save and update the page after configuration has been done.
|Destination Zone
 
|Example: WAN
 
|Specifies the traffic destination zone.
'''Zerotier:'''
|-
 
|11
ZeroTier is a tool that lets you create your own private network over the internet.
|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:'''
Go to ZeroTier Central and sign up for a free account.


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.
In ZeroTier Central, click on "Create a Network". This will generate a unique 16-digit network ID for your new network.


To add new source NAT,
Go to settings => VPN, in general settings, enable ZeroTier and save.


Click on “ADD” in “New Source NAT:”
[[File:RB44 Zerotier Enable.png|1024x1024px]]


[[File:SNAT Traffic Rule.png|frameless|620x620px]]
Copy and paste the unique 16-digit network ID in the edit section.


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


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


'''Parental Control:'''


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


destination zones, as well as specific devices.
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 parental control in firewall,


Click on “Add and Edit” in “New parental control:” field.
''*Refer the image below*''


[[File:Parental Control.png|frameless|620x620px]]
[[File:L2TP Configuration.png|1024x1024px]]  


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


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




'''Zone Forwarding:'''
=== 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.


Zone forwarding in network configuration allows traffic to be directed from one zone to another.
[[File:RB44 Firewall Config.png|1024x1024px]]


To ADD new zone,
There are 6 types of setting available under firewall.


Click on “Add” in “New Zone Forward:” field.
* General Settings
* Port forwards
* Traffic Rules
* SNAT traffic Rules
* Parental Control
* Zone Forwarding
 
'''General Settings:'''
 
General settings are subdivided into 2 parts,


[[File:Zone Forwarding RC44.png|frameless|620x620px]]
'''1.) General settings'''


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


[[File:Parental Control Zone Configuration.png|frameless|620x620px]]
[[File:RB44 Firewall General Settings.png|1024x1024px]]


Specification details are below:
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|'''SN'''
|Field  Name
|'''Field  Name'''
|Sample  Value
|'''Sample  Value'''
|Description
|'''Description'''
|-
|-
|1
|1
|Source Zone
|Enable SYN-flood  protection
|Example options: lan, wan, etc.
|Enabled
|'''--please choose--''': Select the source zone from which the traffic originates.
|This is enabled by default; setting can be changed if required.
|-
|-
|2
|2
|Destination Zone
|Disable IPV6
|Example options: lan, wan, etc.
|Disabled
|'''--please choose--''': Select the destination zone to which the traffic is directed.
|This is  enabled by default; setting can be changed if required.
|}
|-
 
|3
=== 2.6 Loopback Rule ===
|Drop invalid packets
In this page the user can configure the port where he wants to forward the traffic to. Here the user can add/edit/delete different ports as per the requirement.  
|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.
|}
 


[[File:Parental Control Zone Loopback Rule.png|frameless|620x620px]]
'''2.) Zone settings'''


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


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


[[File:Parental Control Zone Loopback Rule 1.png|frameless|650x650px]]
[[File:RB44 Port Forwarding Settings.png|1024x1024px]]


Specification details are given below:
Click on the save button after the required configuration.
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field name
|Sample  Value
|Sample  value
|Description
|Description
|-
|-
|1
|1
|Name
|Name
|Example: loopback
|Example: <code>Web_Server_Forward</code>
|Provide a descriptive name for the rule.
|Field must  not be empty. Provide a name for the rule to easily identify it.
|-
|-
|2
|2
|Protocol
|Protocol
|Example: TCP+UDP
|Example: <code>TCP+UDP</code>
|'''TCP+UDP''':  Select the protocols that the rule will apply to.
|Select the protocol  for the rule.
 
Options  typically include TCP+UDP, TCP, UDP, ICMP, Custom.
|-
|-
|3
|3
|Source IP Address [Optional]
|Source zone
|Example: any or a specific IP range like 192.168.1.0/24
|Example: <code>SW_LAN</code>
|Optionally specify the source IP address or range. Leave empty if the rule should apply  to any source IP.
|Select the source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
|-
|-
|4
|4
|Source Port [Optional]
|Source MAC address [optional]
|Example: any
|Example: <code>any</code>
|'''any''': Specify  the source port or port range from which the traffic originates. any allows  traffic from all ports.
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|-
|-
|5
|5
|Loopback IP Address
|Source IP address[optional]
|Example: 127.0.0.1
|Example: Leave blank if not needed.
|Specify the loopback IP address. Typically, this is 127.0.0.1.
|Optionally specify an IP address or range.
|-
|-
|6
|6
|Port
|Source port
|Example: any
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|'''any''':  Specify the destination port or port range to which the traffic is directed.  any allows traffic to all ports.
|Specify the source port or port range.
|-
|-
|7
|7
|Action
|Destination zone
|Example: DNAT
|Example: <code>SW_LAN</code>
|This specifies the action to take either DNAT or SNAT.
|Select the destination zone where the traffic is heading to.
|-
|-
|8
|8
|Internal IP Address
|Destination IP address
|Example: 192.168.1.100
|Leave blank if not needed.
|'''Field must not be empty''': Specify the internal IP address to which the traffic should  be redirected.
|Optionally specify the destination IP address or range.
|-
|-
|9
|9
|Internal Port
|Destination port
|Example: any
|Example: <code>80</code>  (if redirecting to a web server port)
|Redirect matched incoming traffic to the given port on the internal host.
|Specify the destination port or port range.
|}
|}
Once the user is done with the required configurations, should click save button and then click on the update to save the changes.
'''Traffic Rule:'''
 
=== 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.
"Traffic rules" refer to the policies and regulations that govern the flow of data packets within a network.


[[File:Remote Monitoring.png|frameless|620x620px]]
To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.


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


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


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 Traffic Rule Edit.png|1024x1024px]]


[[File:Remote Management System NMS Configuration.png|frameless|620x620px]]
Specification details are below:
 
{| class="wikitable"
 
|SN
 
|Field name
'''TR_069:'''
|Sample value
 
|Description
To enable the TR_069 the user needs to click on the enable check box.
 
[[File:TR 069.png|frameless|620x620px]]
 
Once the user clicks on the check box of enable it will display all the required filed to configured.
 
[[File:Remote Monitoring Tr-069.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|1
|1
|Serving  Interval
|Name
|300
|Example: Allow_HTTP_and_HTTPS
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|Field must not be empty: Provide a descriptive name for the traffic rule.
|-
|-
|2
|2
|Interface
|Restrict to Address Family
|This can be something like eth0 or wan.
 
|This specifies the network interface used for TR-069 communication.
|1.      Options:  IPv4, IPv6
 
2.      Example: IPv4 if dealing with typical internet traffic.
|Select the  address family to generate iptables rules for.
|-
|-
|3
|3
|Username
|Protocol
|Example: User
|Example: TCP+UDP
|The username used to authenticate with the ACS.
|TCP+UDP: Match incoming traffic using the given protocol.
|-
|-
|4
|4
|Password
|Match ICMP Type
|••••
|Example: any
|The password used to authenticate with  the ACS.
|Match all  ICMP types if set to any. Specific types can be chosen if needed.
|-
|-
|5
|5
|URL
|Source Zone
|<nowiki>http://example.com</nowiki>
|Example: LAN
|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.
|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.
|}
|}
The user should fill all the required fields and click on the save button.
Click on save once configured.  


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


It is further categorised into 3 sections,
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.


1.) General Settings
To add new source NAT,


2.) GRE Tunnel
Click on “ADD” in “New Source NAT:”
 
3.) IPIP Tunnel
 
[[File:Tunnel Settings.png|frameless|620x620px]]
 
 
 
'''General Settings:'''
 
In this page the user needs to select under which type of tunnel it needs to send the data.
 
[[File:Tunnel General Settings 1.png|frameless|620x620px]]
 
Once the user selects the type of tunnel then click on the save button.
 
'''GRE Tunnel:'''


A GRE (Generic Routing Encapsulation) tunnel configuration involves setting up a virtual point-to-point connection between two endpoints over an IP network.
[[File:RB44 SNAT Traffic Rules.png|1024x1024px]]
 
Here the user can add/edit/delete the details of the tunnel.
 
[[File:GRE Dashboard.png|frameless|620x620px]]
 
Once the required update is done then click on update to save the changes.


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


[[File:GRE Tunnel.png|frameless|620x620px]]
[[File:RB44 SNAT Editing.png|1024x1024px]]


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


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


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


[[File:Ipip config.png|frameless|620x620px]]
[[File:RB44 Parental Control.png|1024x1024px]]


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


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


* General
To ADD new zone,
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application


[[File:Maintenance System.png|frameless|620x620px]]
Click on “Add” in “New Zone Forward:” field.


=== 3.1 General ===
''*Refer the image below*''
Here you can configure the basic aspects of router like its hostname or the timezone.


It is further sub-divided into,
[[File:RB44 Zone Forwarding.png|1024x1024px]]


1.) General Settings
'''EDIT:'''
 
2.) Logging
 
3.) Language and Style


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


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


'''Logging:'''


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


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


[[File:Maintenance logging.png|frameless|619x619px]]
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:'''
'''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
|System log buffer size
|Name
|Example: 32 kiB
|Example: loopback
|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.
|Provide a descriptive name for the rule.
|-
|-
|2
|2
|External system log server
|Protocol
|Example: 0.0.0.0
|Example: TCP+UDP
|The IP address of an external server where logs can be sent.
|'''TCP+UDP''': Select the protocols that the rule will apply to.
|-
|-
|3
|3
|External system log server port
|Source IP Address [Optional]
|Example: 514
|Example: any or a specific IP range like 192.168.1.0/24
|The port used to send logs to the external log server. Port 514 is the default port for syslog.
|Optionally  specify the source IP address or range. Leave empty if the rule should apply  to any source IP.
|-
|-
|4
|4
|Log output level
|Source Port [Optional]
|Example: Debug
|Example: any
|Sets the detail level of the system logs.
|'''any''':  Specify the source port or port range from which the traffic originates. any allows traffic from all ports.
|-
|-
|5
|5
|Cron Log level
|Loopback IP Address
|Example: Debug
|Example: 1.1.1.1
|The detail level of the logs for cron jobs.
|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 configures the required details then click on the save button to save all the details.  
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 ===
'''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.


'''Language and Style:'''
[[File:RB44 VRRP Configuration.png|1024x1024px]]


Here the user can configure the basic aspects of your device related to language.
In VRRP section,


Once the user configures the required details then click on the save button to save all the details.
Give a name and ‘Add’ device.


[[File:Maintenance Language and Style.png|frameless|620x620px]]
Click on ‘Edit’ to make changes.


=== 3.2 Password ===
Click on ‘Delete’ if particular instance not required.
In this module the user can set the password for the admin credentials.


Specifies the password for the guest account. If the user enters a plaintext password here, it will get replaced with a crypted password on save. The new password will be effective once the user logs out and log in again.
[[File:RB44 VRRP Configuration Edit.png|1024x1024px]]


[[File:Admin Password Setup.png|frameless|620x620px]]
'''EDIT:'''


=== 3.3 Reboot ===
[[File:RB44 VRRP Configuration Settings.png|1024x1024px]]
In this module the user can reboot the device remotely.


First option is to directly reboot the device without enabling the maintenance reboot tab.
Specification details are given below:
 
{| class="wikitable"
Click on “Reboot Now” at the bottom of the screen to start the reboot process.
|SN
 
|Field Name
[[File:Reboot Dashboard enable.png|frameless|620x620px]]
|Sample Value
 
To start maintenance reboot process first the user needs to fill all the required fields.
 
Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.
 
[[File:Maintenance Reboot.png|frameless|620x620px]]
 
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Enable  Maintenance Reboot
|Role
|Enable/Disable
|1.      Master
|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
|Type
|Virtual ID
|Maintenance Reboot
|Ex: 0
|Specifies the type of reboot being  scheduled.
|The value can range from 0 to 255.
 
Ensure all  routers in the same VRRP group share the same '''Virtual ID'''.
|-
|-
|3
|3
|Reboot  Type
|Priority
|Software/Hardware
|Ex: 100
|'''Hardware''': A hardware reboot involves restarting the entire device as if it were powered off and on again.
|For the '''Master''' role, use the highest priority, typically above 100.


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


=== 3.4 Import and Export ===
=== 2.9 Remote Monitoring ===
In this section, User can Import & Export Configuration files of the Device.
In this page the user can select which equipment needs to be monitored remotely.


[[File:Import and Export Options.png|frameless|601x601px]]
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:Import window.png|frameless|620x620px]]
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 ===
[[File:RB44 NMS Dashboard.png|1024x1024px]]
The user can upgrade with the latest software for the existing firmware.  


[[File:Firmware Upgrade .png|frameless|620x620px]]
'''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:Flash Image.png|frameless|620x620px]]
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:Flash Image.png|frameless|620x620px]]
Specification details are given below:
 
Click on the '''Factory Reset''' for the complete retest of the device.
 
[[File:Factory Reset.png|frameless|620x620px]]
 
=== 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:Monitor Application Dashboard.png|frameless|620x620px]]
 
 
'''Modem Monitor Application Configuration:'''
 
[[File:Monitor Application.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Enable Ping Check Application
|Serving  Interval
|Enable/Disable
|300
|Turns on the functionality to perform ping checks on specified IP addresses.
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|-
|-
|2
|2
|Time Interval for Check (In minutes)
|Interface
|'''Example:''' 10 minutes
|This can  be something like eth0 or wan.
|Frequency at which the ping checks are performed.
|This specifies the network interface used for TR-069 communication.
|-
|-
|3
|3
|Select No of IP addresses to ping
|Username
|'''Example:''' 1
|Example: User
|Number of IP addresses that will be pinged.
|The username used to authenticate with  the ACS.
|-
|-
|4
|4
|IP Address 1
|Password
|'''Example:''' 8.8.8.8
|••••
|The IP address to ping.
|The password used to authenticate with  the ACS.
|-
|-
|5
|5
|No. of Retries
|URL
|'''Example:''' 5
|<nowiki>http://example.com</nowiki>
|Number of times to retry pinging an IP address  if the initial ping fails.
|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.
|Failure Criteria in (%)
 
|'''Example:''' 80% (If 4 out of 5 pings fail, it’s considered  a failure)
=== 2.10 Tunnel ===
|Percentage of failed pings required to consider  the ping check a failure.
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,
|Action On Failure
 
|'''Example:''' Restart Modem
1.) General Settings
|Action to be taken if the ping check fails  according to the criteria.
 
|-
2.) GRE Tunnel
|8
 
|Enable Second Level Action
3.) IPIP Tunnel
|Enable/Disable
 
|Option to enable a secondary action if the  primary action fails multiple times.
[[File:RB44 Tunnel Configuration.png|1024x1024px]]
|-
 
|9
 
|Second Level Action Threshold
'''General Settings:'''  
|'''Example:''' 2
 
|Number of failures required to trigger the  secondary action.
In this page the user needs to select under which type of tunnel it needs to send the data.
|-
 
|10
[[File:RB44 Tunnel General Settings.png|1024x1024px]]
|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:'''


[[File:Router Monitor Application Configuration.png|frameless|620x620px]]
Once the user selects the type of tunnel then click on the save button.  


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


= 4.Status =
'''IPIP Tunnel:'''
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.
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.


* Interfaces
Here the user can add/edit/delete the details of the tunnel.
* Internet
* Modem
* Routes


[[File:Status Dashboard.png|frameless|620x620px]]
[[File:RB44 IPIP Tunnel Configuration.png|1024x1024px]]  


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


[[File:Status Interfaces.png|frameless|620x620px]]
[[File:RB44 IPIP Tunnel Edit.png|1024x1024px]]


Looking on the network status the user can check if the cellular, wifi, ewan, vpn etc is up.
Once the required update is done then click on update to save the changes.


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


[[File:Internet Status.png|frameless|620x620px]]
Specification details are given below:
 
{| class="wikitable"
  To see the latest status of the internet connection the user needs to click on the refresh button.
|SN
 
|Field Name
=== 4.3 Modem ===
|Sample Value
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.
|Description
 
|-
[[File:Modem Status.png|frameless|602x602px]]
|1
 
|Tunnel  name
=== 4.4 Routes ===
|Example:  IPIPTunnel
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.
|'''IPIPTunnel:''' The name of the IPIP tunnel.
 
|-
'''ARP Table:''' Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.
|2
 
|Local  external IP
'''IPv4 Routes:''' This shows which network is directly connected on which interface.
|Example: 10.1.1.66
 
|The IP address of the local endpoint  that will initiate the IPIP tunnel.
Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''
|-
 
|3
'''IPv6 Routes:''' Similar routes as IPv4, but this time listed under IPv6 routing rules.
|Remote  external IP
 
|Example: 10.1.1.40
Example: Local networks '''192.168.10.0/24''' and '''192.168.100.0/24''' are managed through '''eth0.1''' and '''ra0''', respectively.
|The IP address of the remote endpoint  that will terminate the IPIP tunnel.
 
|-
[[File:Route Status.png|frameless|620x620px]]
|4
 
|Peer  tunnel IP
= 5. Features =
|Example: 10.1.1.4
In this module the user can see all the features that the router device has.
|The IP address of the peer's tunnel  interface.
 
|-
This module includes 7 features.
|5
 
|Local tunnel IP
* Mac Address Binding
|Example: 10.1.1.6
* URL Filtering
|The IP address of the local tunnel  interface.
* Web Server
* Wi-Fi MacID Filtering
* Routing
* Others
 
[[File:RD44 A Mac Address Binding.png|frameless|620x620px]]
 
=== 5.1 Mac Address Binding ===
MAC address binding is a configuration that binds a specific MAC address to a specific IP address. This ensures that a particular device on the network always receives the same IP address from the DHCP server, which can be useful for network management, security, and ensuring consistent network behaviour.
 
Under this submodule the user can configure/update/edit the IP Address for MAC.
 
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.
 
[[File:Mac Addressing Binding.png|frameless|620x620px]]
 
'''EDIT:'''
 
[[File:MAC Binding.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|1
|6
|Device Name
|Local  tunnel net mask
|Macbinding1
|Example:  255.255.255.0
|A user-defined name for the binding configuration.
|The subnet mask of the local tunnel interface.
|-
|-
|2
|7
|MAC Address
|Remote IP
|48:9e:bd:da:45:91
|Example: 192.168.10.0/24
|The unique identifier for the network interface of the device to which the IP address will be bound.
|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.
|-
|-
|3
|11
|IP Address
|TTL
|192.168.10.55
|Example:  64
|The IP address that will be consistently assigned to the device with the specified MAC address.
|'''64''': Time To Live value for the packets within the IPIP tunnel.
|}
|-
 
|12
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.
|Tunnel  key
 
|Example: 12345678
* Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
|Although typically not used in IPIP, this field might be included for compatibility with certain configurations.
* The user can click on the deleted button to delete an existing configured device.
|-
 
|13
Post all the changes the user needs to click on the update to reflect all the changes in the application.
|Enable  keep alive
 
|Check to enable
=== 5.2 URL Filtering ===
|Enable or disable the keep-alive  feature to monitor the tunnel's status.
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.
|-
 
|14
[[File:URL Filtering.png|frameless|620x620px]]
|Keep  alive interval
 
|Example:  10
To add the new URL for blocking, click on the Add New button.
|'''10''':  Interval in seconds for the keep-alive packets.
|}


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.
== 3.Maintenance ==
In this module the user can configure/upgrade/modify the settings related to system, password, firmware and monitoring.


The user can select the status of that URL while defining the URL.
It includes below submodules.


[[File:Url Update.png|frameless|620x620px]]
* General
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application


To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.
[[File:RB44 Maintenance Dashboard.png|1024x1024px]]


[[File:URL Filtering .png|frameless|620x620px]]
''*Below is the detailed explanation of every field*''


Click on “save” after the changes are done as per the need.
=== 3.1 General/ System ===
Here you can configure the basic aspects of router like its hostname or the time zone.


=== 5.3 Web Server ===
It is further sub-divided into,
This configuration will allow your device to serve web traffic securely over HTTPS, keep its system time synchronized, and ensure that all HTTP traffic is redirected to HTTPS for better security.


[[File:Web server.png|frameless|620x620px]]
1.) General Settings


'''EDIT:'''
2.) Logging


[[File:Webserver Configuration Editing.png|frameless|620x620px]]
3.) Language and Style


Specification details are given below:
 
'''General Settings:'''
 
[[File:RB44 Maintenance General Settings.png|1024x1024px]]
 
'''EDIT:'''
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Enable HTTP
|Local Time
|'''HTTP Port:''' 80
|2024/07/30  13:25:47
 
|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
|Enable HTTPS
|Hostname
|'''HTTPS Port:''' 443
|22B25240007
 
|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
|Redirect HTTPS
|Time zone
|Option to redirect HTTP traffic to  HTTPS.
|Asia/Kolkata
|When enabled, all HTTP requests will be  automatically redirected to the HTTPS port to ensure secure communication.
|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.
 
[[File:RB44 Logging .png|1024x1024px]]
 
'''EDIT:'''
{| class="wikitable"
|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
|4
|Enable NTP Sync
|Log  output level
|Enable or disable NTP synchronization.
|Example:  Debug
|Synchronizes the device’s system clock with an external NTP server to maintain accurate time.
|Sets the detail level of the system  logs.
|-
|-
|5
|5
|NTP Server
|Cron Log  level
|0.openwrt.pool.ntp.org
|Example:  Debug
|The address of the NTP server used for time synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
|The detail level of the logs for cron jobs.
|-
|6
|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.
|}
|}
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 ===
'''Language and Style:'''
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.
 
Here the user can configure the basic aspects of your device related to language.


It is further divided into 2 categories,
Once the user configures the required details then click on the save button to save all the details.


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


'''WIFI 2.4G AP Guest'''
=== 3.2 Password ===
In this module the user can set the password for the admin credentials.


[[File:Wi-Fi MacID Filtering .png|frameless|620x620px]]
Specifies the password for the guest account. If the user enters a plaintext password here, it will get replaced with a crypted password on save. The new password will be effective once the user logs out and log in again.


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


=== 3.3 Reboot ===
In this module the user can reboot the device remotely.


Before adding the MacIDs the user needs to select the mode from the dropdown menu.
First option is to directly reboot the device without enabling the maintenance reboot tab.


In ‘Change Mode’ select one option,
Click on “Reboot Now” at the bottom of the screen to start the reboot process.


'''Blacklist'''
[[File:RB44 Maintenance Reboot.png|1024x1024px]]


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'''
To start maintenance reboot process first the user needs to fill all the required fields.


In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.
Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.


To Add the MacID the user needs to click on Add New option.
[[File:RB44 Reboot settings.png|1024x1024px]]


[[File:WIFI 2.4G AP Guest.png|frameless|620x620px]]


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
|Status
|Enable Maintenance  Reboot
|Enable/Disable
|Enable/Disable
|Enable or disable the MAC ID filtering.
|Indicates whether the maintenance  reboot feature is enabled or not.
|-
|-
|2
|2
|MAC ID
|Type
|Example: e8:6f:38:1a:f2:61
|Maintenance  Reboot
|The MAC address of the device to be whitelisted or blocklisted.
|Specifies the type of reboot being scheduled.
|-
|-
|3
|3
|Network Name
|Reboot Type
|Example: WIFI 2.4G AP or Wi-Fi 2.4G AP Guest.
|Software/Hardware
|The network to apply the MAC ID filtering.
|'''Hardware''': A hardware reboot involves restarting the entire device as if it were powered off and on again.
|}
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.
'''Software''': A software reboot involves restarting the  operating system without powering off the hardware.
 
|-
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.
|4
 
|Minutes
=== 5.5 Routing ===
|Example:  59
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.
|The minute at which the reboot should  occur (0-59).
 
|-
It is further divided into 2 sections,
|5
 
|Hours
'''Static IPV4 Routes'''
|Example:  22 (10 PM)
 
|The hour at which the reboot should  occur (0-23, in 24-hour format).
'''Advanced Static IPV4 Routes'''
|-
|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.


'''Static IPV4 Routes:'''
=== 3.4 Import and Export ===
In this section, User can Import & Export Configuration files of the Device.


Click on ‘Add’ to add a new interface.
[[File:RB44 Import and Export.png|1024x1024px]]


[[File:Static IPV4 Routes.png|frameless|620x620px]]
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.


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


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


To edit the existing device the user needs to click on the edit option.
[[File:RB44 Firmware Upgrade.png|1024x1024px]]


Once the changes are done click on the save button to save all the changes.
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.


Click on the deleted button to delete the existing device detail.
This option will completely reset the device to default settings.


[[File:Static IPV4 Routes Editing.png|frameless|620x620px]]
[[File:RB44 Flash Image.png|1024x1024px]]


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


[[File:Advanced Static IPV4 Routes v1.png|frameless|620x620px]]
'''Router Monitor Application Configuration:'''


'''EDIT:'''
[[File:RB44 Monitor Application Configuration.png|1024x1024px]]
 
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:Advanced Static IPV4 Routes Editing.png|frameless|620x620px]]


Specification details are given below:
Specification details are given below:
Line 2,741: Line 3,022:
|-
|-
|1
|1
|Interface
|Enable Ping Check Application
|Ex: ra0
|Enable/Disable
|The network interface through which the traffic will be routed. Select as per requirement.
|Activates the  ping check functionality to monitor router performance.
|-
|-
|2
|2
|To
|Time Interval for Check (In minutes)
|Ex: 192.168.10.1
|'''Example:''' 10 minutes
|This is the target address to which the traffic  is being directed. In this case, all traffic destined for 192.168.10.1 will  follow this route.
|How  frequently the ping checks are performed.
|-
|-
|3
|3
|IPv4 Netmask
|Select No of IP Addresses to Ping
|255.255.255.192
|'''Example:''' 1 (Please select the appropriate number  based on your requirements)
|This defines the subnet of the destination address.
|Choose the number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
|-
|-
|4
|4
|Table
|No. of Retries
|1.) Local
|'''Example:''' 3
 
|Number of retries if a ping fails.
2.) Main
 
3.) Default
 
4.) 220
 
5.) custom
|1.) This table contains local routes for the  addresses assigned to the local interfaces. It's  typically used for host and broadcast addresses.
 
2.) The  primary routing table used by the system.
 
3.) A  fallback table used when no other table is specified.
 
4.) Often  used for policy-based routing.
 
5.) A user-defined routing table.
|-
|-
|5
|5
|From
|Failure Criteria in (%)
|Ex: 192.168.100.1
|'''Example:''' 80% (If 80% of the pings fail, it’s  deemed a failure)
|This source address restricts the route to  traffic originating from 192.168.100.1. Traffic from other sources won't use  this route.
|Percentage of  failed pings required to consider the ping check as failed.
|-
|-
|6
|6
|Priority
|Action On Failure
|20
|'''Example:''' Restart IPsec
|The priority value determines the preference of this route. A lower number means higher priority; 20 is relatively high, so  this route will be preferred over routes with higher priority values.
|The action taken if the ping check fails according to the criteria.
|}
|-
Once all the configurations are done click on the update button to reflect the changes made.
|7
 
|Enable Second Level Action
=== 5.6 Others ===
|Enable/Disable
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.
|Option to enable an additional action if the primary action fails.
 
[[File:Miscellaneous configuration v2.png|frameless|620x620px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample Value
|Description
|-
|-
|1
|8
|Set Date
|Second Level Action Threshold
|Date and time fields (day, month, year,  hour, minute, second)
|'''Example:''' Specify the number of failures, such as 2
|Sets the system date and time to the specified  values.
|Number of  times the primary action must fail before the secondary action is triggered.
|-
|-
|2
|9
|Get Date
|Second Level Action
|System
|'''Example:''' Restart Board
|Retrieves and displays the current system date  and time.
|The action to  be taken if the second level action threshold is met.
|-
|}
|3
Save the details once made necessary changes.
|ipsec status all
 
|Command ‘Get’
== 4.Status ==
|Displays the status of all IPsec connections.
In this module the user can view the status of the router device with respect to the network, Wan, modem etc.
|-
 
|4
It has 4 submodules.
|Wi-Fi Scan
 
|Command ‘Get’
* Interfaces
|Initiates a scan for available Wi-Fi networks.
* Internet
|-
* Modem
|5
* Routes
|iPerf3 Client
[[File:RB44 Status .png|1024x1024px]]
|IP address (e.g., 192.168.10.100)
 
|Runs an iPerf3 client to measure network performance.
=== 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.
|6
 
|iPerf3 Server
[[File:RB44 Interfaces.png|1024x1024px]]
|Command ‘Run’
 
|Runs an iPerf3 server to measure network performance.
Looking on the network status the user can check if the cellular, Wi-Fi, Ewan, VPN etc is up.
|-
 
|7
=== 4.2 Internet ===
|Ping
In this submodule the user can view the status of the internet connections.
|IP address or domain (e.g., 8.8.8.8)
 
|Sends ICMP echo requests to the specified  address to check connectivity.
[[File:RB44 Internet.png|1024x1024px]]
|-
 
|8
To see the latest status of the internet connection the user needs to click on the refresh button.
|traceroute
 
|IP address or domain (e.g., 8.8.8.8)
=== 4.3 Modem ===
|Traces the route packets take to reach the specified address.
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.
|-
 
|9
[[File:RB44 Modem Status.png|1024x1024px]]
|NTP Sync
 
|Command ‘Sync’
=== 4.4 Routes ===
|Synchronizes the system time with the  configured NTP server.
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.
|-
 
|10
'''ARP Table:''' Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.
|Download Files
 
|File or database identifier
'''IPv4 Routes:''' This shows which network is directly connected on which interface.
|Initiates a download of the specified file or  database.
 
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*''
 
[[File:RB44 Routes.png|1024x1024px]]
 
== 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
 
[[File:RB44 Features.png|1024x1024px]]
 
=== 5.1 Mac Address Binding ===
MAC address binding is a configuration that binds a specific MAC address to a specific IP address.
 
This ensures that a particular device on the network always receives the same IP address from the DHCP
 
server, which can be useful for network management, security, and ensuring consistent network
 
behaviour.
 
Under this submodule the user can configure/update/edit the IP Address for MAC.
 
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.  
 
[[File: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
|-
|-
|11
|1
|Restart Power
|Device Name
|Command ‘Restart’
|mac1
|Restarts the power of the device.
|A user-defined name for the binding  configuration.
|-
|-
|12
|2
|Restart Modem
|MAC Address
|Command ‘Restart’
|48:9e:bd:da:45:91
|Restarts the modem.
|The unique identifier for the network interface  of the device to which the IP address will be bound.
|-
|-
|13
|3
|Run AT Command
|IP Address
|Enter AT command
|192.168.10.55
|Executes the specified AT command on the modem.
|The IP address that will be consistently  assigned to the device with the specified MAC address.
|-
|}
|14
 
|Show Board Configuration
By applying this configuration, the DHCP server will always assign the IP address 192.168.10.55 to the device with the MAC address 48:9e:bd:da:45:91, ensuring consistency and stability in network addressing for that device.
|Command ‘Show’
 
|Displays the current board configuration.
* 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.
|15
 
|Show VPN Certificate Name
Post all the changes the user needs to click on the update to reflect all the changes in the application.
|Command ‘Show’
 
|Displays the name of the VPN certificate in use.
=== 5.2 URL Filtering ===
|-
In this submodule the user should provide the URL which needs to be blocked for the device.
|16
 
|Switch SIM to Secondary (Takes >2  mins)
By implementing URL filtering with the specified URL, you can control and restrict access to certain
|Command ‘Run’
 
|Switches the active SIM to the secondary SIM  card.
websites, thereby improving network security and managing user access.
|-
|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)
[[File:RB44 URL Filtering.png|1024x1024px]]To add the new URL for blocking, click on the Add New button.
|Displays data usage statistics for the specified date range.
|-
|20
|Monthly Data Usage
|'''Month:''' Month (e.g., 07)


'''Year:''' Year (e.g., 2024)
Once the user clicks on the Add New button a new pop will appear in that page write the URL and click
|Displays data usage statistics for the specified month and year.
 
on the save.
 
The user can select the status of that URL while defining the URL.
 
[[File:RB44 URL Filter Edit.png|1024x1024px]]To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.
 
[[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
|-
|-
|21
|1
|Modem Debug Info
|Enable HTTP
|Command ‘Read’
|'''HTTP Port:''' 80
|Displays debug information for the modem.
 
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.
|-
|-
|22
|2
|Scan Network operators (Takes >3  mins)
|Enable HTTPS
|Command ‘Scan’
|'''HTTPS Port:''' 443
|Initiates a scan for available network operators.
 
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.
|-
|-
|23
|3
|Network operator list (First Perform  Scan Network Operators)
|Redirect HTTPS
|Command ‘Show’
|Option to redirect HTTP traffic to  HTTPS.
|Displays the list of network operators detected in the previous scan.
|When enabled, all HTTP requests will be automatically redirected to the HTTPS port to ensure secure communication.
|-
|-
|24
|4
|ReadLogFiles
|Session Timeout (in millisecs)
|Log file identifier
|Ex: 60000
|Reads and displays the specified log file
|In this scenario the webpage will logout after  60secs of inactivity.
|-
|-
|25
|5
|Enable ssh (Admin)
|RFC1918 Filter
|Command ‘Run’
|Enable/Disable
|Enables SSH access for the admin user.
|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.
|-
|-
|26
|6
|Disable ssh (Admin)
|Enable NTP Sync
|Command ‘Run’
|Enable or disable NTP synchronization.
|Disables SSH access for the admin user.
|Synchronizes the device’s system clock with an  external NTP server to maintain accurate time.
|-
|-
|27
|7
|ClearSIM1Data
|NTP Server
|Command ‘Clear’
|0.openwrt.pool.ntp.org
|Clears data usage statistics for SIM1.
|The address of the NTP server used for time synchronization.  The openwrt.pool.ntp.org server is a public NTP server pool.
|-
|-
|28
|8
|ClearSIM2Data
|NTP Sync Interval (In Minutes)
|Command ‘Clear’
|15
|Clears data usage statistics for SIM2.
|The interval at which the device will sync its  clock with the NTP server, set to every 15 minutes in this case.
|-
|}
|29
Click on save once changes are made.
|Create Bridge with SW_LAN
 
|Network interface identifier
5.4 Wi-Fi MacID Filtering
|Creates a network bridge with the specified  interface and SW_LAN.
 
|-
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.
|30
 
|Show Bridge
It is further divided into 2 categories,
|Command ‘Show’
 
|Displays information about the current network bridges.
'''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
|-
|-
|31
|1
|Delete Bridge
|Status
|Command ‘Delete’
|Enable/Disable
|Deletes the specified network bridge.
|Enable or disable the MAC ID filtering.
|-
|-
|32
|2
|Output
|MAC ID
|Any value
|Example: e8:6f:38:1a:f2:61
|Displays output for all the above actions.
|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. 
[[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
|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.
[[File:RB44 Advanced Static IPV4 Routes-.png|1024x1024px]]
'''EDIT:'''
[[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:RB44 Application Start Stop.png|1024x1024px]]
'''General settings:'''
First make configuration changes in this section and save.
Specification details are given below:
{| class="wikitable"
|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.
[[File:RB44 Connection status and management.png|1024x1024px]]
'''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.
[[File:RB44 Application Start Stop 1.png|980x980px]]
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.9 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
[[File:RB44 Package Manager.png|1024x1024px]]
'''Installed APP:'''
When you select Installed APP, you will see all the software that is actively running or installed on the device.
This could include system utilities, network management tools, monitoring software, or any third-party apps that were previously installed.
'''Common Actions''':
* '''View Details''': You can check each application's version, source, and    installation date.
* '''Uninstall''': You can remove applications that are no longer needed.
* '''Check for Updates''': You can see if there are updates available for any    installed application.
'''Available APP''':
When you select '''Available APP''', you will see a list of software that can be installed from the system's repositories or sources.
These applications are not yet installed but are ready for installation if needed.
'''Common Actions''':
* '''Install''':    You can install any of the available applications by selecting them.
* '''View    Details''': You can review each application's description, version, and    functionality before installing.
* '''Search''':    You can search for specific apps by name or category.
'''Manual Upgrade''':
In contrast to automatic updates, '''Manual Upgrade''' lets you take control over which packages or applications you want to upgrade and when.
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 =
= 6.Logout =
The user should click on log out option to logged out from the router application.
The user should click on log out option to logged out from the router application.


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

Latest revision as of 05:31, 3 January 2025

This page contains the user manual for RB44.

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

To log in to SILBO_RB44 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 two available) while making sure the WAN interface is not used.

                                                                                                                                                         

How to connect with the SILBO_RB44 application

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

Please open the command prompt and ping go 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 31B30241002 This field displays the router serial number of the device
2 Model Silbo_RB44- 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 Tuesday, December 3, 2024 at 11:26:32 AM This field displays the local time
6 Uptime 0h 3m 10s This field displays the uptime of the device
7 Load Average 2.47 2.24 2.06 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.

Ethernet Setting:

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

For this device 5 ports are configured.

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

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

EDIT:

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

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

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

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

Note: If required, add an interface in Settings-->Multi-WAN-->Failover

Specification details are given below:  Type: WAN

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

WAN: Connects the device to the internet.

LAN: Connects the device to the internal network.

                                                                     Protocol: Static
3 Static IP Address Ex: 192.168.1.10 The manually assigned IP address for the interface.
4 Static Netmask Ex: 255.255.255.0 Subnet mask corresponding to the IP address.
5 Static Gateway Ex: 192.168.1.1 The IP address of the gateway (router) that the interface will use to send traffic outside its own subnet.
                                                                     Protocol: DHCP
6 DHCP Gateway Ex: 10.1.1.1 The IP address of the DHCP server (often the same as the router or gateway).
                                                                     Protocol: PPPoE
7 Username Any Name The username provided by your ISP for PPPoE authentication.
8 Password ***** The password provided by your ISP for PPPoE authentication.
9 Access Concentrator Typically, the name of the ISP's PPPoE server.
10 Service Name Sometimes required by ISPs, this field specifies a particular service offered by the ISP.
11 Gateway Ex: 0.0.0.0 The IP address used as the default route.
12 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
  1. CWAN1_0
  1. SW_LAN
  1. VPN
  1. ra0 
 Since this is a WAN interface, it is not typically bridged with others. Bridges are more common for LAN interfaces to combine multiple connections.
14 Create Firewall Zone Enable/Disable You can assign this interface to a particular firewall zone, which determines its access rules (e.g., WAN zone for internet traffic, LAN zone for internal traffic).
Advanced Settings: Enable/Disable
15 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.

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

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.

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.

20 Force Link Enable/Disable Forces the interface to be up even if no physical link is detected.

Type: LAN

Specification details are given below:

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

WAN: Connects the device to the internet.

LAN: Connects the device to the internal network.

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

More than one DNS Address can be added.

10 Enable DHCP Server Enable/Disable If enabled, this setting allows the interface to function as a DHCP server, automatically assigning IP addresses to devices connected to the LAN.
11 DHCP Start Address 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)

Seconds-(S)

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

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

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

14 Lease Time 12 The DHCP lease time is set to 12 hours. After this period, a device must renew its IP address lease with the DHCP server to continue using the assigned IP address.
15 Enable Bridge 1.     CWAN1_0

2.     SW_LAN

3.     VPN

4.     ra0

Since this is a WAN interface, it is not typically bridged with others. Bridges are more common for LAN interfaces to combine multiple connections.
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.
17 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).
18 Internet Over SW_LAN Enable/Disable Allow all outbound traffic from the LAN to the internet.
Advanced Settings: Enable/Disable
19 IPv4 Route Table Enable/Disable This field is used to specify static routes for IPv4.
20 Table No. 254: Default main routing table.

100: Custom routing table for specific purposes.

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

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

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

22 Broadcast Ex: 192.168.123.34 Broadcast address for the network, typically calculated based on the IP and subnet mask.
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.


Relay Server:

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

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

EDIT:

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

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

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

Specification details are given below:

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

2.)   ra0

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

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

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

Save and update.

Cellular Setting:

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

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

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 VLAN

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

It is further divided into 2 sections,

Port-Based VLAN

Tagged Port Configuration

Port-Based VLAN:

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

EDIT:

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

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

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

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

Specification details are given below:

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

Save and update the page.

Tagged Port Configuration:

EDIT:

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

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

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

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

Specification details are given below:

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

Save and update the page.

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

As shown below, this section has 4 categories,

Status

General settings

Failover

Load Balancing

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

General Settings:

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

Click on save and update.

Failover:

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

EDIT:

The specifications details are below.

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

Click on save and update tab.

Load Balancing:

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

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

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

EDIT:



Specification details are given below:

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

The ratio must be the same for CWAN1_0 and CWAN1_1.

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

Click on save and update tab.


2.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
  • PPTP
  • L2TP

General Settings:

In this page the user must choose which type of VPN connection is required for the device. The user must select from 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.

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:

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

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

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

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

VPN TUN has been established.

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

WireGuard:

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

Click on “Edit” to start configurations as needed.

EDIT:

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

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

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

Save and update the page after configuration has been done.


Zerotier:

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

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

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

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

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

Click on the save button after the required configuration.

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

PPTP:

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

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


*Refer the image below*

EDIT:

Specification details are given below:

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

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

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

EWAN5

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

Once Configured, click on save and update.


L2TP:

L2TP (Layer 2 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.


*Refer the image below*

EDIT:

Specification details are given below:

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

Server: the server listens for incoming client connections.

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

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

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

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

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

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

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

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

Must match credentials configured on the L2TP server.

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

Masked for privacy during configuration.

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

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

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

The server verifies this username against its authentication database.

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

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


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

In this page the user can configure the port where he wants to forward the traffic to. Here the user can add/edit/delete different 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.8 VRRP

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

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

In VRRP section,

Give a name and ‘Add’ device.

Click on ‘Edit’ to make changes.

Click on ‘Delete’ if particular instance not required.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Role 1.      Master

2.      Backup

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

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

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

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

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

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

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

Save and update once changes have been made.

2.9 Remote Monitoring

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

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

NMS:

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

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

TR_069:

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

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


Specification details are given below:

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

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

2.10 Tunnel

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

It is further categorised into 3 sections,

1.) General Settings

2.) GRE Tunnel

3.) IPIP Tunnel


General Settings:

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


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

GRE Tunnel:

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

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


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


EDIT:


Specification details are given below:

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

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

IPIP Tunnel:

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

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

EDIT:

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


Specification details are given below:

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

3.Maintenance

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

It includes 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 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


Specification details are given below:

SN Field Name Sample Value Description
1 Enable DMZ Enable/Disable Enable DMZ to configure it further.
2 Host IP Address Ex: 192.168.10.1 This is the internal IP address of the device or server that will be in the DMZ.
3 Protocol 1.) TCP

2.) UDP

3.) ICMP

4.) All

TCP: Used for reliable services like HTTP, HTTPS, FTP, and SSH.

UDP: Often used for services like DNS that don't require as much reliability.

ICMP: Used for sending control messages like "ping."

All: Select this if you're unsure which protocol to allow, but it's less secure.

4 Allow HTTP Internal Port: 80

External Port: 80

Enables web traffic over the unsecured HTTP protocol.

(Port 80 is the standard port for HTTP traffic on our internal network).

5 Allow HTTPS Internal Port: 443

External Port: 443

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

External Port: 52434

This is a custom port we’re using for SSH.

The default is 22.

7 Allow FTP Internal Port: 21/20

External Port: 21/20

FTP is used to transfer files between computers.

(These are the standard ports for FTP traffic. Port 21 is used for control commands, and port 20 for the data transfer.)

8 Allow DNS Internal Port: 53

External Port: 53

Standard DNS port within our internal network.

5.7 Others

In this page the user will get to do all the other miscellaneous configuration with respect to the device based on the required parameters. Each utility serves a specific purpose, providing various functionalities for managing and troubleshooting network configurations and statuses.

Specification details are given below:

SN Field Name Sample Value Description
1 Set Date Date and time fields (day, month, year, hour, minute, second) Sets the system date and time to the specified values.
2 Get Date System Retrieves and displays the current system date and time.
3 ipsec status all Command ‘Get’ Displays the status of all IPsec connections.
4 Wi-Fi Scan Command ‘Get’ Initiates a scan for available Wi-Fi networks.
5 iPerf3 Client IP address (e.g., 192.168.10.100) Runs an iPerf3 client to measure network performance.
6 iPerf3 Server Command ‘Run’ Runs an iPerf3 server to measure network performance.
7 Ping IP address or domain (e.g., 8.8.8.8) Sends ICMP echo requests to the specified address to check connectivity.
8 traceroute IP address or domain (e.g., 8.8.8.8) Traces the route packets take to reach the specified address.
9 NTP Sync Command ‘Sync’ Synchronizes the system time with the configured NTP server.
10 Download Files File or database identifier Initiates a download of the specified file or database.
11 Restart Power Command ‘Restart’ Restarts the power of the device.
12 Restart Modem Command ‘Restart’ Restarts the modem.
13 Run AT Command Enter AT command Executes the specified AT command on the modem.
14 Show Board Configuration Command ‘Show’ Displays the current board configuration.
15 Show VPN Certificate Name Command ‘Show’ Displays the name of the VPN certificate in use.
16 Switch SIM to Secondary (Takes >2 mins) Command ‘Run’ Switches the active SIM to the secondary SIM card.
17 Send test SMS Phone number (e.g., +911234567890) message text (e.g., "Hello how are you?") Sends a test SMS to the specified phone number.
18 ReadlatestSMS Command ‘Read’ Reads the most recent SMS received by the device.
19 Data Usage From: Start date (YYYY-MM-DD)

To: End date (YYYY-MM-DD)

Displays data usage statistics for the specified date range.
20 Monthly Data Usage Month: Month (e.g., 07)

Year: Year (e.g., 2024)

Displays data usage statistics for the specified month and year.
21 Modem Debug Info Command ‘Read’ Displays debug information for the modem.
22 Scan Network operators (Takes >3 mins) Command ‘Scan’ Initiates a scan for available network operators.
23 Network operator list (First Perform Scan Network Operators) Command ‘Show’ Displays the list of network operators detected in the previous scan.
24 ReadLogFiles Log file identifier Reads and displays the specified log file
25 Enable ssh (Admin) Command ‘Run’ Enables SSH access for the admin user.
26 Disable ssh (Admin) Command ‘Run’ Disables SSH access for the admin user.
27 ClearSIM1Data Command ‘Clear’ Clears data usage statistics for SIM1.
28 ClearSIM2Data Command ‘Clear’ Clears data usage statistics for SIM2.
29 Create Bridge with SW_LAN Network interface identifier Creates a network bridge with the specified interface and SW_LAN.
30 Show Bridge Command ‘Show’ Displays information about the current network bridges.
31 Delete Bridge Command ‘Delete’ Deletes the specified network bridge.
32 Output Any value Displays output for all the above actions.

5.8 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.9 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=RB44_Manual&oldid=2540"