similar to: [PATCH] ipconfig: do_pkt_recv() refix ret initialisation

This patch fixes a bug on systems with multiple connected network devices. As packet_peek uses all devices to receive data instead of a specific device. As the return value was never reset it was possible that packets from other devices were returned by packet_peek. That means that the ifindex did not match any ifindex of the specified devices the packet was never removed and packets for the

klibcs ipconfig tries to guess the nameserver if no nameserver is provided. This may happen due to misconfigured dhcp or the use of the ip= parameter. This patch removes the guessing from ipconfig as it is not possible for any other script to determine if the provided nameserver is valid or a guessed one. If the old behavior is really needed this could be easily implemented in an external script.

Enough small fixes have pilled up to make it worth a release: A Google patch adds sched_setaffinity, sched_getaffinity support. Openembedded uses kexec_load(). Gentoo folks add a Kbuild fix. ipconfig no longer wild guesses a nameserver when none is provided by the DHCP server. strndup() and unlinkat() saw fixes for various problems. codingstyle cleanup in kinit and tools. git repository:

Hi, it seems that ipconfig has a problem if multiple devices are up and connected to the same network. It seems that it uses the wrong socket/device index to compare it to incoming packet. To be more precise, the packet gets discarded in do_pkt_recv as the ifindex from state differs always from the incoming packet To reproduce create two tap devices: $ sudo tunctl -u uli -t tap0

When configuring multiple interfaces, the existing logic in ipconfig can fail if DHCP replies are received out of the expected order, or if one or more interfaces never receive replies. The current ipconfig logic uses a single packet socket to handle all incoming DHCP replies. If, for example, the host has two interfaces, A and B, and only B will be sent a DHCP reply, the order of events goes

The ipconfig code does not drop incoming packets that it can't handle. Since the packet socket sends ipconfig its own broadcast requests, ipconfig has the unfortunate behaviour of eating 100% of the CPU time when it does not receive an immediate response to its outgoing requests. This patch fixes the problem, by ensuring that packets are dropped if they are not handled. It also introduces a

Commit-ID: 31810c21e6e7ee7c0478e80cee35b0b7e51de826 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=31810c21e6e7ee7c0478e80cee35b0b7e51de826 Author: Jay Vosburgh <jay.vosburgh at canonical.com> AuthorDate: Fri, 3 Feb 2017 16:36:51 -0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 02:23:46 +0000 [klibc] ipconfig: handle

Thank you Maximilian, this was much easier! I still have problems with my email setup, I haven't found the time to migrate my mailbox from Windows yet. And gmail (webmail) doesn't allow many customizations, so I'm also uploading the patch to http://users.sch.gr/alkisg/temp/0001-Signed-off-by.patch I'm sending a patch regarding the discard_packet() function, please consider it for

DHCP options like domain-name or hostname are written to /tmp/net-$DEVICE.conf which is typically later used by other scripts to determine the network configuration. This is done by sourcing the /tmp/net-$DEVICE.conf file to get all defined variables. This patch escapes the DHCP options written to /tmp/net-$DEVICE.conf to prevent arbitrary code execution. Signed-off-by: Ulrich Dangel <uli at

Hey, I was scripting in klibc and wanted to make an action when the dhcp client failed at grabing an IP after the defined timeout. I found that klibc always exit 0 which isn't that convenient . I wrote a stupid patch that solve this issue. Cheers, Erwan From: Erwan Velu <erwan.velu at zodiacaerospace.com> Date: Tue, 24 Aug 2010 10:00:23 +0000 (+0200) Subject: Exiting -1 if ipconfig

Knocking a small item off Russell's feature list. This applies on top of my earlier bugfix+options patch. README | 15 ++++----------- main.c | 28 +++++++++++++++++++++++----- 2 files changed, 27 insertions(+), 16 deletions(-) diff -Nru a/ipconfig/README b/ipconfig/README --- a/ipconfig/README Tue Apr 29 13:03:14 2003 +++ b/ipconfig/README Tue Apr 29 13:03:14 2003 @@ -10,22 +10,15 @@

Hello, all: I am executing ipconfig under a terminal and find one thing: If I execute ipconfig the first time, it will get an ip address from dhcp server, If I execute ipconfig the second time (or more times), since my TP-LINK TL-R402M router will give an icmp(ping) packet before DHCPOFFER, the ipconfig will fail after it receive the packet and tries unpack teh packet in packet_recv() since we

hello, Preparing my first klibc maintainenace release. :) My plan is to have the patches cook in klibc-queue and once everythings is fine deploy them in the main klibc repo. Please test/review belows patches. I plan to release the current queue really soon for klibc 1.5.20 due to the urgent ipconfig fixes. For now you find my patch queue on:

A friend who plays Rift just told me the the notes for the latest game patch say that they have 'refixed' making the game work with WINE. I know there had been several posts about Rift the last few weeks so if anyone walked away from the game without getting it working it may be worth trying again.

On Sat, Jul 25, 2020 at 1:57 PM Ben Hutchings <ben at decadent.org.uk> wrote: > > On Sat, 2020-07-25 at 17:47 +0100, Ben Hutchings wrote: > > On Sun, 2020-03-29 at 04:38 -0700, Bill Wendling wrote: > > > - Renamed IMAGE_BASE to LD_IMAGE_BASE_OPT. > > > - Moved "-fcommon" to KLIBCREQFLAGS in scripts/Kbuild.klibc. > > > - Remove "dash"

On Sat, 2020-07-25 at 17:47 +0100, Ben Hutchings wrote: > On Sun, 2020-03-29 at 04:38 -0700, Bill Wendling wrote: > > - Renamed IMAGE_BASE to LD_IMAGE_BASE_OPT. > > - Moved "-fcommon" to KLIBCREQFLAGS in scripts/Kbuild.klibc. > > - Remove "dash" warning fixes which have been upstreamed. > > - Conditionalize the inclusion of compiler flags by using the

kinit.c contains the following lines before calling ipconfig_main: #ifdef INI_DEBUG args[a++] = (char *)"-n"; #endif In my attempts to debug the NFS mounting, this threw me off for a bit. (The -n parameter runs a "dry run" and does not actually configure the network). Thus, it seems it's actually impossible to debug NFS mounting with the stock, unpatched klibc. It

Hello hpa, please pull from my debian klibc tree to kernel.org for minor fixes, that piled up after kernel.org shutdown, inluding a build fix against current linux 3.1. git pull git://anonscm.debian.org/users/maks/klibc.git scripts/basic/fixdep.c | 27 +++++++++++++-------------- usr/include/limits.h | 2 ++ usr/include/sys/file.h | 9 +++++++++ usr/include/sys/types.h |

I am new to Ruby so I thought the best way to get into it would be to follow the ONLamp "Rolling with Ruby on Rails" intro. I followed the instructions to the letter and everything work just great, very impressive:-). A couple of days later when I went back to it I got the following message when trying to start the WEBrick server. U:\RoRProjects\cookbook>ruby script\server =>

1. Is it possible to add elements to a sortable after the sortable has become active? I guess just inserting new li elements into the list won''t be enough, is there a way to tell the sortable that it has a new element? 2. Can I change the containment settings of a sortable after it is active? I want to add sortables dynamically and want to enable moving sortables between this new