I have the exact same problem.
But since I had eight rules in my shaper it took a while to figure it out.

The rule that "broke" port forwarding to my LAN subnet was:
Int: WAN (imcoming)
Src: *
Dst: LAN subnet
...placed in a pipe with my max bandwidth - medium weight.

Here's an example of the "block" in the log:
16:46:24.781984 rl1 @0:18 B 192.168.1.3,3389 -> 204.1.226.228,50825 PR tcp
len 20 44 -AS IN
(Okay, so I'm running MS-TS ;o)

Manuel: I can mail you my config.xml and log if it's any help?
I can have it log on the additional forwarded ports if you wish?

/Martin

-----Original Message-----
From: Mark N. [mailto:mark at nellemann dot nu] 
Sent: 19. januar 2004 23:18
To: Manuel Kasper
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Traffic shaper breaks inbound NAT ?


Manuel Kasper said:
> On 19.01.2004, at 23:08, Mark N. wrote:
>
>> Thats it! When I change the shaper rules to use the lan/optional
>> interfaces everything works.
>
> Weird. Were those traffic shaper rules for in- or outbound traffic (on
> WAN)? Which image do you use (platform)? I've got traffic shaper rules
> on WAN too, and they work fine...

I've tested the 45xx and generic images. Same behavior.

There's rules for both inbound and outbound traffic on the WAN interface.
Should I try to disable one at a time and test?

>
> - Manuel
>
>

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch