[Bug 1813541] Re: Shim uses wrong TFTP server IP in proxyDHCP mode
This is still unsolved. where is "upstream" to politely request this fixed? Even if shim is highly security sensitive it's TFTP requesting the wrong server in a proxyDHCP environment. thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813541 Title: Shim uses wrong TFTP server IP in proxyDHCP mode To manage notifications about this bug go to: https://bugs.launchpad.net/shim/+bug/1813541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] Re: DNS name resolution doesn't work on Artful
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1725680 Title: DNS name resolution doesn't work on Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1725680] Re: DNS name resolution doesn't work on Artful
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 23networking
if [ -f /root/etc/systemd/resolved.conf ]; then
resolv=/root/etc/systemd/resolved.conf
cat > $resolv <> $resolv
[ -n "$rc_server0" ] && [ "$rc_server0" != "0.0.0.0" ] && echo
"DNS=$rc_server0" >> $resolv
[ -n "$rc_server1" ] && [ "$rc_server1" != "0.0.0.0" ] && echo
"FallbackDNS=$rc_server1" >> $resolv
[ -n "$rc_server1" ] && [ "$rc_server1" = "0.0.0.0" ] && [
"$rc_server0" != "0.0.0.0" ] && echo "FallbackDNS=$rc_server0" >> $resolv
[ -n "$rc_domain" ] && echo "Domains=${rc_domain}" >> $resolv
echo "#LLMNR=yes" >> $resolv
echo "#MulticastDNS=yes" >> $resolv
echo "#DNSSEC=no" >> $resolv
echo "#Cache=yes" >> $resolv
echo "#DNSStubListener=udp" >> $resolv
fi
and now 17.10 live PXE boots correctly with a healthy DNS
Best,
Patrick
** Attachment added: "23networking"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+attachment/5021036/+files/23networking
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1725680
Title:
DNS name resolution doesn't work on Artful
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1725680/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
>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 because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
> * 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 nonsense. The fixed bug has nothing to do with multi-homed PCs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1331547 Probably someone here can take a look at it. thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331547] Re: No network when PXE booting Live Ubuntu with CIFS
just by watching the code it is obvious the export command is missing. the BUG remains; I do not see any "feature" here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331547 Title: No network when PXE booting Live Ubuntu with CIFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1331547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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. Best, Patrick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
--- 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; + /* yiaddr should always be set to 0 for the messages we're likely +* to send as a DHCP client: DHCPDISCOVER, DHCPREQUEST, DHCPDECLINE, +* DHCPINFORM, DHCPRELEASE +* cf. RFC2131 section 4.1.1, table 5. +*/ + bootp.yiaddr= INADDR_ANY; bootp.giaddr= INADDR_ANY; + bootp.flags = htons(0x800); bootp.secs = htons(time(NULL) - dev->open_time); memcpy(bootp.chaddr, dev->hwaddr, 16); Hallelujah; you got it done; Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
@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 but do not make waste my time testing something I know that goes against the corresponding RFCs. >I believe that you misunderstand how klibc on the whole works, You are guessing again... I just said "please do not flag this issue as solved by a patch that does not work". >this is why we shouldn't change yiaddr directly in dhcp_send you wrong again; by RFC2131 all the DHCP traffic generated by a DHCP client "must" have yiaddr = 0, then you can VERY WELL define yiaddr = 0 at dhcp_send() > I've re-read the spec, and it looks like klibc only ever does a discover and > request with the dhcp_send() method; so I'll rework the patch to make this > clear and correctly fix the issue. You just want to re-invent the wheel here; just add the missing line and give all of us a break; >This is the kind of package in which you really need to know what you're doing >when making changes. I do. do you? >dhcp_send_discover() was doing the right thing for yiaddr: it sets >dev->ip_addr = INADDR_ANY; >which value will get copied in yiaddr in dhcp_send(), "as it should", except >that's only good for dhcp_discover. >dhcp_send_request() also needs to keep >track of dev->ip_addr, and shouldn't overwrite it, >but still ought to send with yiaddr set to INADDR_ANY. So??? Are you trying to tell me that you finally understood what's going on here ??? Did you finally see the problem? well it only takes one line of code to force yiaddr to 0 and finish with this long story. Best, Patrick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
>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 netdev *dev)
{
dev->ip_addr = INADDR_ANY;
dev->ip_gateway = INADDR_ANY;
dprintf("-> dhcp discover ");
return dhcp_send(dev, dhcp_discover_iov);
}
> please check whether this actually fixes the issue.
I encourage you to stop the guesswork and fix this upon what RFC2131 says
(which is pretty clear on this regard, just see its page 36)
yiaddr must be 0 on packets sent by the client.
I encourage you not to tag this bug as "fix released"
Best,
Patrick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 padding[BOOTP_MIN_LEN - sizeof(struct bootp_hdr)];
int padding_len;
int i = 4;
int j;
memset(&bootp, 0, sizeof(struct bootp_hdr));
bootp.op= BOOTP_REQUEST;
bootp.htype = dev->hwtype;
bootp.hlen = dev->hwlen;
bootp.xid = dev->bootp.xid;
bootp.ciaddr= INADDR_ANY;
- bootp.yiaddr= dev->ip_addr; //<<< wrong >>>
+bootp.yiaddr = INADDR_ANY;// needed
+bootp.flags = htons(0x800); // needed
bootp.giaddr= INADDR_ANY;
bootp.secs = htons(time(NULL) - dev->open_time);
memcpy(bootp.chaddr, dev->hwaddr, 16);
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
It seems the fix is only partial ; >From RFC2131 (Dynamic Host Configuration Protocol) for a client we have: FieldDHCPDISCOVER DHCPREQUEST DHCPDECLINE, DHCPINFORM DHCPRELEASE - --- --- 'yiaddr'0 0 0 but the mentioned patch does not include - bootp.yiaddr= dev->ip_addr; + bootp.yiaddr= INADDR_ANY; The patch only adds the flags... Considering it is the client DHCP request the yiaddr should be 0 (INADDR_ANY) ***debian/patches/broadcast_dhcp_send.patch*** --- a/usr/kinit/ipconfig/dhcp_proto.c +++ b/usr/kinit/ipconfig/dhcp_proto.c @@ -203,6 +203,7 @@ static int dhcp_send(struct netdev *dev, bootp.ciaddr= INADDR_ANY; bootp.yiaddr= dev->ip_addr; bootp.giaddr= INADDR_ANY; + bootp.flags = htons(0x800); bootp.secs = htons(time(NULL) - dev->open_time); memcpy(bootp.chaddr, dev->hwaddr, 16); Best, Patrick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
no news from Ubuntu, your link seems broken... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 have been talking to Debian people (Daniel Baumann, )who have proved their
complete lack of understanding/interest; they just do not care about this bug.
Talking to them is wasting my time; hopefully Ubuntu will fix this soon.
NOTE:
Please consider ipconfig needs to know (command line parameter)
if your server is of type "bootp" or "dhcp", if this parameter is wrong
ipconfig gives up.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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 ignores the bad conformed ipconfig DHCP request but in the second case the NETGEAR DHCP refuses to provide the required DHCP parameters. 2) This bug has also been reported upstream https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633 Please guys do something with this; today this issue affects virtually all the Debian/Ubuntu distros and their derivatives. ** Bug watch added: Debian Bug tracker #756633 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756633 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
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= dev->ip_addr; //this line must be replaced by the
following two lines
...
}
new:
static int dhcp_send(struct netdev *dev, struct iovec *vec)
{
...
bootp.yiaddr= INADDR_ANY;
bootp.flags = htons(0x800);
...
}
This bug does not affect 100% of the DHCP servers as some of them are more
forgiving than others with client protocol mistakes;
for those needing a quick solution for PXE booting see/get Serva complementary
INITRD_N11.GZ which includes the already patched ipconfig
http://www.vercot.com/~serva/an/NonWindowsPXE3.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327412
Title:
Delay during PXE Boot, IP-Config gives up
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
** Package changed: initramfs-tools (Ubuntu) => klibc (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1327412] Re: Delay during PXE Boot, IP-Config gives up
Very weird bug; I have PXE booted over VMWare VM w/o problem but when PXE booting on real hardware I got the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1327412 Title: Delay during PXE Boot, IP-Config gives up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1327412/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331547] Re: No network when PXE booting Live Ubuntu with CIFS
** Summary changed: - No network when PXE booting with CIFS (Live) + No network when PXE booting Live Ubuntu with CIFS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331547 Title: No network when PXE booting Live Ubuntu with CIFS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1331547/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331547] [NEW] No network when PXE booting with CIFS (Live)
Public bug reported:
the initrd.lz\initrd\scripts\casper script has a bug
function
do_netmount() {
...
if [ "${NETBOOT}" != "nfs" ] && do_cifsmount ; then
rc=0
elif do_nfsmount ; then
NETBOOT="nfs"
export NETBOOT
rc=0
fi
...
should be changed to
...
if [ "${NETBOOT}" != "nfs" ] && do_cifsmount ; then
export NETBOOT ##<
rc=0
elif do_nfsmount ; then
NETBOOT="nfs"
export NETBOOT
rc=0
fi
...
If we use netboot=cifs the variable NETBOOT is not exported and that impacts
initrd.lz\initrd\scripts\casper-bottom\23networking
that ends up recreating with delay and errors /etc/network/interfaces.
Next when Ubuntu boots Internet/Networking is not available.
seen in
ubuntu-14.04-desktop-amd64.iso
ubuntu-14.04-desktop-i386.iso
** Affects: casper (Ubuntu)
Importance: Undecided
Status: New
** Package changed: dia (Ubuntu) => casper (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331547
Title:
No network when PXE booting with CIFS (Live)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1331547/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169581] Re: desktop LTS 12.04.2 broken cifs support on install
There's even a new annoyance; ubuntu-12.04.3-desktop-amd64.iso has a renamed kernel; the old \casper\vmlinuz is now called \casper\vmlinuz.efi forcing to edit all the working scripts and menus "only" for the 12.04.3 amd64 version... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169581 Title: desktop LTS 12.04.2 broken cifs support on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1169581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169581] Re: desktop LTS 12.04.2 broken cifs support on install
@mantas ubuntu-12.04.3-desktop-amd64.iso ubuntu-12.04.3-desktop-i386.iso des_generic.ko and md4.ko are still not included within initrd PXE/CIFS still broken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169581 Title: desktop LTS 12.04.2 broken cifs support on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1169581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169581] Re: desktop LTS 12.04/.2 broken cifs support on install
The bug is confirmed and it is displayed on install when CIFS services are needed; The install aborts. The solution has been tested and is included in the first post. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169581 Title: desktop LTS 12.04/.2 broken cifs support on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1169581] [NEW] desktop LTS 12.04/.2 broken cifs support on install
Public bug reported: desktop LTS 12.04/.2 broken cifs support on install While initrd.lz includes cifs.ko the modules des_generic.ko and md4.ko are missing. CIFS is very handy when PXE booting Ubuntu LTS Desktop live from Windows OSs as Serva does it here. http://vercot.com/~serva/an/NonWindowsPXE3.html The inclusion of des_generic.ko and md4.ko within initrd.lz would avoid the need of loading manually made complementary initrd files. I hope you guys can add these 2 files for 12.04.3 considering this is an LTS. Thanks ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169581 Title: desktop LTS 12.04/.2 broken cifs support on install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1169581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 44194] Re: wpasupplicant doesn't start when the network start
I agree 100% with Paul; I preffer a slower rate on new releases than this mess of unsolved bugs on LTS editions... how can we serioulsy consider an LTS edition if bugs are only solved on new releases forcing us to upgrade when what we really want is stability??? -- wpasupplicant doesn't start when the network start https://bugs.launchpad.net/bugs/44194 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 131134] Re: When attempting to install lamp-server, returns "aptitude failed (100)"
the above comment is not always true... 8.04 custom install defining new tasks for tasksel, tasksel works ok but when invoke "apt-get install" this one is unable to find the requested task for its installation... the tasks are perfectly defined on /usr/share/tasksel/ubuntu-tasks.desc but they never get to apt-get cache even after a apt-get update, a manual apt-get install xxx_task^ will also fail... question... when apt-get populates its cache; does ever read /usr/share/tasksel/ubuntu-tasks.desc ??? -- When attempting to install lamp-server, returns "aptitude failed (100)" https://bugs.launchpad.net/bugs/131134 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
the same thing here on 8.04 tryng to run a humble debconf script... the proposed solution didn't work , the file has no one locking it... I've reinstalled debconf & debconf-utils... so far no luck... -- debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable https://bugs.launchpad.net/bugs/349469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569503] Re: errors messages are not ended by \n
there you can se what I say... console on putty com1 final phase of booting ** Attachment added: "screen with the problem" http://launchpadlibrarian.net/49135618/screen.jpg -- errors messages are not ended by \n https://bugs.launchpad.net/bugs/569503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569503] Re: errors messages are not ended by \n
guau... nobody reads this? -- errors messages are not ended by \n https://bugs.launchpad.net/bugs/569503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569503] Re: errors messages are not ended by \n
more info, the problem appears when booting a 8.04.3 headless system, messages are routed to a serial console, When chown fails finding certaing files on /var it sends error messages to console with missing carriage returns. taking a look to the package source it seems al non-interactive utils use the error routines provided by error.c. this file uses "\n" when writing to stderr but for some reason the serial console requieres the \r also? -- errors messages are not ended by \n https://bugs.launchpad.net/bugs/569503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569503] Re: errors messages are not ended by \n
acually it seems the new line is there the one is missing is the carriage return... -- errors messages are not ended by \n https://bugs.launchpad.net/bugs/569503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569503] [NEW] errors messages are not ended by \n
Public bug reported: Binary package hint: coreutils When coreutils utilities report errors to console using error.c/error.h their error messages are not prepended with a new line character, then the console error report results scrambled... ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- errors messages are not ended by \n https://bugs.launchpad.net/bugs/569503 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 35839] Re: defoptions overwritten by update-grub
8.04.3 still has this problem... '# defoptions=' is NOT empty but update-grub prepends the line with 'quiet splash' -- defoptions overwritten by update-grub https://bugs.launchpad.net/bugs/35839 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
