Bridge and NAT in the same MT box

Dear all,

Within my MT box (normal PC with DOM & RB44), normally we only use for NAT and QoS.

The public IP interface connected into ether1 and the private IP interface connected into ether3.

According to one of customer request about allocation of Public IP, we create bridge interface call ‘Dedicated’ that bridge ether1 and ether2.

At customer site, we used WRT54GS with DD-WRT act as Client with mode RIP2 Routing.

The problem that we found is, all client behind WRT54GS cannot surf to the net unless NAT turned into disable.

We tried to create another MT box with similar configuration, but this time we create bridge first before NAT. When NAT created and turn into active, the customer cannot go to the net.

Pls confirm, is it true that Bridge can not work within the same box that having NAT rule ?

TIA

PD

Use address-list, add client`s public addresses to the list, and exclude them from the NAT rule.

What I did are :

/inte brid port prin
Flags: X - disabled, I - inactive, D - dynamic

INTERFACE BRIDGE PRIORITY PATH-COST

0 ether1 Dedicated 128 10
1 ether2 Dedicated 128 10

/ip fire nat prin
Flags: X - disabled, I - invalid, D - dynamic
0 chain=srcnat out-interface=ether1 action=masquerade

NAT user connected to ether3

I did try to change the out-interface at nat rule into Dedicated but the same problem still persist.

PC that connected directly behind bridge, can do any internet activies but if other routing equipment (such as WRT54G with dd-wrt RIP2 mode), all PC behind that equipment only can do ping but not for other network activities such as ssh, telnet, ftp, mail, web, etc.

Any other clues pls.

PD