Skip to content

Improve ProActiveInet address detection mechanism #1310

@fviale

Description

@fviale

Currently ProActiveInet behaves like this:

  • If no proactive.net property is set, it will search for a public interface, then a private and finally a loopback
  • otherwise it will filter the whole list of inet adresses according to the proactive.net filters set, without preference.
  • additionnally all IPv6 are filtered by default.

It should rather:

  1. filter first the list of available ip adresses according to the proactive.net properties, then execute the standard preference algorithm
  2. don't discard IPv6 adresses but rather prefer IPv4, and only discard link-local ones
  3. only the proactive.hostname property would skip the algorithm and bind to a specific IP address

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions