Ok, managed to get back on the box for a little more troubleshooting!
Interesting part is that there's no traffic on the carp pseudo interface
although the machine certainly knows about it as it responds to the arp.  I
tried setting an ip address on the vlan30 interface but there was no change
in the dump traffic behaviour.
How come traffic leaving a vlan device isn't being encapsulated?  Is the
unencapsulated packet showing up on the trunk1 device through some other
path?  Any comments?

Here's some dump traffic:
Nothing from : carp3 carp2 carp1 vlan20 vlan10
vlan30
05:32:37.664607 arp who-has 1.1.1.189 tell 1.1.1.188
05:32:37.664621 arp reply 1.1.1.189 is-at 00:00:5e:00:01:04
trunk1
05:32:37.664603 802.1Q vid 30 pri 0 arp who-has 1.1.1.189 tell 1.1.1.188
05:32:37.664626 arp reply 1.1.1.189 is-at 00:00:5e:00:01:04
nfe1
05:32:37.664599 802.1Q vid 30 pri 0 arp who-has 1.1.1.189 tell 1.1.1.188
05:32:37.664631 arp reply 1.1.1.189 is-at 00:00:5e:00:01:04

The pertinent routing:
Destination        Gateway            Flags    Refs      Use    Mtu
Interface
1.1.1.184/29  1.1.1.189     U           1      539      -   carp3
1.1.1.189     1.1.1.189     UH          0        2      -   carp3

And some configuration files (again):
/etc/hostname.carp1:inet 2.2.2.246 255.255.255.248 2.2.2.247 vhid 2 carpdev
vlan10 pass password advbase 1 advskew 0 down
/etc/hostname.carp2:inet 2.2.2.254 255.255.255.248 2.2.2.255 vhid 3 carpdev
vlan20 pass password advbase 1 advskew 0
/etc/hostname.carp3:inet 1.1.1.189 255.255.255.248 1.1.1.191 vhid 4 carpdev
vlan30 pass password advbase 1 advskew 0
/etc/hostname.nfe0:up
/etc/hostname.nfe1:up
/etc/hostname.trunk1:trunkproto failover trunkport nfe0 trunkport nfe1 up
/etc/hostname.vlan10:vlan 10 vlandev trunk1 up
/etc/hostname.vlan20:vlan 20 vlandev trunk1 up
/etc/hostname.vlan30:vlan 30 vlandev trunk1 up

I'm running a Generic kernel on an amd64 save for RAID being enabled.

Reply via email to