/etc/hostname.em0: up mtu 9000 /etc/hostname.em1 up mtu 9000
/etc/hostname.trunk0 trunkproto lacp trunkport em0 trunkport em1 10.10.10.10 netmask 255.255.255.0 -inet6 mtu 9000 "mtu 9000" in hostname.trunk0 probably not needed as it will get its' correct mtu from em0. //mxb On 09/18/2012 10:04 AM, Scott wrote: > On 18 September 2012 03:47, mxb <m...@alumni.chalmers.se> wrote: >> Yes you can, but the real hw has to support it as well. >> >> On 09/18/2012 02:34 AM, S. Scott wrote: >>> Is it possible to use non-standard (1500) MTU on a trunk(4) >>> pseudo-interface or on the real em(4) interfaces that comprise the >>> trunk0 interface, or on the VLANs carried therein. We'd like to use >>> jumbo frames on the link-aggregate between a Cisco catalyst switch >>> (port group) and the openBSD router and firewall. >>> >>> $ uname -a >>> 5.1 GENERIC.MP#207 amd64 >>> >>> With thanks, >>> >>> ————— >>> iThing: Big thumbs & little keys. Please excuse typo, spelling and >>> grammar errors • Good planets are hard to find – think before you >>> print • My desire to be well-informed is currently at odds with my >>> desire to remain sane. • Last night I played a blank CD at full blast. >>> The Mime next door went nuts. >> > > Could you please explain how. > > ifconfig trunk0 mtu nnnn, where nnnn > 1500 results in the error, > > ifconfig: SIOCSIFMTU: Invalid argument > > em(4) hardware does support jumbo's (nnnn > 1500)
