RD44 A Manual: Difference between revisions

From Silbo Networks
VisualWikitext
No edit summary
No edit summary
 
(3 intermediate revisions by the same user not shown)
Line 1,350: Line 1,350:
Copy and paste the unique 16-digit network ID in the edit section.
Copy and paste the unique 16-digit network ID in the edit section.


[[File:RB44 Zerotier Editing .png|1024x1024px]]
[[File:RD44A 16 digit network ID Update.png|1024x1024px]]
 
[[File:RD44 A Zerotier Unique ID.png|1024x1024px]]
 


Click on the save button after the required configuration.
Click on the save button after the required configuration.
Line 1,370: Line 1,373:


|}
|}
'''PPTP:'''
=== 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.


This configuration is for setting up a PPTP (Point-to-Point Tunnelling Protocol) VPN connection.
[[File:RB44 Firewall Config.png|1024x1024px]]


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.
There are 6 types of setting available under firewall.


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


''*Refer the image below*''
'''General Settings:'''
 
General settings are subdivided into 2 parts,


[[File:RB44 PPTP Config.png|1024x1024px]]
'''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:PPTP Connection Settings.png|1024x1024px]]
[[File:RB44 Firewall General Settings.png|1024x1024px]]


Specification details are given below:
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|'''SN'''
|Field Name
|'''Field Name'''
|Sample Value
|'''Sample Value'''
|Description
|'''Description'''
|-
|-
|1
|1
|PPTP Role
|Enable SYN-flood  protection
|Client/Server
|Enabled
|'''Client:''' meaning it will  initiate the connection to the remote PPTP server.
|This is enabled by default; setting can be changed if required.
 
'''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
|2
|Default  Route
|Disable IPV6
|Enable/Disable
|Disabled
|Enabling the default route means that all network traffic will be routed through the  VPN tunnel once the connection is established.
|This is enabled by default; setting can be changed if required.
|-
|-
|3
|3
|Metric
|Drop invalid packets
|Ex: 0
|Disabled
|The  metric is a value that defines the priority of this route among other available routes. Lower metrics indicate higher priority.
|This is  enabled by default; setting can be changed if required.
|-
|-
|4
|4
|Server  IP
|TCP SYN Cookies
|Ex:  192.168.10.1
|Disabled
|This  is the IP address of the PPTP server the client will connect to.
|This is enabled by default; setting can be changed if required.
|-
|-
|5
|5
|Interface
|Input
|Any
|Reject/Accept
 
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’  compulsory.
EWAN5
|Selecting the correct interface is essential because it tells the system which network  adapter should be used to establish the VPN connection.
|-
|-
|6
|6
|Username
|Output
|******
|Reject/Accept
|This field is the login username for the PPTP server.
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’  compulsory.
|-
|-
|7
|7
|Password
|Forward
|****
|Reject/Accept
|This is the password associated with the username.
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|-
| colspan="4" |'''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:'''
'''2.) Zone settings'''
 
In zone settings, there’s an option to add “New Zone”, according to user’s requirement.
 
[[File:RB44 Zone Settings.png|1024x1024px]]
 
'''Port Forwards:'''


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


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


[[File:L2TP Configuration.png|1024x1024px]]  
[[File:RB44 Port Forward.png|1024x1024px]]


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


[[File:RB44 L2TP Connection Settings.png|1024x1024px]]
[[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
|L2TP Role
|Name
|Client/Server
|Example: <code>Web_Server_Forward</code>
|'''Client''': connecting to an L2TP server to establish a secure tunnel for communication.
|Field must  not be empty. Provide a name for the rule to easily identify it.
 
'''Server''': the server listens for incoming client connections.
|-
| colspan="4" |'''L2TP Role: CLIENT'''
|-
|-
|2
|2
|Default Route
|Protocol
|Enable/Disable
|Example: <code>TCP+UDP</code>
|If enabled, all outbound traffic will be routed through the L2TP connection.
|Select the protocol for the rule.


If disabled, only specific traffic destined for the L2TP network will use the tunnel.
Options  typically include TCP+UDP, TCP, UDP, ICMP, Custom.
|-
|-
|3
|3
|Metric
|Source zone
|Ex: 1
|Example: <code>SW_LAN</code>
|The system uses this metric to decide which route to prioritize if multiple routes exist.
|Select the source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
 
L2TP connection  with Metric 1 will take precedence over a LAN or WAN route with Metric 10.
|-
|-
|4
|4
|Server IP
|Source MAC address [optional]
|Ex: 192.168.10.1
|Example: <code>any</code>
|This is the '''IP  address of the L2TP server''' to which the client will connect.
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
 
'''Local Networks''': If connecting  within a LAN, the server might have an IP like 192.168.x.x.
 
'''Remote  Connections''': The server IP might be a public address like 203.0.113. x.
|-
|-
|5
|5
|Checkup  Interval Time (in sec)
|Source IP address[optional]
|Ex: 30/60 secs
|Example: Leave blank if not needed.
|Setting 30  seconds ensures the client checks the connection every half-minute. If the tunnel drops, the client can quickly reconnect.
|Optionally specify an IP address or range.
|-
|-
|6
|6
|Interface
|Source port
|Any
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|Example interfaces might include eth0, usb0, or ra0.
|Specify the source port or port range.
|-
|-
|7
|7
|Username
|Destination zone
|Ex: User
|Example: <code>SW_LAN</code>
|The server verifies the username to grant or deny access.
|Select the destination zone where the traffic is heading to.
 
Must match  credentials configured on the L2TP server.
|-
|-
|8
|8
|Password
|Destination IP address
|******
|Leave blank if not needed.
|Should be kept secure and match the configuration on the server.
|Optionally specify the destination IP address or range.
 
Masked for  privacy during configuration.
|-
|-
|9
|9
|MPPE Encryption
|Destination port
|Enable/Disable
|Example: <code>80</code>  (if redirecting to a web server port)
|'''Enabled''': Encrypts  traffic using MPPE, enhancing security (recommended).
|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.


'''Disabled''': Transmits  data unencrypted, reducing overhead but exposing traffic to potential risks.
To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.
|-
| colspan="4" |'''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.
[[File:RB44 Traffic Rule.png|1024x1024px]]
|-
|14
|Password
|******
|The server  verifies the password along with the username.


The password  must match the one configured on the server for successful authentication.
'''EDIT:'''
|}


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


=== 2.5 Firewall ===
Specification details are below:
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.
{| 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


[[File:RB44 Firewall Config.png|1024x1024px]]
|1.      Options: IPv4, IPv6


There are 6 types of setting available under firewall.
2.      Example:  IPv4 if dealing with typical internet traffic.
 
|Select the address family to generate iptables rules for.
* General Settings
|-
* Port forwards
|3
* Traffic Rules
|Protocol
* SNAT traffic Rules
|Example: TCP+UDP
* Parental Control
|TCP+UDP: Match incoming traffic using the given protocol.
* Zone Forwarding
 
'''General Settings:'''
 
General settings are subdivided into 2 parts,
 
'''1.) General settings'''
 
In general settings, the settings that are made are default settings and can be changed according to user’s preference.
 
[[File:RB44 Firewall General Settings.png|1024x1024px]]
 
Specification details are below:
{| class="wikitable"
|'''SN'''
|'''Field  Name'''
|'''Sample Value'''
|'''Description'''
|-
|-
|1
|4
|Enable SYN-flood  protection
|Match ICMP Type
|Enabled
|Example: any
|This is  enabled by default; setting can be changed if required.
|Match all ICMP types if set to any. Specific types can be chosen if needed.
|-
|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
|5
|Input
|Source Zone
|Reject/Accept
|Example: LAN
|By  default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|Specifies the  traffic source zone.
|-
|-
|6
|6
|Output
|Enable DDoS Prevention
|Reject/Accept
|Example: ‘Checked’ if you want to enable DDoS prevention  measures
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’ compulsory.
|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.
|-
|-
|7
|10
|Forward
|Destination Zone
|Reject/Accept
|Example: WAN
|By default, the setting is ‘Reject’ but this needs to be changed to ‘Accept’  compulsory.
|Specifies the  traffic destination zone.
|}
|-
 
|11
 
|Action
'''2.) Zone settings'''
|Example: ACCEPT
 
|Options: ACCEPT, DROP, REJECT. Specify the action to take for matched traffic.
In zone settings, there’s an option to add “New Zone”, according to user’s requirement.
|-
 
|12
[[File:RB44 Zone Settings.png|1024x1024px]]
|Limit
 
|Example: 10/minute to limit matches to 10 times per  minute.
'''Port Forwards:'''
|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.


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


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


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


[[File:RB44 Port Forward.png|1024x1024px]]
Click on “ADD” in “New Source NAT:”
 
[[File:RB44 SNAT Traffic Rules.png|1024x1024px]]


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


[[File:RB44 Port Forwarding Settings.png|1024x1024px]]
[[File:RB44 SNAT Editing.png|1024x1024px]]


Click on the save button after the required configuration.
Specification details are below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field name
|Field name
|Sample  value
|Sample  value
|Description
|Description
Line 1,671: Line 1,627:
|1
|1
|Name
|Name
|Example: <code>Web_Server_Forward</code>
|Example: SNAT_WAN_to_LAN
|Field must  not be empty. Provide a name for the rule to easily identify it.
|'''Field must  not be empty''': Provide a unique and descriptive name for the SNAT rule.
|-
|-
|2
|2
|Protocol
|Protocol
|Example: <code>TCP+UDP</code>
|Example: TCP+UDP
|Select the protocol  for the rule.
|'''TCP+UDP''':  Select the protocols that the SNAT rule will apply to.
 
Options  typically include TCP+UDP, TCP, UDP, ICMP, Custom.
|-
|-
|3
|3
|Source zone
|Source Zone
|Example: <code>SW_LAN</code>
|Example: wan
|Select the source zone where the traffic is originating from. Options typically include EWAN2,SW_LAN,CWAN1,CWAN1_0,CWAN1_1,VPN
|'''wan''': Specifies  the source zone from which the traffic originates.
|-
|-
|4
|4
|Source MAC address [optional]
|Source IP Address
|Example: <code>any</code>
|Example: any or a specific range like 192.168.1.0/24
|'''any''': Leave as <code>any</code> if you don't want to specify a MAC address.
|'''-- please  choose --''': Specify the source IP address or range. Leave empty if the  rule applies to any source IP.
|-
|-
|5
|5
|Source IP address[optional]
|Source Port
|Example: Leave blank if not needed.
|Example: any
|Optionally specify an IP address or range.
|'''any''': Specify the source port or port range from which the traffic originates.
|-
|-
|6
|6
|Source port
|Destination Zone
|Example: <code>80, 443</code>  (if matching traffic for web server ports)
|Example: lan
|Specify the source port or port range.
|'''lan''':  Specifies the destination zone to which the traffic is directed.
|-
|-
|7
|7
|Destination zone
|Destination IP Address
|Example: <code>SW_LAN</code>
|Example: any or a specific IP like 192.168.1.100
|Select the  destination zone where the traffic is heading to.
|'''-- please  choose --''': Specify the destination IP address or range. Leave empty if the rule applies to any destination IP.
|-
|-
|8
|8
|Destination IP address
|Destination port
|Leave blank if not needed.
|Example: any
|Optionally specify the destination IP address or range.
|'''any''': Specify the destination port or port range to which the traffic is directed.
|-
|-
|9
|9
|Destination port
|SNAT IP Address
|Example: <code>80</code> (if redirecting to a web server port)
|Example: 203.0.113.5 (an external IP address)
|Specify the destination port or port range.
|'''-- 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.
|}
|}
'''Traffic Rule:'''
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.


"Traffic rules" refer to the policies and regulations that govern the flow of data packets within a network.
To add parental control in firewall,


To allow new traffic, click on “Add and Edit” in “New Traffic Rule”.
Click on “Add and Edit” in “New parental control:” field.


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


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


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


Specification details are below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field  name
|Field  Name
|Sample  value
|Sample  Value
|Description
|Description
|-
|-
|1
|1
|Name
|Name
|Example: Allow_HTTP_and_HTTPS
|Example: Parental_Control_Sunday
|Field must  not be empty: Provide a descriptive name for the traffic rule.
|'''Field must  not be empty''': Provide a unique and descriptive name for the parental  control rule.
|-
|-
|2
|2
|Restrict to Address Family
|Proto
 
|all
|1.      Options:  IPv4, IPv6
|'''all''':  This specifies that the rule will apply to all protocols.
 
2.      Example:  IPv4 if dealing with typical internet traffic.
|Select the address family to generate iptables rules for.
|-
|-
|3
|3
|Protocol
|Source Zone
|Example: TCP+UDP
|Example: lan
|TCP+UDP:  Match incoming traffic using the given protocol.
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone names.
|-
|-
|4
|4
|Match ICMP Type
|Destination  Zone
|Example: any
|Example: wan
|Match all ICMP types if set to any. Specific types can be chosen if needed.
|'''Field must not be empty''': Please look at Firewall->Zone Settings to find zone  names.
|-
|-
|5
|5
|Source Zone
|Source MAC  Address
|Example: LAN
|Example: 00:1A:2B:3C:4D:5E
|Specifies the  traffic source zone.
|'''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
|Enable DDoS Prevention
|Target
|Example: ‘Checked’ if you want to enable DDoS prevention measures
|Example: Reject
|Enable or disable Distributed Denial of Service (DDoS) prevention.
|'''Accept''':  This specifies the action to take. For parental controls, you might want to  use ‘Reject’ or ‘Drop’ to block traffic.
|-
|-
|7
|7
|Source MAC Address
|Weekdays
|Example: any
|Example: Sunday
|any: Match traffic from any MAC address or specify a particular MAC address.
|'''Sunday''':  Specify the days of the week when the rule should be active.
|-
|-
|8
|8
|Source Address
|Month Days
|Example: 192.168.1.0/24
|Example: All
|Match incoming traffic from the specified source IP address or range.
|'''All:''' Specify the days of the month when the rule should be active.
|-
|-
|9
|9
|Source Port
|Start Time (hh:mm:ss)
|Example: any if all source ports should be matched
|Example: 18:00:00 (6:00 PM)
|any: Match  incoming traffic from the specified source port or port range.
|'''Field must  not be empty:''' Specify the start time when the rule should begin to apply.
|-
|-
|10
|10
|Destination Zone
|Stop Time (hh:mm:ss)
|Example: WAN
|Example:  22:00:00 (10:00 PM)
|Specifies the traffic destination zone.
|'''Field must not be empty:''' Specify the stop time when the rule should end.
|-
|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.  
Click on save once configured.
 
 
'''Zone Forwarding:'''


'''SNAT Traffic Rule:'''
Zone forwarding in network configuration allows traffic to be directed from one zone to another.


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 zone,


To add new source NAT,
Click on “Add” in “New Zone Forward:” field.


Click on “ADD” in “New Source NAT:”
''*Refer the image below*''


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


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


[[File:RB44 SNAT Editing.png|1024x1024px]]
[[File:RB44 Zone Forwarding Edit.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
|Name
|Source Zone
|Example: SNAT_WAN_to_LAN
|Example options: lan, wan, etc.
|'''Field must not be empty''': Provide a unique and descriptive name for the SNAT rule.
|'''--please choose--''': Select the source zone from which the traffic originates.
|-
|-
|2
|2
|Protocol
|Destination Zone
|Example: TCP+UDP
|Example options: lan, wan, etc.
|'''TCP+UDP''': Select the protocols that the SNAT rule will apply to.
|'''--please  choose--''': Select the destination zone to which the traffic is directed.
|-
|}
|3
Click on save once configured.
|Source Zone
 
|Example: wan
 
|'''wan''': Specifies  the source zone from which the traffic originates.
=== 2.6 Loopback Rule ===
|-
In this page the user can configure the port where he wants to forward the traffic to. Here the user can add/edit/delete different port ports as per the requirement.
|4
 
|Source IP Address
[[File:RB44 Loopback Rule.png|1024x1024px]]
|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.
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:'''
 
[[File:RB44 Loopback Rule Edit.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample Value
|Description
|-
|-
|5
|1
|Source Port
|Name
|Example: any
|Example: loopback
|'''any''': Specify the source port or port range from which the traffic originates.
|Provide a descriptive name for the rule.
|-
|-
|6
|2
|Destination Zone
|Protocol
|Example: lan
|Example: TCP+UDP
|'''lan''':  Specifies the destination zone to which the traffic is directed.
|'''TCP+UDP''':  Select the protocols that the rule will apply to.
|-
|-
|7
|3
|Destination IP Address
|Source IP Address [Optional]
|Example: any or a specific IP like 192.168.1.100
|Example: any or a specific IP range like 192.168.1.0/24
|'''-- please choose --''': Specify the destination IP address or range. Leave empty if the rule applies to any destination IP.
|Optionally specify the source IP address or range. Leave empty if the rule should apply  to any source IP.
|-
|-
|8
|4
|Destination port
|Source Port [Optional]
|Example: any
|Example: any
|'''any''':  Specify the destination port or port range to which the traffic is directed.
|'''any''':  Specify the source port or port range from which the traffic originates. any  allows traffic from all ports.
|-
|-
|9
|5
|SNAT IP Address
|Loopback IP Address
|Example: 203.0.113.5 (an external IP address)
|Example: 1.1.1.1
|'''-- please  choose --''': Specify the IP address to which the source IP should be  translated.
|Specify the loopback IP address.
|-
|-
|10
|6
|SNAT Port
|Port
|Example: Leave empty if not needed, or specify a port  like ‘12345’
|Example: 81
|Optionally, rewrite matched traffic to a specific source port. Leave empty to only  rewrite the IP address.
|'''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.
|-
|-
|11
|9
|Extra Arguments
|Internal Port
|Example: --log-prefix "SNAT_traffic: " (to add  a log prefix to log messages for this rule)
|Example: 81
|Pass additional arguments to iptables. Use with care as it can significantly alter  rule behaviour.
|Redirect matched incoming traffic to the given port on the internal host.
|}
|}
Click on save once configured.
Once the user is done with the required configurations, user should click save button and then click on the update to save the changes.


'''Parental Control:'''
=== 2.7 Remote Monitoring ===
In this page the user can select which equipment needs to be monitored remotely.


For configuring parental control rules, you want to set restrictions based on time, source, and destination zones, as well as specific devices.
Once the user selects the type of RMS click on save.


To add parental control in firewall,
[[File:RB44 Remote Managment System.png|1024x1024px]]


Click on “Add and Edit” in “New parental control:” field.
'''NMS:'''
 
IN this page the user should type the server IP or domain name in the URL then click on save.
 
Click on upload and start (Once key is uploaded and this option is clicked, NMS automatically starts, and this router device gets registered with the NMS server provided).
 
[[File:RB44 NMS Dashboard.png|1024x1024px]]
 
'''TR_069:'''
 
To enable the TR_069 the user needs to click on the enable check box.
 
[[File:RB44 TR 069 Config.png|1024x1024px]]


[[File:RB44 Parental Control.png|1024x1024px]]
Once the user clicks on the check box of enable it will display all the required filed to configured.


'''EDIT:'''
[[File:RB44 TR 069 Edit.png|1024x1024px]]


[[File:RB44 Parental Control Editing .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
|Serving  Interval
|Example: Parental_Control_Sunday
|300
|'''Field must not be empty''': Provide a unique and descriptive name for the parental  control rule.
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|-
|-
|2
|2
|Proto
|Interface
|all
|This can  be something like eth0 or wan.
|'''all''':  This specifies that the rule will apply to all protocols.
|This specifies the network interface  used for TR-069 communication.
|-
|-
|3
|3
|Source Zone
|Username
|Example: lan
|Example: User
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone names.
|The username used to authenticate with the ACS.
|-
|-
|4
|4
|Destination  Zone
|Password
|Example: wan
|••••
|'''Field must  not be empty''': Please look at Firewall->Zone Settings to find zone names.
|The password used to authenticate with the ACS.
|-
|-
|5
|5
|Source MAC  Address
|URL
|Example: 00:1A:2B:3C:4D:5E
|<nowiki>http://example.com</nowiki>
|'''Field''':  Enter the MAC address of the device you want to apply the parental control  rule to. This is useful for restricting specific devices.
|The 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.
|Target
 
|Example:  Reject
=== 2.8 Tunnel ===
|'''Accept''':  This specifies the action to take. For parental controls, you might want to use ‘Reject’ or ‘Drop’ to block traffic.
Tunnels are a method of transporting data across a network using protocols which are not supported by that network.
|-
|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.


It is further categorised into 3 sections,


'''Zone Forwarding:'''
1.) General Settings


Zone forwarding in network configuration allows traffic to be directed from one zone to another.
2.) GRE Tunnel


To ADD new zone,
3.) IPIP Tunnel


Click on “Add” in “New Zone Forward:” field.
[[File:RB44 Tunnel Configuration.png|1024x1024px]]


''*Refer the image below*''


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


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


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


Specification details are below:
 
{| class="wikitable"
Once the user selects the type of tunnel then click on the save button.
|SN
 
|Field  Name
'''GRE Tunnel:'''
|Sample  Value
 
|Description
A GRE (Generic Routing Encapsulation) tunnel configuration involves setting up a virtual point-to-point connection between two endpoints over an IP network.
|-
 
|1
Here the user can add/edit/delete the details of the tunnel.
|Source Zone
 
|Example options: lan, wan, etc.
[[File:RB44 GRE Tunnel Config.png|1024x1024px]]
|'''--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.


[[File:RB44 Loopback Rule.png|1024x1024px]]
Once the required update is done then click on update to save the changes.


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]]
[[File:RB44 GRE Tunnel Configuration .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
|Tunnel  name
|Example: loopback
|Example: GRETunnel
|Provide a  descriptive name for the rule.
|'''GRETunnel''': The name of the GRE tunnel.
|-
|-
|2
|2
|Protocol
|Local external  IP
|Example: TCP+UDP
|Example: 10.1.1.66
|'''TCP+UDP''': Select the protocols that the rule will apply to.
|The IP address of the local endpoint that will initiate the GRE tunnel.
|-
|-
|3
|3
|Source IP Address [Optional]
|Remote  external IP
|Example: any or a specific IP range like 192.168.1.0/24
|Example: 10.1.1.40
|Optionally  specify the source IP address or range. Leave empty if the rule should apply to any source IP.
|The IP address of the remote endpoint that will terminate the GRE tunnel.
|-
|-
|4
|4
|Source Port [Optional]
|Peer  tunnel IP
|Example: any
|Example: 10.1.1.4
|'''any''':  Specify the source port or port range from which the traffic originates. any allows traffic from all ports.
|The IP address of the peer's tunnel interface.
|-
|-
|5
|5
|Loopback IP Address
|Local  tunnel IP
|Example: 1.1.1.1
|Example: 10.1.1.6
|Specify the  loopback IP address.
|The IP address of the local tunnel interface.
|-
|-
|6
|6
|Port
|Local  tunnel net mask
|Example: 81
|Example: 255.255.255.0
|'''any''':  Specify the destination port or port range to which the traffic is directed. any allows traffic to all ports.
|The subnet mask of the local tunnel interface.
|-
|-
|7
|7
|Action
|Remote IP
|Example: DNAT
|Example: 192.168.10.0/24
|This specifies the action to take either DNAT or SNAT.
|The remote network that is reachable through the GRE tunnel.
|-
|-
|8
|8
|Internal IP Address
|Enable  Tunnel Link
|Example: 2.2.2.2
|Check to  enable
|'''Field must  not be empty''': Specify the internal IP address to which the traffic should  be redirected.
|Enable or disable the GRE tunnel link.
|-
|-
|9
|9
|Internal Port
|Interface  type
|Example: 81
|Example: EWAN2
|Redirect matched incoming traffic to the given port on the internal host.
|'''EWAN2''': The type of network interface used for the GRE tunnel.
|}
|-
Once the user is done with the required configurations, user should click save button and then click on the update to save the changes.
|10
 
|MTU
=== 2.8 VRRP ===
|Example:  1476
'''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.
|'''1476''': Maximum  Transmission Unit size for the GRE tunnel.
 
|-
In General Settings, click on ‘Enable VRRP’ and save.
|11
 
|TTL
[[File:RB44 VRRP Configuration.png|1024x1024px]]
|Example:  64
 
|'''64''': Time To  Live value for the packets within the GRE tunnel.
In VRRP section,
|-
 
|12
Give a name and ‘Add’ device.
|Tunnel  key
 
|Example:  12345678
Click on ‘Edit’ to make changes.
|'''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:'''


Click on ‘Delete’ if particular instance not required.
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.


[[File:RB44 VRRP Configuration Edit.png|1024x1024px]]
Here the user can add/edit/delete the details of the tunnel.
 
[[File:RB44 IPIP Tunnel Configuration.png|1024x1024px]]  


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


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


Specification details are given below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
|Field Name
|Field Name
|Sample Value
|Sample Value
|Description
|Description
|-
|-
|1
|1
|Role
|Tunnel  name
|1.      Master
|Example:  IPIPTunnel
 
|'''IPIPTunnel:''' The name of the IPIP tunnel.
2.      Backup
|Choose '''Master''' for the primary router that should handle the traffic under normal  circumstances.
 
Choose '''Backup'''  for a secondary router that will take over if the master fails.
|-
|-
|2
|2
|Virtual ID
|Local  external IP
|Ex: 0
|Example: 10.1.1.66
|The value can range from 0 to 255.
|The IP address of the local endpoint that will initiate the IPIP tunnel.
 
Ensure all  routers in the same VRRP group share the same '''Virtual ID'''.
|-
|-
|3
|3
|Priority
|Remote  external IP
|Ex: 100
|Example:  10.1.1.40
|For the '''Master''' role, use the highest priority, typically above 100.
|The IP address of the remote endpoint that will terminate the IPIP tunnel.
 
For the '''Backup''' role, set a lower priority number, usually below the master's priority.
|-
|-
|4
|4
|Interface
|Peer  tunnel IP
|SW_LAN
|Example:  10.1.1.4
|This is the  network interface on which VRRP operates.
|The IP address of the peer's tunnel interface.
|-
|-
|5
|5
|Source IP
|Local  tunnel IP
|Ex: 192.168.10.1
|Example: 10.1.1.6
|This is the  IP address used as the source in VRRP advertisements.
|The IP address of the local tunnel  interface.
|-
|-
|6
|6
|Peer IP
|Local  tunnel net mask
|Ex: 192.168.10.10
|Example: 255.255.255.0
|This is the  IP address of the other VRRP peer (usually the backup router). It helps the routers identify each other.
|The subnet mask of the local tunnel interface.
|-
|-
|7
|7
|Virtual IP Address
|Remote IP
|192.168.10.100/24
|Example:  192.168.10.0/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.
|The remote network that is reachable through the IPIP tunnel.
|-
|-
|8
|8
|Enable  Authentication
|Enable  Tunnel Link
|Enable/Disable
|Check to  enable
|Enable this  if you want to secure your VRRP communications.
|Enable or disable the IPIP tunnel link.
|-
|-
|9
|9
|Password
|Interface  type
|*********
|Example:  EWAN2
|It ensures that only routers with the correct password can join the VRRP group.
|'''EWAN2''': The type of network interface used for the IPIP tunnel.
|}
|-
Save and update once changes have been made.
|10
 
|MTU
=== 2.9 Remote Monitoring ===
|Example:  1476
In this page the user can select which equipment needs to be monitored remotely.
|'''1476''': Maximum  Transmission Unit size for the IPIP tunnel.
 
|-
Once the user selects the type of RMS click on save.
|11
 
|TTL
[[File:RB44 Remote Managment System.png|1024x1024px]]
|Example:  64
 
|'''64''': Time To  Live value for the packets within the IPIP tunnel.
'''NMS:'''
|-
 
|12
IN this page the user should type the server IP or domain name in the URL then click on save.
|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 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.Maintenance ==
In this module the user can configure/upgrade/modify the settings related to system, password, firmware and monitoring.


[[File:RB44 NMS Dashboard.png|1024x1024px]]
It includes below submodules.


'''TR_069:'''
* General
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application


To enable the TR_069 the user needs to click on the enable check box.
[[File:RB44 Maintenance Dashboard.png|1024x1024px]]
 
''*Below is the detailed explanation of every field*''
 
=== 3.1 General/ System ===
Here you can configure the basic aspects of router like its hostname or the time zone.
 
It is further sub-divided into,
 
1.) General Settings
 
2.) Logging


[[File:RB44 TR 069 Config.png|1024x1024px]]
3.) Language and Style


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


[[File:RB44 TR 069 Edit.png|1024x1024px]]
'''General Settings:'''


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


Specification details are given below:
'''EDIT:'''
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 2,175: Line 2,171:
|-
|-
|1
|1
|Serving  Interval
|Local Time
|300
|2024/07/30  13:25:47
|A value of 300 seconds means the device will check in with the ACS (auto-configuration servers) every 5 minutes.
|The current local date and time set on  the device.
|-
|-
|2
|2
|Interface
|Hostname
|This can  be something like eth0 or wan.
|22B25240007
|This specifies the network interface used for TR-069 communication.
|The hostname of the device, which is used to identify it on the network.
|-
|-
|3
|3
|Username
|Time zone
|Example: User
|Asia/Kolkata
|The username used to authenticate with  the ACS.
|The time zone setting of the device,  which determines the local time.
|-
|4
|Password
|••••
|The password used to authenticate with  the ACS.
|-
|5
|URL
|<nowiki>http://example.com</nowiki>
|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.
Once the user configures the required details then click on the save button to save all the details.  


=== 2.10 Tunnel ===
'''Logging:'''
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,
Here the user can configure the basic aspects of your device related to system.


1.) General Settings
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.


2.) GRE Tunnel
[[File:RB44 Logging .png|1024x1024px]]


3.) IPIP Tunnel
'''EDIT:'''
 
{| class="wikitable"
[[File:RB44 Tunnel Configuration.png|1024x1024px]]
|SN
 
|Field Name
 
|Sample Value
'''General Settings:'''  
|Description
 
|-
In this page the user needs to select under which type of tunnel it needs to send the data.
|1
 
|System  log buffer size
[[File:RB44 Tunnel General Settings.png|1024x1024px]]
|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.
 
|-
Once the user selects the type of tunnel then click on the save button.
|2
 
|External  system log server
'''GRE Tunnel:'''
|Example:  0.0.0.0
 
|The IP address of an external server  where logs can be sent.
A GRE (Generic Routing Encapsulation) tunnel configuration involves setting up a virtual point-to-point connection between two endpoints over an IP network.
|-
|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.


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


[[File:RB44 GRE Tunnel Config.png|1024x1024px]]
'''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.


Once the required update is done then click on update to save the changes.
[[File:RB44 Language and Style.png|1024x1024px]]


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


'''EDIT:'''
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 GRE Tunnel Configuration .png|1024x1024px]]
[[File:RB44 Password Setting.png|1024x1024px]]
 
=== 3.3 Reboot ===
In this module the user can reboot the device remotely.
 
First option is to directly reboot the device without enabling the maintenance reboot tab.
 
Click on “Reboot Now” at the bottom of the screen to start the reboot process.
 
[[File:RB44 Maintenance Reboot.png|1024x1024px]]
 
 
To start maintenance reboot process first the user needs to fill all the required fields.
 
Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.
 
[[File:RB44 Reboot settings.png|1024x1024px]]  




Specification details are given below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 2,251: Line 2,270:
|-
|-
|1
|1
|Tunnel name
|Enable Maintenance Reboot
|Example:  GRETunnel
|Enable/Disable
|'''GRETunnel''': The name of the GRE tunnel.
|Indicates whether the maintenance  reboot feature is enabled or not.
|-
|-
|2
|2
|Local external  IP
|Type
|Example: 10.1.1.66
|Maintenance Reboot
|The IP address of the local endpoint that will initiate the GRE tunnel.
|Specifies the type of reboot being scheduled.
|-
|-
|3
|3
|Remote external IP
|Reboot Type
|Example:  10.1.1.40
|Software/Hardware
|The IP address of the remote endpoint that will terminate the GRE tunnel.
|'''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
|4
|Peer  tunnel IP
|Minutes
|Example:  10.1.1.4
|Example:  59
|The IP address of the peer's tunnel interface.
|The minute at which the reboot should occur (0-59).
|-
|-
|5
|5
|Local  tunnel IP
|Hours
|Example:  10.1.1.6
|Example:  22 (10 PM)
|The IP address of the local tunnel interface.
|The hour at which the reboot should occur (0-23, in 24-hour format).
|-
|-
|6
|6
|Local tunnel net mask
|Day Of Month
|Example:  255.255.255.0
|Example:  All
|The subnet mask of the local tunnel interface.
|Specifies which days of the month the reboot should occur (1-31). "All" means it will occur every day.
|-
|-
|7
|7
|Remote IP
|Month
|Example: 192.168.10.0/24
|Example: All
|The remote network that is reachable through the GRE tunnel.
|Specifies which months the reboot should occur (1-12). "All" means it will occur every month.
|-
|-
|8
|8
|Enable Tunnel Link
|Day Of Week
|Check to  enable
|Example:  All
|Enable or disable the GRE tunnel link.
|Specifies which days of the week the  reboot should occur (0-6, where 0 is Sunday). "All" means it will occur every day of the week.
|-
|}
|9
Once the user fills all the required given parameters click on the save.
|Interface  type
 
|Example:  EWAN2
=== 3.4 Import and Export ===
|'''EWAN2''': The  type of network interface used for the GRE tunnel.
In this section, User can Import & Export Configuration files of the Device.
|-
 
|10
[[File:RB44 Import and Export.png|1024x1024px]]
|MTU
 
|Example: 1476
Click “Export Config” to export device configuration & settings to a text file,
|'''1476''': Maximum  Transmission Unit size for the GRE tunnel.
 
|-
Click “Import Config” to import device configuration & settings from a previously exported text file.
|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:'''
[[File:RB44 Import Config.png|1024x1024px]]


An IPIP (IP-in-IP) tunnel is a simple tunnelling protocol used to encapsulate IP packets within IP packets. This is like GRE but without additional features such as keying and type fields.
The user needs to select on the “choose file”, upload the required file and click on apply.


Here the user can add/edit/delete the details of the tunnel.
=== 3.5 Firmware Upgrade ===
The user can upgrade with the latest software for the existing firmware.


[[File:RB44 IPIP Tunnel Configuration.png|1024x1024px]]  
[[File:RB44 Firmware Upgrade.png|1024x1024px]]


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


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


Once the required update is done then click on update to save the changes.
'''Modem Monitor Application Configuration:'''


[[File:RB44 Modem Monitor Application.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
|Tunnel  name
|Enable Ping Check Application
|Example:  IPIPTunnel
|Enable/Disable
|'''IPIPTunnel:''' The name of the IPIP tunnel.
|Turns on the functionality to perform ping  checks on specified IP addresses.
|-
|-
|2
|2
|Local  external IP
|Time Interval for Check (In minutes)
|Example: 10.1.1.66
|'''Example:''' 10 minutes
|The IP address of the local endpoint  that will initiate the IPIP tunnel.
|Frequency at which the ping checks are performed.
|-
|-
|3
|3
|Remote  external IP
|Select No of IP addresses to ping
|Example: 10.1.1.40
|'''Example:''' 1
|The IP address of the remote endpoint  that will terminate the IPIP tunnel.
|Number of IP addresses that will be pinged.
|-
|-
|4
|4
|Peer  tunnel IP
|IP Address 1
|Example: 10.1.1.4
|'''Example:''' 8.8.8.8
|The IP address of the peer's tunnel  interface.
|The IP address to ping.
|-
|-
|5
|5
|Local  tunnel IP
|No. of Retries
|Example: 10.1.1.6
|'''Example:''' 5
|The IP address of the local tunnel  interface.
|Number of times to retry pinging an IP address if the initial ping fails.
|-
|-
|6
|6
|Local  tunnel net mask
|Failure Criteria in (%)
|Example:  255.255.255.0
|'''Example:''' 80% (If 4 out of 5 pings fail, it’s considered a failure)
|The subnet mask of the local tunnel  interface.
|Percentage of failed pings required to consider  the ping check a failure.
|-
|-
|7
|7
|Remote IP
|Action On Failure
|Example: 192.168.10.0/24
|'''Example:''' Restart Modem
|The remote network that is reachable through the IPIP tunnel.
|Action to be taken if the ping check fails according to the criteria.
|-
|-
|8
|8
|Enable Tunnel Link
|Enable Second Level Action
|Check to enable
|Enable/Disable
|Enable or disable the IPIP tunnel link.
|Option to enable a secondary action if the primary action fails multiple times.
|-
|-
|9
|9
|Interface  type
|Second Level Action Threshold
|Example:  EWAN2
|'''Example:''' 2
|'''EWAN2''': The  type of network interface used for the IPIP tunnel.
|Number of failures required to trigger the secondary action.
|-
|-
|10
|10
|MTU
|Second Level Action
|Example:  1476
|'''Example:''' Restart Board (Reboots the entire hardware board)
|'''1476''': Maximum  Transmission Unit size for the IPIP tunnel.
|The action to be taken if the second level action threshold is met.
|-
|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.
|}
|}
Save the details once made necessary changes.


== 3.Maintenance ==
'''Router Monitor Application Configuration:'''
In this module the user can configure/upgrade/modify the settings related to system, password, firmware and monitoring.


It includes below submodules.
[[File:RB44 Monitor Application Configuration.png|1024x1024px]]


* General
Specification details are given below:
* Password
* Reboot
* Import and Export config
* Firmware upgrade
* Monitor Application
 
[[File:RB44 Maintenance Dashboard.png|1024x1024px]]
 
''*Below is the detailed explanation of every field*''
 
=== 3.1 General/ System ===
Here you can configure the basic aspects of router like its hostname or the time zone.
 
It is further sub-divided into,
 
1.) General Settings
 
2.) Logging
 
3.) Language and Style
 
 
'''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
|Local Time
|Enable Ping Check Application
|2024/07/30  13:25:47
|Enable/Disable
|The current local date and time set on the device.
|Activates the ping check functionality to monitor router performance.
|-
|-
|2
|2
|Hostname
|Time Interval for Check (In minutes)
|22B25240007
|'''Example:''' 10 minutes
|The hostname of the device, which is used to identify it on the network.
|How frequently the ping checks are performed.
|-
|-
|3
|3
|Time zone
|Select No of IP Addresses to Ping
|Asia/Kolkata
|'''Example:''' 1 (Please select the appropriate number  based on your requirements)
|The time zone setting of the device,  which determines the local time.
|Choose the number of IP addresses to ping. This typically involves selecting from a list  or entering multiple addresses.
|}
|-
Once the user configures the required details then click on the save button to save all the details.
|4
 
|No. of Retries
'''Logging:'''
|'''Example:''' 3
 
|Number of  retries if a ping fails.
Here the user can configure the basic aspects of your device related to system.
|-
 
|5
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.
|Failure Criteria in (%)
 
|'''Example:''' 80% (If 80% of the pings fail, it’s  deemed a failure)
[[File:RB44 Logging .png|1024x1024px]]
|Percentage of  failed pings required to consider the ping check as failed.
 
'''EDIT:'''
{| class="wikitable"
|SN
|Field Name
|Sample Value
|Description
|-
|-
|1
|6
|System  log buffer size
|Action On Failure
|Example: 32 kiB
|'''Example:''' Restart IPsec
|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.
|The action  taken if the ping check fails according to the criteria.
|-
|-
|2
|7
|External  system log server
|Enable Second Level Action
|Example:  0.0.0.0
|Enable/Disable
|The IP address of an external server  where logs can be sent.
|Option to  enable an additional action if the primary action fails.
|-
|-
|3
|8
|External  system log server port
|Second Level Action Threshold
|Example: 514
|'''Example:''' Specify the number of failures, such as 2
|The port used to send logs to the external log server. Port 514 is the default port for syslog.
|Number of  times the primary action must fail before the secondary action is triggered.
|-
|-
|4
|9
|Log  output level
|Second Level Action
|Example: Debug
|'''Example:''' Restart Board
|Sets the detail level of the system  logs.
|The action to  be taken if the second level action threshold is met.
|-
|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.
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.


'''Language and Style:'''
It has 4 submodules.


Here the user can configure the basic aspects of your device related to language.
* Interfaces
* Internet
* Modem
* Routes
[[File:RD44A Status.png|1024x1024px]]


Once the user configures the required details then click on the save button to save all the details.
=== 4.1 Interfaces ===
Each network device (interface) is associated with specific traffic statistics, uptime, and status. Active interfaces are operational, while inactive interfaces are not currently transmitting data.


[[File:RB44 Language and Style.png|1024x1024px]]
[[File:RB44 Interfaces.png|1024x1024px]]


=== 3.2 Password ===
Looking on the network status the user can check if the cellular, Wi-Fi, Ewan, VPN etc is up.
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.
=== 4.2 Internet ===
In this submodule the user can view the status of the internet connections.


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


=== 3.3 Reboot ===
To see the latest status of the internet connection the user needs to click on the refresh button.
In this module the user can reboot the device remotely.


First option is to directly reboot the device without enabling the maintenance reboot tab.
=== 4.3 Modem ===
This modem status page provides comprehensive information about the cellular connection's network operator, technology, mode, and various signal quality metrics.


Click on “Reboot Now” at the bottom of the screen to start the reboot process.
[[File:RB44 Modem Status.png|1024x1024px]]


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


To start maintenance reboot process first the user needs to fill all the required fields.
'''IPv4 Routes:''' This shows which network is directly connected on which interface.


Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.
Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''


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


Specification details are given below:
''*Refer the below image*''
{| class="wikitable"
|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.
[[File:RB44 Routes.png|1024x1024px]]
|-
|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 ===
== 5. Features ==
In this section, User can Import & Export Configuration files of the Device.
In this module the user can see all the features that the router has.


[[File:RB44 Import and Export.png|1024x1024px]]
This module includes 9 features.


Click “Export Config” to export device configuration & settings to a text file,
* Mac Address Binding
* URL Filtering
* Web Server
* Wi-Fi MacID Filtering
* Routing
* DMZ
* Others
* Connection Diagnostics
* Package Manager


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


[[File:RB44 Import Config.png|1024x1024px]]
=== 5.1 Mac Address Binding ===
MAC address binding is a configuration that binds a specific MAC address to a specific IP address.


The user needs to select on the “choose file”, upload the required file and click on apply.
This ensures that a particular device on the network always receives the same IP address from the DHCP


=== 3.5 Firmware Upgrade ===
server, which can be useful for network management, security, and ensuring consistent network
The user can upgrade with the latest software for the existing firmware.


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


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.
Under this submodule the user can configure/update/edit the IP Address for MAC.


This option will completely reset the device to default settings.
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.  


[[File:RB44 Flash Image.png|1024x1024px]]
[[File:RB44 MAC Address Binding.png|1024x1024px]]  


Click on the '''Retain Config and flash''' and chose the path where the sys-upgrade file is kept and then click on Retain Config and flash, it will upgrade to the latest software once the reboot is done.
'''EDIT:'''


This refers to updating the firmware (flashing) of a device while preserving the current configuration settings.
[[File:RB44 Mac Address Edit.png|1024x1024px]]
 
[[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:
Specification details are given below:
Line 2,652: Line 2,568:
|-
|-
|1
|1
|Enable Ping Check Application
|Device Name
|Enable/Disable
|mac1
|Turns on the functionality to perform ping checks on specified IP addresses.
|A user-defined name for the binding configuration.
|-
|-
|2
|2
|Time Interval for Check (In minutes)
|MAC Address
|'''Example:''' 10 minutes
|48:9e:bd:da:45:91
|Frequency at which the ping checks are performed.
|The unique identifier for the network interface  of the device to which the IP address will be bound.
|-
|-
|3
|3
|Select No of IP addresses to ping
|IP Address
|'''Example:''' 1
|192.168.10.55
|Number of IP addresses that will be pinged.
|The IP address that will be consistently  assigned to the device with the specified MAC address.
|-
|}
|4
 
|IP Address 1
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.
|'''Example:''' 8.8.8.8
 
|The IP address to ping.
* 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.
|5
 
|No. of Retries
Post all the changes the user needs to click on the update to reflect all the changes in the application.
|'''Example:''' 5
 
|Number of times to retry pinging an IP address  if the initial ping fails.
=== 5.2 URL Filtering ===
|-
In this submodule the user should provide the URL which needs to be blocked for the device.
|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:'''
By implementing URL filtering with the specified URL, you can control and restrict access to certain
 
websites, thereby improving network security and managing user access.
 
[[File:RB44 URL Filtering.png|1024x1024px]]To add the new URL for blocking, click on the Add New button.
 
Once the user clicks on the Add New button a new pop will appear in that page write the URL and click
 
on the save.
 
The user can select the status of that URL while defining the URL.
 
[[File: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:Rd44A Webserver .png|1024x1024px]]
 
'''EDIT:'''


[[File:RB44 Monitor Application Configuration.png|1024x1024px]]
[[File:RD44A Webserver Config.png|1024x1024px]]


Specification details are given below:
Specification details are given below:
Line 2,715: Line 2,628:
|-
|-
|1
|1
|Enable Ping Check Application
|Enable HTTP
|Enable/Disable
|'''HTTP Port:''' 80
|Activates the  ping check functionality to monitor router performance.
 
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
|Time Interval for Check (In minutes)
|Enable HTTPS
|'''Example:''' 10 minutes
|'''HTTPS Port:''' 443
|How frequently the ping checks are performed.
 
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
|Select No of IP Addresses to Ping
|Redirect HTTPS
|'''Example:''' 1 (Please select the appropriate number based on your requirements)
|Option to redirect HTTP traffic to HTTPS.
|Choose the number of IP addresses to ping. This typically involves selecting from a list  or entering multiple addresses.
|When enabled, all HTTP requests will be  automatically redirected to the HTTPS port to ensure secure communication.
|-
|-
|4
|4
|No. of Retries
|Session Timeout (in millisecs)
|'''Example:''' 3
|Ex: 60000
|Number of retries if a ping fails.
|In this scenario the webpage will logout after  60secs of inactivity.
|-
|-
|5
|5
|Failure Criteria in (%)
|RFC1918 Filter
|'''Example:''' 80% (If 80% of the pings fail, it’s  deemed a failure)
|Enable/Disable
|Percentage of failed pings required to consider the ping check as failed.
|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
|6
|Action On Failure
|Enable NTP Sync
|'''Example:''' Restart IPsec
|Enable or disable NTP synchronization.
|The action taken if the ping check fails according to the criteria.
|Synchronizes the device’s system clock with an external NTP server to maintain accurate time.
|-
|-
|7
|7
|Enable Second Level Action
|NTP Server
|Enable/Disable
|0.openwrt.pool.ntp.org
|Option to enable an additional action if the primary action fails.
|The address of the NTP server used for time synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
|-
|-
|8
|8
|Second Level Action Threshold
|NTP Sync Interval (In Minutes)
|'''Example:''' Specify the number of failures, such as 2
|15
|Number of times the primary action must fail before the secondary action is triggered.
|The interval at which the device will sync its clock with the NTP server, set to every 15 minutes in this case.
|-
|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.
Click on save once changes are made.


== 4.Status ==
=== 5.4 Wi-Fi MacID Filtering ===
In this module the user can view the status of the router device with respect to the network, Wan, modem etc.
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 has 4 submodules.
It is further divided into 2 categories,


* Interfaces
'''WIFI 2.4G AP'''
* Internet
* Modem
* Routes
[[File:RB44 Status .png|1024x1024px]]


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


[[File:RB44 Interfaces.png|1024x1024px]]
[[File:RB44 WIFI 2.4G AP Guest.png|1024x1024px]]


Looking on the network status the user can check if the cellular, Wi-Fi, Ewan, VPN etc is up.
Before adding the MacIDs the user needs to select the mode from the dropdown menu.


=== 4.2 Internet ===
In ‘Change Mode’ select one option,
In this submodule the user can view the status of the internet connections.


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


To see the latest status of the internet connection the user needs to click on the refresh button.
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.


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


[[File:RB44 Modem Status.png|1024x1024px]]
In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.


=== 4.4 Routes ===
To Add the MacID the user needs to click on Add New option.
This configuration shows how the router directs traffic between different networks and interfaces, ensuring proper communication within the local network and to external networks via the default gateway.


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


'''IPv4 Routes:''' This shows which network is directly connected on which interface.
Specification details are given below:
{| class="wikitable"
|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.


Example: Network '''192.168.10.0/24''' is directly connected on interface '''eth0.1.'''
The user needs to click on the edit button to do modifications on the pre-existing configuration.


'''IPv6 Routes:''' Similar routes as IPv4, but this time listed under IPv6 routing rules.
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.


Example: Local networks '''192.168.10.0/24''' and '''192.168.100.0/24''' are managed through '''eth0.1''' and '''ra0''', respectively.
=== 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.


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


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


== 5. Features ==
'''Advanced Static IPV4 Routes'''
In this module the user can see all the features that the router has.


This module includes 9 features.
'''Static IPV4 Routes:'''


* Mac Address Binding
Click on ‘Add’ to add a new interface. 
* URL Filtering
* Web Server
* Wi-Fi MacID Filtering
* Routing
* DMZ
* Others
* Connection Diagnostics
* Package Manager


[[File:RB44 Features.png|1024x1024px]]
[[File:RB44 Routing .png|1024x1024px]]


=== 5.1 Mac Address Binding ===
'''EDIT:'''
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
To edit the existing device the user needs to click on the edit option.


server, which can be useful for network management, security, and ensuring consistent network
Once the changes are done click on the save button to save all the changes.


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


Under this submodule the user can configure/update/edit the IP Address for MAC.
[[File:RB44 Static IPV4 Routes.png|1023x1023px]]
 
Specification details are given below:
You can edit the pre-existing configuration, or you can ‘Add’ in the ‘New MAC ADDRESS’ field.
 
[[File:RB44 MAC Address Binding.png|1024x1024px]]
 
'''EDIT:'''
 
[[File:RB44 Mac Address Edit.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
|SN
|SN
Line 2,852: Line 2,760:
|-
|-
|1
|1
|Device Name
|Interface
|mac1
|Ex: eth0.1
|A user-defined name for the binding  configuration.
|The network interface to be used for this route.  Select the one to use from dropdown.
|-
|-
|2
|2
|MAC Address
|Target
|48:9e:bd:da:45:91
|Ex: 192.168.20.0
|The unique identifier for the network interface  of the device to which the IP address will be bound.
|The destination subnet to which traffic should  be routed.
|-
|-
|3
|3
|IP Address
|IPv4 Netmask
|192.168.10.55
|255.255.255.0
|The IP address that will be consistently  assigned to the device with the specified MAC address.
|The subnet mask for the target network.
|}
|-
|4
|Metric
|0
|The priority of the route.


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


* Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
Custom changes can be made.
* The user can click on the deleted button to delete an existing configured device.
|}
Click on save once configuration changes have been made.  


Post all the changes the user needs to click on the update to reflect all the changes in the application.
'''Advanced Static IPV4 Routes:'''


=== 5.2 URL Filtering ===
This is further divided into 2 sections,
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
Routing Tables


websites, thereby improving network security and managing user access.
Routing Rules for IPV4


[[File:RB44 URL Filtering.png|1024x1024px]]To add the new URL for blocking, click on the Add New button.
'''Routing Tables:'''


Once the user clicks on the Add New button a new pop will appear in that page write the URL and click
Adding a new table in static routing allows you to define specific routes for traffic within a network.


on the save.
Click on ‘Add’ to add a new Table.


The user can select the status of that URL while defining the URL.
[[File:RB44 Advanced Static IPV4 Routes-.png|1024x1024px]]
 
[[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:'''
'''EDIT:'''


[[File:RB44 Webserver Config.png|1024x1024px]]
[[File:RB44 Advanced Static IPV4 Routes Editing.png|1024x1024px]]


Specification details are given below:
Specification details are given below:
Line 2,912: Line 2,823:
|-
|-
|1
|1
|Enable HTTP
|ID of Table
|'''HTTP Port:''' 80
|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.
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
|Name of Table
|'''HTTPS Port:''' 443
|Ex: Route
 
|A descriptive name for the routing table, making it easier to manage and identify different tables.
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
|Target
|Option to redirect HTTP traffic to  HTTPS.
|Ex: 192.168.10.0
|When enabled, all HTTP requests will be automatically redirected to the HTTPS port to ensure secure communication.
|Specifies the destination network or IP address that the route is intended for.
|-
|-
|4
|4
|Session Timeout (in millisecs)
|IPv4 Netmask
|Ex: 60000
|255.255.255.0
|In this scenario the webpage will logout after  60secs of inactivity.
|Defines the subnet mask for the target network.
|-
|-
|5
|5
|RFC1918 Filter
|Metric
|Enable/Disable
|Ex: 0
|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.
|Indicates the priority of the route. A lower metric value means a higher priority. Routes with lower metrics are preferred over those with higher metrics.
|-
|-
|6
|6
|Enable NTP Sync
|IPv4 Gateway
|Enable or disable NTP synchronization.
|Ex: 10.1.1.1
|Synchronizes the device’s system clock with an external NTP server to maintain accurate time.
|Specifies the next hop or gateway IP address through which the traffic to the target network should be routed.
|-
|-
|7
|7
|NTP Server
|Route Type
|0.openwrt.pool.ntp.org
|1.) Unicast
|The address of the NTP server used for time synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
 
|-
2.) Custom
|8
|'''Unicast''': Standard route where packets are sent to a single destination IP address.
|NTP Sync Interval (In Minutes)
 
|15
'''Custom''': Enables  advanced routing configurations or specific protocols that might not be covered by default.
|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,
'''Routing Rules for IPV4:'''


'''WIFI 2.4G AP'''
Click on ‘Add’ to add a new interface.  


'''WIFI 2.4G AP Guest'''
[[File:RB44 Routing Rules for IPV4.png|1024x1024px]]


[[File:RB44 WIFI 2.4G AP Guest.png|1024x1024px]]
'''EDIT:'''


Before adding the MacIDs the user needs to select the mode from the dropdown menu.
To edit the existing device the user needs to click on the edit option.


In ‘Change Mode’ select one option,
Once the changes are done click on the save button to save all the changes.


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


In blacklist mode, you specify which MAC addresses are not allowed to connect to the wireless network. Devices not on the blacklist will be able to connect.
[[File:RB44 Routing Rules for IPV4 Editing.png|1024x1024px]]
 
'''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:
Specification details are given below:
Line 2,993: Line 2,888:
|-
|-
|1
|1
|Status
|Interface
|Enable/Disable
|Ex: ra0
|Enable or disable the MAC ID filtering.
|Select the specific network interface on the  router through which traffic enters or exits.
|-
|-
|2
|2
|MAC ID
|To
|Example: e8:6f:38:1a:f2:61
|Ex: 192.168.10.1
|The MAC address of the device to be whitelisted  or blocklisted.
|The destination IP address or network. In this  case, 192.168.10.1 is the target IP address for routing traffic.
|-
|-
|3
|3
|Network Name
|IPv4 Netmask
|Example: WIFI 2.4G AP or Wi-Fi 2.4G AP Guest.
|Ex: 255.255.255.192
|The network to apply the MAC ID filtering.
|Defines the subnet mask, which helps determine the size of the network.
|}
|-
Once the required MAC ID and Network Name is configured the user needs to click on the save button to add the details.
|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


The user needs to click on the edit button to do modifications on the pre-existing configuration.
2.) iif (Incoming Interface)


Once the required MACID / Network Name is modified the user needs to click on the save button to reflect the changed value in the application.
3.) oif (Outgoing Interface)


=== 5.5 Routing ===
4.) lookup
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,
5.) blackhole


'''Static IPV4 Routes'''
6.) prohibited


'''Advanced Static IPV4 Routes'''
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.


'''Static IPV4 Routes:'''
3.) This  allows you to control the flow of traffic based on the desired outgoing  interface.


Click on ‘Add’ to add a new interface.
4.) It tells the router to check the specific  routing table ID mentioned to determine how to route the traffic.


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


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


To edit the existing device the user needs to click on the edit option.
7.) Causes  the router to send an ICMP unreachable message to the source IP, notifying  that the destination is unreachable.
|}


Once the changes are done click on the save button to save all the changes.
=== 5.6 Others ===
In this page the user will get to do all the other miscellaneous configuration with respect to the device based on the required parameters. Each utility serves a specific purpose, providing various functionalities for managing and troubleshooting network configurations and statuses.


Click on the deleted button to delete the existing device detail.
[[File:RB44 Others .png|1024x1024px]]


[[File:RB44 Static IPV4 Routes.png|1023x1023px]]
Specification details are given below:
Specification details are given below:
{| class="wikitable"
{| class="wikitable"
Line 3,045: Line 2,960:
|-
|-
|1
|1
|Interface
|Set Date
|Ex: eth0.1
|Date and time fields (day, month, year,  hour, minute, second)
|The network interface to be used for this route. Select the one to use from dropdown.
|Sets the system date and time to the specified values.
|-
|-
|2
|2
|Target
|Get Date
|Ex: 192.168.20.0
|System
|The destination subnet to which traffic should be routed.
|Retrieves and displays the current system date and time.
|-
|-
|3
|3
|IPv4 Netmask
|ipsec status all
|255.255.255.0
|Command ‘Get’
|The subnet mask for the target network.
|Displays the status of all IPsec connections.
|-
|-
|4
|4
|Metric
|Wi-Fi Scan
|0
|Command ‘Get’
|The priority of the route.
|Initiates a scan for available Wi-Fi networks.
 
Lower values indicate higher priority.
|-
|-
|5
|5
|IPv4 Gateway
|iPerf3 Client
|Ex: 192.168.10.1
|IP address (e.g., 192.168.10.100)
|The gateway IP address to be used for routing traffic to the target subnet.
|Runs an iPerf3 client to measure network performance.
|-
|-
|6
|6
|Route Type
|iPerf3 Server
|Unicast
|Command ‘Run’
|Standard route for individual destination IP addresses.
|Runs an iPerf3 server to measure network performance.
 
|-
Custom changes can be made.
|7
|}
|Ping
Click on save once configuration changes have been made.  
|IP address or domain (e.g., 8.8.8.8)
 
|Sends ICMP echo requests to the specified  address to check connectivity.
'''Advanced Static IPV4 Routes:'''
|-
 
|8
This is further divided into 2 sections,
|traceroute
 
|IP address or domain (e.g., 8.8.8.8)
Routing Tables
|Traces the route packets take to reach the  specified address.
 
|-
Routing Rules for IPV4
|9
 
|NTP Sync
'''Routing Tables:'''
|Command ‘Sync’
 
|Synchronizes the system time with the  configured NTP server.
Adding a new table in static routing allows you to define specific routes for traffic within a network.
|-
 
|10
Click on ‘Add’ to add a new Table.
|Download Files
 
|File or database identifier
[[File:RB44 Advanced Static IPV4 Routes-.png|1024x1024px]]
|Initiates a download of the specified file or database.
 
'''EDIT:'''
 
[[File:RB44 Advanced Static IPV4 Routes Editing.png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample Value
|Description
|-
|-
|1
|11
|ID of Table
|Restart Power
|Ex: 1
|Command ‘Restart’
|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.
|Restarts the power of the device.
|-
|-
|2
|12
|Name of Table
|Restart Modem
|Ex: Route
|Command ‘Restart’
|A descriptive name for the routing table,  making it easier to manage and identify different tables.
|Restarts the modem.
|-
|-
|3
|13
|Target
|Run AT Command
|Ex: 192.168.10.0
|Enter AT command
|Specifies the destination network or IP address  that the route is intended for.
|Executes the specified AT command on the modem.
|-
|-
|4
|14
|IPv4 Netmask
|Show Board Configuration
|255.255.255.0
|Command ‘Show’
|Defines the subnet mask for the target network.
|Displays the current board configuration.
|-
|-
|5
|15
|Metric
|Show VPN Certificate Name
|Ex: 0
|Command ‘Show’
|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.
|Displays the name of the VPN certificate in use.
|-
|-
|6
|16
|IPv4 Gateway
|Switch SIM to Secondary (Takes >2  mins)
|Ex: 10.1.1.1
|Command ‘Run’
|Specifies the next hop or gateway IP address through  which the traffic to the target network should be routed.
|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.
|-
|-
|7
|19
|Route Type
|Data Usage
|1.) Unicast
|'''From:''' Start  date (YYYY-MM-DD)


2.) Custom
'''To:''' End date  (YYYY-MM-DD)
|'''Unicast''': Standard route where packets are sent to a single destination IP address.
|Displays data usage statistics for the specified date range.
 
|-
'''Custom''': Enables  advanced routing configurations or specific protocols that might not be  covered by default.
|20
|}
|Monthly Data Usage
|'''Month:''' Month (e.g., 07)


 
'''Year:''' Year  (e.g., 2024)
 
