-
Notifications
You must be signed in to change notification settings - Fork 75
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
Constant No route to host while running the Windows version #5
Comments
Are you able to ping your server? |
Hi friedrich, Thanks for taking time and replying to my post! I can only ping my server if I use the "-r" parameter while starting hans as I have disabled the server from responding to ICMP requests, but it doesn't matter if I enable or disable it, the same error keeps repeating for around 1-2 seconds then nothing else appears in my Windows command prompt. What do you think the problem is? Thanks again! |
I am not sure if I understand your reply correctly. Could you paste the output of the commands "route print", "ipconfig /all" and "ping YOURSERVER". |
I meant that it keeps outputting the "no route to host" error message for 2 seconds then it doesn't output anything else. Here's the output you requested, I'm connected to my USB Modem (Profile name: Etisalat Internet) and the TAP driver is not used by any processes:
|
Hi,
I keep receiving the following message from the Windows client when trying to connect to a server that is running hans as well.
hans: error sending icmp packet: No route to host
This message is repeated 34 times and then the output stops. Is this a bug with the Windows version? or did I miss something while setting up hans? Here's the full output I receive
hans: opened tunnel device: Local Area Connection 2
Ok.
hans: connection established
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
hans: error sending icmp packet: No route to host
^C
hans: SIGINT received
hans: select: Interrupted system call
The text was updated successfully, but these errors were encountered: