History for "Differences Between Meraki & RADIUS Integration"

Meraki

• Uses a Captive Portal (this is the same technology used in Coffee Shops and Hotels but much cleaner and less intrusive)
• Ability to publicly post passwords to a network allowing users to access the network, but not the internet.
• User gets a splash page or captive portal on the device, which prompts them to register for new membership or log in to an existing one at a space.
• Proximity system checks to see if membership registered for grants internet access or not. If it does it leverages Meraki's API to provision device for life of user's membership. User will not see splash page again as long as user has paid membership. As soon as user's membership expires their device is reprovisioned and user is kicked off network.
• This also works for drop-in members. They will be presented with the Captive Portal at the beginning of each drop-in prompting them to use a punch. If they activate a punch prior to joining the network and have been at the space before they will not see the Captive Portal because their device will already be provisioned with internet access when the punch is activated.
• For conference room bookings Meraki automatically creates a new SSID for guests for the duration of the reservation. Once the reservation is over Meraki tears down network.

Radius

• Uses WEP Enterprise Encryption (802.1x)
• User selects network and enters username and password (same login credentials to log into Proximity site)
• User can't log into the WiFi network if they don't have a username or password set up within the Proximity Network and have an active membership at the space that grants them internet access.
• It's recommended to have a secondary network just for onboarding new members. (Meraki is great for this!)
• It's recommended to "throttle" this onboarding network and cycle password once a month. Throttling the traffic on this network encourages members to move over to the RADIUS network as soon as they have an active membership.
• In the "New Membership" email the space manager can add copy to ask new members to join the RADIUS network.
• For resource reservation bookings RADIUS creates temporary credentials for guests which are emailed to the owner of the reservation, displayed in the web app to the manager and on the interior Room View app. Guests log in using temporary username and password. These credentials are only good for the duration of the reservation.
• Once device has logged into network there's not a way to automatically kick that device off. However, the device will attempt to authenticate to the network after it sleeps, has left the space and in some cases when it moves between access points so this is usually not an issue.

Main Differences Between the Two

• RADIUS requires the user already have an active membership with access to the internet at the space. This is required because with an 802.1x authenticated network both a username and password are required, not just a shared password.
• RADIUS is a much more secure network because each user has a unique log in and all traffic is encrypted with the key from that user.
• The Meraki integration will work for both existing members and new users to the space. The shared password can be given to the new user and the Captive Portal will allow them to create a membership and then grant them access to the internet.

The ultimate setup is to use Meraki for onboards and drop-ins and RADIUS for full-time members.

Meraki

• Uses a Captive Portal (This is the same technology used in Coffee Shops and Hotels but much cleaner and less intrusive)(this is the same technology used in Coffee Shops and Hotels but much cleaner and less intrusive)
• Ability to publicly post passwordpasswords to a network allowing users to access the network, but not the internet.
• User gets a splash page or captive portal on the device, which prompts them to register for new membership or log in to an existing one at a space.
• Proximity system checks to see if membership registered for grants internet access or not. If it does it leverages Meraki's API to provision device for life of user's membership. User will not see splash page again as long as user has paid membership. As soon as user's membership expires their device is reprovisioned and user is kicked off network.
• This also works for drop-in members. They will be presented with the Captive Portal at the beginning of each drop-in prompting them to use a punch. If they activate a punch prior to joining the network and have been at the space before they will not see the Captive Portal because their device will already be provisioned with internet access when the punch is activated.
• For conference room bookings Meraki automatically creates a new SSID for guests for the duration of the reservation. Once the reservation is over Meraki tears down network.

Radius

