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.mcma...@oracle.com> wrote:
> Sounds like a native configuration issue all right. The native
> connect appears to be getting an
On Mon, Jun 1, 2015 at 4:46 PM, Bobby Bissett wrote:
> I *think* I have it set to allow anything. This is on the node where I'm
> running the test app:
>
But I get the same result after stopping ip6tables anyway:
[root@TWO test]}> service ip6tables stop
ip6tables: Setting
On Mon, Jun 1, 2015 at 4:45 PM, Vitaly Davidovich wrote:
> Is ip6tables running?
>
I *think* I have it set to allow anything. This is on the node where I'm
running the test app:
[root@TWO test]}> ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination
ACCEP
Hi all,
Can someone tell me how to diagnose this issue? I can't create a connection
to another node using IPv6 because of the error below -- a short app
demonstrates the problem. Everything I've found online so far is aimed at
using IPv4 instead, but that's not my goal. This is on a Centos 6.6 vir
