[chef] RE: Force 'main' IP on multi-homed Chef nodes


Chronological Thread 
  • From: Kevin Keane Subscription < >
  • To: < >
  • Subject: [chef] RE: Force 'main' IP on multi-homed Chef nodes
  • Date: Thu, 7 May 2015 13:00:34 -0700

Title: RE: [chef] Force 'main' IP on multi-homed Chef nodes

Just to add to this: the same problem exists with IPv6 even on a single interface (at least it did last time I checked, which was a number of versions ago), especially with privacy extensions enabled.

To be fair, it is a hard problem to solve.

Kevin Keane

The NetTech

760-721-8339

http://www.4nettech.com

Our values: Privacy, Liberty, Justice

See https://www.4nettech.com/corp/the-nettech-values.html


-----Original message-----
From: Vauter, George < >
Sent: Wednesday 6th May 2015 17:27
To:
Subject: [chef] Force 'main' IP on multi-homed Chef nodes

Has anyone found a straightforward way to force Ohai to use a specific interface’s IP address as the “main” ip address for the Chef node?  All our server’s are multi-homed (have 2-3 interfaces).  Chef is currently picking the IP of an interface that should not be considered the main interface for the node.  From what I found so far, Ohai references the order of the routes to determine which interface IP to select…?

Thanks,
George


  • [chef] RE: Force 'main' IP on multi-homed Chef nodes, Kevin Keane Subscription, 05/07/2015

Archive powered by MHonArc 2.6.16.

§