Because Multi-Portal allows several portal services to share a single IP address while binding to distinct, dynamically-assigned ports, the port bound to a given service can only be reliably retrieved through the Multi-Portal client utility rather than generic socket-listing tools. The Mobile Access Portal is served through the sslvpn topic of the Multi-Portal daemon, so the command that returns the actual port Multi-Portal assigned to it is mpclient getdata sslvpn; netstat cannot map the abstract Multi-Portal service name to the correct listening port because that association is tracked internally by the Multi-Portal daemon, not exposed through standard socket state.
Community Discussion