IP Addresses - Revision history

Nic at 22:33, 28 January 2025

2025-01-28T22:33:44Z

← Older revision		Revision as of 17:33, 28 January 2025
Line 36:		Line 36:

	Note that, for non-administrators, this feature is only applicable for IP-based entries and is not available for Geo-based entries.		Note that, for non-administrators, this feature is only applicable for IP-based entries and is not available for Geo-based entries.

			It is also possible to allow a user specific IP address to apply to all users. See [[Allowing a user-specific IP address to apply to all users]].

Nic at 22:32, 28 January 2025

2025-01-28T22:32:34Z

← Older revision		Revision as of 17:32, 28 January 2025
Line 23:		Line 23:

	::: [[File:IPAddresses_GeoBased.png\|border\|400px]]		::: [[File:IPAddresses_GeoBased.png\|border\|400px]]

			: You can easily convert an IP-based entry to a Geo-based entry. See [[Converting an IP-based IP address to a Geo-based IP address]].

Nic at 04:07, 28 January 2025

2025-01-28T04:07:16Z

← Older revision		Revision as of 23:07, 27 January 2025
Line 19:		Line 19:
	::: [[File:IPAddresses_IPbased.png\|border\|400px]]		::: [[File:IPAddresses_IPbased.png\|border\|400px]]

	* '''~~GEO~~-based entries'''		* '''Geo-based entries'''
	: For those whose ISPs reassign their IP addresses frequently, OdataLink provides a ~~GEO~~-based mechanism. Using this mechanism, the ASN (or ISP) along with a specific geographical region (e.g. city, state or country) can be configured in the OdataLink Firewall. This is particularly useful for Countries whose internet infrastructure is more mobile.		: For those whose ISPs reassign their IP addresses frequently, OdataLink provides a Geo-based mechanism. Using this mechanism, the ASN (or ISP) along with a specific geographical region (e.g. city, state or country) can be configured in the OdataLink Firewall. This is particularly useful for Countries whose internet infrastructure is more mobile.

	::: [[File:IPAddresses_GeoBased.png\|border\|400px]]		::: [[File:IPAddresses_GeoBased.png\|border\|400px]]

Nic at 02:20, 28 January 2025

2025-01-28T02:20:37Z

← Older revision		Revision as of 21:20, 27 January 2025
Line 4:		Line 4:


	== Understanding the different mechanisms of IP ~~Adddresses~~ available in OdataLink ==		== Understanding the different mechanisms of IP addresses available in OdataLink ==

	OdataLink provides three different mechanisms of IP addresses to assist securing OdataLink.		OdataLink provides three different mechanisms of IP addresses to assist securing OdataLink.
Line 25:		Line 25:


	== Understanding how IP ~~Addresses~~ relate to users of OdataLink ==		== Understanding how IP addresses relate to users of OdataLink ==

	In addition to the mechanisms described above, IP addresses can either apply to all users of OdataLink or to a single user.		In addition to the mechanisms described above, IP addresses can either apply to all users of OdataLink or to a single user.

Nic at 02:11, 28 January 2025

2025-01-28T02:11:03Z

← Older revision		Revision as of 21:11, 27 January 2025
Line 38:		Line 38:
	== Understanding how IP addresses are associated with models ==		== Understanding how IP addresses are associated with models ==

	[[Models]] control all aspects of security within OdataLink. [[~~Add a new~~ IP ~~address~~\|Defining an IP address]] does not automatically make it active. It must also be [[Allowing / disallowing IP addresses access to a model\|associated with a model]].		[[Models]] control all aspects of security within OdataLink. [[Adding IP addresses\|Defining an IP address]] does not automatically make it active. It must also be [[Allowing / disallowing IP addresses access to a model\|associated with a model]].

Nic at 02:10, 28 January 2025

2025-01-28T02:10:42Z

← Older revision		Revision as of 21:10, 27 January 2025
Line 34:		Line 34:

	Note that, for non-administrators, this feature is only applicable for IP-based entries and is not available for Geo-based entries.		Note that, for non-administrators, this feature is only applicable for IP-based entries and is not available for Geo-based entries.


			== Understanding how IP addresses are associated with models ==

			[[Models]] control all aspects of security within OdataLink. [[Add a new IP address\|Defining an IP address]] does not automatically make it active. It must also be [[Allowing / disallowing IP addresses access to a model\|associated with a model]].

Nic at 00:37, 28 January 2025

2025-01-28T00:37:35Z

