Package Details: mkinitcpio-netconf 0.0.4-2

Git Clone URL: https://aur.archlinux.org/mkinitcpio-netconf.git (read-only)
Package Base: mkinitcpio-netconf
Description: Archlinux mkinitcpio hook for configuring early userspace networking
Upstream URL: https://github.com/grazzolini/mkinitcpio-netconf
Keywords: mkinitcpio network
Licenses: BSD
Submitter: grazzolini
Maintainer: grazzolini
Last Packager: grazzolini
Votes: 16
Popularity: 0.387693
First Submitted: 2015-07-11 02:43
Last Updated: 2016-10-21 11:23

Latest Comments

wgedda commented on 2016-10-10 15:35

@grazzolini
Thank you for your answer, I tested it and it works very well. If anyone is looking for this, too: Specify timeout in seconds, for example "netconf_timeout=30" and add the parameter to GRUB_CMDLINE_LINUX_DEFAULT.

grazzolini commented on 2016-10-10 11:08

@wgedda
Yes, if you pass netconf_timeout argument to the kernel, you can configure a timeout for the DHCP. But, if there are situations where the DHCP server might not be available, I strongly advise you use a static ip address.

wgedda commented on 2016-10-09 13:03

Hey,

I installed and configured the mkinitcpio-netconf hook. Does anyone know if it is possible to terminate (DHCP) autoconfiguration to continue booting? Or is there a timeout when no DHCP response was received?

grazzolini commented on 2016-08-25 18:12

@Elvis
This is documentation for the ip= parameter: https://www.kernel.org/doc/Documentation/filesystems/nfs/nfsroot.txt

It can take up to 9 parameters. But not all are parsed by Archlinux's ipconfig. The ipconfig utility on arch is a patched one from the original's and, even though it accepts all the options on the kernel documentation page, it doesn't deal with them in the same way. If you notice on the dm-crypt page, it ends with :none. This means to not autoconf the device, and the dns parameters are not required.

If you're using netconf only, them formatting the ip= parameter correctly will work. You can always use ip=dhcp if you want auto-configuration also.

Evils commented on 2016-08-25 17:44

@grazzolini
I use the netconf module, not the net module.

The wiki page I linked to says that ipconfig takes 9 parameters through the kernel parameter, while the page you linked to says 7 parameters (explanation missing though).

This should be updated imho as both appear on the same page and cause confusion.

grazzolini commented on 2016-08-19 18:51

@Elvis,

Given that mkinitcpio-nfs-utils isn't updated since 2014, I doubt it is the cause for your issue. More likely you have your ip= parameter malformed. Also, you should follow this:

https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Remote_unlocking_.28hooks:_netconf.2C_dropbear.2C_tinyssh.2C_ppp.29

And explicitly *not* use the net hook, as it conflicts with netconf. Both use ipconfig, but the net hook should really be called nfs hook, since it is meant for nfs.

Evils commented on 2016-08-19 14:50

@grazzolini
I recently started to get a message saying "IPConfig: Too many options for eth0", now my ip line/kernel parameter is specified as mentioned here: https://wiki.archlinux.org/index.php/Mkinitcpio#Using_net and it used to work until recently. So I do wonder why ipconfig and this package lately seem to have a different behaviour?!

grazzolini commented on 2016-08-09 13:09

@ajs124 @nirnakinho
I have changed the way the filename is saved on the disk, so there shouldn't be any more clashes in the future.

ajs124 commented on 2016-07-13 20:50

Hey, I also ran into the same problem as @nirnakinho. pacman or rather the PKGBUILD format actually has a workaround for this. You can easily specify the filename as which the file is saved like this

source=($pkgname-$pkgver::$url/archive/v$pkgver.tar.gz)

You don't need a wrapper for that, people should just specify this in their PKGBUILD.

grazzolini commented on 2016-05-30 11:52

@nirnakinho
The package names are defined by github, when creating the tags. The only way to influence on that would be to either have different tagging styles for the different packages, or different versions for the tags. Anyway, I'll look into putting the name of the package into the tags so they can't be mixed up.

P.s.: This kind of thing might happen when storing all source files into the same directory. Hence why abs doesn't do that, nor most of the helpers I know of. Even If I change the tagging style, this kind of clash might occur with others. If you want to keep all the sources into the same directory, then a wrapper around the source download function (if you have one), would be beneficial.

All comments