similar to: [PATCH] Don't try to guess the nameserver in ipconfig.

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

Implement classless static routes support as specified in RFC3442. Bug-Debian: https://bugs.debian.org/884716 Bug-Ubuntu: https://launchpad.net/bugs/1526956 Signed-off-by: Benjamin Drung <benjamin.drung at profitbricks.com> --- usr/kinit/ipconfig/bootp_proto.c | 112 +++++++++++++++++++++++++++++++++++++++ usr/kinit/ipconfig/dhcp_proto.c | 1 + usr/kinit/ipconfig/main.c | 43

Implement classless static routes support as specified in RFC3442. Bug-Debian: https://bugs.debian.org/884716 Bug-Ubuntu: https://launchpad.net/bugs/1526956 Signed-off-by: Benjamin Drung <benjamin.drung at profitbricks.com> --- usr/kinit/ipconfig/bootp_proto.c | 110 +++++++++++++++++++++++++++++++ usr/kinit/ipconfig/dhcp_proto.c | 1 + usr/kinit/ipconfig/main.c | 50

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:

Implement classless static routes support as specified in RFC3442. Bug-Debian: https://bugs.debian.org/884716 Bug-Ubuntu: https://launchpad.net/bugs/1526956 Signed-off-by: Benjamin Drung <benjamin.drung at profitbricks.com> --- usr/kinit/ipconfig/bootp_proto.c | 109 +++++++++++++++++++++++++++++++ usr/kinit/ipconfig/dhcp_proto.c | 1 + usr/kinit/ipconfig/main.c | 54

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

Hi!! I found your ipconfig stuff in the udev rpm in SuSE 9.1. I'm about to setup a initramfs (pretty cool - much better than initrd) to boot linux diskless clients over the net. All the tools I would need, seem to be there with ipconfig/nfsmount ... I like to use the information I get from PXE/syslinux or Etherboot writing something like:

From: Geert Stappers <stappers at debian.org> To make klibc-ipconfig transmit the DHCP vendor class "d-i" and get the DHCP preseeding filename in a text file, it needs the attached patch. belows patch allows ipconfig to be used in Debian installer once the hostname is sent too, see http://blog.andrew.net.au/2006/05/17#d-i_dhcp_hacking Signed-off-by: maximilian attems <maks at

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:

If a hostname is requested, for example -d ::::foo::dhcp, then include the hostname in the DHCP discover/request. This patch also allows the vendor class identifier to be omitted from the DHCP discover/request by specifying -i "" Signed-off-by: Aron Griffis <agriffis at n01se.net> --- usr/kinit/ipconfig/dhcp_proto.c | 49 ++++++++++++++++++++++++++++++--------

Whilst ip= command is documented to support dns0:dns1 options as arguments 7 and 8, the -d parser in ipconfig does not. This breaks bringing up static ip configuration with dns nameservers set in the ip= command. Testcase: $ ip link add name dummy0 type dummy $ sudo /usr/lib/klibc/bin/ipconfig -d 10.245.237.7::10.245.237.1:255.255.255.0:ottawa:dummy0:none:8.8.8.8:8.8.4.4 IP-Config: dummy0

Commit-ID: b86cd0ef3f225b0e68a7c49de2460829f6bfe2be Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=b86cd0ef3f225b0e68a7c49de2460829f6bfe2be Author: Dimitri John Ledkov <xnox at ubuntu.com> AuthorDate: Wed, 17 Jul 2019 22:18:23 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sun, 28 Jul 2019 20:12:38 +0100 [klibc] ipconfig: Implement

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:

On Fri, 27 Aug 2010, Vagrant Cascadian wrote: > > ipconfig apparently assumes that the dhcp server's ip address is the > nameserver when dhcp gives it no nameservers, dhcp gives the nameserver > 0.0.0.0, or the nameservers are not ip addresses (i.e. ns1.example.org). > while these scenarios are probably not extremely common, i'm not sure > this is a good default with no

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

Commit-ID: 56dcdac0ffc1d86d196a1d04933288b0c0ef8417 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=56dcdac0ffc1d86d196a1d04933288b0c0ef8417 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 11 Dec 2019 17:38:21 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 11 Dec 2019 17:48:47 +0000 [klibc] ipconfig: Ignore NTP

I have removed the updated caching-nameserver from the core OS repo of CentOS 3.4 i386 as there have been reports of nameservers losing their configuration and stopping when the update was applied. I have reverted caching-nameserver in the 3.4 core OS back to the CentOS 3.3 version caching-nameserver-7.2-7.noarch.rpm. The new version caching-nameserver-7.3-3_EL3.noarch.rpm is now in the testing

I am having some issue with setting up a caching nameserver. here's the link: http://www.centos.org/modules/newbb/viewtopic.php?topic_id=150&forum=10&post_id=400#forumpost400 the OS is now CentOS4 -- My "Foundation" verse: Isa 54:17 No weapon that is formed against thee shall prosper; and every tongue that shall rise against thee in judgment thou shalt condemn. This is

--On Thursday, April 20, 2017 12:34 AM -0400 Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > works fine. until I fire up a vpn. having done that, looking in > /etc/resolv.conf (while the vpn is connected) it has reverted to > 192.168.2.1. > > after shutting down the vpn, 192.168.2.1 remains in resolv.conf Which VPN? It's not uncommon for VPN software to change

--On Thursday, April 20, 2017 9:10 AM -0400 Fred Smith <fredex at fcshome.stoneham.ma.us> wrote: > problem is, where is it getting the old address from? It isn't in > the resolv.conf before the vpn is started, and it is not in the NM > setups, anywhere, and it isn't in any of the files in > /etc/sysconfig/network*, so where is it coming from? And that particular >