This Networking article pertains to the 7202 Cortexa and previous models that have dual network ports. For networking information on new Cortexa hardware (with only one network port) please refer to the Cortexa Network Guide

General

The Cortexa is both a network device and a network controller at the same time. It can be used as a router or as a simple network device. The most common configuration, and the only one that retains its full features is to use it as the network's router. This is also the default configuration of the device as it is shipped from the factory or after a restore to default has been accomplished. Many of the features are dependent on one network interface or the other.

Network Interfaces

The Cortexa has two network interfaces. The WAN port is pre-configured for access to the internet. The LAN port is pre-configured for local network access.

• NOTE: If both interfaces of Cortexa are ever set to the same subnet (i.e. the third octet of the IP address), all network traffic will be blocked and it will be necessary to manually reset the network settings to the factory defaults as described Here

WAN Interface

By default, the WAN interface will obtain a IP from an available DHCP server. The web interface will be accessible from this IP. This interface is made to be plugged directly into a modem, or other direct data network. While the Cortexa is capable of controlling a modem, it is recommended to allow the modem to manage itself and set the Cortexa as the DMZ Host (De-Militarized Zone Host). This allows all network traffic to the external IP to come directly to the Cortexa, while maintaining the modem control, specifically the MTU (Maximum Transmission Unit) size function. This portion of the modem control is managed on the fly by most modems, but has to be manually specified in the Cortexa, thus causing issues with many websites.

• Note: by default, there is a check box checked in the "Wide Area Network" setup page called "Block Private Networks" that will disallow any computer with a 192.168 address from accessing the Cortexa via the WAN interface. This box must be unchecked to enable access to the system via the WAN interface.

Features that are dependent on the WAN interface

• Firmware update
• Weather from The Weather Channel
• Ping
• Dynamic DNS

LAN Interface

By default, the LAN interface will be statically set to an IP of 192.168.10.1. This interface is designed to be run to a switch and then have your internal network functioning with the Cortexa as the router. The IP can be set to anything you desire in the Local Area Network settings page.

Features that are dependent on the LAN interface

• Cortexa Media Player
• Global Cache
• Touchscreen messages (both text and video)

Router

To use the Cortexa as a router, either enter the configuration page and check the DHCP box or restore the factory defaults.

• The default network settings are WAN DHCP, LAN 192.168.10.1 and DHCP server on.
• All of the settings can be accessed from the configuration back end at http://<IP HERE>/advance then selecting setup and configuration.
• The system also offers a fairly comprehensive suite for port forwarding and traffic routing.

Network Management

This section of the back end offers basic networking controls.

General Settings

This page offers fields for basic configuration of the Cortexa. Often this page is the first page configured once a Cortexa is brought online.

The fields include:

Hostname

This is the equivalent of a computer name for Windows or Mac. The default is "cortexa".

Domain

This is the domain name appendage to the computer name to create a FQDN. It defaults to "cortexa.com".

DNS Servers

This is where you place your primary and backup DNS server IPs. There is also a check box to allow the DHCP server's DNS information to override these settings. This is recommended.

WWW port

Here you may change the port on which the Cortexa listens for http requests and presents it's interface. This is primarily useful for when you already have a web server running on your network or when the default port of 80 is blocked by your ISP.

Filtering Bridge

This check box will cause bridged packets to be treated the same way as routed packets are. If you enable this option, you'll have to add filter rules to selectively permit traffic from bridged interfaces.

IPv6 Tunneling

This causes all IPv6 traffic to forward to a specific address or subnet. A forward rule must still be created.

Wide Area Network

This section controls how the WAN interface works.

Type

This is the IP address type. Depending on the setting you select below, additional boxes will be highlighted or greyed out. Options are:

Static

Manually assigned address.

IP Address

The IP you are statically assigning.

Subnet Mask

The subnet mask the Cortexa will use.

Gateway

The gateway that all IP traffic from the Cortexa and all LAN devices will transit through.

DHCP

Address assigned by DHCP server.

DHCP Hostname

Hostname if required for your DHCP server.

PPPoE

Point-to-Point Protocol Over Ethernet. Commonly used for ADSL connections.

Username

The user name you will be using for your connection. Provided by your ISP.

Password

The password provided by your ISP for use with your username.

Service Name

The name of your ISP service if required.

Dial on Demand

A check box that will enable the dial on demand feature in which the connection will remain dormant until needed.

Idle Timeout

The amount of time in seconds to allow the connection to remain idle before disconnecting. Best used with the dial on demand feature above.

PPTP

Point-to-Point Tunneling Protocol. Commonly used for VPN connections.

Username

The username you will be using for your connection. Provided by your ISP or network admin.

Password

The password provided by your ISP or network admin for use with your username.

Local IP Adress

The local IP that will be used with the VPN connection.

Remote IP Address

The remote IP that will be used for the other end of the connection.

Dial on Demand

A check box that will enable the dial on demand feature in which the connection will remain dormant until needed.

Idle Timeout

The amount of time in seconds to allow the connection to remain idle before disconnecting. Best used with the dial on demand feature above.

BigPond

A ISP in England and Australia that requires special settings.

Username

The username you will be using for your connection. Provided by your ISP.

Password

The password provided by your ISP for use with your username.

Authentication Server

The server your ISP provides for authentication. Usually this is left blank for the default value of "dce-server".

Authentication Domain

The domain used with the authentication server above. If this field is left empty, the domain name assigned via DHCP will be used.

Note: the BigPond client implicitly sets the "Allow DNS server list to be overridden by DHCP/PPP on WAN" on the System: General Setup Page.

General Configuration

These settings apply to all forms of WAN connection.

MAC Address

This is the twelve digit MAC address you wish to use. Some connections require the MAC address to be set for use with their system. The address is entered in hexadecimal with a colon every third character, so it will look like this: A0:6F:E1:56:C8:01. This field will most commonly be left blank.

MTU

This is the Maximum Transmission Unit size control. This feature is only needed if you are using the Cortexa directly attached to a modem that is not also a router. The settings here are very difficult to set correctly. An incorrect setting causes some web pages to not load. The only way to find the correct setting for your modem and configuration is trial and error.

Block Private Networks

This check box prevents any computer from the WAN side of the Cortexa from accessing any feature or setup utility in the Cortexa if they have a private network IP. These include 192.168.X.X, 172.16.X.X, and the loopback address pool of 127.X.X.X. This is checked by default and is a very common mistake people make when trying to access their machine from the WAN side.

Local Area Network

This section controls the LAN side IP addressing.

IP Address

The IP assigned to the LAN interface.

Subnet Mask

The subnet mask assigned to the LAN interface.

Network Status

This page displays network configuration information and current status.

Note: The settings displayed above are from a specially configured demo unit and are not indicative of a standard or normal configuration. They are provided purely as a reference of what the page displays.

Network Traffic

This page displays a graph of network traffic. Adobe SVG viewer is required for this display.

Interface Assignments

This section allows you to swap the LAN and WAN ports. There is also a link to the VLAN setup page.

Ping Host

This page has a simple interface that allows you to send a ping to a device on the network.

Network Services

This section controls several aspects of the router features of the Cortexa.

DHCP Server

DHCP specific configuration is handled here.

Enable DHCP Server on LAN Interface

This check box will enable or disable the local DHCP server. This option is checked by default.

Deny Unknown Clients

If this box is checked, no client not specified on this page will be allowed to connect to the DHCP server.

Subnet

This is a display of the subnet that will be used. This cannot be edited here, and must be changed in the Local Area Network page.

Subnet Mask

This is a display of the subnet mask that will be used. This cannot be edited here, and must be changed in the Local Area Network page.

Available Range

This is a display of the available IPs for DHCP assignment. This cannot be directly edited.

Range

This section is where you can control the available IPs for the DHCP pool. Only IPs between the two range addresses will be given out.

WINS Servers

WINS servers may be entered here if used. This will normally be blank.

Default Lease Time

This is the amount of time in seconds that a DHCP address lease will be issued for. This will normally be left blank for a default of 7200 seconds.

Maximum Lease Time

This is where you can control the limit on how long a client that asks for a specific lease time can have. This will normally be left blank for a default of 86400 seconds.

MAC Addresses

Any devices in the DHCP pool will have their MAC addresses listed here.

DNS Override

Here you may allow the Cortexa to forward DNS queries onward or to ignore queries that cannot be resolved.

Dynamic DNS

This section will allow you to setup your Cortexa to dynamically update a URL with it's external IP address, allowing you to access your Cortexa from anywhere in the world with a simple browser. For detailed instructions on how to configure this feature, please see DynDNS (Cortexa).

Proxy ARP

