> Currently we set up our routes and IP aliasing in init.d / network and > network config. They look like the following: > init.d /network configuration: > ip addr add 192.168.128.1/24 brd + dev eth2 label eth2 label eth2:extra_sub1 > ip addr add 207.195.73.2/26 brd + dev eth2 label eth2 label eth2:extra_sub2 > ip addr add 207.195.73.65/26 brd + dev eth2 label eth2 label eth2:extra_sub3 > ip route add 192.168.129/24 via 192.168.131.2 > ip route add 192.168.129.128/26 via 192.168.131.2 > ip route add 207.195.73.128/26 via 192.168.131.2 > ip route add 192.168.140/24 via 192.168.131.2 > ip route add 192.168.132/24 via 192.168.131.2 > > > This is the relevant info from network conf. > Network config: > eth0_IPADDR= 192.168.131.1 > eth0_MASKLEN=24 > eth0_BROADCAST=192.168.131.255 > +++++++++++++++++++++++++++++++++++++++++++++++ > eth1_IPADDR= 192.168.127.2 > eth1_MASKLEN=24 > eth1_BROADCAST=192.168.127.255 > +++++++++++++++++++++++++++++++++++++++++++++++ > eth2_IPADDR=207.195.73.65 > eth2_MASKLEN=26 > eth2_BROADCAST=207.195.73.127 > eth2_IP_SHARED_MEDIA=YES > ++++++++++++++++++++++++++++++++++++++++++++++++ > > I would like to set up our routes in the network config. I need to > know how that is done. I would like to add my routes using eth2_ROUTES= and > add my addresses using eth2_IP_EXTRA_ADDRS= . The problem is that I don't > know how to do this. Can you please explain how this would be done. In the > example they show the following: > > eth2_IP_EXTRA_ADDRS="192.168.1.193 192.168.2.1/24" (What does the first ip > represent?)
The first IP is an entry on the same subnet as the primary IP assigned to the interface, so it doesn't need a network mask (inherited from the existing settings). The second entry assigns an IP on an entirely different subnet, so a masklength is required to correctly generate a route to that network, determine broadcast IP, etc... > eth2_ROUTES="1.1.1.13 2.2.2.0/24_via_1.1.1.18" (What does the first ip > represent?) A host route to ip 1.1.1.13 out dev eth2. This is useful when running proxy-arp, and you need to control via routing which IP's are on which side of the router. The second entry is a more typical static route... > The KISS principle seems to be my goal here. I think this could be > done allot simpler than the way we are currently doing it by using the > network config to add our routes and extra ip's I think once I understand > the proper syntax for the network config lines I will be far better off. Please use the leaf-user list for support questions...see the support page on my website. Details of exactly what happens can be determined by examining the if_up procedure in /etc/network.conf. You can use network.conf to configure everything you're doing manually, except for labeling the extra interfaces, which is currently not handled by the automatic scripts. Basically, the scripts do an "ip address add" for each entry in <iface>_IP_EXTRA_ADDRS, and an "ip route add" for every entry in <iface>_ROUTES. Charles Steinkuehler http://lrp.steinkuehler.net http://c0wz.steinkuehler.net (lrp.c0wz.com mirror) _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
