Bug#617258: isc-dhcp-relay: segfaults if client-facing interface has label

Package: isc-dhcp-relay Version: 4.2.4-7 Followup-For: Bug #617258 hi, this is also an issue when using carp¹ to implement vrrp-like failover. virtual interface(s) managed by the carp userspace daemon are named $raw_device:carp by default (and by convention), using these interfaces to relay

Bug#617258: isc-dhcp-relay: segfaults if client-facing interface has label

Hi Andrew, sorry for taking so long to reply. The bug has changed. dhcrelay does not crash any more, but it does also not work. root@testkiste:/home/mh# ip a 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet

Bug#617258: isc-dhcp-relay: segfaults if client-facing interface has label

tags 617258 + unreproducible thanks On Mon, Mar 07, 2011 at 05:12:26PM +0100, Marc Haber wrote: Package: isc-dhcp-relay Version: 4.1.1-P1-16 Severity: normal Hi, dhcrelay segfaults on first incoming packet if the client-facing interface has a label on its IP address Steps to

Bug#617258: isc-dhcp-relay: segfaults if client-facing interface has label

Package: isc-dhcp-relay Version: 4.1.1-P1-16 Severity: normal Hi, dhcrelay segfaults on first incoming packet if the client-facing interface has a label on its IP address Steps to reproduce: Have Debian box with two interfaces, two networks 192.168.0.0/24 and 10.0.0.0/24. ip link set dev eth0