cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Knopf (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-10227) Can't accept remove connections using VirtualBox host-only adapter (Windows 10).
Date Mon, 31 Aug 2015 06:24:45 GMT


Paul Knopf commented on CASSANDRA-10227:

I am able to connect to the port if I use "simpleproxy" on the guest machine.

"simpleproxy -L :9043 -R"

Then, from the host, making a remove connection to "ip:9043", it works! I will be using this
for development at least. I really hope we can figure this out though.

> Can't accept remove connections using VirtualBox host-only adapter (Windows 10).
> --------------------------------------------------------------------------------
>                 Key: CASSANDRA-10227
>                 URL:
>             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.
- Not working
- Working
> 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. The "public network" vm works with remote access,
but the "host-only network" does not. Within each VM (ssh), I can succesfully connect to the
IP (either host-only or public) using cqlsh. So, Cassandra is setup and configured properly.
> I also added the VM logs for using both the public network adapter, and the host-only
> 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

View raw message