Tom, If I were in your shoes, I would try to use a bridge to tie eth4 and the external interface as the Berofix folks suggest. Either using BRIDGE0 or rc.elocal, as mentioned previously.
Personally, I have not tried anything similar to what your are doing. Save your current settings, and give the bridge technique a try. Lonnie On Oct 22, 2009, at 2:56 PM, Tom Chadwin wrote: >> I tried using the GUI to set the Berofix (eth4) as the DMZ > > OK, I have a specific issue I'd like to understand. I am bringing up > the Berofix as eth4 via a modprobe and ifconfig eth4 10.0.0.1 up in / > mnt/kd/rc.elocal. To configure the Berofix, I need access to the its > internal IP (10.0.0.2) via a browser on a host on my LAN. The only > way I've managed to get this to work is as follows: > > 1. Enable IP forwarding > 2. Use the Astlinux GUI to place eth4 in the DMZ > 3. Add a route : ip route add to 10.0.0.0/24 via 10.0.0.1 dev eth4 > > Is this the only/the best way to allow this access (LAN host to > other Astlinux NIC)? Could this configuration be causing the problem > of traffic sometimes not being able to get from eth4 (DMZ) to eth0 > (LAN)? > > Really reaching the end of my options here. Any help very gratefully > received. > > Thanks > ------------------------------------------------------------------------------ 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.
