Just an extra bit of info required to make this work, as I discovered on my second install - see inserted step 3a below:
> For others who might > want to use the Berofix (in a net5501), here is the procedure: > > 1. Boot the geni586 image without the Berofix installed > > 2. Use the Astlinux GUI to add the following to user.conf: > > BRIDGE0="eth0 eth1" > > 3. Install the Berofix, reboot, and use the GUI to set the first > internal interface as BR0 3a. Use the GUI to give BR0 an IP address which can talk to the Berofix's internal IP address whose default is 10.0.0.2/8 - If this is not done, the bfdetect tool (step 4) cannot reach the Berofix to change its IP settings (obviously this means you need to be able to give your client a 10.0.0.0/8 address too, until you change the Berofix and BR0 addresses to suit your existing LAN) > 4. Use the bfdetect tool to change the IP address of the Berofix to > something in the same subnet as BR0 > > Hope this helps > > Tom > > > On Tue, Oct 27, 2009 at 6:20 PM, IT Services > <nnpait.servi...@googlemail.com> 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). >>> >>> This would not work for me, as I mentioned, because if I try >>> to use rc.modules to enable the 8139too driver, the box boots >>> with the Berofix interface as eth0, and hence as $EXTIF, so I >>> can get no access to the box. Even changing the order of the >>> modules in rc.modules did not solve this problem. This is why >>> I am modprobing 8139too in rc.elocal. >> >> I used the set-up I had (using modprobe in rc.elocal) which, though not >> working, at least allowed me access to the box, and then reverted to the >> recommended approach (reinstate 8139too in /etc/rc.modules, and avoid >> rc.elocal) - thanks Philip and Lonnie. I now have no rc.elocal, with only a >> single line in user.conf. It works here in the office, so I'll go out >> on-site this week to see if I have more success. >> >> Thanks for all your patience and advice >> >> Tom >> > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ 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.
