You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Paul Knopf (JIRA)" <ji...@apache.org> on 2015/08/30 19:40:45 UTC

[jira] [Created] (CASSANDRA-10227) Can't accept remove connections using VirtualBox host-only adapter (Windows 10).

Paul Knopf created CASSANDRA-10227:
--------------------------------------

             Summary: Can't accept remove connections using VirtualBox host-only adapter (Windows 10).
                 Key: CASSANDRA-10227
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10227
             Project: Cassandra
          Issue Type: Bug
            Reporter: Paul Knopf


Before I begin, I have created a simple project that reproduces this issue. It uses Vagrant (1.7.4) to dynamically setup the box for each network adapter.

 https://bitbucket.org/theonlylawislove/cassandrahostonlyadapter/commits/tag/network-host-only

 https://bitbucket.org/theonlylawislove/cassandrahostonlyadapter/commits/tag/network-public

Check out each tag, then run "vagrant up". This will setup the VM. Then run CassandraTest.exe on the host machine to test remote access.

I also added the VM logs for using both the public network adapter, and the host-only adapter.

Any guidance on this issue would be greatly appreciated.

I would like to add that I have successfully used other applications with host-only adapter on Windows 10, such as Redis and Postgres. There is something unique about Cassandra, and I am honestly not smart enough to figure it out. Something is definitely broken though :)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)