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 t
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
>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 B
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
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, re
> 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
>>
> 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
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 wo
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] G
> 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
> -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
>
> 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
> >>> 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
> user
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 th
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.
> >> 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
> >> G
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 th
>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
18 matches
Mail list logo
