aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRobin H. Johnson <robbat2@gentoo.org>2013-08-23 18:04:28 -0700
committerRobin H. Johnson <robbat2@gentoo.org>2013-08-23 18:04:28 -0700
commitf0730199d43cd02e1b0a4b79707799bd377e1ae3 (patch)
tree5af27bf0b9b8b2b0ad3c2057dfe105ff9ec52276
parentCREDITS: give credit where due (diff)
downloadnetifrc-f0730199d43cd02e1b0a4b79707799bd377e1ae3.tar.gz
netifrc-f0730199d43cd02e1b0a4b79707799bd377e1ae3.tar.bz2
netifrc-f0730199d43cd02e1b0a4b79707799bd377e1ae3.zip
Other files to have.
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
-rw-r--r--README19
-rw-r--r--TODO14
2 files changed, 33 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..e7d8a94
--- /dev/null
+++ b/README
@@ -0,0 +1,19 @@
+netifrc README
+
+You should probably go and read the OpenRC README.
+
+netifrc is what was previously called 'oldnet' in OpenRC, and was the only
+networking system in Baselayout 1.x. This system has been around a very long
+time, at least as far back as September 2001 (that was the rc-scripts-1.1.5
+release).
+
+If you're interested in who contributed to this, please see the extensive
+CREDITS file.
+
+Reporting Bugs
+--------------
+Since Gentoo Linux is hosting OpenRC development, Bugs should go to
+the Gentoo Bugzilla:
+ http://bugs.gentoo.org/
+They should be filed under the "Gentoo Hosted Projects" product and
+the "netifrc" component.
diff --git a/TODO b/TODO
new file mode 100644
index 0000000..e19f27a
--- /dev/null
+++ b/TODO
@@ -0,0 +1,14 @@
+- Review setting of bridge configuration on dynamic interface add
+- _ifindex is not a reliable means of calculating metrics:
+ _ifindex is used for calculating metrics for new devices but has a major
+ problem: Since it's only the nth entry in /proc/net/dev
+ And devices may be removed from that file, and reordered, you won't always
+ get the same result.
+ If you do:
+ - add eth0 - _ifindex (eth0=0)
+ - add vlan1 - _ifindex (eth0=0,vlan1=1)
+ - add vlan2 - _ifindex (eth0=0,vlan1=1,vlan2=2)
+ - rem vlan1 - _ifindex (eth0=0,vlan2=1)
+ - add vlan3 - _ifindex (eth0=0,vlan2=1,vlan3=2)
+ Now your routing table has entries for both vlan2 and vlan3 with a metric of 2.
+