We would like to submit an enhancement request related to the handling of geographic location profiles in HCL Notes when using IPSEC VPN connections.
Problem Description
In our environment, users are required to connect via an IPSEC VPN. When Notes is launched under this connection type, the following file is updated:
C:\Users\<username>\AppData\Local\HCL\Notes\Data\workspace\.metadata\.plugins\com.ibm.collaboration.realtime.location\locprofile-config.xml
The geographic location entry created in this file does not contain an IP address or a MAC address. Because no MAC address is recorded, the Notes client treats the connection as a new geographic location on every subsequent launch, repeatedly creating new location entries.
Technical Background
This behavior appears to be related to the nature of IPSEC VPN connections:
IPSEC operates at Layer 3 (L3) and does not create a virtual network interface.
As a result, there is no MAC address associated with the VPN connection.
The IP address is assigned from a VPN IP pool rather than via DHCP.
The Notes client does not appear to persist or use the assigned IP address in the location profile.
Due to the absence of a MAC address (and apparently the lack of a stored IP address), the client cannot reliably identify the connection as an existing geographic location.
Impact
Repeated creation of new geographic locations for the same VPN connection
Location profile clutter and inconsistent client behavior
Increased administrative and user overhead
Enhancement Requests
We would like to request one or more of the following enhancements:
Provide an option to disable the creation of geographic locations when no MAC address is available.
Allow geographic locations to be identified and reused based on a defined IP address range or VPN IP pool.
Persist and use the assigned IP address (even when not DHCP-based) as part of the location identification logic.
Provide configuration options or documentation that allow administrators to influence which connection parameters (e.g., IP, subnet, adapter type) are used to determine geographic location.
Clearly document how the Notes client currently distinguishes and assigns geographic locations, including which network parameters are evaluated.
This enhancement is addition to https://domino-ideas.hcltechsw.com/ideas/STC-I-657
Additional observation on HCL Notes 14.5 FP1 behavior:
I would like to clarify the current behavior, as it is slightly more specific than the initial description. In my environment (running Notes 14.5 FP1 over IPSEC-VPN), the client does not necessarily create a new location every time. Instead, the problem seems to be a failure in the automatic "handshake" or selection of the existing profile.
When connected via IPSEC-VPN, the following manual routine consistently works:
Double-click "Set custom geographic location" in the Sametime sidebar.
The Preferences > Sametime > Geographic Location window opens.
The correct VPN-related location profile is already highlighted/selected in the list.
I only need to click "Apply" and then "Apply and Close".
Once these clicks are performed, Sametime identifies the location correctly. This confirms that the location profile is stored properly and is compatible with the connection. The missing piece is simply the automation of this "confirmation" step. If the Notes client could automatically apply the pre-selected location on startup when a match is found (even without a MAC address), it would resolve the issue for IPSEC-VPN users.