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.

Reply via email to