"Permission denied" using socket with IPv6

[Bernd Eckenfels]

Hello,

The reason the IPv6 Stack requires you to specify the interface for a link local address is because such an address has no identifying prefix (since the link local network prefix is the same for all interfaces and therefore the Is no entry in the forwarding information base (routing table).

The EPERM is a rather unfortunate choice for that illegal (missing) argument. In some conditions - (especially older OS kernels) it worked if you had only one global interface.

Gross
Bernd

> Am 02.06.2015 um 17:58 schrieb Bobby Bissett <bbissett at gmail.com>:
> 
> Whoo-hoo! With these two bits of info and some time with my network guru, I can finally connect. Info below:
> 
>> On Tue, Jun 2, 2015 at 5:09 AM, Michael McMahon <michael.x.mcmahon at oracle.com> wrote:
>> Sounds like a native configuration issue all right. The native
>> connect appears to be getting an EPERM which according to Linux manpage
>> could be caused b a local firewall rule
> 
>> On Mon, Jun 1, 2015 at 10:22 PM, Bernd <ecki at zusammenkunft.net> wrote:
>> For a Link-Local Address you might need to define the device scope with the % suffix. If you cant specify that in your software, you can use a /etc/host entry.
>> 
> 
> Things weren't working for me despite stopping NetworkManager and ip6tables, but the combo of stopping those *and* creating a proper global address for both machines instead of a link-local address means I can connect fine now. I'm not sure I want to try going back to the link-local based on info from my network admin.
> 
> Thanks everyone for the suggestions. Once I wrap my head around what actually happened (and try this with centos 7 using nmtui) will write up the details and can share with this list.
> 
> Thank you again,
> Bobby
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/net-dev/attachments/20150602/fc93e94f/attachment.html>