It seems Casper does not update /etc/systemd/resolved.conf
then I do not really know how you get this working if booting
from an untouched live 17.10 Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
I'm PXE booting 17.10 live with Serva.
I also found that the booting image DNS is broken.
I traced the problem to Casper within the booting initrd.lz, the file
/script/casper-bottom/23networking
does not populate
/etc/systemd/resolved.conf
therefore the DNS daemon does not work.
I've added to
I stand corrected;
there's a typo on my patch the correct line should look like:
+ bootp.flags = htons(0x8000);
as mentioned by jvosburgh
Unfortunately this mistake was not previously detected because
all the net gear I've used on tests and Wireshark completely
ignored it.
Best,
Patrick
--
you know what
fixing 2 + 2 = 5
with 2 + 2 = 4
does not really need to be "confirmed" in every single Ubuntu flavor.
if I were you I would not remove anything because that would only add confusion.
Best,
Patrick
--
You received this bug notification because you are a member of Ubuntu
Touch
>This has broken DHCP in our environment.
>I suspect it has something to do with dhcp relaying.
If your DHCP relay is broken after this change that means your DHCP
relay needs the client's IP on the yiaddr field and that means you have
a broken DHCP relay.
--
You received this bug notification
> * debian/patches/broadcast_dhcp_send.patch: set the broadcast
> bit and yiaddr to 0 (INADDR_ANY) when sending DHCPDISCOVER/
> DHCPREQUEST, as per RFC 2131; section 4.1.
This is OK
>This helps when there is more than one interface
>trying to do DHCP at the same time.
This is complete
here you have also an old bug (2 years) affecting PXE scenarios when
using CIFS. It was never fixed even when the solution is right there.
seen in:
ubuntu-14.04-desktop-amd64.iso
ubuntu-14.04-desktop-i386.iso
ubuntu-16.04-desktop-amd64.iso
ubuntu-16.04-desktop-i386.iso
I have sent the patch to Debian long ago,
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633
I found Daniel Baumann there who systematically refused to do anything
on this matter answering very funny things.
I have also sent the patch to the klibc list but it was completely
ignored.
--- a/usr/kinit/ipconfig/dhcp_proto.c
+++ b/usr/kinit/ipconfig/dhcp_proto.c
@@ -201,8 +201,14 @@ static int dhcp_send(struct netdev *dev,
bootp.hlen = dev->hwlen;
bootp.xid = dev->bootp.xid;
bootp.ciaddr= INADDR_ANY;
- bootp.yiaddr= dev->ip_addr;
+
@Mathieu Trudel-Lapierre
> please check whether this actually fixes the issue.
> this is no guesswork.
Yes it is; I'm saying here for almost 2 years what it has to be done to fix
this problem and you recommend to see if a partial fix solves the problem or
not. well...
>Bits can be missed.
Sure
>yiaddr is set elsewhere in the code already (in dhcp_send_discover()
If that is the case it is also wrong;
I wonder what IP are they using in a DHCP DISCOVERY??
that makes absolute not sense for a booting client trying to get an IP.
anyway it seems you are wrong:
int dhcp_send_discover(struct
Patch sent upstream
But I think that list is not really active
http://www.zytor.com/pipermail/klibc/2016-March/003923.html
Best,
Patrick
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
It seems the fix is only partial ;
>From RFC2131 (Dynamic Host Configuration Protocol) for a client we have:
FieldDHCPDISCOVER DHCPREQUEST DHCPDECLINE,
DHCPINFORM DHCPRELEASE
-
I just recompiled ipconfig "once" and I got it working
I can confirm that /klibc-2.0.4/usr/kinit/ipconfig/dhcp_proto.c
did not fix this bug yet
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
struct bootp_hdr bootp;
char dhcp_hostname[SYS_NMLN+2];
uint8_t
This is an old bug never fixed by Ubuntu, never fixed by Debian either...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633
You have to recompile ipconfig with the patch I wrote above and everything
works OK.
Hopefully some day Ubuntu and/or Debian will fix this ;-)
--
You received
PXE booting w/o the ipconfig issue
; ubuntu-15.10-desktop-amd64.iso
; ubuntu-15.10-desktop-i386.iso
; ubuntukylin-15.10-desktop-amd64.iso
; ubuntukylin-15.10-desktop-i386.iso
requires INITRD_N11.1.GZ
source:
http://www.vercot.com/~serva/an/NonWindowsPXE3.html
--
You received this bug
no news from Ubuntu, your link seems broken...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
Status in klibc
This is the patch that fix this issue...
I have been using this patch for almost a year and works perfectly
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
...
- bootp.yiaddr = dev-ip_addr;
+bootp.yiaddr = INADDR_ANY;
+bootp.flags = htons(0x800);
...
}
I
Additional info
1)
When PXE installing on a VMware Workstation using the VMware DHCP server plus
Serva as proxyDHCP the bug is not present.
When PXE installing on a real PC with a Netgear ISP router as DHCP plus Serva
as proxyDHCP the bug is present.
In the first case the VMware DHCP module
I think I have found/solved this bug;
The problem is located at ipconfig (klibc-utils) not implementing the DHCP
standard as it should at the file
/klibc-2.0.3/usr/kinit/ipconfig/dhcp_proto.c
old:
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
...
bootp.yiaddr=
20 matches
Mail list logo
