Skip to content
Browse files

some changes for new new netscript design

  • Loading branch information...
1 parent 69bd497 commit f3bc09da3762e278c58b2d8a8ee4db840adfb2f0 @danielrobbins danielrobbins committed Oct 16, 2009
View
0 basic/README → interfaces/basic/README
File renamed without changes.
View
5 basic/net.eth0 → interfaces/basic/netif.eth0
@@ -10,11 +10,6 @@ DOM=example.org
NS1=a.b.c.d
NS2=e.f.g.h
-depend() {
- provide net
- after net.lo
-}
-
start() {
ebegin "Bringing up network interface $INT"
ifconfig $INT $IP netmask $NM up && \
View
7 bond+bridge/README → interfaces/bond+bridge/README
@@ -3,11 +3,16 @@ eth4 and eth5 (let's assume this is an Intel PCI Express dual-port gigabit
adapter) are bonded, creating the "bond0" device, which is then added to the
br1 bridge. The br1 bridge is configured with an non-routeable IP. No DNS
information is associated with this network connection, so there is no call to
-resolvconf.
+resolvconf. (If you need to set up name servers, copy resolvconf lines from
+interfaces/basic/netif.eth0.)
We do not need to explicitly create a route for the network, since a network
route will be automatically created for br1 when we assign an IP address to it
(type "route -n" to verify).
Other network devices, such as OpenVZ or Xen virtual ethernet devices, can be
added to the bridge as well. The MTU for all interfaces is set to 9000 bytes.
+
+Note that the br1 bridge will use the lesser of all child interface MTUs as
+its MTU, so if you want the bridge to have a 9000 MTU, make sure all child
+devices added to the bridge have an MTU of 9000.
View
5 bond+bridge/net.bond0 → interfaces/bond+bridge/netif.bond0
@@ -5,11 +5,6 @@
INT="bond0"
SLAVES="eth4 eth5"
-depend() {
- provide net
- need net.lo
-}
-
start() {
ebegin "Bringing up bond $INT"
ifconfig $INT 0.0.0.0 up && \
View
4 bond+bridge/net.br1 → interfaces/bond+bridge/netif.br1
@@ -9,9 +9,7 @@ INT="$INT"
SLAVE=bond0
depend() {
- provide net
- need net.$SLAVE
- after net.lo vz
+ need netif.$SLAVE
}
start() {
View
0 bond/README → interfaces/bond/README
File renamed without changes.
View
5 bond/net.bond0 → interfaces/bond/netif.bond0
@@ -11,11 +11,6 @@ DOM=example.org
NS1=a.b.c.d
NS2=e.f.g.h
-depend() {
- provide net
- need net.lo
-}
-
start() {
ebegin "Bringing up bond $INT"
ifconfig $INT $IP netmask $NM up && \
View
3 bridge/README → interfaces/bridge/README
@@ -2,4 +2,5 @@ This network configuration shows how you might create a bridge, and assign a
routeable IP address to it. Then, you would add eth0 to the bridge. Other
interfaces, such as OpenVZ or Xen virtual ethernet devices, could be added to
the bridge as well, allowing them to access the Internet. This can be done
-dynamically by typing "brctl addif br0 veth100.0", for example.
+dynamically by typing "brctl addif br0 veth100.0", for example, in the case
+of OpenVZ with "veth" virtual interfaces.
View
4 bridge/net.br0 → interfaces/bridge/netif.br0
@@ -13,11 +13,9 @@ NS1=a.b.c.d
NS2=e.f.g.h
depend() {
- provide net
- after net.lo vz
for SLAVE in $SLAVES
do
- need net.$SLAVE
+ need netif.$SLAVE
done
}
View
5 bridge/net.eth0 → interfaces/bridge/netif.eth0
@@ -4,11 +4,6 @@
INT=eth0
-depend() {
- provide net
- after net.lo
-}
-
start() {
ebegin "Bringing up network interface $INT"
ifconfig $INT 0.0.0.0 up

0 comments on commit f3bc09d

Please sign in to comment.
Something went wrong with that request. Please try again.