On 2022/03/12 22:05, Ian Chilton wrote: > 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?
"ifconfig <interface> mtu $number" (or "mtu $number" in /etc/hostname.if). "ifconfig <interface> hwfeatures" shows the max supported in "hardmtu". I'm not sure what if anything needs doing for the parent interface for vlans; I configure mtu on them as well but it might not be needed. > 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? Creating multiple pfsync devices isn't supported at all: # ifconfig pfsync1 create ifconfig: SIOCIFCREATE: Invalid argument It would also need something changed in PF so that states could be sent to multiple pfsync devices, I'm pretty sure this would be too complicated an approach. I don't know the code internals well enough to know how tricky it would be, but I would expect it to be simpler to allow multiple sync devices on one pfsync interface (this could have other uses, e.g. to allow multiple unicast endpoints).
