On 12/02/13 23:48, Sheng Yang wrote:
Hi,
I've set up following dhcphost.txt for dual stack support using dnsmasq:
id:00:03:00:01:06:a4:ea:00:00:2c,[fc00:3:1610::ff14:2],test-2,infinite
06:a4:ea:00:00:2c,set:10_223_161_42,10.223.161.42,test-2,infinite
Though dnsmasq works fine, it
We use dnsmasq in CloudStack [1] to serve dhcp requests to VM instances in a
cloud environment.
In a cloud environment, VMs come and go frequently so there dnsmasq gets
reconfigured quite often.
Specifically we update the files pointed to by dhcp-hostsfile and dhcp-optsfile
using automation
On 12/02/13 23:48, Sheng Yang wrote:
Hi,
I've set up following dhcphost.txt for dual stack support using dnsmasq:
id:00:03:00:01:06:a4:ea:00:00:2c,[fc00:3:1610::ff14:2],test-2,infinite
06:a4:ea:00:00:2c,set:10_223_161_42,10.223.161.42,test-2,infinite
Though dnsmasq works fine, it complains
Yes.
in /etc/hosts
10.223.161.44 vm1
fc00:3:1610::ff14:3 vm1
Is that allowed?
--Sheng
On Wed, Feb 13, 2013 at 1:07 PM, Simon Kelley si...@thekelleys.org.uk wrote:
On 12/02/13 23:48, Sheng Yang wrote:
Hi,
I've set up following dhcphost.txt for dual stack support using dnsmasq:
On 12/02/13 22:42, Sheng Yang wrote:
No, it still doesn't work.
I am using Debian package, version 2.62.
Would it be possible to try 2.65 instead? A lot of fixes have gone into
the DHCPv6 code since 2.62. 2.65 is in unstable, or the stuff required
to build a Debian package is in the dnsmasq
On 13/02/13 21:43, Sheng Yang wrote:
Yes.
in /etc/hosts
10.223.161.44 vm1
fc00:3:1610::ff14:3 vm1
Is that allowed?
The above should be fine: I'm concerned that if you had, for instance,
fc00:3:1610::ff14:2 test-2
then dnsmasq would add the fc00:3:1610::ff14:2 address to the
dhcphost.txt
BTW, I showed /etc/hosts from a different setup, but same issue.
On Wed, Feb 13, 2013 at 1:43 PM, Sheng Yang sh...@yasker.org wrote:
Yes.
in /etc/hosts
10.223.161.44 vm1
fc00:3:1610::ff14:3 vm1
Is that allowed?
--Sheng
On Wed, Feb 13, 2013 at 1:07 PM, Simon Kelley
not be the real problem. In this case the
logrotate causes dnsmasq to not write to the new dnsmasq.log file. It writes to
the old file (dnsmasq.log-20130213). The logs indicate that SIGHUP indeed is
processed.
There is a bug in our logrotate config
postrotate
[ ! -f /var/run/dnsmasq.pid ] || kill
Same result with 2.65... I just compiled it and tried.
--Sheng
On Wed, Feb 13, 2013 at 1:42 PM, Simon Kelley si...@thekelleys.org.uk wrote:
On 12/02/13 22:42, Sheng Yang wrote:
No, it still doesn't work.
I am using Debian package, version 2.62.
Would it be possible to try 2.65 instead? A
On Wed, Feb 13, 2013 at 1:52 PM, Simon Kelley si...@thekelleys.org.uk wrote:
On 13/02/13 21:43, Sheng Yang wrote:
Yes.
in /etc/hosts
10.223.161.44 vm1
fc00:3:1610::ff14:3 vm1
Is that allowed?
The above should be fine: I'm concerned that if you had, for instance,
fc00:3:1610::ff14:2
10 matches
Mail list logo