Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#1046 closed defect (fixed)

Zeroconf/link-local/ActiveSync IPv4 adress 169.254.x.x may be used on Windows Mobile devices (thanks Jan Boquist for the info)

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-1.6
Component: pjlib Version: trunk
Keywords: Cc:
Backport to 1.x milestone: Backported:


Windows Mobile devices when hooked to ActiveSync uses IP address 169.254.2.x for the hostname and default route (implicitly this means that this address is also returned by IP interface enumeration function).

This would cause this address to be returned by PJLIB's pj_gethostip() even when there is another valid and better IP address returned by the interface enumeration function (for example, valid Wi-Fi address).

Change History (3)

comment:1 Changed 14 years ago by bennylp

  • Resolution set to fixed
  • Status changed from new to closed

In r3121:

  • add treatment for special IPv4/IPv6 addresses: loopback address and link-local address
  • with this treatment, link-local address will only be used if there is no other non-loopback/non-link-local IP addresses, and loopback address will only be used if there's absolutely no other IP address

comment:2 Changed 14 years ago by bennylp

In r3124:

  • fixed MSVC compilation warning

comment:3 Changed 14 years ago by bennylp

In r3133:

  • fixed the wrong priority which caused zeroconf address to end up having the same priority as a legitimate interface (thanks Karl-Fredrik Blixt Hagholm for the report)
Note: See TracTickets for help on using tickets.