Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
>This has taken a bit of work. Trying to install a Berofix card into a >net5501 running Astlinux 0.6.7. This is what I've done: Nice that it works now. >Notes: > >Step 1: Though installed on a net5501, the net5501 0.6.7 Astlinux >build doesn't have the 8139too driver - do I understand it is under >consideration for 0.7? It's already in svn: http://astlinux.svn.sourceforge.net/viewvc/astlinux?view=rev&revision=3358 >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. >Make sure you have a route set up on your workstation (or whatever) so >that requests for 10.0.0.2 will route via the Astlinux box. Point your >browser at http://10.0.0.2, and from here on in, the documentation at >www.berofix.com should do the trick, though I believe there is an >error. When setting up your Asterisk server in the SIP section of the >Berofix GUI, it tells you to give it the address 10.0.0.2, but I >believe this should be 10.0.0.1. I am happy to be corrected in this. > >Hope this helps for people, and many, many thanks for all the help in >getting this up and running. I'm sure I'll run into further amateur >problems, and will report back. > >Cheers > >Tom Michael -- 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
On Oct 14, 2009, at 12:03 PM, Michael Keuter wrote: >> 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. 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. 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> >> 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
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. > >> 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> >>> 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). Before I start trying to get the bridge approach to work, I'll try to finish the IP forwarding method. Currently working only on outgoing calls. The destination phone rings, but I hear no ringing tone in my SIP phone, and, once the call is answered, I get no audio either way. Any ideas about that? I know SIP with no audio often points towards a NAT issue, but figuring out what is going on in this scenario, and whether it qualifies as NAT, makes my head hurt. Anyone have any ideas on this? Please take my thanks as read for all this help - it really is invaluable. Cheers 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> Before I start trying to get the bridge approach to work, > I'll try to finish the IP forwarding method. Currently > working only on outgoing calls. The destination phone rings, > but I hear no ringing tone in my SIP phone, and, once the > call is answered, I get no audio either way. > Any ideas about that? I know SIP with no audio often points > towards a NAT issue, but figuring out what is going on in > this scenario, and whether it qualifies as NAT, makes my head hurt. OK, I guess this is to do with Asterisk taking itself out of the media path. I am seeing packet2packet bridging appearing on the console when I pick up the call, but the dialling handset has no route to the Berofix. I've tried adding canreinvite=no to both the handset and Berofix entries in sip.conf, and I've tried adding a route to the handset's gateway pointing requests for the Berofix at the Astlinux box, but I still have no audio. Any ideas? UPDATE: V odd. I changed everything from GSM to alaw, and it now seems to work. A puzzle for Monday, methinks. Thanks 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> -Original Message- > From: Philip A. Prindeville > [mailto:philipp_s...@redfish-solutions.com] > Sent: 16 October 2009 03:15 > To: astlinux-users@lists.sourceforge.net > Subject: Re: [Astlinux-users] Getting Berofix to work in > net5501 with Astlinux 0.6.7 > > 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). 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 shall try to get a bridge up and running today. 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> I shall try to get a bridge up and running today. OK, I think the bridge is up and running. eth0 and eth4 are br0 10.4.0.4. The internal IP address of the Berofix is 10.4.0.5. I can ping 10.4.0.4 from another host on the LAN. I can ping 10.4.0.5 from the Astlinux box. However, I cannot ping 10.4.0.5 from other hosts on the LAN. I've not added any routes to anything, as I presumed a broadcast would reach across the bridge. What am I missing? Thanks 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
On 10/23/2009 04:31 AM, Tom Chadwin wrote: >> -Original Message- >> From: Philip A. Prindeville >> [mailto:philipp_s...@redfish-solutions.com] >> Sent: 16 October 2009 03:15 >> To: astlinux-users@lists.sourceforge.net >> Subject: Re: [Astlinux-users] Getting Berofix to work in >> net5501 with Astlinux 0.6.7 >> >> 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). >> > 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 shall try to get a bridge up and running today. > > Thanks again > > Tom > This would be so much easier if you were running 0.7... -Philip -- 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
On 23 Oct 2009, at 22:47, "Philip Prindeville" wrote: > On 10/23/2009 04:31 AM, Tom Chadwin wrote: >>> Tom Chadwin , ICT & Web Development Officer Telephone: 01434 611530 Web : www.northumberlandnationalpark.org.uk IMPORTANT NOTICE - Disclaimer - October 24, 2009 - REF Email-200910-00482097. This communication is from Northumberland National Park Authority (NNPA).The Authority's head office and principal place of business is Eastburn, South Park, Hexham, Northumberland, NE46 1BS, United Kingdom. This communication and any attachments contain information which is confidential and may also be privileged. It is for the exclusive use AstLinux Users Mailing List.If you are not the intended recipient(s) please note that any form of disclosure, distribution, copying or use of this communication or the information in it or in any attachments is strictly prohibited and may be unlawful. If you have received this communication in error, please delete the email and destroy any copies of it. Any views or opinions presented are solely those of the author and do not necessarily represent those of NNPA.Contractors or potential contractors are reminded that a formal Order or Contract is needed for NNPA to be bound by any offer or acceptance of terms for the supply of goods or services Although this email and any attachments are believed to be free of any virus or other defects which might affect any computer or IT system into which they are received, no responsibility is accepted by the NNPA for any loss or damage arising in any way from the receipt or use thereof. Computer systems of this Authority may be monitored and communications carried out on them recorded, to secure the effective operation of the system and for other lawful purposes. -Original Message- >>> From: Philip A. Prindeville >>> [mailto:philipp_s...@redfish-solutions.com] >>> Sent: 16 October 2009 03:15 >>> To: astlinux-users@lists.sourceforge.net >>> Subject: Re: [Astlinux-users] Getting Berofix to work in >>> net5501 with Astlinux 0.6.7 >>> >>> 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 >>> >>&g
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> Apologies for ridiculous long work sig. Now juggling accounts to rid > myself (and you) of it. 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
> 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 -- 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
All went well on-site, so it's now in production. 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 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 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 > -- 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 Don
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
On Oct 29, 2009, at 6:06 AM, Tom Chadwin wrote: > All went well on-site, so it's now in production. 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 > > 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 Ahhh, the Berofix network-interface is an INTERNAL interface, not a shared as an external interface as I thought for some reason. That explains why the rc.elocal example for you didn't work. :-) Anyway, using BRIDGE0 in user.conf is the better way to handle this anyway. In 0.7 there is a new feature to allow traffic between LAN interfaces: Network Tab -> Firewall Tab _x_ Allow LAN to LAN for the [1st and 2nd] LAN Interfaces Without using a bridge, this might also work for you in the future. The Arno firewall command in 0.7 for the above is IF_TRUSTS="eth0 eth1" In 0.6 similarly (but slightly different command), adding INT_IF_TRUST="eth0 eth1" would allow traffic between the two different LAN interface/subnets without a bridge. Tom, thanks for documenting your experience. 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
>All went well on-site, so it's now in production. 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 > >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 Hi Tom, nice, that it works now for you and it's now in production. Are you happy with the ISDN features, is the speech quality OK? Michael http://www.mksolutions.info -- 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
Yes, I realized I hadn't clarified, and that you were talking of external interfaces - no matter. The other approaches sound good, too, but hopefully this will do us for the mo. > Are you happy with the ISDN features, is the speech quality OK? Speech quality good. Echo totally gone. Only problem is that incoming calls started to fail today. All that appeared in the Berofix debug dialplan during one was: I SETUP|INDICATION: port=2, channel=1, dad=620887, oad=1434611530 Nothing appeared on the Asterisk side. A successful incoming call looks like this: I SETUP|INDICATION: port=2, channel=1, dad=620887, oad=1434611530 D INCOMING port:2, channel: 1 src:1434611530dest:620887 -- OUTGOING src:"01434611530" dest:"620887" S INVITE|REQUEST: from="1434611530" 01434611...@10.4.0.5, to= "620887" 620...@10.4.0.4 Anyone know (generically) what would cause the first behaviour? A reboot brought it back to life. Cheers Tom On Thu, Oct 29, 2009 at 2:32 PM, Lonnie Abelbeck wrote: > > On Oct 29, 2009, at 6:06 AM, Tom Chadwin wrote: > >> All went well on-site, so it's now in production. 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 >> >> 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 > > Ahhh, the Berofix network-interface is an INTERNAL interface, not a > shared as an external interface as I thought for some reason. > > That explains why the rc.elocal example for you didn't work. :-) > Anyway, using BRIDGE0 in user.conf is the better way to handle this > anyway. > > > In 0.7 there is a new feature to allow traffic between LAN interfaces: > > Network Tab -> Firewall Tab > _x_ Allow LAN to LAN for the [1st and 2nd] LAN Interfaces > > Without using a bridge, this might also work for you in the future. > > The Arno firewall command in 0.7 for the above is IF_TRUSTS="eth0 eth1" > > > In 0.6 similarly (but slightly different command), adding > INT_IF_TRUST="eth0 eth1" would allow traffic between the two different > LAN interface/subnets without a bridge. > > > Tom, thanks for documenting your experience. > > 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. > -- 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.
Re: [Astlinux-users] Getting Berofix to work in net5501 with Astlinux 0.6.7
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 > 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. >> >> Th
