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

systemd can do most of this by itself now #30

Open
ad90df8e708e8fa8153e56a059 opened this issue Apr 20, 2017 · 0 comments
Open

systemd can do most of this by itself now #30

ad90df8e708e8fa8153e56a059 opened this issue Apr 20, 2017 · 0 comments

Comments

@ad90df8e708e8fa8153e56a059
Copy link
Contributor

ad90df8e708e8fa8153e56a059 commented Apr 20, 2017

The current default systemd can handle setting up your local network, serve local DHCP client IPs, and do DNS by just configuring /etc/systemd/network/eth0.network file:
[Match]
Name=eth0
[Network]
Address=172.16.0.1/16
DHCPServer=yes
[DHCPServer]
DNS=172.16.0.1
EmitDNS=yes

Then you can install iptables and tor with the same configs and it works. You can write an eth1.network file to handle the public connection similarly.

All you need to install is tor and iptables with the same configs. It makes things a lot simpler and I'm happy to submit a pull request, but I don't know if trusting systemd with that much of the networking stuff is the best idea as people have strong feelings about it.

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

1 participant