This feature is very rarely used and should not be changed unless your are very comfortable with networking and have a valid backup of your system ready. It could be needed for some advanced network setups involving server and 1:1 forwards.

SNMP

Simple Network Management Protocol is a feature that will allow the Cortexa to report problems to a network administrator with the correct software running on their machine or server. This feature will almost never be used in home networks. The fields available are:

System Location

This is the physical location of the system to aid the administrator in finding the unit.

System Contact

This is who should be contacted with any system poblems.

Community

This is the community that the problem will be broadcast on to. The default of "public" will usually be good enough.

Firewall

The Cortexa has a built in hardware firewall. By default, all traffic is blocked with the exception of port 80 which is directed to the LAN side of the interface to allow access to the web interface from external to the network.

Port Forwarding

Ports may be forwarded individually or in groups and rules may be setup to direct the flow of traffic. The setup is somewhat counter-intuitive as many times both a forward and a rule are required to accomplish the desired outcome. This section is divided up into four tabs, each with it's own set of forwards.

Inbound

This is where inbound ports are forwarded to specific devices on the LAN.

There is one rule in this section by default. This rule is required for access to the Cortexa from the WAN side (i.e. the internet). It looks like this:

The following fields are available in a forward in this section:

Interface

This option controls which interface that the forward will look for packets on. There is only one option in the drop down box, making the concept of a drop down, somewhat superfluous.

• The options are:
  • WAN - The Wide Area Network interface.

External Address

This will allow you to assign IPs other than the interface address if you have already setup a server forward.

Protocol

This is the protocol that is being listened for.

• The options are:
  • TCP - Transmission Control Protocol. The internet standard protocol.
  • UDP - User Datagram Protocol. Another standard protocol, often used for instant messaging among other things.
  • TCP/UDP - This causes the rule to listen for both of the listed protocols.

External Port Range

This is where the port(s) to be forwarded range can be configured. Only packets sent to a port in this range will be forwarded. You may specify a single port by leaving the "To" field empty.

• From: - This is where the bottom side of the range is specified. A list of common ports is provided in the form of a drop down box.
  • (other) - This allows a port to be manually specified.
  • any - This setting basically disables this field and allows packets for any port to be considered.
  • FTP - Specifies port 21, the common File Transfer Protocol port.
  • SSH - Specifies port 22, the common port for Secure Shell.
  • Telnet - Specifies port 23, the common Telnet port.
  • SMTP - Specifies port 25 the Simple Mail Transmission Protocol port.
  • DNS - Specifies port 53, the common Domain Name Services port.
  • HTTP - Specifies port 80 the Hyper Text Transfer Protocol port.
  • POP3 - Specifies port 110, the common Post Office Protocol port.
  • IMAP - Specifies port 143, the default Internet Message Access Protocol port.
  • HTTPS - Specifies port 443 the Hyper Text transfer Protocol Secure port.
• To: This is where the top side of the range is specified. A list of common ports is provided in the form of a drop down box.
  • (other) - This allows a port to be manually specified.
  • any - This setting basically disables this field and allows packets for any port to be considered.
  • FTP - Specifies port 21, the common File Transfer Protocol port.
  • SSH - Specifies port 22, the common port for Secure Shell.
  • Telnet - Specifies port 23, the common Telnet port.
  • SMTP - Specifies port 25 the Simple Mail Transmission Protocol port.
  • DNS - Specifies port 53, the common Domain Name Services port.
  • HTTP - Specifies port 80 the Hyper Text Transfer Protocol port.
  • POP3 - Specifies port 110, the common Post Office Protocol port.
  • IMAP - Specifies port 143, the default Internet Message Access Protocol port.
  • HTTPS - Specifies port 443 the Hyper Text transfer Protocol Secure port.

Forward IP

This is where you enter the IP of the device that will be receiving the packets from the port(s) listed above. An alias may be used.

Local Port

This is where you may specify that the traffic coming in on the port above will be sent to the final destination on this port instead. This is useful for security reasons. for example you can allow traffic on port 8945 from the outside to go to port 80 on a local computer to be a web server. Also you can use this to allow multiple devices on your network to function on the same port. For example, say you have three IP cameras that all use port 80 for their interface. You can map external ports 8001, 8002, and 8003 each to a single camera on port 80. A common list of ports is provided in the form of a drop down box.

• (other) - This allows a port to be manually specified.
• any - This setting basically disables this field and allows packets for any port to be considered.
• FTP - Specifies port 21, the common File Transfer Protocol port.
• SSH - Specifies port 22, the common port for Secure Shell.
• Telnet - Specifies port 23, the common Telnet port.
• SMTP - Specifies port 25 the Simple Mail Transmission Protocol port.
• DNS - Specifies port 53, the common Domain Name Services port.
• HTTP - Specifies port 80 the Hyper Text Transfer Protocol port.
• POP3 - Specifies port 110, the common Post Office Protocol port.
• IMAP - Specifies port 143, the default Internet Message Access Protocol port.
• HTTPS - Specifies port 443 the Hyper Text transfer Protocol Secure port.

Description

This is where the descriptive text that identifies the forward is entered. This is the name of the forward in the main forwards display.

Server Forward

This is where you may specify alternate IPs for the interface addresses.

There are two fields available:

External IP Address

This is the location you wish to forward the packets to.

Description

This is where you may enter a name for the forward to be displayed on the server forward tab.

1:1

This section allows two or more subnets to be linked across the Cortexa. this feature should almost never be needed, as this style of networking is extremely rare in home or even small business networks. The options are as follows:

Interface

This option controls which interface that the forward will look for packets on. There is only one option in the drop down box, making the concept of a drop down, somewhat superfluous.

• The options are:
  • WAN - The Wide Area Network interface.

External Subnet

This is the subnet attached to the WAN side of the Cortexa that will be linked to the LAN side. A single IP can be linked by selected the /32 bit option in the subnet mask (this is the default).

Internal Subnet

This should be the subnet that your LAN is running on.

Description

This is the name of the rule as it will appear in the 1:1 forwards tab.

Outbound

This is where outbound ports are forwarded to either specific locations on the internet, or other devices on the LAN, possibly on different subnets. There is a check box to disable the automatic forward creation on the main page.

DO NOT check this box unless you are very comfortable with networking as you will cause your LAN to lose internet access. The options in the forwards are as follows:

Interface

This option controls which interface that the forward will look for packets on. There is only one option in the drop down box, making the concept of a drop down, somewhat superfluous.

• The options are:
  • WAN - The Wide Area Network interface.

Source

This is where you must specify which internal IP that this forward will be for. Subnet mask included.

Destination

This is where the destination of the forward is entered. There is a "not" check box to invert the rule and send to all matching anything other than this address. An IP must be entered here with a subnet.

Target

Packets that are handled by this forward will be sent to the IP listed in this field. If you leave this field black then the interface's IP will be used. An alias may be used as well.

Description

This is where the descriptive text that identifies the forward is entered. This is the name of the forward in the main forwards display.

Rules

Rules may be created to direct specific ports and protocols to specific devices on the network, or to the LAN interface of the Cortexa. There are two tabs, LAN and WAN.

LAN

This is where rules that apply to packets originating from the LAN side (typically your local computers) are stored.

• There is one rule in this section by default. This rule is required for LAN devices to access the internet. It looks like this:

WAN

This is where rules that apply to packets originating from the WAN side (typically the internet) are stored.

• There is one rule in this section by default. That rule is required for operation of the web interface via the WAN port. It looks like this:

Note that any change to the LAN IP address will require this rule to be changed as well if you still wish to have WAN Cortexa access.

Rules

This section explains in more detail the functions of each field in a rule. The available fields are:

Action

This controls what the rule will do with the packets that match the criteria that is extablished by the rest of the rule.

• The options are:
  • Pass - Allows the packets through and send them to the specified host.
  • Block - Stop the packets from getting to the specified host.
  • Reject - Inform the sender that there is no host at that address.

Disabled

This check box controls whether the rule is enabled or not.

• The options are:
  • Enabled - Allow this rule to run.
  • Disabled - Stop this rule from running. It will take no action.

Interface

This option controls which interface that the rule will look for packets on.

• The options are:
  • WAN - The Wide Area Network interface.
  • LAN - The Local Area Network interface.
  • PPTP - Point-to-Point Tunneling Protocol. This is the VPN interface.

Protocol

This is the protocol that is being listened for.

• The options are:
  • TCP - Transmission Control Protocol. The internet standard protocol.
  • UDP - User Datagram Protocol. Another standard protocol, often used for instant messaging among other things.
  • TCP/UDP - This causes the rule to listen for both of the listed protocols.
  • ICMP - Internet Control Message Protocol.
  • ESP - Encapsulating Security Payload.
  • AH - Authentication Header. The header on some requests and messages.
  • GRE - Generic Route Encapsulation. Another VPN protocol.
  • IPv6 - The new generation of IP addresses.
  • IGMP - Internet Group Management Protocol.
  • any - Listen for any of the above.

