How are you testing it? (nmap or something) Are you testing from within the LAN to the WAN address? Is it just a default install with just NIC configured or do you have packages and other config setup?
Testing is via NetworkActiv Port Scanner and Angry IP Scanner.
I have done a standard install (about 3 hours ago) and have 2 NICs in the machine. The LAN NIC is 192.168.1.6 statically allocated, the WAN port is 192.168.1.112 (DHCP) and is gatewayed out through my current router (192.168.1.1). Setting up a test machine so that its gateway is 192.168.1.6 (the LAN port on the new router) works nicely. I can browse the web and see the traffic on the bandwidth monitors.
The only config I have done is the NIC config, added a rule to forward FTP to my internal FTP server and installed, but not configured, snort. It is installed, the rules are updated from the internet but there is no configuration that I've applied to it so it isn't running (services->status shows it as stopped).
All I am then doing is from another machine on the network I'm just running a portscan on the WAN port and both pieces of software report that the ports are open.
If you try and connect to the ports (port 80) via a web browser, it doesn't reply with anything. Putting a rule in the WAN firewall to silently drop anything appearing as TCP on port 80 and log it produces no log entries as far as I can tell.
I also have this set up in a virtual machine and running the tests on the VM'd router shows the ports "open" as well....