On 10/15/2009 10:09 AM, Lonnie Abelbeck wrote: > On Oct 15, 2009, at 4:32 AM, Tom Chadwin wrote: > >>> This will work if the 8139too module is enabled in >>> /etc/rc.modules, but if "modprobe 8139too" is called in >>> /mnt/kd/rc.elocal the BRIDGE0 variable won't work as expected >>> if any of the bridged interfaces are not defined until >>> /mnt/kd/rc.elocal is called. Advanced users could place the >>> 'brctl' calls in rc.elocal if they wish. >>> >> The documentation says this: >> >> "In this example eth1 is the berofix card and eth0 is our interface to >> the LAN. We want to apply our LAN interface the ip-address 192.168.0.2 >> and our berofix device the ip-address 192.168.0.3. After we setup the >> Bridge we want to access the berofix device from all devices in our >> LAN which are all in the network 192.168.0.1-254. To setup this >> bridge, you need to enter a few commands like in the following >> example: >> >> berofix:# ifconfig eth0 0.0.0.0 up >> berofix:# ifconfig eth1 0.0.0.0 up >> berofix:# brctl addbr br0 >> berofix:# brctl addif br0 eth0 >> berofix:# brctl addif br0 eth1 >> berofix:#ifconfig br0 192.168.0.2 up >> >> "These commands will first remove the ip-addresses from your network >> cards, then will create the bridge and add your network card and the >> berofix card to this bridge. In this case the bridge gets the >> IP-address 192.168.0.2. The default IP of the berofix is 10.0.0.2 with >> the subnet 255.0.0.0 and we have to change this with the bfdetect tool >> to 192.168.0.3 with 255.255.255." >> >> So would putting that into rc.elocal do the trick, do we think? Not >> worked with either bridges or ip forwarding before, so I'm flying >> somewhat in the dark here. As I say, Beronet recommend the bridge >> approach, so it might be nice to get that working. >> > Tom, you need one "modprobe bridge" before the first 'brctl' command. > To make it look like /etc/init.d/network, something like: > > -- rc.elocal snip -- > > modprobe 8139too > modprobe bridge > > EXTIF="br0" > BRIDGE0="eth0 eth1" > > brctl addbr $EXTIF > brctl setfd $EXTIF 0 > for i in $BRIDGE0; do > ifconfig $i 0.0.0.0 up > brctl addif $EXTIF $i > done > ifconfig $EXTIF $EXTIP netmask $EXTNM up > if [ -n "$EXTGW" ]; then > route add -net default gw $EXTGW dev $EXTIF > fi > -- snip -- > > In the Network tab set External Interface: br0 with Connection Type: > Static IP, define Static IP:/NetMask:/Gateway: > > I have not tested this, so expect errors, but should give you > something to test. >
I wouldn't recommend using /mnt/kd/rc.elocal in this case. Edit /etc/rc.modules to add/enable the module. Modify /mnt/kd/rc.conf to set BRIDGE0 and EXTIF as above (or as appropriate). -Philip >>> In 0.7 there is a file '/etc/udev/rules.d/70-persistent-net.rules' >>> that keeps the network interface ordering consistent by MAC >>> address, Tom - I think the changing ordering with/without the >>> Berofix card was confusing you with in 0.6. >>> >> Thanks again >> >> Tom >> > Lonnie > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Astlinux-users mailing list Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
