From e9ceb5e199380e8bede31a091f423e4bcbc46458 Mon Sep 17 00:00:00 2001 From: Robby Workman Date: Sat, 7 Jan 2017 20:34:38 -0600 Subject: README: Additional notes --- README | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/README b/README index 5fa958b..9cd7f39 100644 --- a/README +++ b/README @@ -2,6 +2,8 @@ Greetings, Slackers! Let's look into migrating Slackware's net config to use iproute2! +This document is/will be useful: http://baturin.org/docs/iproute2/ + To prevent multiple people trying to push changes to master branch, please make changes in a user branch, push them, and I'll merge, or make a diff and send it to me. @@ -9,3 +11,27 @@ or make a diff and send it to me. Before production use and/or heavy testing, grep through for any instances of "TODO" and fix them :-) +TODO: + +There's plenty of room for refactoring and even rewriting here, such +as supporting addition of tun/tap devices for adding to bridges or +using for VPNs, supporting IPv6, etcetera. However, primary focus thus +far is to simply duplicate existing functionality and make sure it all +works as expected. Once that's confirmed, we can reassess where to go +from there. + +I've got one host here (no tests run on this host though) that shows +the loopback interface in state UNKNOWN: + 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1 + link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 +No idea how common this is, but perhaps a slight change of the loopback +checking logic is needed... + +Tested successfully so far: + * dhcp configuration of one interface + * static configuration of one interface + * bridge with four interfaces (eth0, tap1, tap2, tap3) with static + IP address; I created the tap interfaces manually in rc.modules.local + since there's currently no support for creating them in the network + scripts + -- cgit v1.2.3