-
Notifications
You must be signed in to change notification settings - Fork 0
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
[Discussion]: A couple questions #1
Comments
containerization tools use user namespaces too, but there isnt such a tool specifically designed for purpose of proxying like nsproxy.
they are not available on the registry so instead of making cargo pull the repos I'd rather make them submodules, which is better in terms of tracking code, etc. plus, I forked some of them.
here is the script i use daily sproxy new -m -v -t ./config.json ./browser.sh which creates a new namespace, and you can get a shell in the space, by |
Where's the config docs and do you have to leave a persistent namespace on the machine? |
docs are in the comments. configs are straight deserialized from files no namespaces persist across reboots iirc. you either have anonymous namespaces that disappear as the contained processes all exit, or some namespaces mounted on paths that persist during one boot. i pretty much have coded all the ways of doing the nsproxying thing in the repo. |
there are indeed note worthy details. like how DNS is handled, and what if your socks proxy only works with ipv6, etc. and you might need to fix tip, you may bind mount a file on that path in a mount namespace, to shadow the resolv.conf, (which nsproxy may create for you) the point of this tool is. when i initially started looking into this problem the code pasted from stackoverflow didnt work. it was close though. i worked out some details to make it work with various softwares, flatpak, appimage, etc. which are picky about the environment where they are run |
@planetoryd |
its up to whether your android system has network namespaces (as an optional feature of linux kernel). And if it does it needs to be ported. I'm not familiar with android systems sorry. the tool is mostly designed with use in a quite complete installation of a desktop linux system in mind, with or without gui. in any case, its just a lot of glue code doing the dirty work interfacing the user and system, which unavoidably tends to be specific. |
Hi, you have an amazing project.
There have been some small problems with it, but generally, it's great. I couldn't find any alternatives that used user namespaces instead of hijacking function calls (and as a result, supported UDP), and would really appreciate it if you could name some.
I was thinking of reading the code and adding some things that I like, but noticed that you use submodules instead of cargo packages, why?
And I recall using
-s SERVER -p PORT
in an old version, but it seems thatnsproxy
no longer recognizes that. What's the correct way to use it in the offhand way thatproxychains-ng
lets you to? i.e.,nsproxy ssh Y@X
.The text was updated successfully, but these errors were encountered: