similar to: ipconfig problem if multiple devices are up

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

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

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

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

This patch adds a flag to mdb entries so that we can distinguish permanent entries with temporary ones. Cc: Stephen Hemminger <shemminger at vyatta.com> Signed-off-by: Cong Wang <amwang at redhat.com> --- bridge/mdb.c | 24 +++++++++++++++--------- include/linux/if_bridge.h | 3 +++ 2 files changed, 18 insertions(+), 9 deletions(-) diff --git a/bridge/mdb.c

Hello, Can someone explain why I don't get a timeout when I use the community string "public" even if I don't have it defined in my snmpd.conf file. It doesn't return data but it also doesn't timeout. See example below. ... rocommunity nobody 127.0.0.1 ... [root at L703108 pgsql]# snmpwalk -v 1 -c public 127.0.0.1 1.3.6.1.2.1.2.2.1 ifMIB [root at L703108 pgsql]#

Hi, I have a working fc14 install with a few virtual interfaces set up, and just noticed the following in messages: Apr 18 13:07:43 fc14 libvirtd: 13:07:43.155: error : interfaceGetXMLDesc:355 : internal error could not get interface XML description (netcf: NETLINK socket operation failed - couldn't find ifindex for interface `br0:0`) Apr 18 13:07:43 fc14 libvirtd: 13:07:43.165: error :

Hello, I found a bug in ipconfig and I'm sending a proposed patch for it. I've only seen it happen in 2 dhcp-server environments. Scenario: ipconfig sends a DHCP_DISCOVER, server A answers with a DHCP_OFFER, server B answers with a DHCP_OFFER, ipconfig sends a DHCP_REQUEST for server A, ipconfig accepts the DHCP_OFFER from server B instead of DHCP_ACK from server A. <== BUG The reason

From: Cong Wang <amwang at redhat.com> V4: remove some useless #include some coding style fix V3: drop debugging printk's update selinux perm table as well V2: drop patch 1/2, export ifindex directly Redesign netlink attributes Improve netlink seq check Handle IPv6 addr as well This patch exports bridge multicast database via netlink message type RTM_GETMDB.

V3: drop debugging printk's update selinux perm table as well V2: drop patch 1/2, export ifindex directly Redesign netlink attributes Improve netlink seq check Handle IPv6 addr as well This patch exports bridge multicast database via netlink message type RTM_GETMDB. Similar to fdb, but currently bridge-specific. We may need to support modify multicast database too

Hi Is there a way to either: Find the real ifindex/ifname a mac-address is bound to or Find the real ifindex/ifname of an incoming packet ? I am writing a dhcp server and need to know what real interface the dhcp re= quest packet came from. An acceptable solution would be to get the interfac= e by the mac-address, but that can be faked so I would rather get the inter= face by knowing where the

On Wed, Feb 21, 2018 at 1:51 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Tue, Feb 20, 2018 at 11:33:56PM CET, kubakici at wp.pl wrote: >>On Tue, 20 Feb 2018 21:14:10 +0100, Jiri Pirko wrote: >>> Yeah, I can see it now :( I guess that the ship has sailed and we are >>> stuck with this ugly thing forever... >>> >>> Could you at least make some

On Wed, Feb 21, 2018 at 1:51 AM, Jiri Pirko <jiri at resnulli.us> wrote: > Tue, Feb 20, 2018 at 11:33:56PM CET, kubakici at wp.pl wrote: >>On Tue, 20 Feb 2018 21:14:10 +0100, Jiri Pirko wrote: >>> Yeah, I can see it now :( I guess that the ship has sailed and we are >>> stuck with this ugly thing forever... >>> >>> Could you at least make some

From: Cong Wang <amwang at redhat.com> V5: fix two bugs pointed out by Thomas remove seq check for now, mark it as TODO V4: remove some useless #include some coding style fix V3: drop debugging printk's update selinux perm table as well V2: drop patch 1/2, export ifindex directly Redesign netlink attributes Improve netlink seq check Handle IPv6 addr as well

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: