CARP and freebsd
Hi, all: Is carp a part of freebsd 8.1? or I have to download from somewhere and install it? Thanks in advance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CARP and freebsd
Hi, all: Is carp a part of freebsd 8.1? or I have to download from somewhere and install it? Thanks in advance ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org The FreeBSD hand book says: To enable support for CARP, the FreeBSD kernel must be rebuilt with the following option: device carp (http://www.freebsd.org/doc/handbook/carp.html) It's indicated as covering FreeBSD 7.3-RELEASE and FreeBSD 8.1-RELEASE so you should be OK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CARP and freebsd
On 3 September 2010 10:37, gahn ipfr...@yahoo.com wrote: Is carp a part of freebsd 8.1? or I have to download from somewhere and install it? Everything you could want to know about CARP and FreeBSD: http://www.freebsd.org/doc/handbook/carp.html On my 8.1 box - fbsdsroute0# sysctl net.inet.carp.allow sysctl: unknown oid 'net.inet.carp.allow' So I can't say for certain but I would hazard the guess that it is not included in the GENERIC kernel. Alas, there is documentation for rebuilding your kernel, too: http://www.freebsd.org/doc/handbook/kernelconfig.html kmw ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: CARP and FreeBSD 6.3
Am Donnerstag, den 24.01.2008, 22:45 -0800 schrieb shinny knight:
Rakhesh Sasidharan [EMAIL PROTECTED] wrote:
Hi,
I have two machines. Each have two interfaces, xl0 and fxp0. And each have
two carp interfaces -- carp1 (xl0 of both) and carp2 (fxp0 of both). One of
the machines is master, the other is backup.
I also have the following sysctl set: net.inet.carp.preempt - 1
My understanding is that if I down one of the interfaces on the master
machine (say ''ifconfig xl0 down''), then both carp interfaces on the
master
will be marked as down. And the backup will become the new master. Later,
when the interface is marked up (''ifconfig xl0 up''), the old master will
resume control. This is my understanding and that's how things were till
yesterday (when I was on FreeBSD 6.2/i386 with both machines).
Today morning I upgraded both machines to FreeBSD 6.3 and that does not
seem
to be the case any more.
Now, on the master machine when I down the xl0 interface, only carp1 (the
group containing xl0) goes into init state (and the other machine's carp1
interface becomes the new master). Ditto for fxp0 and carp2. So in essence,
the net.inet.carp.preempt=1 sysctl does not seem to be working as expected
which is unlike how things were in FreeBSD 6.2.
Has something changed with regards to carp between FreeBSD 6.2 and 6.3? Any
one else encountering a similar problem?
I happened to reboot the machines now while sitting at the console. And I
noticed that the master machine emits an error like ''carp2: incorrect
hash'' while booting up. Checking the console logs showed me that the
errors have been appearing ever since I upgraded the machine. Most of the
times it was to do with carp2, once it was to do with carp1.
Here's the relevant bits of my rc.conf file from the master machine.
---8--
ifconfig_fxp0=inet 192.168.10.10 netmask 255.255.255.0 polling
ifconfig_fxp0_alias0=inet 192.168.10.11 netmask 255.255.255.255
ifconfig_xl0=inet 192.168.20.20 netmask 255.255.255.0 polling
cloned_interfaces=carp1 carp2
ifconfig_carp1=vhid 1 pass password advskew 0 192.168.10.2 netmask
255.255.255.0
ifconfig_carp2_alias0=vhid 2 pass password advskew 0 192.168.20.1 netmask
255.255.255.0
ifconfig_carp2_alias1=vhid 2 pass password advskew 0 192.168.20.2 netmask
255.255.255.0
---8--
Its the same on the backup machine, except for the different IPs for fxp0
and xl0.
Thanks,
Rakhesh
---
http://rakhesh.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hello Rakhesh,
I never had hash errors on startup for CARP, but for demote, promote you
should try /usr/ports/net/ifstated. It's working fine for me.
Best Regards,
Catalin
Any news on this ? I see the same problem on our freebsd + pf + carp
installation...
Cheers,
Norman
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CARP and FreeBSD 6.3: is it working for someone?
Sorry to step in this way... I was planning to upgrade a 6.2/amd64 SMP box to 6.3, hoping I could rid myself of those deadlocks that are still occasionally plaguing that server. Now I read this thread and stopped, since I'm also using CARP on that one. Can someone confirm CARP works on 6.3 for them? bye Thanks av. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CARP and FreeBSD 6.3
Hi,
I have two machines. Each have two interfaces, xl0 and fxp0. And each
have two carp interfaces -- carp1 (xl0 of both) and carp2 (fxp0 of both).
One of the machines is master, the other is backup.
I also have the following sysctl set: net.inet.carp.preempt - 1
My understanding is that if I down one of the interfaces on the master
machine (say ''ifconfig xl0 down''), then both carp interfaces on the
master will be marked as down. And the backup will become the new master.
Later, when the interface is marked up (''ifconfig xl0 up''), the old
master will resume control. This is my understanding and that's how things
were till yesterday (when I was on FreeBSD 6.2/i386 with both machines).
Today morning I upgraded both machines to FreeBSD 6.3 and that does not
seem to be the case any more.
Now, on the master machine when I down the xl0 interface, only carp1 (the
group containing xl0) goes into init state (and the other machine's carp1
interface becomes the new master). Ditto for fxp0 and carp2. So in
essence, the net.inet.carp.preempt=1 sysctl does not seem to be working as
expected which is unlike how things were in FreeBSD 6.2.
Has something changed with regards to carp between FreeBSD 6.2 and 6.3?
Any one else encountering a similar problem?
Thanks,
Rakhesh
---
http://rakhesh.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CARP and FreeBSD 6.3
Hi,
I have two machines. Each have two interfaces, xl0 and fxp0. And each have
two carp interfaces -- carp1 (xl0 of both) and carp2 (fxp0 of both). One of
the machines is master, the other is backup.
I also have the following sysctl set: net.inet.carp.preempt - 1
My understanding is that if I down one of the interfaces on the master
machine (say ''ifconfig xl0 down''), then both carp interfaces on the master
will be marked as down. And the backup will become the new master. Later,
when the interface is marked up (''ifconfig xl0 up''), the old master will
resume control. This is my understanding and that's how things were till
yesterday (when I was on FreeBSD 6.2/i386 with both machines).
Today morning I upgraded both machines to FreeBSD 6.3 and that does not seem
to be the case any more.
Now, on the master machine when I down the xl0 interface, only carp1 (the
group containing xl0) goes into init state (and the other machine's carp1
interface becomes the new master). Ditto for fxp0 and carp2. So in essence,
the net.inet.carp.preempt=1 sysctl does not seem to be working as expected
which is unlike how things were in FreeBSD 6.2.
Has something changed with regards to carp between FreeBSD 6.2 and 6.3? Any
one else encountering a similar problem?
I happened to reboot the machines now while sitting at the console. And I
noticed that the master machine emits an error like ''carp2: incorrect
hash'' while booting up. Checking the console logs showed me that the
errors have been appearing ever since I upgraded the machine. Most of the
times it was to do with carp2, once it was to do with carp1.
Here's the relevant bits of my rc.conf file from the master machine.
---8--
ifconfig_fxp0=inet 192.168.10.10 netmask 255.255.255.0 polling
ifconfig_fxp0_alias0=inet 192.168.10.11 netmask 255.255.255.255
ifconfig_xl0=inet 192.168.20.20 netmask 255.255.255.0 polling
cloned_interfaces=carp1 carp2
ifconfig_carp1=vhid 1 pass password advskew 0 192.168.10.2 netmask
255.255.255.0
ifconfig_carp2_alias0=vhid 2 pass password advskew 0 192.168.20.1 netmask
255.255.255.0
ifconfig_carp2_alias1=vhid 2 pass password advskew 0 192.168.20.2 netmask
255.255.255.0
---8--
Its the same on the backup machine, except for the different IPs for fxp0
and xl0.
Thanks,
Rakhesh
---
http://rakhesh.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CARP and FreeBSD 6.3
Rakhesh Sasidharan [EMAIL PROTECTED] wrote:
Hi,
I have two machines. Each have two interfaces, xl0 and fxp0. And each have
two carp interfaces -- carp1 (xl0 of both) and carp2 (fxp0 of both). One of
the machines is master, the other is backup.
I also have the following sysctl set: net.inet.carp.preempt - 1
My understanding is that if I down one of the interfaces on the master
machine (say ''ifconfig xl0 down''), then both carp interfaces on the master
will be marked as down. And the backup will become the new master. Later,
when the interface is marked up (''ifconfig xl0 up''), the old master will
resume control. This is my understanding and that's how things were till
yesterday (when I was on FreeBSD 6.2/i386 with both machines).
Today morning I upgraded both machines to FreeBSD 6.3 and that does not seem
to be the case any more.
Now, on the master machine when I down the xl0 interface, only carp1 (the
group containing xl0) goes into init state (and the other machine's carp1
interface becomes the new master). Ditto for fxp0 and carp2. So in essence,
the net.inet.carp.preempt=1 sysctl does not seem to be working as expected
which is unlike how things were in FreeBSD 6.2.
Has something changed with regards to carp between FreeBSD 6.2 and 6.3? Any
one else encountering a similar problem?
I happened to reboot the machines now while sitting at the console. And I
noticed that the master machine emits an error like ''carp2: incorrect
hash'' while booting up. Checking the console logs showed me that the
errors have been appearing ever since I upgraded the machine. Most of the
times it was to do with carp2, once it was to do with carp1.
Here's the relevant bits of my rc.conf file from the master machine.
---8--
ifconfig_fxp0=inet 192.168.10.10 netmask 255.255.255.0 polling
ifconfig_fxp0_alias0=inet 192.168.10.11 netmask 255.255.255.255
ifconfig_xl0=inet 192.168.20.20 netmask 255.255.255.0 polling
cloned_interfaces=carp1 carp2
ifconfig_carp1=vhid 1 pass password advskew 0 192.168.10.2 netmask
255.255.255.0
ifconfig_carp2_alias0=vhid 2 pass password advskew 0 192.168.20.1 netmask
255.255.255.0
ifconfig_carp2_alias1=vhid 2 pass password advskew 0 192.168.20.2 netmask
255.255.255.0
---8--
Its the same on the backup machine, except for the different IPs for fxp0
and xl0.
Thanks,
Rakhesh
---
http://rakhesh.net/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Hello Rakhesh,
I never had hash errors on startup for CARP, but for demote, promote you should
try /usr/ports/net/ifstated. It's working fine for me.
Best Regards,
Catalin
-
Never miss a thing. Make Yahoo your homepage.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CARP and FreeBSD
On Thursday 08 March 2007 08:59, Elliot Finley wrote: Hello, Is CARP functional in FreeBSD 6.x? I'm not able to find any docs on it in the Handbook or by doing a site restricted search on google. there you go then. http://www.freebsd.org/cgi/man.cgi?query=carp Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
CARP and FreeBSD
Hello, Is CARP functional in FreeBSD 6.x? I'm not able to find any docs on it in the Handbook or by doing a site restricted search on google. TIA for any pointers. Elliot Finley ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [Xorp-feedback] Xorp and CARP on FreeBSD]
Hello,
here is a reply from one of the XORP developers, Pavlin Radoslavov. What is
your opinion to this problem?
Thanks,
Bohus
- Forwarded message from Pavlin Radoslavov [EMAIL PROTECTED] -
To: [EMAIL PROTECTED]
Subject: Re: [Xorp-feedback] Xorp and CARP on FreeBSD
Date: Thu, 29 Jun 2006 15:54:06 -0700
From: Pavlin Radoslavov [EMAIL PROTECTED]
On Fri, Jun 09, 2006 at 09:46:36AM -0700, Pavlin Radoslavov wrote:
I've two FreeBSD 6.1-RELEASE routers (R1, R2) with CARP configured
and it was working OK untill I've installed Xorp and tried to configure
multicast PIM-SM. After that the CARP has stoped working. I've found
out by the tcpdump that after Xorp is started the source IP address
of CARP packets is changed to IP address used as register_vif in Xorp:
Do you get the same error if you configure only the interfaces
section in the XORP config.
No, the problem occures, only when the plumbing section is present.
Also, is any of the IP address changed (by CARP) while XORP is running?
No. There are the CARP virtual interfaces created befor XORP is started.
CARP dosn't change any IP address, but XORP changes source IP address
of multicast CARP packets. When I stop XORP the IP address is retutned
to original IP address.
Thank you for the info.
I did some investigation (FreeBSD-6.1) and I was able to see the
the problem: VRRPv2 Advertisement messages with the wrong source
address.
For the record, this is what I did (on a single machine):
=
ifconfig vlan97 create
ifconfig vlan97 inet 192.168.100.2 netmask 255.255.255.0 vlan 97 vlandev xl0
ifconfig vlan71 create
ifconfig vlan71 inet 10.122.25.66 netmask 255.255.255.224 vlan 71 vlandev xl0
ifconfig carp97 create
ifconfig carp97 vhid 1 pass foofoo1 192.168.100.1/24
ifconfig carp71 create
ifconfig carp71 vhid 2 pass foofoo2 10.122.25.64/27
=
Then I started XORP with the configuration file included at the end
of this email. Basically, the important thing in that configuration
file is that inside the MFEA I enabled only the vlan71 interface.
Indeed, by running tcpdump I was able to see that the VRRPv2
Advertisement messages sent over vlan97 changed their source address
to be same ass the source address of vlan71:
=
[EMAIL PROTECTED] tcpdump -n -i vlan97 proto 112
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan97, link-type EN10MB (Ethernet), capture size 96 bytes
15:38:04.614085 IP 192.168.100.2 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 0, authtype none, intvl 1s, length 36
15:38:05.615058 IP 192.168.100.2 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 0, authtype none, intvl 1s, length 36
...
15:38:22.635132 IP 10.122.25.66 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 0, authtype none, intvl 1s, length 36
15:38:23.636107 IP 10.122.25.66 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 0, authtype none, intvl 1s, length 36
=
After some investigation, I was able to trace the problem to the
setsockopt(_mrouter_socket, IPPROTO_IP, MRT_ADD_VIF, ...) system
call. In fact, I was able to reproduce the problem with other
multicast routing implementations: mrouted and pimd which obviously
also use the same setsockopt().
After some further investigation, it seems to happen only when
running CARP over vlan interfaces, but I haven't investigated this
in greater details. At least, it didn't happen when I enabled in MFEA
the physical xl0 network interface (also running CARP).
Hence, I belive the problem is in the FreeBSD kernel, and happens
when we have 2+ vlan interfaces configured to run CARP and one of
them is also configured for multicast routing.
You might want to contact the FreeBSD folks about that, because the
problem is not XORP-specific.
Please let us know how it goes.
Thanks,
Pavlin
=
interfaces {
interface vlan97 {
description: DMZ
disable: false
default-system-config
}
interface vlan71 {
description: intranet
disable: false
default-system-config
}
}
fea {
unicast-forwarding4 {
disable: false
}
}
plumbing {
mfea4 {
disable: false
interface vlan71 {
vif vlan71 {
disable: false
}
}
/*
interface vlan97 {
vif vlan97 {
disable: false
}
}
*/
/*
interface register_vif {
vif register_vif {
Note: this vif should be always enabled
disable: false
}
}
*/
traceoptions {
flag all {
disable: false
Xorp and CARP on FreeBSD
Hello,
I've two FreeBSD 6.1-RELEASE routers (R1, R2) with CARP configured
and it was working OK untill I've installed Xorp and tried to configure
multicast PIM-SM. After that the CARP has stoped working. I've found
out by the tcpdump that after Xorp is started the source IP address
of CARP packets is changed to IP address used as register_vif in Xorp:
# tcpdump -n -i vlan97 proto 112
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan97, link-type EN10MB (Ethernet), capture size 96 bytes
13:11:32.694192 IP 192.168.100.2 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 50, authtype none, intvl 1s, length 36
13:11:33.891182 IP 192.168.100.2 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 50, authtype none, intvl 1s, length 36
13:11:35.088237 IP 192.168.100.2 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 50, authtype none, intvl 1s, length 36
13:11:36.285276 IP 10.122.25.66 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 50, authtype none, intvl 1s, length 36
13:11:37.482275 IP 10.122.25.66 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 50, authtype none, intvl 1s, length 36
13:11:38.679312 IP 10.122.25.66 224.0.0.18: VRRPv2, Advertisement, vrid 1,
prio 50, authtype none, intvl 1s, length 36
^C
Is it possible to run Xorp and CARP together?
Or can somebody advise me other routing software with PIM-SM support?
Here are some additional info:
R1 host:
cat /etc/rc.conf.local:
---
cloned_interfaces=vlan97 vlan71 carp97 carp71
ifconfig_vlan97=inet 192.168.100.2 netmask 255.255.255.0 vlan 97 vlandev
em0
ifconfig_vlan71=inet 10.122.25.66 netmask 255.255.255.224 vlan 71 vlandev
em0
ifconfig_carp97=vhid 1 pass advskew 500 192.168.100.1 255.255.255.0
ifconfig_carp71=vhid 2 pass advskew 50 10.122.25.65 255.255.255.224
cat /usr/local/xorp/etc/config.boot:
interfaces {
restore-original-config-on-shutdown: true
interface vlan97 {
description: DMZ
disable: false
default-system-config
}
interface vlan71 {
description: intranet
disable: false
default-system-config
}
}
fea {
unicast-forwarding4 {
disable: false
}
}
plumbing {
mfea4 {
disable: false
interface vlan71 {
vif vlan71 {
disable: false
}
}
interface vlan97 {
vif vlan97 {
disable: false
}
}
interface register_vif {
vif register_vif {
/* Note: this vif should be always enabled */
disable: false
}
}
traceoptions {
flag all {
disable: false
}
}
}
}
R2 host:
cat /etc/rc.conf.local:
---
cloned_interfaces=vlan97 vlan71 carp97 carp71
ifconfig_vlan97=inet 192.168.100.3 netmask 255.255.255.0 vlan 97 vlandev
em0
ifconfig_vlan71=inet 10.122.25.67 netmask 255.255.255.224 vlan 71 vlandev
em0
ifconfig_carp97=vhid 1 pass advskew 200 192.168.100.1 255.255.255.0
ifconfig_carp71=vhid 2 pass advskew 200 10.122.25.65 255.255.255.224
Thanks
Bohus Plucinsky
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
