-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 21/05/15 08:59, Alkis Georgopoulos wrote:
> On 20/05/2015 10:21 μμ, Simon Kelley wrote:
>> Thanks for staying with this. I just checked in another patch. Is
>> that any better?
>
>
> That did the trick! It worked in all the cases that I tried.
On 20/05/2015 10:21 μμ, Simon Kelley wrote:
Thanks for staying with this. I just checked in another patch. Is that
any better?
That did the trick! It worked in all the cases that I tried.
Btw if there's any testing that I could do to help in implementing the
proxyDHCP support for UEFI client
Thanks for staying with this. I just checked in another patch. Is that
any better?
Cheers,
Simon.
On 20/05/15 05:24, Alkis Georgopoulos wrote:
> Whoops sorry I think that I misunderstood the difference of the two
> packets that I attached.
>
> In both the successful and the unsuccessful boots,
On 20/05/2015 01:04 πμ, Simon Kelley wrote:
I just pushed a patch into git
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=7f8565b94ca52dde31f7688a9f9a0cc611d9dae3
Please could you see if that helps? It should apply to the Ubuntu 14.04
version, if that's easier.
Hi Simon,
I te
Whoops sorry I think that I misunderstood the difference of the two
packets that I attached.
In both the successful and the unsuccessful boots, the transaction has
this exact message:
06:54:45.724145 3c:07:71:a2:02:e3 > c0:4a:00:02:bc:1e, ethertype IPv4
(0x0800), length 590: (tos 0x0, ttl 20
Hi Alkis,
I just pushed a patch into git
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=7f8565b94ca52dde31f7688a9f9a0cc611d9dae3
Please could you see if that helps? It should apply to the Ubuntu 14.04
version, if that's easier.
Cheers,
Simon.
On 16/05/15 10:19, Alkis Geor
OK, I managed to pinpoint the difference using another tcpdump command
line (-XX):
$ sudo tcpdump -i eth1 port 67 or port 68 or port 69 or port 4011 -e -n
-vv -XX
1) Without the normal dhcp-range, so that the client boots successfully:
11:51:23.036199 c0:4a:00:02:bc:1e > 3c:07:71:a2:02:e3, et
I just tried with git head, with the same results.
Another debugging hint... I tried commenting out the following line:
#dhcp-range=tag:efi,192.168.68.20,192.168.68.250,8h
Meaning that I only had the proxyDHCP range in effect:
dhcp-range=tag:!efi,10.161.254.0,proxy
The client of course booted
On 15/05/2015 11:13 μμ, Simon Kelley wrote:
Do you have dhcp-boot configuration. Do they have tags to select the
correct one depending on the efi tag you're using?
Hi Simon, here's my minimal.conf with which I can reproduce the problem:
enable-tftp
tftp-root=/var/lib/tftpboot/
dhcp-option=17,/
On 15/05/15 07:43, Alkis Georgopoulos wrote:
> Hi Simon, thanks for the patch,
>
> it's a bit better, the client reports the correct proxyDHCP, but then
> tries to fetch pxelinux.0 from the wrong TFTP server IP and fails.
>
> Some network dump info: *only* when I'm using iPXE for the client, in
>
Hi Simon, thanks for the patch,
it's a bit better, the client reports the correct proxyDHCP, but then
tries to fetch pxelinux.0 from the wrong TFTP server IP and fails.
Some network dump info: *only* when I'm using iPXE for the client, in
`dhcpdump -i eth1`, I see the wrong SIADDR:
On 14/05/15 06:34, Alkis Georgopoulos wrote:
> Since proxyDHCP mode doesn't yet work for UEFI clients, I'm using the
> following as a workaround:
>
> dhcp-range=tag:!efi,10.161.254.0,proxy
> dhcp-range=tag:efi,192.168.67.20,192.168.67.250,8h
>
> This is with a single NIC, dual IP server (10.161.2
Since proxyDHCP mode doesn't yet work for UEFI clients, I'm using the
following as a workaround:
dhcp-range=tag:!efi,10.161.254.0,proxy
dhcp-range=tag:efi,192.168.67.20,192.168.67.250,8h
This is with a single NIC, dual IP server (10.161.254.11, 192.168.67.1).
The 192.168.67.1 server IP is only
13 matches
Mail list logo
