> (PS: all firewalls are running m0n0wall) Firewall A:
> Nic 1: WAN 118.x.x.x / 29
> Nic 2: LAN 192.168.0.5 / 16
> Nic 3: Bridge to FW A??? 10.0.0.2 / 24
Nic 3: Bridge to FW B 192.169.0.6/16
> Add Static Route for 192.169.x.x/16 to point to gateway 192.169.0.5???
Should not be needed.  With Nic 3 being on 192.169.0.6/16, you have a route.


> Firewall B
> Nic 1: WAN 10.0.0.50 / 24 -->  Treat this as bridge?
> Nic 2: LAN 192.169.0.5 / 16
> Add Static Route for 192.168.x.x to point to gateway 192.168.0.5???
Add Static Route for 192.168.0.0/16 to point to gateway 192.169.0.6
> Then set all the users in company B with 192.169.x.x /16 with gateway 
> and dns to 192.168.0.5? For Internet sharing.
DO NOT TOUCH THE USERS!  Handle all routes in the firewall.  You will also
need firewall rules in each segment allowing traffic on FW A.

What will happen.  User on firewall A wants to go to user on firewall B. 
  It will go to the default route of 192.168.0.5 and be routed to
192.169.0.6, and on to the user.

User on firewall B wants to go to user on firewall A.  It will go to the
default route of 192.169.0.5 and be routed to 192.169.0.6, and on to the
user.
=============================================

Oooh... Based on what you said above, please allow me to rephrase them in my
understanding. Also, two more questions for confirmation. I am excited to
test this soon :).

Firewall A:
Nic 1: WAN 118.x.x.x / 29
Nic 2: LAN 192.168.0.5 / 16
Nic 3: Bridge to FW B 192.168.0.6/16 --> Should I the third NIC as VLAN?? Or
can m0n0wall recognize 3 NICs? (1WAN and 2 LANs)?

Firewall B:
Nic 1: WAN 192.168.0.50/16 --> Is this the correct IP for connecting to the
Firewall A?
Nic 2: LAN 192.169.0.5 / 16