From: Jason Dixon (jasondixongroup.net)
Date: Tue Aug 01 2006 - 15:08:50 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Aug 1, 2006, at 4:00 PM, Tim Pushor wrote:

> Thanks a lot for replying. I am new to ethernet redudancy (and carp
> to boot) so I probably don't know what I'm talking about. We have a
> rack of servers that are now for the most part fully redundant. You
> can pull the plug on any box and nothing stops - almost. The
> ethernet switch is the last holdout.
>
> So now I am looking at adding ethernet redundancy to an already
> redundant firewall setup. So now instead of having 1 interface in,
> 1 interface out, and 1 interface pfsync, classically I'd need
> another 2 ports per server for redundancy. So I was thinking that
> instead of all this, I could run it all on vlans, if openbsd will
> do it.
>
> Am I wrong in thinking that I'd use a trunk(4) for a redundant
> ethernet connection? If not, then I was thinking that since the
> servers already have 2 gigabit ports on them (bge, from dell 850's)
> that I could run two vlan's each (one internal, one external), trunk
> (4) the vlans, then carp(4) the trunks.. Does that make sense? I'd
> still use the add-in card for pfsync.

Based on your description, it does appear that trunk(4) is what
you're looking for. I assumed you were trying to route between
segments, not providing fault tolerance. Sorry for hijacking the
thread.

--
Jason Dixon
DixonGroup Consulting
http://www.dixongroup.net

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]