Dmitry Morozovsky
2013-Mar-04 22:49 UTC
carp on stable/9: is there a way to keep jumbo? (fwd)
Collegaues, sorry, sent to the wrong list (the only escuse for me is possibly that I'm trying to make HAST base on carp...) -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck at FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru *** ------------------------------------------------------------------------ ---------- Forwarded message ---------- Date: Tue, 5 Mar 2013 02:31:51 From: Dmitry Morozovsky <marck at rinet.ru> To: freebsd-fs at freebsd.org Subject: carp on stable/9: is there a way to keep jumbo? Dear collesagues, yes, I know glebius@ overhauled carp in -current, but I'm a bit nervous to deploy bleeding edge system on a NAS/SAN ;) So, my question is about current state of carp in stable/9: building HA pair I found that carp interfaces lose jumbo capabilities: root at cthulhu4:~# ifconfig | grep mtu em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000 em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384 lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> metric 0 mtu 9000 carp0: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500 carp1: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500 root at cthulhu4:~# ifconfig carp1 mtu 9000 ifconfig: ioctl (set mtu): Invalid argument Is it unavoidable at the moment, or am I missing something obvious? Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: marck at FreeBSD.org ] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru *** ------------------------------------------------------------------------ _______________________________________________ freebsd-fs at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-fs To unsubscribe, send any mail to "freebsd-fs-unsubscribe at freebsd.org"
Steven Hartland
2013-Mar-05 01:21 UTC
carp on stable/9: is there a way to keep jumbo? (fwd)
You might want to try:-
http://blog.multiplay.co.uk/dropzone/freebsd/carp-mtu.patch
Be warned it doesn't do any validation so if you use it against physical
interfaces with a smaller MTU things will likely go badly wrong, hell
they may go badly wrong anyway as its just a very quick and dirty hack ;-)
Regards
Steve
----- Original Message -----
From: "Dmitry Morozovsky" <marck at rinet.ru>
To: <freebsd-stable at FreeBSD.org>
Sent: Monday, March 04, 2013 10:49 PM
Subject: carp on stable/9: is there a way to keep jumbo? (fwd)
> Collegaues,
>
> sorry, sent to the wrong list (the only escuse for me is possibly that
I'm
> trying to make HAST base on carp...)
>
> --
> Sincerely,
> D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
> [ FreeBSD committer: marck at FreeBSD.org ]
> ------------------------------------------------------------------------
> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
> ------------------------------------------------------------------------
>
> ---------- Forwarded message ----------
> Date: Tue, 5 Mar 2013 02:31:51
> From: Dmitry Morozovsky <marck at rinet.ru>
> To: freebsd-fs at freebsd.org
> Subject: carp on stable/9: is there a way to keep jumbo?
>
> Dear collesagues,
>
> yes, I know glebius@ overhauled carp in -current, but I'm a bit nervous
to
> deploy bleeding edge system on a NAS/SAN ;)
>
> So, my question is about current state of carp in stable/9: building HA
pair I
> found that carp interfaces lose jumbo capabilities:
>
> root at cthulhu4:~# ifconfig | grep mtu
> em0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 9000
> em1: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 9000
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
> lagg0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 9000
> carp0: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
> carp1: flags=49<UP,LOOPBACK,RUNNING> metric 0 mtu 1500
> root at cthulhu4:~# ifconfig carp1 mtu 9000
> ifconfig: ioctl (set mtu): Invalid argument
>
> Is it unavoidable at the moment, or am I missing something obvious?
>
> Thanks!
>
> --
> Sincerely,
> D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
> [ FreeBSD committer: marck at FreeBSD.org ]
> ------------------------------------------------------------------------
> *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
> ------------------------------------------------------------------------
> _______________________________________________
> freebsd-fs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-fs
> To unsubscribe, send any mail to "freebsd-fs-unsubscribe at
freebsd.org"
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
>
===============================================This e.mail is private and
confidential between Multiplay (UK) Ltd. and the person or entity to whom it is
addressed. In the event of misdirection, the recipient is prohibited from using,
copying, printing or otherwise disseminating it or any information contained in
it.
In the event of misdirection, illegible or incomplete transmission please
telephone +44 845 868 1337
or return the E.mail to postmaster at multiplay.co.uk.