Date: 21 Mar 2013 02:14:04 +0000 From: "Mark D" <markd-freebsd-net@bushwire.net> To: freebsd-net@FreeBSD.org Subject: Re: Best way for an app to accept traffic on 30,000+ interfaces? Message-ID: <20130321021404.98962.qmail@f5-external.bushwire.net> In-Reply-To: <CACVs6=94Trc8vtey8PhPyugsntccCX0mL-uCX2JRJeAZDPZbtQ@mail.gmail.com> References: <20130321005959.98706.qmail@f5-external.bushwire.net> <CACVs6=94Trc8vtey8PhPyugsntccCX0mL-uCX2JRJeAZDPZbtQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20Mar13, Juli Mallett allegedly wrote: > Well, the easiest thing is to add 30k aliases to your Ethernet > interface (you may hit a limit, not sure) and then just listen on > INADDR_ANY (or the IP6 equivalent), assuming you don't mind listening > to other addresses you have configured as well. The application can > always decide to close an incoming connection that wasn't going to one > of those 30k IP addresses. Agreed that INADDR_ANY will fix the socket count. But what of the interface/alias count? Is 300K ok? How about 3M aliases? I'll spin up an instance and try it out, but I'm a little worried that there might be something non-linear or some threshold limit that won't necessarily be exposed by a modicum of adhoc testing. Mark.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130321021404.98962.qmail>