On Mon, 19 Jan 2004, Randall R. Stewart (home) wrote:
> One of the problems I think that is fundamental to BSD and multi-homing
> is the lack of supports for multiple-default routes. And even in O/S's
there's a patch to FreeBSD 4.8 which adds multipath support at
http://www.dsm.fordham.edu/~tanz
Poul-Henning Kamp wrote:
In message <[EMAIL PROTECTED]>, 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 si
On Mon, 19 Jan 2004, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Garrett Wollman
> writes:
> >< said:
> >
> >> 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".
> >
> >Um, th
In message <[EMAIL PROTECTED]>, "Bjo
ern A. Zeeb" writes:
>You mean for FreeBSD or in ISBN 0-13-490012-X ?
>
>For FreeBSD it is man 4 ip:
>
>--- cite ---
> If the IP_RECVDSTADDR option is enabled on a SOCK_DGRAM socket, the
> recvmsg(2) call will return the destination IP address for a UDP
In message <[EMAIL PROTECTED]>, Garrett Wollman
writes:
>< said:
>
>> 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".
>
>Um, they already do the right thing. That's what the IP_RECVDESTADDR
>
< said:
> 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".
Um, they already do the right thing. That's what the IP_RECVDESTADDR
option (and its dual whose name I forget right now) is all about.
In message <[EMAIL PROTECTED]>, "Randall R. Stewart (home)
" 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.
In message <[EMAIL PROTECTED]>, 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 tric
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 desti
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 ?
Notice I said "simple", monitoring the routetable or polling
10 matches
Mail list logo