|Displays data usage statistics for the  specified month and year.
'''Routing Rules for IPV4:'''
|-
 
|
Click on ‘Add’ to add a new interface.  
|
 
|
[[File:RB44 Routing Rules for IPV4.png|1024x1024px]]
|
 
|-
'''EDIT:'''
|21
 
|Modem Debug Info
To edit the existing device the user needs to click on the edit option.
|Command ‘Read’
 
|Displays debug information for the modem.
Once the changes are done click on the save button to save all the changes.
|-
 
|22
Click on the deleted button to delete the existing device detail.
|Scan Network operators (Takes >3 mins)
 
|Command ‘Scan’
[[File:RB44 Routing Rules for IPV4 Editing.png|1024x1024px]]
|Initiates a scan for available network  operators.
 
Specification details are given below:
{| class="wikitable"
|SN
|Field Name
|Sample  Value
|Description
|-
|-
|1
|23
|Interface
|Network operator list (First Perform  Scan Network Operators)
|Ex: ra0
|Command ‘Show’
|Select the specific network interface on the router through which traffic enters or exits.
|Displays the list of network operators detected  in the previous scan.
|-
|-
|2
|24
|To
|ReadLogFiles
|Ex: 192.168.10.1
|Log file identifier
|The destination IP address or network. In this  case, 192.168.10.1 is the target IP address for routing traffic.
|Reads and displays the specified log file
|-
|-
|3
|25
|IPv4 Netmask
|Enable ssh (Admin)
|Ex: 255.255.255.192
|Command ‘Run’
|Defines the subnet mask, which helps determine  the size of the network.
|Enables SSH access for the admin user.
|-
|-
|4
|26
|Table ID
|Disable ssh (Admin)
|Ex: 1
|Command ‘Run’
|Identifies which routing table this rule  applies to.
|Disables SSH access for the admin user.
|-
|-
|5
|27
|From
|ClearSIM1Data
|Ex: 192.168.100.1
|Command ‘Clear’
|Specifies the source IP address or network from  which the traffic originates. In this case, the traffic is coming from  192.168.100.1.
|Clears data usage statistics for SIM1.
|-
|-
|6
|28
|Priority
|ClearSIM2Data
|Ex:20
|Command ‘Clear’
|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.
|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.
|-
|-
|7
|32
|Outgoing Interface
|Output
|1.) fwmark
|Any value
|Displays output for all the above actions.
|}


2.) iif (Incoming Interface)
=== 5.7 Connection Diagnostics ===
This can ensure that your connection diagnostics application effectively monitors and reports the status of your network connections, providing valuable data for troubleshooting and performance optimization.


3.) oif (Outgoing Interface)
[[File:RD44A Connection Diagnostics.png|1024x1024px]]


4.) lookup
This Application works in 3 parts,


5.) blackhole
1.) General settings


6.) prohibited
2.) Connection status and management


7.) unreachable
3.) Application Start/Stop
|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.
[[File:RB44 Application Start Stop.png|1024x1024px]]


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


4.) It tells the router to check the specific  routing table ID mentioned to determine how to route the traffic.
First make configuration changes in this section and save.
 
5.) This is  used when you want to block traffic without notifying the sender.
 
6.) Like  blackhole but sends an ICMP unreachable message to the sender, indicating  that the route is prohibited.
 
7.) Causes  the router to send an ICMP unreachable message to the source IP, notifying  that the destination is unreachable.
|}
 
=== 5.6 DMZ ===
A '''DMZ (Demilitarized Zone)''' is a subnetwork that provides an extra layer of security for an organization's internal network.
 
In this case we are configuring several services (HTTP, HTTPS, SSH, FTP, DNS) in a DMZ, and each service requires the correct '''internal port''' (the port used within the network) and '''external port''' (the port used by external clients to access the service) setting
 
[[File:RB44 DMZ .png|1024x1024px]]
 
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Enable DMZ
|Enable/Disable
|Enable DMZ to configure it further.
|-
|2
|Host IP Address
|Ex: 192.168.10.1
|This is the internal IP address of the device  or server that will be in the DMZ.
|-
|3
|Protocol
|1.) TCP
 
2.) UDP
 
3.) ICMP
 
4.) All
|'''TCP''': Used  for reliable services like HTTP, HTTPS, FTP, and SSH.
 
'''UDP''': Often  used for services like DNS that don't require as much reliability.
 
'''ICMP''': Used  for sending control messages like "ping."
 
'''All''': Select  this if you're unsure which protocol to allow, but it's less secure.
|-
|4
|Allow HTTP
|Internal Port: 80
 
External Port: 80
|Enables web traffic over the unsecured '''HTTP'''  protocol.
 
(Port 80 is the standard port for HTTP traffic  on our internal network).
|-
|5
|Allow HTTPS
|Internal Port: 443
 
External Port: 443
|Enables secure web traffic over '''HTTPS.''' (Port  443 is the standard port for HTTPS on our internal network).
|-
|6
|Allow SSH
|Internal Port: 52434
 
External Port: 52434
|This is a custom port we’re using for SSH.
 
The default is 22.
|-
|7
|Allow FTP
|Internal Port: 21/20
 
External Port: 21/20
|FTP is used to transfer files between  computers.
 
(These are the standard ports for FTP traffic.  Port 21 is used for control commands, and port 20 for the data transfer.)
|-
|8
|Allow DNS
|Internal Port: 53
 
External Port: 53
|Standard DNS port within our internal network.
|}
 
=== 5.7 Others ===
In this page the user will get to do all the other miscellaneous configuration with respect to the device based on the required parameters. Each utility serves a specific purpose, providing various functionalities for managing and troubleshooting network configurations and statuses.
 
[[File:RB44 Others .png|1024x1024px]]
 
Specification details are given below:
{| class="wikitable"
|SN
|Field  Name
|Sample  Value
|Description
|-
|1
|Set Date
|Date and time fields (day, month, year,  hour, minute, second)
|Sets the system date and time to the specified  values.
|-
|2
|Get Date
|System
|Retrieves and displays the current system date  and time.
|-
|3
|ipsec status all
|Command ‘Get’
|Displays the status of all IPsec connections.
|-
|4
|Wi-Fi Scan
|Command ‘Get’
|Initiates a scan for available Wi-Fi networks.
|-
|5
|iPerf3 Client
|IP address (e.g., 192.168.10.100)
|Runs an iPerf3 client to measure network  performance.
|-
|6
|iPerf3 Server
|Command ‘Run’
|Runs an iPerf3 server to measure network  performance.
|-
|7
|Ping
|IP address or domain (e.g., 8.8.8.8)
|Sends ICMP echo requests to the specified  address to check connectivity.
|-
|8
|traceroute
|IP address or domain (e.g., 8.8.8.8)
|Traces the route packets take to reach the  specified address.
|-
|9
|NTP Sync
|Command ‘Sync’
|Synchronizes the system time with the  configured NTP server.
|-
|10
|Download Files
|File or database identifier
|Initiates a download of the specified file or  database.
|-
|11
|Restart Power
|Command ‘Restart’
|Restarts the power of the device.
|-
|12
|Restart Modem
|Command ‘Restart’
|Restarts the modem.
|-
|13
|Run AT Command
|Enter AT command
|Executes the specified AT command on the modem.
|-
|14
|Show Board Configuration
|Command ‘Show’
|Displays the current board configuration.
|-
|15
|Show VPN Certificate Name
|Command ‘Show’
|Displays the name of the VPN certificate in  use.
|-
|16
|Switch SIM to Secondary (Takes >2  mins)
|Command ‘Run’
|Switches the active SIM to the secondary SIM  card.
|-
|17
|Send test SMS
|Phone number (e.g., +911234567890)  message text (e.g., "Hello how are you?")
|Sends a test SMS to the specified phone number.
|-
|18
|ReadlatestSMS
|Command ‘Read’
|Reads the most recent SMS received by the  device.
|-
|19
|Data Usage
|'''From:''' Start  date (YYYY-MM-DD)
 
'''To:''' End date  (YYYY-MM-DD)
|Displays data usage statistics for the  specified date range.
|-
|20
|Monthly Data Usage
|'''Month:''' Month (e.g., 07)
 
'''Year:''' Year  (e.g., 2024)
|Displays data usage statistics for the  specified month and year.
|-
|
|
|
|
|-
|21
|Modem Debug Info
|Command ‘Read’
|Displays debug information for the modem.
|-
|22
|Scan Network operators (Takes >3  mins)
|Command ‘Scan’
|Initiates a scan for available network  operators.
|-
|23
|Network operator list (First Perform  Scan Network Operators)
|Command ‘Show’
|Displays the list of network operators detected  in the previous scan.
|-
|24
|ReadLogFiles
|Log file identifier
|Reads and displays the specified log file
|-
|25
|Enable ssh (Admin)
|Command ‘Run’
|Enables SSH access for the admin user.
|-
|26
|Disable ssh (Admin)
|Command ‘Run’
|Disables SSH access for the admin user.
|-
|27
|ClearSIM1Data
|Command ‘Clear’
|Clears data usage statistics for SIM1.
|-
|28
|ClearSIM2Data
|Command ‘Clear’
|Clears data usage statistics for SIM2.
|-
|29
|Create Bridge with SW_LAN
|Network interface identifier
|Creates a network bridge with the specified  interface and SW_LAN.
|-
|30
|Show Bridge
|Command ‘Show’
|Displays information about the current network  bridges.
|-
|31
|Delete Bridge
|Command ‘Delete’
|Deletes the specified network bridge.
|-
|32
|Output
|Any value
|Displays output for all the above actions.
|}
 
=== 5.8 Connection Diagnostics ===
This can ensure that your connection diagnostics application effectively monitors and reports the status of your network connections, providing valuable data for troubleshooting and performance optimization.
 
[[File:RB44 Connection Diagnostics.png|1024x1024px]]
 
This Application works in 3 parts,
 
1.) General settings
 
2.) Connection status and management


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


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


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


Latest revision as of 12:24, 6 January 2025

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

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


Connecting via LAN:

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

                                                                                                                                   

How to connect with the SILBO_RD44-A application

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

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

Type the command Ipconfig

How to connect with the SILBO RB44 application

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

Log In

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

It will show the log in page of the application.

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

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

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

The application is divided in to 6 Modules.

  • Info
  • Settings
  • Maintenance
  • Status
  • Features
  • Logout

1.Info

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

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

It has 3 submodules.

  • Overview
  • System Log
  • Kernel Log

