Project

General

Profile

Bug #25421

Unattended flow does not allow mapped IPv4 addresses

Added by Arend Lapere 8 months ago. Updated 8 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Unattended installations
Target version:
-
Difficulty:
trivial
Triaged:
No
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

Because our end-system does not allow the use of tokens (because it can't process the "?" in the URL) we had to disable token based unattended installs altogether.
However, in our system we run in a dual stack environment. What appears to be happening, is that the REMOTE_ADDR is an IPv6 mapped to an IPv4 address; however, foremand does not seem to take into account these types of addresses and thys no host is found.

The fix will only parse these mapped or translated IPv6 addresses back to IPv4 addresses.

Associated revisions

Revision 013da0ae (diff)
Added by arend.lapere@gmail.com 8 months ago

Fixes #25421 - Allow mapped IPv4 in forwarded address list

History

#1 Updated by Arend Lapere 8 months ago

  • Assignee set to Arend Lapere
  • Category set to Unattended installations

#2 Updated by The Foreman Bot 8 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/6222 added

#3 Updated by Arend Lapere 8 months ago

  • Subject changed from Unattended flow without token does not accept mapped or translated IPv4 addresses to IPv6 to Unattended flow does not allow mapped IPv4 addresses

#4 Updated by Lukas Zapletal 8 months ago

  • Fixed in Releases 1.21.0 added

#5 Updated by Anonymous 8 months ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF