Activity
From 10/02/2011 to 10/31/2011
10/31/2011
- 09:35 PM Bug #1280: MS DHCP ignores address exclusions
- We can get the excluded ranges by using the following command:
netsh dhcp server 192.168.1.1 scope 192.168.1.0 sho... - 08:49 PM Bug #1280 (Resolved): MS DHCP ignores address exclusions
- I have the following set in my MS DHCP scope
Address range 192.168.1.1 - 192.168.1.254
Address Excluded Range: 19... - 09:32 PM Feature #1172: MS dhcp proxy does not know about leases
- The attached pictures shows the list of available options when using the following:
netsh dhcp server 192.168.1.1 s...
10/28/2011
- 12:32 AM Bug #1270: Deleting Host or Updating IP address Gives Error 400
- Johann Agnarsson wrote:
> You are correct, this was an isolated incident and was due to the machine having gotten an ...
10/27/2011
- 05:43 PM Bug #1270: Deleting Host or Updating IP address Gives Error 400
- You are correct, this was an isolated incident and was due to the machine having gotten an ip address from the DHCP s...
- 04:42 PM Bug #1270 (Feedback): Deleting Host or Updating IP address Gives Error 400
- I could not reproduce this, is this an isolated problem? happens on all entries?
the error message does say that the... - 04:35 PM Bug #1270 (Closed): Deleting Host or Updating IP address Gives Error 400
- When trying to delete a host or update the ip address from foreman the smart-proxy responds with an error 400.
Th...
10/26/2011
- 02:06 AM Bug #1260: autosign.conf doesn't support puppet enterprise
- I think the problem was that I had puppet and puppet enterprise installed and smart-proxy picked the puppet autosign....
- 12:38 AM Bug #1260 (Feedback): autosign.conf doesn't support puppet enterprise
- afair it does, you simply didnt select the puppet proxy in your host.
10/25/2011
- 10:46 PM Bug #1260 (Resolved): autosign.conf doesn't support puppet enterprise
- smart-proxy should be looking for /etc/puppetlabs/puppet/autosign.conf instead of /etc/puppet/autosign.conf...
10/13/2011
- 12:16 AM Feature #1224: DNSMadeEasy/Foreman/SmartProxy integration
- Here is some sample code https://github.com/bgupta/dnsmadeeasy
- 12:07 AM Feature #1224 (New): DNSMadeEasy/Foreman/SmartProxy integration
- Now that DNSmadeeasy has REST API, we should support it http://www.dnsmadeeasy.com/enterprise-dns/rest-api/
- 12:12 AM Feature #1225: AWS-Route53/Foreman/SmartProxy DNS integration
- Please switch to Feature not bug.
- 12:08 AM Feature #1225 (Resolved): AWS-Route53/Foreman/SmartProxy DNS integration
- Now that Amazon has a DNS service we should integrate. http://aws.amazon.com/documentation/route53/
10/12/2011
- 10:26 AM Bug #1221 (Resolved): Bug with server.next-server in DHCP
- Hey Ohad,
Ever since I upgraded to the latest git head I've been having an issue with the proxy putting in the wrong...
10/04/2011
- 09:13 AM Feature #1202: Read all subnet info from DHCP server (including name and DNS)
- Ranges and VLAN IDS should probably be read as well.
10/03/2011
- 04:50 AM Bug #1124 (Closed): dhcp smart proxy expcet nextserver, but return nextServer
- this was already resolved as part of commit:f2248accb5
10/02/2011
- 07:22 PM Feature #1202 (Resolved): Read all subnet info from DHCP server (including name and DNS)
- Because dhcp server configuration would probably be managed by a recipe, Foreman should read DNS info and name automa...
Also available in: Atom