Date: Mon, 19 Jan 2004 12:58:00 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Maxim Konovalov <maxim@macomnet.ru> Cc: net@freebsd.org Subject: Re: Multihomed UDP server Message-ID: <92245.1074513480@critter.freebsd.dk> In-Reply-To: Your message of "Mon, 19 Jan 2004 14:39:20 %2B0300." <20040119143315.N81347@news1.macomnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20040119143315.N81347@news1.macomnet.ru>, Maxim Konovalov writes: >On Mon, 19 Jan 2004, 12:07+0100, Poul-Henning Kamp wrote: > >> Simple question: >> >> Very simple UDP server daemon. >> >> Many clients (connect(2)'ing a socket for each is not an option) >> >> Multihomed machine. >> >> What's the simple trick to replying with the same source-IP as the >> client used as destination-IP ? > >Probably bin/58012 worth to look (Multihomed tftpd enhancement). Yes, >it relies on protocol but still. But that's not a general solution, and it certainly doesn't solve the problem for my application. I'm considering ways to make sendmsg(2)/recvmsg(2) DTRT, and my current candidate is give them a flag bit which says "msg_name has both addresses". -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?92245.1074513480>