vtun | A simple VPN written in Go | VPN library

by net-byte Go Version: v1.7.0 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | vtun Summary

vtun is a Go library typically used in Networking, VPN applications. vtun has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

A simple VPN written in golang.

Support

Quality

Security

License

Reuse

Support

vtun has a low active ecosystem.

It has 648 star(s) with 124 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 44 have been closed. On average issues are closed in 17 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of vtun is v1.7.0

Quality

vtun has 0 bugs and 0 code smells.

Security

vtun has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

vtun code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

vtun is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

vtun releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

It has 873 lines of code, 39 functions and 13 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of vtun

Get all kandi verified functions for this library.

vtun Key Features

No Key Features are available at this moment for vtun.

vtun Examples and Code Snippets

No Code Snippets are available at this moment for vtun.

Community Discussions

Trending Discussions on vtun

Should the kernel pass data from a tap interface to an application listening on INADDR_ANY?

Launching Docker containers with arguments using Python3

QUESTION

Should the kernel pass data from a tap interface to an application listening on INADDR_ANY?

Asked 2020-Sep-25 at 12:29

I have an application that creates, listens on and writes to a tap interface. The software will read(tun_fd,...) and perform some action on that data, and it will return data to the system as UDP packets via write(tun_fd,...).

I assign an IP to the interface, 10.10.10.10\24 so that a socket application can bind to it and so that the kernel will pass any packets for the virtual subnet to the tap interface.

The software generate frames with IP/UDP packets with the destination IP being that assigned to the interface, and a source IP existing in the same subnet. The source and dest mac address match that of the tap device. Those frames are written back to the kernel with write(tun_fd,...).

If I open said tap interface in wireshark I will see my frames/packets as I expect to, properly formatted, expected ports, expected macs and IPs. But if I try to read those packets with netcat -lvu 0.0.0.0 ${MY_UDP_PORT} I don't see anything.

Is this expected behavior?

Update 1

INADDR_ANY is a red herring. I have the problem even when explicitly binding to an interface / port as in this pseudo code:

...

ANSWER

Answered 2020-Sep-25 at 12:29

Yes, data written into the tuntap device via write(tun_fd...) should get passed to the kernel protocol stack and distributed to listening sockets with matching packet information just like the frame had arrived over a wire attached to a physical ethernet device.

It requires that the packets be properly formed (IP checksum is good, UDP checksum is good or 0). It requires that the kernel know how to handle the packet (is there an interface on the system with a matching destination IP?). If it's a tap device it may also require that your application is properly ARP'ing (although this might not be necessary for a 'received' packet from the perspective of a socket application listening to an address assigned to the tap device).

In my case the problem was silly. While I had turned on UDP checksum verification in wireshark I forgot to turn on IP header verification. An extra byteswap was breaking that checksum. After fixing that I was immediately able to see packets written into the TAP device in a socket application listening on the address assigned to that interface.

Source https://stackoverflow.com/questions/63996520

QUESTION

Launching Docker containers with arguments using Python3

Asked 2020-Jan-16 at 13:10

I have a Python3 application launching inside a Docker container; and when the Docker container is launched, it accepts arguments that are passed to the Python3 application. Pretty straight forward and works well.

The Dockerfile :

...

ANSWER

Answered 2020-Jan-15 at 06:11

the image name should be sperated from the reset of arguments :

Source https://stackoverflow.com/questions/59745286

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install vtun

Add TLS for websocket,reverse proxy server(3001) via nginx/caddy(443). Enable IP forwarding on server.
Add TLS for websocket,reverse proxy server(3001) via nginx/caddy(443)
Enable IP forwarding on server

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: