similar to: the return value of packet_peek()

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

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

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

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

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

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

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, 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:

fix: usr/kinit/ipconfig/main.c: In function ?ipconfig_main?: usr/kinit/ipconfig/main.c:350:7: warning: ?ret? may be used uninitialized in this function [-Wuninitialized] usr/kinit/ipconfig/main.c:346:6: note: ?ret? was declared here I think the initialisation change in 6df362216a2e5beb4f29feafeabc630034a76914 was unintentional. Cc: Ulrich Dangel <uli at spamt.net> Signed-off-by:

The following patches come from Debian and/or Ubuntu packages of klibc. Ben. Ben Hutchings (1): [klibc] run-init: Add dry-run mode Jay Vosburgh (1): [klibc] ipconfig: Use separate sockets for DHCP from multiple interfaces Mathieu Trudel-Lapierre (1): [klibc] ipconfig: Set broadcast when sending DHCPREQUEST and DHCPDISCOVER YunQiang Su (1): [klibc] mips: setjmp.S: don't

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 |

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

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:

Various coding style fixes checkpatch warns about. The goal is not to be 100% checkpatch compliant, but to have more consistent coding style. As this is a trivial patch serie, will land in 24 hours in klibc git, unless of course ml review hits a bugger. Checked with size(3) that the generated kinit, fstype, ipconfig and nfsmount are the same. maximilian attems (4): [klibc] ipconfig: reduce

Hi! Some time ago I faced a problem in limiting traffic on host with multiple uplinks. Since all the stuff worked nice seemed that there will be no problems. But then I realized that P2P users are smart enough to bypass limits as sfq doesn''t give fair sharing in this case (thousands of connections from one user versus few from the other). I tried IMQ but it''s instability in my

I am trying to build a custom kernel for the HIPL code (infrahip.hip.fi), using the patch for the Linux 2.6.18 kernel. I followed all the instructions for getting the kernel source and making a custom kernel provided on the wiki. The rpmbuild fails with the following messages: Get an error on this step (figured out my other problem): Patch #40000

Commit-ID: ee59de58cd3ebe9e98d19aeaadb39915b0b235fc Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ee59de58cd3ebe9e98d19aeaadb39915b0b235fc Author: Benjamin Drung <benjamin.drung at profitbricks.com> AuthorDate: Wed, 13 Dec 2017 23:04:29 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] ipconfig:

---------- Forwarded message ---------- Received: from brimstone.netspace.org (brimstone.netspace.org [128.148.157.143]) by blues.jpj.net (backatcha) with ESMTP id CAA13949; Fri, 14 Nov 1997 02:08:13 -0500 (EST) Received: from unknown@netspace.org (port 25452 [128.148.157.6]) by brimstone.netspace.org with ESMTP id <818-20257>; Fri, 14 Nov 1997 01:41:22 -0500 Received: from NETSPACE.ORG by

--7ZAtKRhVyVSsbBD2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Netfilter Core Team Security Advisory =20 CVE: CAN-2003-0467 Subject: Netfilter / NAT Remote DoS Released: 01 Aug 2003 Effects: Under limited circumstances, a remote user may be able to crash

Below is a fix for the current problem of checksum offload not working in a NAT''ed network. The cause is the NAT/iptables code incorrectly modifying the TCP/UDP checksum (for the checksum offload case). The original code assumes a valid checksum, which is not the case for checksum offload packets (which has a complimented, partial checksum for the hardware to use). The fix is to