Date: Wed, 17 Jun 2015 07:58:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 200379] SCTP stack is not FIB aware 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200379-2472-pYlj0m3lul>