Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.4.1-37631-1513708758-1002.46084-0-0@isc.org>
Content-Transfer-Encoding: binary
In-Reply-To: <rt-4.4.1-21856-1513707459-1970.46084-0-0@isc.org>
X-RT-Interface: Web
X-Mailer: MIME-tools 5.508 (Entity 5.508)
MIME-Version: 1.0
X-RT-Original-Encoding: utf-8
References: <1506206488416.71351@kuleuven.be> <RT-Ticket-46084@isc.org>
 <rt-4.4.1-21856-1513675576-484.46084-0-0@isc.org>
 <rt-4.4.1-37631-1513683621-432.46084-0-0@isc.org>
 <rt-4.4.1-21856-1513699626-1972.46084-0-0@isc.org>
 <rt-4.4.1-21856-1513707459-1970.46084-0-0@isc.org>
Content-Disposition: inline
RT-Send-CC:
Content-Length: 1042

On Tue Dec 19 18:17:39 2017, tmark wrote:
> On Tue Dec 19 16:07:06 2017, fdupont wrote:
> > Done. Ready for review.
> 
> I made some minor wording changes to the man page, so please pull.
> 
> The code looks ok.  I tested it using two Centos VMs.  local-address
> by itself worked fine, the src value was indeed the address I
> specified, 3002::30.  This is the address on the interface the server
> was listening upon.

=> note no check is done for the address so if you put a junk
value you likely get an error.

> However, when I enabled bind-local-address, the
> client stopped get server replies, nor did they show under pcap for
> the server interface.
> 
> It's probably something in my environment, how did you test this?

=> I verified the socket was correctly bound by lsof. Note
it is likely not compatible with multicast so with 2 VMs it becomes
very system dependent so I am not surprised it fails with CentOS.
Did the server get solicits/requests? I am afraid this kind of setup
requires a relay: same than for local-address...