> >> Step 7: IP forwarding is required to get the card working > properly - > >> can anyone tell me if enabling it is A Bad Thing in any way? The > >> other Berofix approach is to use a bridge rather than ip > forwarding, > >> but since I'm not sure this is directly supported in the Astlinux > >> GUI, I thought I'd try this method first. If I get the chance, I > >> might test the bridge method, which is the one favoured by Beronet. > > > > Bridging is easy: > > Put something like the following in your > "/mnt/kd/rc.conf.d/user.conf" > > (via Network (User System Variables) or Edit tab in GUI): > > > > ### Bridge eth1 + eth2 to one (br0) for internal LAN > > BRIDGE0="eth1 eth2" > > > > and reboot. After that you have an additional interface > "br0", you can > > select in the Network tab. > > 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. > 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 ------------------------------------------------------------------------------ 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.
