On 2016-02-18, 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'? >> > > I went back to 2016/02/01 and 2016/01/12 (packet.c) and I have the same > problem > so it doesn't seem like a dhcrelay problem. > > I changed it to print the interfaces > Feb 17 18:04:28 dhcrelay: send_packet: No buffer space available on carp63 > Feb 18 09:16:35 dhcrelay: send_packet: No buffer space available on carp32 > Feb 18 09:27:45 dhcrelay: send_packet: No buffer space available on carp32 > but there is no network/routing problem. > > Setup is trunk (lacp) - vlans - carps - dhcrelay for internal > trunk (lacp) / nat for external > > ospf in (passive on carps) / out on ext trunk. > > Any way to debug this further? > > thanks, > > Giannis >
Are the carp interfaces "up" (i.e. master) when you see these messages?
