On 2016-02-13, Kapetanakis Giannis <bil...@edu.physics.uoc.gr> wrote: > On 12/02/16 18:56, Stuart Henderson wrote: >> On 2016-02-12, Kapetanakis Giannis <bil...@edu.physics.uoc.gr> wrote: >>> Hi, >>> >>> I have a carped firewall which is using dhcrelay to forward dhcp >>> requests to another carped dhcp server. >>> After upgrade to Feb 4 snapshot I'm seeing these in my logs: >> What version were you running before? >> >> To establish whether it's a dhcrelay problem or something to do with carp >> can you try dhcrelay from slightly older source e.g. 'cvs up -D 2016/02/01'? >> > > The previous version was from July 2015 so it was far away from now.
So there are a lot of changea to networking in that timeframe, but only a few changes to dhcrelay. To narrow it down and establish whether it's a dhcrelay problem or something to do with carp can you try dhcrelay from slightly older source e.g. 'cvs up -D 2016/02/01'? > I guess it will not work with current kernel and pledge(2), tame(2) > changes correct? This isn't anything to do with pledge. I wouldn't expect old network-related binaries to work on -current due to the network stack changes though.
