Modify

Ticket #420 (closed defect: fixed)

Opened 15 years ago

Last modified 15 years ago

Problem with UUIDs and NAT in 0.9.3-pre3

Reported by: [email protected] Owned by: desai
Priority: major Milestone: Bcfg2 0.9.3 Release
Component: bcfg2-server Version:
Keywords: Cc:

Description

When multiple clients, each with a unique UUID, share a fixed NAT address, only one will successfully authenticate. For example, suppose clients.xml contains the following entries:

<Client profile="group1" pingable="N" pingtime="0" name="host1" uuid="uuid1" address="10.0.0.1"/>

<Client profile="group1" pingable="N" pingtime="0" name="host2" uuid="uuid2" address="10.0.0.1"/>

Client host2 will authenticate; host1 will not. For host1, the server reports

Got request for non-floating UUID uuid1 from 10.0.0.1

If the Client entry for host1 is changed to replace the 'address' attribute with the attribute location="floating", host1 will then authenticate, but the server reports that it generated the configuration for host2.

Attachments

Change History

comment:1 Changed 15 years ago by desai

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone set to Bcfg2 0.9.3 Release

There was a bad assumption in Metadata.py that each address would only be included once. I've fixed this in r3007, which will be included in 0.9.3pre4, to be released later today.

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.