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

Commit 4bba4665aa14429567194e20d47a16c577b3e2d0 is not published at crates.io #1

Closed
vi opened this issue May 22, 2017 · 5 comments
Closed

Comments

@vi
Copy link

vi commented May 22, 2017

So device enabling doesn't work with the version 0.1.

There should be 0.1.1 with the device enabling.

@meh
Copy link
Owner

meh commented May 22, 2017

I know, I wasn't done yet with other stuff, that's why I haven't published yet, sadly I haven't had time to work on it in the past few weeks.

Was going to add documentation and I was considering separating the interface handling stuff into a separate crate since all those bindings and wrappers for ioctls could be used on any other interface.

I can publish a 0.1.1 tomorrow if you need it, but stuff is probably going to change.

@vi
Copy link
Author

vi commented May 22, 2017

Also ability to split Read and Write parts and send one to another thread would be nice, to allow mio-less full duplex mode.

@meh
Copy link
Owner

meh commented May 22, 2017

Yeah that's also in the works, I just have to figure out the best way to go about it, since I also want to create a tap crate with an interface similar to this one, which means common traits between the two.

Just need to figure out how to split out the interface related stuff and the file descriptor related stuff so there's no pain adding support for more platforms.

@vi
Copy link
Author

vi commented May 22, 2017

Now I use a hack to get multi-threadable tun: let dev_copy = unsafe { ::std::fs::File::from_raw_fd(dev.as_raw_fd()) };

@meh
Copy link
Owner

meh commented May 27, 2017

Alright, there's tun::platform::Device::split() on Linux, and other configuration stuff, one change I needed and can't figure out how to make better is that IFF_NO_PI is not set now, but you can't change that flag after creating the device, so gotta figure out something to make that flag optional.

@meh meh closed this as completed May 27, 2017
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

2 participants