Stuart Henderson stu at spacehopper.org writes:
I setup carp-on-vlan-on-trunk-on-bnx0/1 on an R210-II running 5.1
the other day, no trouble. In this case they're webservers so I didn't
set net.inet.ip.forwarding in sysctl.conf and i'm using ip balancing
rather than simple carp failover.
OK,
Aha! I have finally solved this. I've no idea *why* it is happening, but
it seems the order of the lines in /etc/hostname.carp119 is an issue.
It seems that the inet config needs to come after the carp details. See
below:
# ifconfig carp119 destroy
# cat /etc/hostname.carp119
carpdev
BARDOU Pierre bardou.p at mipih.fr writes:
Hello,
I have dozens of CARP interfaces over VLAN interfaces over LACP trunk
interfaces over physical EM/BGE/BNX. Carp is in multicast mode, multicast
routing is disabled. Works like a charm with various OpenBSD versions since
4.4 to 5.0.
OK,
On 2012-04-25, Matt Hamilton ma...@netsight.co.uk wrote:
BARDOU Pierre bardou.p at mipih.fr writes:
Hello,
I have dozens of CARP interfaces over VLAN interfaces over LACP trunk
interfaces over physical EM/BGE/BNX. Carp is in multicast mode, multicast
routing is disabled. Works like a
...
--
Cordialement,
Pierre BARDOU
-Message d'origine-
De : Matt Hamilton [mailto:ma...@netsight.co.uk]
Envoyi : lundi 23 avril 2012 17:49
@ : misc@openbsd.org
Objet : Re: bnx[01] - trunk0 - vlan119 - carp119 problem
Kapetanakis Giannis bilias at edu.physics.uoc.gr writes:
On 23/04/12 17:13, Matt
OK, A few more tests done. It seems it is the multicast being blocked.
If I use carppeer then it starts to
work and I can see packets on the vlan interface with tcpdump.
So here is my ifconfig setup:
# ifconfig -a
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 33152
priority: 0
On 23/04/12 17:13, Matt Hamilton wrote:
So it appears there is somewhere a problem with multicast packets being
filtered out somewhere.
This is all running with pfctl -d
-Matt
Hi,
Not sure if multicast routing is related with this since it's a single host,
but check netstart(8) and search
Kapetanakis Giannis bilias at edu.physics.uoc.gr writes:
On 23/04/12 17:13, Matt Hamilton wrote:
So it appears there is somewhere a problem with multicast packets being
filtered out somewhere.
This is all running with pfctl -d
-Matt
Hi,
Not sure if multicast routing is
2012/4/19 Stuart Henderson s...@spacehopper.org:
I have now removed the trunking to see if that affected it, but no
joy. So I now have:
bnx0: flags=28843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NOINET6 mtu
1500
Don't know how you got to this state but I'm pretty sure this
interface should be
On 2012/04/20 08:54, Janne Johansson wrote:
Overall, this sounds like the missing arp issue in some regards.
That was specifically affecting 50+ carp interfaces with the same
physical parent interface (or iirc bridged vlans).
As for the recent threads about carps misbehaving, I had at least
2012/4/20 Stuart Henderson s...@spacehopper.org:
If you can Matt, try to set the carppeer option so it unicasts carp
status packets between the hosts over the vlans, and see if it helps.
The parent iface not being in promisc mode is likely to at least
break reception of packets destined for
David Goldsmith dgoldsmith at sans.org writes:
I believe the inet option is missing a 3rd component. After the
CARP IP and the netmask, you also need the 'last' IP for the subnet,
in your case it would be 213.133.66.71 (on both servers).
On our servers, we have something like:
inet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/19/2012 11:17 AM, Matt Hamilton wrote:
David Goldsmith dgoldsmith at sans.org writes:
I believe the inet option is missing a 3rd component. After
the CARP IP and the netmask, you also need the 'last' IP for the
subnet, in your case it
On 2012-04-19, Matt Hamilton ma...@netsight.co.uk wrote:
David Goldsmith dgoldsmith at sans.org writes:
I believe the inet option is missing a 3rd component. After the
CARP IP and the netmask, you also need the 'last' IP for the subnet,
in your case it would be 213.133.66.71 (on both
Hi All,
I'm in the process of setting up a pair of OpenBSD 5.0 boxes as
intra-vlan routers. Each one will be configured with approx 100
vlans. I'm just trying to test my setup at the moment, and
AFAICS the carp packets are not being sent :(
Here is the ifconfig outputs:
# ifconfig bnx0
Any ideas why this might be happening? I'm probably doing something
stupid, but can't spot it.
I forgot to add, that pf is disabled (pfctl -d) and if you didn't spot it in
the
previous message, all interfaces have -inet6 on them to get rid of inet6
in case that is an issue (I've read a few
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/18/2012 9:45 AM, Matt Hamilton wrote:
# ifconfig carp119 carp119:
flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 lladdr
00:00:5e:00:01:77 priority: 0 carp: MASTER carpdev vlan119 vhid 119
advbase 1 advskew 10 groups: carp status:
David Goldsmith dgoldsmith at sans.org writes:
Any ideas why this might be happening? I'm probably doing
something stupid, but can't spot it.
Please show the contents of the /etc/hostname.carp119 file on
both servers.
on box A:
# cat /etc/hostname.carp119
inet 213.133.66.67
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/18/2012 2:40 PM, Matt Hamilton wrote:
David Goldsmith dgoldsmith at sans.org writes:
Any ideas why this might be happening? I'm probably doing
something stupid, but can't spot it.
Please show the contents of the /etc/hostname.carp119
19 matches
Mail list logo
