Re: CARP compatibility between 5.1 and 5.2
R0me0 *** knight@gmail.com a écrit : Hello misc, I've a OpenBSD 5.1 in production and I will put another OpenBSD 5.2 and then configure CARP. will I have some compatibility issue ? Thanks in advanced Hi I have such à setup running surtout issue. Cheers Laurent
CARP compatibility between 5.1 and 5.2
Hello misc, I've a OpenBSD 5.1 in production and I will put another OpenBSD 5.2 and then configure CARP. will I have some compatibility issue ? Thanks in advanced
Re: CARP compatibility between 5.1 and 5.2
Hi ! There is no problem as i Know and use Loic Blot Le 15 janv. 2013 à 12:50, R0me0 *** knight@gmail.com a écrit : Hello misc, I've a OpenBSD 5.1 in production and I will put another OpenBSD 5.2 and then configure CARP. will I have some compatibility issue ? Thanks in advanced
Re: CARP compatibility
Router 2 carp1: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:00:00:00:00 priority: 0 carp: INIT carpdev none vhid 2 advbase 1 advskew 0 groups: carp This mightily looks like some other interface is trying to use the same IP-address (the 00:00:00:00:00:00 hints at that). In that case the carp interface naturally remains at INIT. Marcus
Re: CARP compatibility
* Marcus M|lb|sch muelbue...@as-infodienste.de [2011-04-20 13:34]: Router 2 carp1: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:00:00:00:00 priority: 0 carp: INIT carpdev none vhid 2 advbase 1 advskew 0 groups: carp This mightily looks like some other interface is trying to use the same IP-address (the 00:00:00:00:00:00 hints at that). no, that is wrong. In that case the carp interface naturally remains at INIT. it remains at init because afaict there is no IP address on that interface (once again incomplete output has been presented...). carp doesn't work without and stays in init. and the macaddr depends on the vhid so it is set late-ish. -- Henning Brauer, h...@bsws.de, henn...@openbsd.org BS Web Services, http://bsws.de Full-Service ISP - Secure Hosting, Mail and DNS Services Dedicated Servers, Rootservers, Application Hosting
CARP compatibility
Hello, We have two openBSD installation a 4.6 and 4.8 we setup CARP between the two machines, but things are not working properly. On the internal side of the network we have this (ifconfig -A): Router 1 carp0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5e:00:01:01 priority: 0 carp: MASTER carpdev em1 vhid 1 advbase 1 advskew 100 groups: carp Router 2 carp0: flags=8802BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5e:00:01:01 priority: 0 carp: INIT carpdev em1 vhid 1 advbase 1 advskew 0 groups: carp while on the external side we have : Router 1 carp1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:5e:00:01:02 priority: 0 carp: MASTER carpdev em0 vhid 2 advbase 1 advskew 100 groups: carp Router 2 carp1: flags=8803UP,BROADCAST,SIMPLEX,MULTICAST mtu 1500 lladdr 00:00:00:00:00:00 priority: 0 carp: INIT carpdev none vhid 2 advbase 1 advskew 0 groups: carp We turned off carp0. As you can see things are messed up. Does that have something to do with different openBSD versions?? Does anyone had the same issues, as the interface that is meant to be BACKUP is the MASTER. Thanks. -- Abbass MAROUNI Internet Memory Foundation internetmemory.org
carp compatibility 4.0 - current
Hi guys, I have a two redundant OpenBSD firewalls with carp. Both is version 4.0. I am planning to upgrade the one in the BACKUP state to -current and a few days/weeks later the other one. But I am wondering if is there any change in pfsync or carp protocol which will force me to upgrade both at the same time to retain a proper failover capability. IIRC simmilar change happend at 3.8, that's why I am asking. Thanks in advance, cstamas -- Life is complex - It has real and imaginary parts. -- Andrea Leistra CSILLAG Tamas (cstamas) - http://digitus.itk.ppke.hu/~cstamas
Re: carp compatibility 4.0 - current
On Mon, Apr 16, 2007 at 09:15:11PM +0200, Csillag Tamas wrote: Hi guys, I have a two redundant OpenBSD firewalls with carp. Both is version 4.0. I am planning to upgrade the one in the BACKUP state to -current and a few days/weeks later the other one. But I am wondering if is there any change in pfsync or carp protocol which will force me to upgrade both at the same time to retain a proper failover capability. IIRC simmilar change happend at 3.8, that's why I am asking. You'll have to ask someone with more knowledge, but I don't recall seeing any big changes. Although I seem to recall someone proposing to change advskew or something like that, I don't know what became of that. Joachim -- TFMotD: vhold (9) - acquire a hold on a vnode