1.1 Overview

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

System

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


The specifications details are as follows,

SN Field name Sample value Description
1 Hostname 45A27240002 This field displays the router serial number of the device
2 Model Silbo_RD44-A- EC200A This field displays the model number of the device
3 Firmware Version and IPK Version 1.17_1.15 This field displays the firmware version and IPK version
4 Kernel Version 4.14.180 This field displays the kernel version of the device
5 Local Time Thursday, December 5, 2024 at 04:05:24 PM This field displays the local time
6 Uptime 0h 3m 58s This field displays the uptime of the device
7 Load Average 1.03 0.98 0.44 This field displays the average load

Memory

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


The specifications details are as follows.

SN Field name Sample value Description
1 Total Available 68676 kB / 124208 kB (55%) This field displays the total availability of memory space in the device
2 Free 59344 kB / 124208 kB (47%) This field displays the Free memory space in the device
3 Cached 312 kB / 124208 kB (0%) This field displays the Cached memory space in the device
4 Buffered 9332 kB / 124208 kB (7%) This field displays the Buffered memory space in the device


Storage

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


The specifications details are as follows.

SN Field name Sample value Description
1 Root Usage


796 kB / 15488 kB (5%)

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


312 kB / 62104 kB (0%)

This field displays the total temporary usage of the device

Connection Tracking

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


The specifications details are as follows.

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

DHCP Leases:

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

The specifications details are below.

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

1.2 System Log

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

1.3 Kernel Log

This page provides on screen Kernel logging information.

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

2. Setting

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

IT consist of 8 submodules.

  • Network
  • Sim Switch
  • Internet
  • VPN
  • Firewall
  • Loopback Rule
  • Remote Monitoring
  • Tunnel

2.1 Network

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

Relay Server:

A relay server typically functions in a network to forward requests (usually DHCP or DNS) from clients to a designated server when the server is on a different network segment.

EDIT:

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

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

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

Specification details are given below:

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

2.)   ra0

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

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

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

Save and update.


Ethernet Setting:

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

For this device 5 ports are configured.

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

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

For port 5 setting,

Kindly select the option LAN for Port 5 mode LAN/WAN. Based on the option selected the field will also change. The user needs to configure all the required field and click on save.

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

Static

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

Port 5 Static IP

192.168.10.1

5.6.7.8

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

Kindly select the option EWAN2 for Port 5 mode LAN/WAN. Based on the option selected the field will also change. The user needs to configure all the required field and click on the save to save the required fields.

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

2.) Static

3.) PPPoE

4.) PPTP

5.) L2TP

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

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

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

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

5.) Layer 2 Tunnelling Protocol, another VPN protocol option.

3 Gateway 192.168.1.1 This field displays gateway address configured

Click on the save once all the configuration is done and click on the update button to update all the information.


SW_LAN settings,

In this part the user can configure the setting for SW_LAN

The specifications details are below.

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

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


Static option for SW_LAN Ethernet Protocol:

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

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

Cellular Setting:

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

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

The specifications details are below.

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

2.) Single Cellular with Single SIM

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

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

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

2.) Manual

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

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

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

2.) Manual

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

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

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

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

Band lock and Operator Lock:

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

Bands available in the drop-down list.

2G/3G option:

2G/3G: - 3G allows additional features such as mobile internet access, video calls and mobile TV. While the main function of 2G technology is the transmission of information through voice calls.

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

Operator Selection Mode:

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

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

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

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


Wi-Fi Setting:

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

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

It has 3 radio modes.

‘Access point’, ‘client only’ and ‘Access point and client’

Refer the below picture.

Access Point mode:

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

Client only:

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

Access point and client point:

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

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


The specifications details are below.

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

(INDIA by default)

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

2.) Client only

3.) Access point and client

In this drop down the user should select the mode.

(Access point by default)

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

(WPA2 Personal (PSK) by default)

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

(AES by default)

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

(192.168.100.1 will be default which can be changed accordingly)

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

(100 value is default)

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

(50 value is default)

Guest Wifi:

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


Wireless Schedule:

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

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

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

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

SMS Settings:

User needs to enable SMS option in SMS settings page.

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

1 to 5 mobile numbers can be authenticated by choosing from “Select Valid SMS user numbers” and adding the mobile numbers below respectively.

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

Displayed in the below screen is the default API key which can be edited and changed as per choice. After addition of the mobile number’s user needs to click on save button for changes to take place.

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

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

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

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


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

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

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


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


Loop back IP settings:

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

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

The loopback IP address, commonly represented as 127.0.0.1, is a special address used for testing network connectivity on a local machine. It allows a device to send network messages to itself without involving external networks, making it useful for troubleshooting and diagnostics.

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

2.2 SIM Switch

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


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

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


Threshold RSRP:

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

Threshold SINR:

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

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

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

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

2.3 Internet

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

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

The specifications details are below.

SN Field name Sample value Description
1 Name EWAN2 This field displays the name of the WAN connection
2 Priority 1 In this dropdown box the user needs to select the priority.
3 Select Track IP Numbers 2 In this dropdown the user needs to select the track number for the Ips. This specifies the number of IP addresses that will be used for tracking the status of the connection.
4 TrackIP1 8.8.8.8 This is the first IP address used for tracking the connection. 8.8.8.8 is a public DNS server provided by Google.
5 TrackIP2 8.8.4.4 This is the second IP address used for tracking the connection. 8.8.4.4 is another public DNS server provided by Google.
6 Reliability 1 This indicates the reliability threshold for considering the connection as up. A value of 1 typically means that only one successful ping response is needed to deem the connection reliable.
7 Count 1 This specifies the number of consecutive pings sent to the track IP addresses.
8 Up 1 This indicates the number of successful pings required to consider the connection as up.
9 Down 1 This indicates the number of failed pings required to consider the connection as down.

Once the user is done with modification click on the save button to save all the changes and then click on the update button.

2.4 VPN

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

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

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

Refer the below figure.

There are 5 types of setting available under VPN configuration.

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

General Settings:

In this page the user must choose which type of VPN connection is required for the device.

The user must select from IPSEC, Open VPN, Wireguard or Zerotier based on its requirement.

If required, the user can select all the options.

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

IPSEC:

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

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

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

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

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

Click on update once done with configurations.

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


Detailed specifications are below:

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

0

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

trap/start

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

AES 192

AES 256

3DES

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

MD5

SHA 256

SHA 384

SHA 512

SHA 512: Authentication algorithm for Phase I.

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

24 DH Group MODP768(group1)

MODP1024(group2)

MODP1536(group5)

MODP2048(group14)

MODP3072(group15)

MODP4096(group16)

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

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

Proposal settings Phase II
25 Hash Algorithm AES 128

AES 192

AES 256

3DES

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

MD5

SHA 256

SHA 384

SHA 512

SHA 512: Authentication algorithm for Phase II.

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

27 PFS Group MODP768(group1)

MODP1024(group2)

MODP1536(group5)

MODP2048(group14)

MODP3072(group15)

MODP4096(group16)

MODP2048 (group14): Perfect Forward Secrecy group.

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

Open VPN:

In the OpenVPN connection, the home network can function as a server, and the remote device can access the server through the router which acts as an OpenVPN Server gateway.

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

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

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

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

RD44A Open VPN Status

VPN TUN has been established.

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

WireGuard:

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

Click on “Edit” to start configurations as needed.

EDIT:

Click on the save button after the required configuration.

SN Field name Sample value Description
1 Wireguard Role Client/Server In this dropdown box the user needs to select the wireguard role.
2 Listen Port 51820 The UDP port on which the WireGuard client listens for incoming connections.
3 IP Addresses 10.0.0.1/24 The IP address and subnet mask assigned to the WireGuard client's interface. This address is used within the VPN.
4 Allowed PeerIPs 10.1.1.1 The IP address of the allowed peer(s) that can connect to this WireGuard client. This might need adjustment based on the actual peer IPs used in the network.
5 Endpoint HostIP 10.1.1.1 The IP address of the WireGuard server (the endpoint to which the client connects).
6 Endpoint HostPort 51820 The port on the WireGuard server to which the client connects.
7 PeerPublicKey ***** The public key of the peer (the server) the client is connecting to. This key is part of the public-private key pair used in WireGuard for encryption and authentication.
8 Enable Preshared key Yes/No This option indicates that a pre-shared key (PSK) is used in addition to the public-private key pair for an extra layer of security.
9 Preshared key ***** The actual pre-shared key value shared between the client and the server. This option appears only if you have enabled preshared key.

Save and update the page after configuration has been done.


Zerotier:

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

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

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

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

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


Click on the save button after the required configuration.

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

2.5 Firewall

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

There are 6 types of setting available under firewall.

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

General Settings:

General settings are subdivided into 2 parts,

1.) General settings

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

Specification details are below:

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


2.) Zone settings

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

Port Forwards:

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

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

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

EDIT:

Click on the save button after the required configuration.

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

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

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

Traffic Rule:

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

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

EDIT:

Specification details are below:

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

2.      Example: IPv4 if dealing with typical internet traffic.

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

Click on save once configured.

SNAT Traffic Rule:

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

To add new source NAT,

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

EDIT:

Specification details are below:

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

Click on save once configured.

Parental Control:

For configuring parental control rules, you want to set restrictions based on time, source, and destination zones, as well as specific devices.

To add parental control in firewall,

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

EDIT:

Specification details are given below:

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

Click on save once configured.


Zone Forwarding:

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

To ADD new zone,

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

*Refer the image below*

EDIT:

Specification details are below:

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

Click on save once configured.


2.6 Loopback Rule

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

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

EDIT:

Specification details are given below:

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

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

2.7 Remote Monitoring

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

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

NMS:

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

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

TR_069:

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

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


Specification details are given below:

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

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

2.8 Tunnel

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

It is further categorised into 3 sections,

1.) General Settings

2.) GRE Tunnel

3.) IPIP Tunnel


General Settings:

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


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

GRE Tunnel:

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

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


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


EDIT:


Specification details are given below:

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

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

IPIP Tunnel:

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

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

EDIT:

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


Specification details are given below:

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

3.Maintenance

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

It includes below submodules.

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

*Below is the detailed explanation of every field*

3.1 General/ System

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

It is further sub-divided into,

1.) General Settings

2.) Logging

3.) Language and Style


General Settings:

EDIT:

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

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

Logging:

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

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

EDIT:

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

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


Language and Style:

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

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

3.2 Password

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

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

3.3 Reboot

In this module the user can reboot the device remotely.

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

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


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

Need to select the type of reboot for the device whether it needs to be Hardware or Software reboot.


Specification details are given below:

SN Field Name Sample Value Description
1 Enable Maintenance Reboot Enable/Disable Indicates whether the maintenance reboot feature is enabled or not.
2 Type Maintenance Reboot Specifies the type of reboot being scheduled.
3 Reboot Type Software/Hardware Hardware: A hardware reboot involves restarting the entire device as if it were powered off and on again.

Software: A software reboot involves restarting the operating system without powering off the hardware.

4 Minutes Example: 59 The minute at which the reboot should occur (0-59).
5 Hours Example: 22 (10 PM) The hour at which the reboot should occur (0-23, in 24-hour format).
6 Day Of Month Example: All Specifies which days of the month the reboot should occur (1-31). "All" means it will occur every day.
7 Month Example: All Specifies which months the reboot should occur (1-12). "All" means it will occur every month.
8 Day Of Week Example: All Specifies which days of the week the reboot should occur (0-6, where 0 is Sunday). "All" means it will occur every day of the week.

Once the user fills all the required given parameters click on the save.

3.4 Import and Export

In this section, User can Import & Export Configuration files of the Device.

Click “Export Config” to export device configuration & settings to a text file,

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

The user needs to select on the “choose file”, upload the required file and click on apply.

3.5 Firmware Upgrade

The user can upgrade with the latest software for the existing firmware.

Click on the flash image and chose the path where the sys-upgrade file is kept and then click on flash image, it will upgrade to the latest software once the reboot is done.

This option will completely reset the device to default settings.

Click on the Retain Config and flash and chose the path where the sys-upgrade file is kept and then click on Retain Config and flash, it will upgrade to the latest software once the reboot is done.

This refers to updating the firmware (flashing) of a device while preserving the current configuration settings.

Click on the Factory Reset for the complete reset of the device.

3.6 Monitor Application

In this section, the monitor application is divided into major 2 configurations which is further sub-divided into 4 editable options,

1.) Modem Monitor Application Configuration:

2.) Router Monitor Application Configuration:

Modem Monitor Application Configuration:

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Ping Check Application Enable/Disable Turns on the functionality to perform ping checks on specified IP addresses.
2 Time Interval for Check (In minutes) Example: 10 minutes Frequency at which the ping checks are performed.
3 Select No of IP addresses to ping Example: 1 Number of IP addresses that will be pinged.
4 IP Address 1 Example: 8.8.8.8 The IP address to ping.
5 No. of Retries Example: 5 Number of times to retry pinging an IP address if the initial ping fails.
6 Failure Criteria in (%) Example: 80% (If 4 out of 5 pings fail, it’s considered a failure) Percentage of failed pings required to consider the ping check a failure.
7 Action On Failure Example: Restart Modem Action to be taken if the ping check fails according to the criteria.
8 Enable Second Level Action Enable/Disable Option to enable a secondary action if the primary action fails multiple times.
9 Second Level Action Threshold Example: 2 Number of failures required to trigger the secondary action.
10 Second Level Action Example: Restart Board (Reboots the entire hardware board) The action to be taken if the second level action threshold is met.

Save the details once made necessary changes.

Router Monitor Application Configuration:

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Ping Check Application Enable/Disable Activates the ping check functionality to monitor router performance.
2 Time Interval for Check (In minutes) Example: 10 minutes How frequently the ping checks are performed.
3 Select No of IP Addresses to Ping Example: 1 (Please select the appropriate number based on your requirements) Choose the number of IP addresses to ping. This typically involves selecting from a list or entering multiple addresses.
4 No. of Retries Example: 3 Number of retries if a ping fails.
5 Failure Criteria in (%) Example: 80% (If 80% of the pings fail, it’s deemed a failure) Percentage of failed pings required to consider the ping check as failed.
6 Action On Failure Example: Restart IPsec The action taken if the ping check fails according to the criteria.
7 Enable Second Level Action Enable/Disable Option to enable an additional action if the primary action fails.
8 Second Level Action Threshold Example: Specify the number of failures, such as 2 Number of times the primary action must fail before the secondary action is triggered.
9 Second Level Action Example: Restart Board The action to be taken if the second level action threshold is met.

Save the details once made necessary changes.

4.Status

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

It has 4 submodules.

  • Interfaces
  • Internet
  • Modem
  • Routes

4.1 Interfaces

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

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

4.2 Internet

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

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

4.3 Modem

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

4.4 Routes

This configuration shows how the router directs traffic between different networks and interfaces, ensuring proper communication within the local network and to external networks via the default gateway.

ARP Table: Maps IP addresses to MAC addresses for devices on the network, helping in identifying which device is on which interface.

IPv4 Routes: This shows which network is directly connected on which interface.

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

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

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

*Refer the below image*

5. Features

In this module the user can see all the features that the router has.

This module includes 9 features.

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

5.1 Mac Address Binding

MAC address binding is a configuration that binds a specific MAC address to a specific IP address.

This ensures that a particular device on the network always receives the same IP address from the DHCP

server, which can be useful for network management, security, and ensuring consistent network

behaviour.

Under this submodule the user can configure/update/edit the IP Address for MAC.

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

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Device Name mac1 A user-defined name for the binding configuration.
2 MAC Address 48:9e:bd:da:45:91 The unique identifier for the network interface of the device to which the IP address will be bound.
3 IP Address 192.168.10.55 The IP address that will be consistently assigned to the device with the specified MAC address.

By applying this configuration, the DHCP server will always assign the IP address 192.168.10.55 to the device with the MAC address 48:9e:bd:da:45:91, ensuring consistency and stability in network addressing for that device.

  • Once the user modifies the MAC address /IP Address then click on the save button to save the changes done.
  • The user can click on the deleted button to delete an existing configured device.

Post all the changes the user needs to click on the update to reflect all the changes in the application.

5.2 URL Filtering

In this submodule the user should provide the URL which needs to be blocked for the device.

By implementing URL filtering with the specified URL, you can control and restrict access to certain

websites, thereby improving network security and managing user access.

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

Once the user clicks on the Add New button a new pop will appear in that page write the URL and click

on the save.

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

To edit / delete the existing URL the user needs to click on the edit /deleted button respectively.

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

5.3 Web Server

This configuration will allow your device to serve web traffic securely over HTTPS, keep its system time synchronized, and ensure that all HTTP traffic is redirected to HTTPS for better security.

EDIT:

Specification details are given below:

SN Field Name Sample Value Description
1 Enable HTTP HTTP Port: 80

Enable or disable the HTTP server.

Port 80 is the default port for HTTP traffic. It is used to serve web pages over an unencrypted connection.
2 Enable HTTPS HTTPS Port: 443

Enable or disable the HTTPS server.

Port 443 is the default port for HTTPS traffic. It is used to serve web pages over an encrypted connection.
3 Redirect HTTPS Option to redirect HTTP traffic to HTTPS. When enabled, all HTTP requests will be automatically redirected to the HTTPS port to ensure secure communication.
4 Session Timeout (in millisecs) Ex: 60000 In this scenario the webpage will logout after 60secs of inactivity.
5 RFC1918 Filter Enable/Disable When enabled, this filter can block traffic from private IP ranges (e.g., 192.168.x.x, 10.x.x.x) from being routed through the public internet, enhancing network security.
6 Enable NTP Sync Enable or disable NTP synchronization. Synchronizes the device’s system clock with an external NTP server to maintain accurate time.
7 NTP Server 0.openwrt.pool.ntp.org The address of the NTP server used for time synchronization. The openwrt.pool.ntp.org server is a public NTP server pool.
8 NTP Sync Interval (In Minutes) 15 The interval at which the device will sync its clock with the NTP server, set to every 15 minutes in this case.

Click on save once changes are made.

5.4 Wi-Fi MacID Filtering

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

It is further divided into 2 categories,

WIFI 2.4G AP

WIFI 2.4G AP Guest

Before adding the MacIDs the user needs to select the mode from the dropdown menu.

In ‘Change Mode’ select one option,

Blacklist

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

Whitelist

In whitelist mode, you specify which MAC addresses are allowed to connect to the wireless network. Devices not on the whitelist will be blocked.

To Add the MacID the user needs to click on Add New option.

Specification details are given below:

SN Field Name Sample Value Description
1 Status Enable/Disable Enable or disable the MAC ID filtering.
2 MAC ID Example: e8:6f:38:1a:f2:61 The MAC address of the device to be whitelisted or blocklisted.
3 Network Name Example: WIFI 2.4G AP or Wi-Fi 2.4G AP Guest. The network to apply the MAC ID filtering.

Once the required MAC ID and Network Name is configured the user needs to click on the save button to add the details.

The user needs to click on the edit button to do modifications on the pre-existing configuration.

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

5.5 Routing

In this submodule the user can configure the parameters related to routing of the device like Target address, Networks address etc. Routing configurations allow network packets to be directed between different subnets and networks.

It is further divided into 2 sections,

Static IPV4 Routes

Advanced Static IPV4 Routes

Static IPV4 Routes:

Click on ‘Add’ to add a new interface.

EDIT:

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

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

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

Specification details are given below:

SN Field Name Sample Value Description
1 Interface Ex: eth0.1 The network interface to be used for this route. Select the one to use from dropdown.
2 Target Ex: 192.168.20.0 The destination subnet to which traffic should be routed.
3 IPv4 Netmask 255.255.255.0 The subnet mask for the target network.
4 Metric 0 The priority of the route.

Lower values indicate higher priority.

5 IPv4 Gateway Ex: 192.168.10.1 The gateway IP address to be used for routing traffic to the target subnet.
6 Route Type Unicast Standard route for individual destination IP addresses.

Custom changes can be made.

Click on save once configuration changes have been made.

Advanced Static IPV4 Routes:

This is further divided into 2 sections,

Routing Tables

Routing Rules for IPV4

Routing Tables:

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

Click on ‘Add’ to add a new Table.

EDIT:

Specification details are given below:

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

2.) Custom

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

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


Routing Rules for IPV4:

Click on ‘Add’ to add a new interface.

EDIT:

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

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

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

Specification details are given below:

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

2.) iif (Incoming Interface)

3.) oif (Outgoing Interface)

4.) lookup

5.) blackhole

6.) prohibited

7.) unreachable

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

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

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

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

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

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

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

5.6 Others

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

Specification details are given below:

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

To: End date (YYYY-MM-DD)

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

Year: Year (e.g., 2024)

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

5.7 Connection Diagnostics

This can ensure that your connection diagnostics application effectively monitors and reports the status of your network connections, providing valuable data for troubleshooting and performance optimization.

This Application works in 3 parts,

1.) General settings

2.) Connection status and management

3.) Application Start/Stop

General settings:

First make configuration changes in this section and save.

Specification details are given below:

SN Field Name Sample Value Description
1 Enable Connection Diagnostics Enable/Disable This option enables or disables the connection diagnostics functionality.
2 Check Interval (in seconds) Value: 120 Specifies how often (in seconds) the diagnostics checks are performed. In this case, every 120 seconds. (min 60 secs)
3 Number of Pings Value: 5 Determines ping requests sent during each check.
4 Ping Packet Size (in Bytes) Value: 56 Defines the size of each ping packet in bytes.
5 Send to remote MQTT Broker Enable/Disable This option enables the sending of diagnostic data to a remote MQTT broker.
6 Publish Data Format CSV / JSON Specifies the format in which the diagnostic data will be published to the MQTT broker. You can choose either CSV (Comma-Separated Values) or JSON (JavaScript Object Notation).
7 MQTT Broker url Value: broker.hivemq.com The URL of the MQTT broker where the diagnostic data will be sent.
8 TCP port Value: 1883 The TCP port used to connect to the MQTT broker. Port 1883 is the default port for MQTT.
9 Topic Value: 37A26230014/connectionDiagnostics The MQTT topic under which the diagnostic data will be published. This topic is used to categorize and identify the data.


Connection status and management:

To setup a connection,

Click on ‘Add new target’

Enter Target IP (Ex: 8.8.8.8)

Click ‘Add’

Target has been added successfully.

Application Start/Stop:

To check whether the target Ip is sending and receiving packets, you need to start the application to see the desired output.

As shown above, our target Ip is sending packets successfully.

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

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

5.8 Package Manager

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

The package manager interface you are looking at likely allows you to manage the software installed on your device, such as networking tools, firmware, or other applications relevant to your system.

This section has 3 sub-sections,

Installed APP

Available APP

Manual Upgrade

Installed APP:

When you select Installed APP, you will see all the software that is actively running or installed on the device.

This could include system utilities, network management tools, monitoring software, or any third-party apps that were previously installed.

Common Actions:

  • View Details: You can check each application's version, source, and installation date.
  • Uninstall: You can remove applications that are no longer needed.
  • Check for Updates: You can see if there are updates available for any installed application.


Available APP:

When you select Available APP, you will see a list of software that can be installed from the system's repositories or sources.

These applications are not yet installed but are ready for installation if needed.


Common Actions:

  • Install: You can install any of the available applications by selecting them.
  • View Details: You can review each application's description, version, and functionality before installing.
  • Search: You can search for specific apps by name or category.


Manual Upgrade:

In contrast to automatic updates, Manual Upgrade lets you take control over which packages or applications you want to upgrade and when.

This can be useful if you need to avoid upgrading certain apps due to compatibility or testing purposes, or if you want to perform updates at a specific time.

Common Actions:

  • Check for Updates: The system will check for available updates for installed apps.
  • Select Updates: You can select which packages to update manually.
  • Upgrade Now: You can start the upgrade process immediately for selected apps.

6.Logout

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

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