← Older revision		Revision as of 19:37, 27 January 2025
Line 32:		Line 32:

	IP addresses associated to a single user are particularly useful. Each time a user logs into OdataLink, OdataLink checks to see if their IP address is authorised. If it is not authorised, they will be prompted to update their associated IP address. This greatly simplify managing the Firewall for those that have dynamic IP addresses.		IP addresses associated to a single user are particularly useful. Each time a user logs into OdataLink, OdataLink checks to see if their IP address is authorised. If it is not authorised, they will be prompted to update their associated IP address. This greatly simplify managing the Firewall for those that have dynamic IP addresses.

			Note that, for non-administrators, this feature is only applicable for IP-based entries and is not available for Geo-based entries.

Nic at 00:29, 28 January 2025

2025-01-28T00:29:52Z

← Older revision		Revision as of 19:29, 27 January 2025
Line 1:		Line 1:
	IP addresses are used in the OdataLink Firewall to secure access to the [[OData Feed URLs]] and your data.		IP addresses are used in the OdataLink Firewall to secure access to the [[OData Feed URLs]] and your data.

			For more information on configuring IP addresses, see [[Configuring IP addresses\|configuring IP addresses]].


	== Understanding the different mechanisms of IP Adddresses available in OdataLink ==		== Understanding the different mechanisms of IP Adddresses available in OdataLink ==
Line 20:		Line 23:

	::: [[File:IPAddresses_GeoBased.png\|border\|400px]]		::: [[File:IPAddresses_GeoBased.png\|border\|400px]]


	== Understanding how IP Addresses relate to users of OdataLink ==		== Understanding how IP Addresses relate to users of OdataLink ==
Line 29:		Line 33:
	IP addresses associated to a single user are particularly useful. Each time a user logs into OdataLink, OdataLink checks to see if their IP address is authorised. If it is not authorised, they will be prompted to update their associated IP address. This greatly simplify managing the Firewall for those that have dynamic IP addresses.		IP addresses associated to a single user are particularly useful. Each time a user logs into OdataLink, OdataLink checks to see if their IP address is authorised. If it is not authorised, they will be prompted to update their associated IP address. This greatly simplify managing the Firewall for those that have dynamic IP addresses.

	~~For more information on configuring IP addresses, see [[Configuring IP addresses\|configuring IP addresses]].~~

	= Related Topics =		= Related Topics =

	[[Configuring IP addresses]] <br />		[[Configuring IP addresses]] <br />

Nic at 00:29, 28 January 2025

2025-01-28T00:29:06Z

← Older revision		Revision as of 19:29, 27 January 2025
Line 24:		Line 24:

	In addition to the mechanisms described above, IP addresses can either apply to all users of OdataLink or to a single user.		In addition to the mechanisms described above, IP addresses can either apply to all users of OdataLink or to a single user.

			::: [[File:IPAddresses_Users.png\|border\|400px]]

	IP addresses associated to a single user are particularly useful. Each time a user logs into OdataLink, OdataLink checks to see if their IP address is authorised. If it is not authorised, they will be prompted to update their associated IP address. This greatly simplify managing the Firewall for those that have dynamic IP addresses.		IP addresses associated to a single user are particularly useful. Each time a user logs into OdataLink, OdataLink checks to see if their IP address is authorised. If it is not authorised, they will be prompted to update their associated IP address. This greatly simplify managing the Firewall for those that have dynamic IP addresses.

Nic at 00:02, 28 January 2025

2025-01-28T00:02:37Z

← Older revision		Revision as of 19:02, 27 January 2025
Line 14:		Line 14:
	: IP-based entries are those that specify a single or a range of IP addresses. These can be IPv4 or IPv6 based. These IP addresses are static and are best used for offices whose IP addresses are fixed and not dynamic. They ensure that the queries will always work from specific locations.		: IP-based entries are those that specify a single or a range of IP addresses. These can be IPv4 or IPv6 based. These IP addresses are static and are best used for offices whose IP addresses are fixed and not dynamic. They ensure that the queries will always work from specific locations.

			::: [[File:IPAddresses_IPbased.png\|border\|400px]]

	* '''GEO-based entries'''		* '''GEO-based entries'''
	: For those whose ISPs reassign their IP addresses frequently, OdataLink provides a GEO-based mechanism. Using this mechanism, the ASN (or ISP) along with a specific geographical region (e.g. city, state or country) can be configured in the OdataLink Firewall. This is particularly useful for Countries whose internet infrastructure is more mobile.		: For those whose ISPs reassign their IP addresses frequently, OdataLink provides a GEO-based mechanism. Using this mechanism, the ASN (or ISP) along with a specific geographical region (e.g. city, state or country) can be configured in the OdataLink Firewall. This is particularly useful for Countries whose internet infrastructure is more mobile.

			::: [[File:IPAddresses_GeoBased.png\|border\|400px]]

	== Understanding how IP Addresses relate to users of OdataLink ==		== Understanding how IP Addresses relate to users of OdataLink ==