ICMP Type

If ICMP was selected for protocol, then the type may be specified in this block.

Note: I personally don't know enough about this protocol to explain this setting.

Source

This is where the source of the request may be specified. Only requests that come from this source will be considered for the rule.

• The options are:
  • Not - This is a check box that allows everything that does not match the below setting to be considered for the rule.
  • Type - This is where the type of host is specified. The options are:

• • • any - Self explanatory.
    • Single host or alias - allows you to order that only packets from a single specified source will be considered for the rule.
    • Network - Only packets from the local network will be considered.
    • LAN Subnet - Only packets from addresses in the same subnet as the LAN interface will be considered for the rule.
    • PPTP Clients - Only packets from VPN clients will e considered for the rule.
  • Address - If "single host or alias" was specified above, then enter the IP address here. Also a port may be specified. Note: you may also use the name of an Alias as described below.

Destination

This is where the destination of the packets is configured. Only packets bound for this destination will be considered for the rule.

• The options are:
  • Not - This is a check box that allows everything that does not match the below setting to be considered for the rule.
  • Type - This is where the type of host is specified. The options are:
    • any - Self explanatory.
    • Single host or alias - allows you to order that only packets from a single specified source will be considered for the rule.
    • Network - Only packets from the local network will be considered.
    • LAN Subnet - Only packets from addresses in the same subnet as the LAN interface will be considered for the rule.
    • PPTP Clients - Only packets from VPN clients will e considered for the rule.
  • Address - If "single host or alias" was specified above, then enter the IP address here. Also a port may be specified. Note: you may also use the name of an Alias as described below.

Destination Port Range

This is where the destinaton port range can be configured. Only packets sent to a port in this range will be considered for the rule.

• From: - This is where the bottom side of the range is specified. A list of common ports is provided in the form of a drop down box.
  • (other) - This allows a port to be manually specified.
  • any - This setting basically disables this field and allows packets for any port to be considered.
  • FTP - Specifies port 21, the common File Transfer Protocol port.
  • SSH - Specifies port 22, the common port for Secure Shell.
  • Telnet - Specifies port 23, the common Telnet port.
  • SMTP - Specifies port 25 the Simple Mail Transmission Protocol port.
  • DNS - Specifies port 53, the common Domain Name Services port.
  • HTTP - Specifies port 80 the Hyper Text Transfer Protocol port.
  • POP3 - Specifies port 110, the common Post Office Protocol port.
  • IMAP - Specifies port 143, the default Internet Message Access Protocol port.
  • HTTPS - Specifies port 443 the Hyper Text transfer Protocol Secure port.
• To: This is where the top side of the range is specified. A list of common ports is provided in the form of a drop down box.
  • (other) - This allows a port to be manually specified.
  • any - This setting basically disables this field and allows packets for any port to be considered.
  • FTP - Specifies port 21, the common File Transfer Protocol port.
  • SSH - Specifies port 22, the common port for Secure Shell.
  • Telnet - Specifies port 23, the common Telnet port.
  • SMTP - Specifies port 25 the Simple Mail Transmission Protocol port.
  • DNS - Specifies port 53, the common Domain Name Services port.
  • HTTP - Specifies port 80 the Hyper Text Transfer Protocol port.
  • POP3 - Specifies port 110, the common Post Office Protocol port.
  • IMAP - Specifies port 143, the default Internet Message Access Protocol port.
  • HTTPS - Specifies port 443 the Hyper Text transfer Protocol Secure port.

Fragments

This controls whether or not to allow fragmented packets to pass through with this rule. It is provided as a simple check box, unchecked is the default and will deny fragmented packets. Check the box to allow them through.

Log

This controls whether all the packets that are handled by this rule get logged. It is provided as a simple check box, unchecked is the default and will not log the packets. Check the box to log all packets this rule handles.

Description

This is where the descriptive text that identifies the rule is entered. This is the name of the rule in the main rules display.

Traffic Shaping

This is an advanced control that is not to be used without extensive networking knowledge. It allows among other things, bandwidth allocation based on IP address. The simplest method of use is to use the "Magic shaper wizard" and check the "Share bandwidth evenly on LAN" box.

Aliases

Aliases are names that can be used to take the place of IPs in many of the rules and forwards. This is useful if dynamic addressing is enabled to reduce the amount of things that need to be changed each time an address changes. Options are:

Name

The name you will call the alias with. Use something short and easy to remember.

Type

The type you will call. Options are:

• Host - A single computer.
• Network= - A specific network, including subnet.

Address

The IP of the computer or network being called. If network was selected, then the subnet block will be available as well.

Description

The name you will use to remember it with. This can be anything and I would encourage you to be descriptive.

Static Route

This feature allows requests over specific network interfaces to be routed to a given subnet. Options include:

Interface

Controls what interface the route will be in place for.

• Options are:
  • LAN - Local Area Network. Any computer that is in the same subnet as the Cortexa.
  • PPTP - Point-to-Point Transfer Protocol. A VPN connection.

Destination Network

This is the IP segment of the destination for the route. There is also a drop down where you may select the bit count of the destination network's subnet mask.

Gateway

This is the gateway that will be used to reach the destination network.

Description

This is where you may enter a description for the route. This is not used anywhere but the main route display page.

Factory Default

The factory default option does not as it implies completely reset the device to how it came from the factory. Instead it only overwrites the network settings.

• The default network settings are WAN DHCP, LAN 192.168.10.1 and DHCP server on.

For instructions on how to perform a factory default, please see Reset (Cortexa).

Typical Configurations

The following are some of the typical network configurations used with the Cortexa.

The Cortexa as the router in a network

This is how the Cortexa needs to be installed to take advantage of all the Cortexa Features.

The Cortexa with an existing router in a network

You can actually reuse your old and existing router. With this configuration, you will not use the WAN port on the old router. Plug the Cortexa LAN port into a LAN port on your old router. You will need to configure you’re old router to disable DHCP allowing the Cortexa to be the DHCP server. If you have any of the Cortexa access points, you will need to connect them just after the Cortexa and before your router, because the Cortexa sends out broadcast messages so that the access points can update instantly instead of having to poll the Cortexa for data.

• Features Lost:
  • I-Tunes: Since I-Tunes rely on local broadcast message, the messages will be blocked by the router.
  • Broadcast Message: The Cortexa sends Broadcast messages to other Cortexa products like In-Wall touch screen, PC View, etc... To send instant messages like weather warning and text messages.
  • UPNP: Other machines on the network will not be aware of the Cortexa to gain access to its features.

The Cortexa placed after an existing router

This configuration shows you how to connect the Cortexa behind an existing router. With this configuration you will loose some features. To gain access to the Cortexa from the web, you will need to add a port forward to the Cortexa web server, which its default port number is 80. You may also need to setup the Cortexa on a static IP address.

• Features Lost:
  • Dynamic DNS: Since the Cortexa will be getting its IP address from a router and not the Cable/DSL modem, it will not be able to report the correct IP address to your Dynamic DNS service.
  • VPN: Most VPN rely on a range of random ports to help keep the security. You may use forward all ports on the head router to the Cortexa to allow VPN to work again.
  • Extra Security: The Cortexa provides for extra security that most routers do not provide like blocking private networks, and ping denial.

The Cortexa as a normal LAN device

This configuration shows how to add the Cortexa to your existing LAN as another device. You will need to connect the Cortexa WAN port into your existing LAN. The Cortexa relies on the WAN being connected so that it can gain data from the internet like adjusting the Clock, and gaining local weather data.

Note: If you connect the Cortexa LAN port to your LAN, the Cortexa will loose its clock settings.

• Features Lost:
  • Dynamic DNS: Since the Cortexa will be getting its IP address from a router and not the Cable/DSL modem, it will not be able to report the correct IP address to your Dynamic DNS service.
  • VPN: Most VPN rely on a range of random ports to help keep the security. You may use forward all ports on the head router to the Cortexa to allow VPN to work again.
  • Extra Security: The Cortexa provides for extra security that most routers do not provide like blocking private networks, and ping denial.
  • UPNP: For security reasons the Cortexa UPNP client only binds to the Cortexa LAN. You can added a computer to the LAN side of the Cortexa with UPNP on it to make this work
  • Broadcast Message: The Cortexa sends Broadcast messages to other Cortexa products like In-Wall touch screen, PC View, etc... To send instant messages like weather warning and text messages.