Historic archive of defunct list bloat-devel@lists.bufferbloat.net
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat-devel <bloat-devel@lists.bufferbloat.net>
Subject: openssh over ipv6 breakage
Date: Tue, 9 Aug 2011 09:15:41 -0600	[thread overview]
Message-ID: <CAA93jw7hVDuQHK5ZnQ8Dw+kQ62Hpxqr2Zwee5Q0_14p+E6g1rw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

I was wondering why interactive openssh was odd over ipv6.

Now I need not know any longer. From openssh/packet.c:

static void
packet_set_tos(int tos)
{
#if defined(IP_TOS) && !defined(IP_TOS_IS_BROKEN)
        if (!packet_connection_is_on_socket() ||
            !packet_connection_is_ipv4())
                return;
        debug3("%s: set IP_TOS 0x%02x", __func__, tos);
        if (setsockopt(active_state->connection_in, IPPROTO_IP, IP_TOS,
&tos,
            sizeof(tos)) < 0)
                error("setsockopt IP_TOS %d: %.100s:",
                    tos, strerror(errno));
#endif
}


-- void
packet_set_interactive(int interactive, int qos_interactive, int qos_bulk)
{
        if (active_state->set_interactive_called)
                return;
        active_state->set_interactive_called = 1;

        /* Record that we are in interactive mode. */
        active_state->interactive_mode = interactive;

        /* Only set socket options if using a socket.  */
        if (!packet_connection_is_on_socket())
                return;
        set_nodelay(active_state->connection_in);
        packet_set_tos(interactive ? qos_interactive : qos_bulk);
}


Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com

[-- Attachment #2: Type: text/html, Size: 1498 bytes --]

                 reply	other threads:[~2011-08-09 14:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw7hVDuQHK5ZnQ8Dw+kQ62Hpxqr2Zwee5Q0_14p+E6g1rw@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bloat-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox