Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cascaded setup - "recv(): No route to host, closing connection" #201

Open
salakis opened this issue May 2, 2016 · 0 comments
Open

Cascaded setup - "recv(): No route to host, closing connection" #201

salakis opened this issue May 2, 2016 · 0 comments

Comments

@salakis
Copy link

salakis commented May 2, 2016

I have a rather bizarre, but in my case required setup with two instances of sniproxy running behind each other (basically: client[ipv4 only]<-->sniproxy1[dual-stack]<-->sniproxy2[ipv6 only]<-->target host).
So far this sort of works, but I often get an error message with "empty response" when pulling data through this cascaded sniproxy setup.

I switched the error logging to debug and it is filled with

2016-05-02 20:57:48 recv(): No route to host, closing connection

2016-05-02 20:58:33 recv(): No route to host, closing connection

2016-05-02 20:59:09 recv(): No route to host, closing connection

2016-05-02 20:59:09 recv(): No route to host, closing connection

The two servers are not on the same subnet and there is a latency of about 100ms between them.

Is there any way to get this fixed? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant