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

curvetun: No traffic on TUN dev #117

Open
heri16 opened this Issue Apr 14, 2014 · 2 comments

Comments

Projects
None yet
3 participants
@heri16

heri16 commented Apr 14, 2014

I was able to follow the curvetun README exactly and get curvetun compiled with libsodium and running.

However, no RX traffic flows through the device. I am unable to ping as ping just hangs...

I have tried using netcat and socat to test the underlying connection and firewall and it is fine.

Here is my syslog:

Server:
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun server booting!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun on IPv4 via UDP on port 655!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: Allowed overlay proto is IPv4!
Apr 14 08:48:52 ecc-dev1 kernel: curves0: Disabled Privacy Extensions
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU0 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU2 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU3 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU0 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU2 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU3 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU1 up!
Apr 14 08:48:52 ecc-dev1 curvetun[16047]: curvetun thread on CPU1 up!
Apr 14 08:48:53 ecc-dev1 curvetun[16047]: curvetun up and running!

Client:
Apr 14 15:49:50 devops2 curvetun[15608]: curvetun client booting!
Apr 14 15:49:50 devops2 curvetun[15608]: curvetun client ready!

@heri16

This comment has been minimized.

Show comment
Hide comment
@heri16

heri16 Apr 14, 2014

Now I am getting these logs:

Server:
Apr 14 19:13:08 devops1 curvetun[3413]: Got initial userhash from remote end!
Apr 14 19:13:08 devops1 curvetun[3413]: Got good packet hmac!
Apr 14 19:13:08 devops1 curvetun[3413]: User not found! Dropping connection!
Apr 14 19:13:09 devops1 curvetun[3413]: Got initial userhash from remote end!
Apr 14 19:13:09 devops1 curvetun[3413]: Got good packet hmac!
Apr 14 19:13:09 devops1 curvetun[3413]: User not found! Dropping connection!

Client:
Apr 14 18:58:57 devops2 curvetun[2128]: curvetun connection retry attempt!
Apr 14 18:58:58 devops2 curvetun[2128]: curvetun client ready!
Apr 14 18:58:58 devops2 curvetun[2128]: curvetun client prepare shut down!
Apr 14 18:58:58 devops2 curvetun[2128]: curvetun connection retry attempt!
Apr 14 18:58:59 devops2 curvetun[2128]: curvetun client ready!
Apr 14 18:58:59 devops2 curvetun[2128]: curvetun client prepare shut down!
Apr 14 18:58:59 devops2 curvetun[2128]: curvetun connection retry attempt!

heri16 commented Apr 14, 2014

Now I am getting these logs:

Server:
Apr 14 19:13:08 devops1 curvetun[3413]: Got initial userhash from remote end!
Apr 14 19:13:08 devops1 curvetun[3413]: Got good packet hmac!
Apr 14 19:13:08 devops1 curvetun[3413]: User not found! Dropping connection!
Apr 14 19:13:09 devops1 curvetun[3413]: Got initial userhash from remote end!
Apr 14 19:13:09 devops1 curvetun[3413]: Got good packet hmac!
Apr 14 19:13:09 devops1 curvetun[3413]: User not found! Dropping connection!

Client:
Apr 14 18:58:57 devops2 curvetun[2128]: curvetun connection retry attempt!
Apr 14 18:58:58 devops2 curvetun[2128]: curvetun client ready!
Apr 14 18:58:58 devops2 curvetun[2128]: curvetun client prepare shut down!
Apr 14 18:58:58 devops2 curvetun[2128]: curvetun connection retry attempt!
Apr 14 18:58:59 devops2 curvetun[2128]: curvetun client ready!
Apr 14 18:58:59 devops2 curvetun[2128]: curvetun client prepare shut down!
Apr 14 18:58:59 devops2 curvetun[2128]: curvetun connection retry attempt!

@zoobab

This comment has been minimized.

Show comment
Hide comment
@zoobab

zoobab Apr 21, 2015

I got the same error, compiled the HEAD of trunk of today, and those errors are gone.

zoobab commented Apr 21, 2015

I got the same error, compiled the HEAD of trunk of today, and those errors are gone.

@tklauser tklauser added the bug label Oct 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment