similar to: [klibc:master] ipconfig: Implement support -d ...:dns0:dns1 options

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

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

On Wed, 2019-07-17 at 22:18 +0100, Dimitri John Ledkov wrote: > 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. [...] Applied, thanks. Ben. -- Ben Hutchings - Debian developer, member of kernel, installer and LTS

Hello, if ipconfig is run as ipconfig :::::: (i.e. long spec with all fields empty) and the computer has multiple network interfaces and only one of them is connected to dhcp managed network, ipconfig ends up in an infinite loop (see the log bellow). The following patch solved this for me. According to README, if the <device> in the long spec is empty, the first interface should be

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

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

gets assigned a value without any further usage. Signed-off-by: maximilian attems <max at stro.at> --- usr/kinit/ipconfig/main.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/usr/kinit/ipconfig/main.c b/usr/kinit/ipconfig/main.c index b392e6a..d912f6d 100644 --- a/usr/kinit/ipconfig/main.c +++ b/usr/kinit/ipconfig/main.c @@ -484,7 +484,7 @@ static int

Commit-ID: 607dae881e39572e0a0aa6a55a8b750a0b89165f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=607dae881e39572e0a0aa6a55a8b750a0b89165f Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Wed, 11 Dec 2019 17:26:28 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 11 Dec 2019 17:39:18 +0000 [klibc] ipconfig: Document support

Commit-ID: 547b7cf241d4bcf518759d06cff694b9738c57b0 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=547b7cf241d4bcf518759d06cff694b9738c57b0 Author: Dimitri John Ledkov <xnox at ubuntu.com> AuthorDate: Thu, 31 Oct 2019 15:59:02 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 5 Nov 2019 00:42:26 +0000 [klibc] loop: switch to

hi, i trying to install a fai installation server in a DomU for DomUs, but i have some problems with nfs. The DomUs says, that they can''t reach the NFS Server =========== Begin: Retrying nfs mount ... IP-Config: eth0 hardware address 00:16:3e:7a:25:7c mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.16.0.255 IP-Config: eth0 complete (from 172.16.0.151): address:

Otherwise, stack can be corrupted resulting in incorrect runtime behaviour. For example, overriding argc from main(). References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184 Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com> Signed-off-by: Adam Conrad <adconrad at ubuntu.com> Signed-off-by: Dimitri John Ledkov <xnox at ubuntu.com> ---

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.

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

On Sun, 4 Aug 2019, John Pierce wrote: > So you need to modify the source file that NetworkManager is using. > somewhere in /etc/network or /etc/networking-scripts, a config file has > DNS0=192.168.0.1 or sokmething, or your system is getting that from DHCP Will check on that. > the web login on 192.168.0.1 is undoubtably your modem/router. -- Michael hennebry at

The standard mount option nowadays to specify NFS version is "nfsvers", as documented in nfs(5) on modern Linux systems. Up to now, nfsmount only supported the old "v2" or "v3" boolean options. Extend option parsing to support both "nfsvers=X" and "vers=X", with X being equal to either 2 or 3 (nfsmount does not support NFSv4 at present). If both

Commit-ID: c4b811a1e4647224ddc717fac59900d16d0e9d4d Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=c4b811a1e4647224ddc717fac59900d16d0e9d4d Author: Baptiste Jonglez <baptiste.jonglez at imag.fr> AuthorDate: Thu, 14 Sep 2017 09:22:21 -0700 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Wed, 2 Jan 2019 03:08:04 +0000 [klibc] nfsmount: support

linux/loop.h header is exported by linux, for userspace to consume. This would prevent issues with struct sizes incompatibilities. References: https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1850184 Signed-off-by: Michael Hudson-Doyle <michael.hudson at ubuntu.com> Signed-off-by: Adam Conrad <adconrad at ubuntu.com> Signed-off-by: Dimitri John Ledkov <xnox at ubuntu.com>