• Uses WEP Enterprise Encryption (802.1x)
• User selects network and enters username and password (same login credentials to log into Proximity site)
• User can't log into wifithe WiFi network if they don't have a username or password set up within the Proximity Network and have an active membership at the space that grants them internet access.
• It's recommended to have a secondary network just for onboarding new members. (Meraki is great for this!)
• It's recommended to "throttle" this onboarding network and cycle password once a month. Throttling the traffic on this network encourages members to move over to the RADIUS network as soon as they have an active membership.
• In the "New Membership" email the space manager can add copy to ask new members to join the RADIUS network.
• For resource reservation bookings RADIUS creates temporary credentials for guests which are emailed to the owner of the reservation, displayed in the web app to the manager and on the interior Room View app. Guests log in using temporary username and password. These credentials are only good for the duration of the reservation.
• Once device has logged into network there's not a way to automatically kick that device off. However, the device will attempt to authenticate to the network after it sleeps, has left the space and in some cases when it moves between access points so this is usually not an issue.

Main Differences Between the Two

• RADIUS requires the user already have an active membership with access to the internet at the space. This is required because with an 802.1x authenticated network both a username and password are required, not just a shared password.
• RADIUS is a much more secure network because each user has a unique log in and all traffic is encrypted with the key from that user.
• The Meraki integration will work for both existing members and new users to the space. The shared password can be given to the new user and the Captive Portal will allow them to create a membership and then grant them access to the internet.

The ultimate setup is to use Meraki for onboards and drop-ins and RADIUS for full-time members.

Meraki

• Uses a Captive Portal (This is the same technology used in Coffee Shops and Hotels but much cleaner and less intrusive)
• Ability to publicly post password to network allowing users to access network, but not internet.
• User gets splash page or captive portal on device, which prompts them to register for new membership or log in to existing one at coworkinga space.
• Proximity system checks to see if membership registered for grants internet access or not. If it does it leverages Meraki's API to provision device for life of user's membership. User will not see splash page again as long as user has paid membership. As soon as user's membership expires their device is reprovisioned and user is kicked off network.
• This also works for drop-in members. They will be presented with the Captive Portal at the beginning of each drop-in prompting them to use a punch. If they activate a punch prior to joining the network and have been at the space before they will not see the Captive Portal because their device will already be provisioned with internet access when the punch is activated.
• For conference room bookings Meraki automatically creates a new SSID for guests for the duration of the reservation. Once the reservation is over Meraki tears down network.

Radius

• Uses WEP Enterprise Encryption (802.1x)
• User selects network and enters username and password (same login credentials to log into Proximity site)
• User can't log into wifi network if they don't have username or password set up within the Proximity Network and have an active membership at the space that grants them internet access.
• It's recommended to have secondary network just for onboarding new members. (Meraki is great for this!)
• It's recommended to "throttle" this onboarding network and cycle password once a month. Throttling the traffic on this network encourages members to move over to the RADIUS network as soon as they have an active membership.
• In the "New Membership" email the space manager can add copy to ask new members to join the RADIUS network.
• For resource reservation bookings RADIUS creates temporary credentials for guests which are emailed to the owner of the reservation, displayed in the web app to the manager and on the interior Room View app. Guests log in using temporary username and password. These credentials are only good for the duration of the reservation.
• Once device has logged into network there's not a way to automatically kick that device off. However, the device will attempt to authenticate to the network after it sleeps, has left the space and in some cases when it moves between access points so this is usually not an issue.

Main Differences Between the Two

• RADIUS requires the user already have an active membership with access to the internet at the space. This is required because with an 802.1x authenticated network both a username and password are required, not just a shared password.
• RADIUS is a much more secure network because each user has a unique log in and all traffic is encrypted with the key from that user.
• The Meraki integration will work for both existing members and new users to the space. The shared password can be given to the new user and the Captive Portal will allow them to create a membership and then grant them access to the internet.

The ultimate setup is to use Meraki for onboards and drop-ins and RADIUS for full-time members.

Meraki

• Uses captive portal
• Uses a Captive Portal (This is the same technology used in Coffee Shops and Hotels but much cleaner and less intrusive)
• Ability to publicly post password to network allowing users to access network, but not internet.
• User gets splash page or captive portal on device, which prompts them to register for new membership or log in to existing one at coworking space.
• Proximity system checks to see if membership registered for grants internet access or not. If it does it leverages Meraki's API to provision device for life of user's membership. User will not see splash page again as long as user has paid membership. As soon as user's membership expires their device is reprovisioned and user is kicked off network.
• This also works for drop-in members. They will be presented with the Captive Portal at the beginning of each drop-in prompting them to use a punch. If they activate a punch prior to joining the network and have been at the space before they will not see the Captive Portal because their device will already be provisioned with internet access when the punch is activated.
• For conference room bookings Meraki automatically generatescreates a new networkSSID for guests for the duration of meetingthe reservation. Once meetingthe reservation is over Meraki tears down network.

Radius

• Uses WEP Enterprise Encryption (802.1x)
• User selects network and enters username and password (same login credentials to log into Proximity site)
• User can't log into wifi network if they don't have username or password set up within the Proximity Network firstand have an active membership at the space that grants them internet access.
• It's recommended to have secondary network just for onboarding new members. (Meraki is great for this!)
• It's recommended to "throttle" it so it's only maybe 5 megabits and cycle password once a month.
• In 'New Membership' email in Proximity space manager can then ask new members to join other network.
• With conference room bookings Radius creates temporary credentials for guests. Guests log in using temporary username and password.
• Once device has logged into network there's not a way to automatically kick device off. User would have to disconnect from network themselves on computer or by physically leaving the space.
• It's recommended to "throttle" this onboarding network and cycle password once a month. Throttling the traffic on this network encourages members to move over to the RADIUS network as soon as they have an active membership.
• In the "New Membership" email the space manager can add copy to ask new members to join the RADIUS network.
• For resource reservation bookings RADIUS creates temporary credentials for guests which are emailed to the owner of the reservation, displayed in the web app to the manager and on the interior Room View app. Guests log in using temporary username and password. These credentials are only good for the duration of the reservation.
• Once device has logged into network there's not a way to automatically kick that device off. However, the device will attempt to authenticate to the network after it sleeps, has left the space and in some cases when it moves between access points so this is usually not an issue.

Main Differences Between the Two

• Meraki only requires a single SSID or network for members and non-members -- Radius has a single network for each.
• Meraki automatically kicks off members who no longer have an active membership -- with Radius the only way to kick someone off is if they disconnect from the network themselves on their computer or by physically leaving the space.
• RADIUS requires the user already have an active membership with access to the internet at the space. This is required because with an 802.1x authenticated network both a username and password are required, not just a shared password.
• RADIUS is a much more secure network because each user has a unique log in and all traffic is encrypted with the key from that user.
• The Meraki integration will work for both existing members and new users to the space. The shared password can be given to the new user and the Captive Portal will allow them to create a membership and then grant them access to the internet.

The ultimate setup is to use Meraki for onboards and drop-ins and RADIUS for full time members.

Meraki:

• Uses captive portal
• Ability to publicly post password to network allowing users to access network, but not internet.
• User gets splash page or captive portal on device, which prompts them to register for new membership or log in to existing one at coworking space.
• Proximity system checks to see if membership registered for grants internet access or not. If it does it leverages Meraki's API to provision device for life of user's membership. User will not see splash page again as long as user has paid membership. As soon as user's membership expires their device is reprovisioned and user is kicked off network.
• For conference room bookings Meraki automatically generates new network for guests for duration of meeting. Once meeting is over Meraki tears down network.

Radius:

• Uses WEP Enterprise Encryption
• User selects network and enters username and password (same login credentials to log into Proximity site)
• User can't log into wifi network if they don't have username or password set up within Proximity Network first.
• It's recommended to have secondary network just for onboarding new members.
• It's recommended to "throttle" it so it's only maybe 5 megabits and cycle password once a month.
• In 'New Membership' email in Proximity space manager can then ask new members to join other network.
• With conference room bookings Radius creates temporary credentials for guests. Guests log in using temporary username and password.
• Once device has logged into network there's not a way to automatically kick device off. User would have to disconnect from network themselves on computer or by physically leaving the space.

Main differences betweenDifferences Between the twoTwo:

• Meraki only requires a single SSID or network for members and non-members -- Radius has a single network for each.
• Meraki automatically kicks off members who no longer have an active membership -- with Radius the only way to kick someone off is if they disconnect from the network themselves on their computer or by physically leaving the space.