From owner-freebsd-net@FreeBSD.ORG  Wed Jun 17 13:16:43 2015
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 3E1A1D3F
 for <freebsd-net@hub.freebsd.org>; Wed, 17 Jun 2015 13:16:43 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 28CDDC54
 for <freebsd-net@FreeBSD.org>; Wed, 17 Jun 2015 13:16:43 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5H7wBW2095545
 for <freebsd-net@FreeBSD.org>; Wed, 17 Jun 2015 07:58:11 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 200379] SCTP stack is not FIB aware
Date: Wed, 17 Jun 2015 07:58:12 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: tuexen@freebsd.org
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: tuexen@freebsd.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200379-2472-pYlj0m3lul@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200379-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-200379-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Jun 2015 13:16:43 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200379

--- Comment #14 from Michael Tuexen <tuexen@freebsd.org> ---
(In reply to Alan Somers from comment #13)
I think interfaces can assign fibs to packets, it is a field in the mbuf packet
header. It makes sense to use this information in case you have no socket to
get the fib from (for example when receiving a TCP SYN and you have no
listening socket).

An SCTP end-point can have multiple IP addresses. When using multihoming you
use multiple local and remote IP-addresses to provide network fault tolerant.
So you use multiple local interfaces and route traffic on all of them to be
able to fail over in case of network problems. Of course you can setup this in
a single routing table and have a socket in a single fib. I'm tending to
implement it this way. This also means that for response packets (like acks for
data) use the socket's fib, not the one from the incoming packet. At least this
is conceptually simpler. Codewise it doesn't make much of a difference.

Thanks for your feedback.

Best regards
Michael

-- 
You are receiving this mail because:
You are on the CC list for the bug.