hi All,
Feb 19 23:49:48 workhorse dnsmasq-dhcp[6678]: DHCPINFORM(eth-clients)
10.0.1.233 70:54:d2:1b:18:59
Feb 19 23:49:48 workhorse dnsmasq-dhcp[6678]: DHCPACK(eth-clients)
10.0.1.233 70:54:d2:1b:18:59 vweiszfeiler-pc
Feb 19 23:49:51 workhorse dnsmasq-dhcp[6678]: DHCPINFORM(eth-clients)
10.0.1.2
On 19/02/14 14:15, Olaf Hering wrote:
On Tue, Feb 18, Olaf Hering wrote:
On Tue, Feb 18, Olaf Hering wrote:
How should the config look like to offer PXE to old and new VM types at
the same time?
At least the separation appears to work like that:
dhcp-match=x86PC, option:client-arch, 0
dhcp
On 19/02/14 07:46, Da Zhao Y Yu wrote:
I found the root cause about this issue.
I changed the host file, and wrapped the ipv6 address with "[]", as below:
fa:16:3e:25:f4:31,host-2001-2011-0-f104--3.openstacklocal,*[2001:2011:0:f104::3],
* then client can got the targeted IPv6 address.
Ah, ye
On Tue, Feb 18, Olaf Hering wrote:
> On Tue, Feb 18, Olaf Hering wrote:
>
> > How should the config look like to offer PXE to old and new VM types at
> > the same time?
>
> At least the separation appears to work like that:
>
> dhcp-match=x86PC, option:client-arch, 0
> dhcp-match=BC_EFI, option
I found the root cause about this issue.
I changed the host file, and wrapped the ipv6 address with "[]", as below:
fa:16:3e:25:f4:31,host-2001-2011-0-f104--3.openstacklocal,
[2001:2011:0:f104::3], then client can got the targeted IPv6 address.
My environment is use vsphere as host. In kvm env,
