ask us anything

In most cases this will be configured and determined automatically by the tenants’ router, but it can be manually set to 1492, or 1488 if the tenant is experiencing connection issues.  PPPoE requires 8 bytes of overhead for non-encrypted sessions, and an additional 4 bytes of overhead for an encrypted session, which must be subtracted from the standard ethernet maximum frame size of 1500 bytes. Since most consumer devices do not support encrypted PPPoE, an MTU of 1492 is the value that will be used in most cases, though you can always lower it some more for testing (but never below 1400, that can break certain protocols).

The licenses are per connection, with each tenant (regardless of number of individuals inside that tenant space) counting as one connection.

Many consumer routers have their PPPoE client settings set to “Dial on Demand” by default and will actually disconnect the router from the internet if no activity has occurred in set a period of time (Typically called “Idle Timeout”).  Changing the connection mode to “Always On” should keep the session active at all times (on some devices this is done by setting the “Idle Timeout” to ‘0’).

*No, the system is designed to manage entire connections to tenant spaces, not individual devices connected to the internet. If the tenant wants wireless the process is the same as with any other ISP, they simply need to purchase a wireless router.

*With the addition of Zero Touch routers the platform can be used to provide wireless access to tenants, but that is technically not the same as “Managed WiFi”

Wi-Fi settings can be configured on a Tenant account and their assigned Zero Touch Router will automatically configure itself with those settings. These settings can be configured from within the Tenant login of the portal as well as the regular admin section. Individual control of both 2.4 Ghz and 5 Ghz networks are supported.

Manual configuration of the Wi-Fi is possible directly within the Zero Touch configuration screens, but this setting is overridden anytime the Wi-Fi settings are configured on the Tenant account.

Additionally for accounts where the Wi-Fi is not configured on the tenant account, you can specify a default SSID prefix within the client settings. The router will generate a hardware specific SSID suffix that will be appended to the custom prefix in the format “Prefix-HWSuffix”

Here is an example of a 60 Second 20Mbps Burst policy with 10Mbps Sustained rate:

Average rate is calculated every 1/16 of specified burst time.

Absolutely, Simply specify a higher Bandwidth Priority in the bandwidth plan for the group that needs a higher priority of service, just don’t forget to reflect this in the plan name and how you price it to the tenant.

When a tenant at a higher Bandwidth Priority tries to utilize more bandwidth than is currently available (but within their Bandwidth Plan limits), the system will automatically throttle users of lower priority bandwidth plans as necessary to accommodate the needs of the higher priority tenant. At no time will the system throttle a tenant below the Guaranteed speed limits specified on their bandwidth plan, no matter how much bandwidth a higher priority tenant has requested.

Failover to a backup/standby WAN circuit is supported as long as the primary connection failure can be detected by a ARP lookup to the default gateway (roughly equal to ping the default gateway, if offline, then failover to the backup circuit), though it requires a custom config with a small one time setup charge, and has some limitations with regard to Public IP allocations.

Load balanced WAN setups, unless using BGP, are not supported due to the inherent problems of splitting connections across circuits with different subnets. BGP setups are a much more involved setup and quoted per setup, depending on what is required.

As long as you are provisioning tenants with public routable IPs, and presumably a Static IP, then that would be up to the tenant and what equipment they choose to connect, Assuming of course it is not blocked by your upstream ISP providing the connection to the property. Our system will not block, prohibit, or interfere with any type of VPN or server solution the tenant choses to implement.

The configuration within the IMS web portal is simply a checkbox to assign a Static IP, and the system will default to the next available and unassigned Static IP (assuming you programed the IP range of available Static IPs, if not you would enter the Static IP manually).

Yes, assuming the location was provisioned for public IP routing.

The configuration on the tenant account settings within the IMS web portal is simply a checkbox to assign a Static IP, and the system will default to the next available and unassigned Static IP (assuming you programed the IP range of available Static IPs, if not you would enter the Static IP manually).

We use the MAC address of the tenant router to determine it’s brand using a dataset derived from the IEEE MAC Address Block Large (MA-L) registry, formerly known as the OUI registry. The brand reported (for example “NETGEAR INC.,” vs “NETGEAR”) is always shown exactly as was filed with the IEEE, so the difference comes from the manufacturer themselves.

If a device is using a cloned or fake MAC address, or for any other reason fails to get matched to a manufacturer, it will display as an “Unknown” manufacturer.

A tenants usage is tracked for the duration of their session, and then all sessions that have been active in the last 30 days are totaled together to give the total upload and download value in the IMS portal. Therefore if a tenant’s session lasts longer than that 30 day window (for example if they maintain the same session for 90 days) then that session will continue to track their total usage since the start of their session, which is shown as the Last Login field.