Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 2010-08-31 at 15:17 -0700, Steve Langasek wrote: > We already have one of these called resolvconf, and it has plenty of bugs > without adding a *second* framework for managing resolv.conf. Please > coordinate with the resolvconf maintainer and, preferably, merge your > efforts with the existing package. I tried many few years ago, but my patches were rejected (I forget why, don't have the emails anymore), so I created my own variant from scratch keeping a compatible commandline interface. #477723 - author is trying to pass resolvconf off to a new maintainer for over 2 years The other resolvconf bugs do not affect openresolv, and openresolv also solves many of them. > (In fact, I think that should be a blocker and that the ftp team should > reject any upload of a separate openresolv package.) I find that a very narrow minded view. Thanks Roy -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1283293804.1706.10.ca...@uberpc
Bug#595081: ITP: openresolv -- management framework for resolv.conf
On Tue, 2010-08-31 at 15:20 -0700, Don Armstrong wrote: > On Tue, 31 Aug 2010, Roy Marples wrote: > > Description : management framework for resolv.conf > > > > Allows multiple daemons to manage resolv.conf and configures local > > resolvers such as dnsmasq and unbound. > > How does this differ from resolvconf which already has significant > buy-in and integration in Debian? * Works with POSIX shell and userland * Does not need awk, grep or sed which means we can work without /usr mounted * Works with other init systems than Debians' out of the box * Available as a 2 clause BSD license * Prefer configs via IF_METRIC for dynamic ordering * Configures zones for local resolvers other than libc The last point is quite important, especially when running VPN systems. Take the following resolv.conf files which have been generated by a DHCP client and sent to resolvconf: # resolv.conf from bge0 search foo.com nameserver 1.2.3.4 # resolv.conf from tap0 domain bar.org nameserver 5.6.7.8 In this instance, queries for foo.com will go to 1.2.3.4 and queries for bar.org will go to 5.6.7.8. This does require the resolvers to be configured to pickup the resolvconf generated configuration for them though. openresolv ships with helpers for dnsmasq, ISC BIND,PowerDNS Recursor and unbound Other than that, the openresolv is command line compatible with resolvconf. However, the setup is not. Instead of many directories and files to manage, openresolv just uses /etc/resolvconf.conf. Aside from the user specific configuration, openresolv integrates 100% with a Debian based system. Thanks Roy -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1283294919.1706.28.ca...@uberpc
Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, 2010-08-28 at 12:33 +0200, Patrick Matthäi wrote: > Am 28.08.2010 12:11, schrieb Roy Marples: > >>>dhcpcd is a one stop IPv4 network management daemon which includes > >> > >> It only supports IPv6? > > > > Only IPv4 at present. > > IPv6 support, at least for RA is planned for the next major version, > > possibly with support for the experimental RFC5006 (DNS in IPv6 RA). > > Whops, s/IPv6/IPv4/ in my message, please. :) > > IMHO it shouldn't uploaded to Debian, without missing IPv6 support. What makes you think IPv6 support is required? It does not touch any existing IPv6 and neither does dhcpcd3. As such it co-exists just fine with kernel based RA solicitation. Thanks Roy -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282998574.1700.136.ca...@uberpc
Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, 2010-08-28 at 13:13 +0200, Mehdi Dogguy wrote: > On 08/28/2010 12:44 PM, Julien Cristau wrote: > > On Sat, Aug 28, 2010 at 09:35:29 +0100, Roy Marples wrote: > > > >> * Package name: dhcpcd5 > >> Version : 5.2.7 > >> Upstream Author : Roy Marples > >> * URL : http://roy.marples.name/projects/dhcpcd > >> * License : BSD-2 > >> Programming Lang: C, Shell > >> Description : dhcpcd5 - a DHCP client > >> > > What's the difference with the existing dhcpcd package? > > > > It's the same project (according to [1]). It's essentially an upgrade, however it's not 100% compatible with the commandline from dhcpcd3 and it uses a method similar to dhclient for configuring the system - aside from IP and routing which is managed internally. However, it's a new package. See bug #551034. Also, dhcpcd5 is designed to be run as a system daemon instead of per interface. This is so it can react to kernel level events and manage routing on a multi interface system a lot better (esp important for BSD system as they lack route metrics). Essentially it's like NetworkManager in this respect but a lot lot smaller. However unlike NetworkManager dhcpcd does not handle link setup and relies on something else to configure wpa_supplicant, ppp, etc. You can also configure an interface based on ARPping a host, wireless SSID. By this, I mean choose to run DHCP or a static IP, or override key DHCP values. Lastly, it works fine on BSD based systems which finally gives them an alternative. Infact, dhcpcd has been merged into the NetBSD base system since 5.0. I only mention this as Debian has kFreeBSD. I'm sure I missed some features out that maybe important to someone :) There are also related side projects which will find their way into Debian also - dhcpcd-dbus and dhcpcd-ui (GTK+ systray moniter/interface) and openresolv (resolvconf alternative, doesn't appear to suffer from the Debian resolvconf reported bugs). dhcpcd-dbus also talks to wpa_supplicant so that dhcpcd-ui can attempt to configure it. Thanks Roy -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282998474.1700.134.ca...@uberpc
Bug#594672: ITP: dhcpcd5 -- a DHCP client
On Sat, 2010-08-28 at 11:19 +0200, Patrick Matthäi wrote: > Am 28.08.2010 10:35, schrieb Roy Marples: > > Package: wnpp > > Severity: wishlist > > Owner: Roy Marples > > > > > > * Package name: dhcpcd5 > >Version : 5.2.7 > >Upstream Author : Roy Marples > > * URL : http://roy.marples.name/projects/dhcpcd > > * License : BSD-2 > >Programming Lang: C, Shell > >Description : dhcpcd5 - a DHCP client > > > > dhcpcd is a one stop IPv4 network management daemon which includes > > It only supports IPv6? Only IPv4 at present. IPv6 support, at least for RA is planned for the next major version, possibly with support for the experimental RFC5006 (DNS in IPv6 RA). Thanks Roy -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282990309.1700.104.ca...@uberpc
Bug#594672: ITP: dhcpcd5 -- a DHCP client
Package: wnpp Severity: wishlist Owner: Roy Marples * Package name: dhcpcd5 Version : 5.2.7 Upstream Author : Roy Marples * URL : http://roy.marples.name/projects/dhcpcd * License : BSD-2 Programming Lang: C, Shell Description : dhcpcd5 - a DHCP client dhcpcd is a one stop IPv4 network management daemon which includes * RFC2131 compliant DHCP client * IPv4LL (aka ZeroConf) support * ARP address conflict resolution * Link carrier detection * Wireless SSID profiles * ARP ping profiles -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100828083529.2072.9723.report...@uberpc
