Hi Stuart, Thank you for the reply!
Re jumbo frames - what do I need to do to do that on OpenBSD, if the underlying network supports it? Re: multiple networks. I've been thinking, what happens if I just set up multiple pfsync interfaces, on two different underlying interfaces? It's obviously duplicate traffic across the two networks, but surely the receiving end would just ignore the duplicates, whichever one was received second, because it would already have the state entry? Then if one of the networks goes down (or pfsync otherwise broke some how?), then it would still receive the other one. Would that work? Thanks! Ian On Sat, Mar 12, 2022 at 9:47 AM Stuart Henderson <[email protected]> wrote: > > Unsure but I have always used dedicated. For higher performance, jumbo > frames are helpful for the interface carrying pfsync traffic, so apart > from anything else if you didn't want jumbos on that linknet that's > probably a good enough reason in itself to split it. > > > > It looks like there is no facility for specifying multiple networks, so > > it will keep working in the event of a single link failure. Would it > > cause a problem to run two separate pfsync interfaces between the same > > hosts concurrently, over two separate links? > > I don't believe that's possible so link resilience would need to be done > at a lower level. If pfsync traffic is carried on physical interfaces > with usable link state, trunk or aggr interfaces would work, but it > doesn't seem like this will be a good fit for your use case. > >
