1.3 Development

[3 secs]

... just as versions 1.3b1 and 1.3b2 are.

When I upgrade my WRAP box (233 MHz CPU, 128 MB RAM) from m0n0wall 1.231 to 1.3b3 I experience a huge slowdown in page loading while surfing the world wide web.

Some examples:
complete refresh of http://www.heise.de/newsticker/ - with m0n0wall 1.231: 3 secs ; with m0n0wall 1.3b3: 30 secs
complete refresh of http://m0n0.ch/wall/download.php?file=wrap-1.3b3.img - with m0n0wall 1.231: 2 secs ; with m0n0wall 1.3b3: 10 secs

I understand that the hardware requirements of FreeBSD 6.x are higher but the CPU load is never above 15%.

Any ideas on what could be causing this?
Anyone experiencing the same or similar?

Ok the wraps are not the fastest and if you ever had pfsense on a wrap you may know what real slow is.
But if you have a little faster Box (Can't wait for the ALIX boards) it looks like this

(http://www.speedtest.net/result/165206581.png)

m0n0wall 1.3b3
on Celeron 600MHz ULV
512 MB Ram onBoard DDR Ram
Intel Gigabit Nics

I'm real happy with beat 1.3b3 !
Wireless works like a champ

Manuel, does 1.3b3 use more than 64M Memory

Keep your perfect work going

I just found that disabling the traffic shaper makes web page loading even impossible,
the pages won't load up at all (yet the connect works as the browser states 'Waiting for ...').

I looked in my advanced outbound NAT rules and set destination to any, web page loading was fast again as it was with m0n0wall 1.231.
Disabling whole advanced outbound NAT makes web page loading also fast.
Setting certain destination networks in the NAT rules makes web page loading to that certain network slow.
Setting certain destination networks and NOT (inverting the match) in the NAT rules makes web page loading to all other networks also slow.

So it has something to do with the destination setting of the advanced outbound NAT rules, and with the traffic shaper.

Bug? Feature? Manuel?

Have you tried a factory reset on m0n0wall running 1.3b3?

How much memory does m0n0wall report? Check the main GUI page for Memory utilization or use the http://<ipaddres>/status.php page.

I run a WRAP 1.E2 with 128MB DRAM and don't notice any difference in speed to 1.2x. I get an avg of 10-12Mbps down and 5-7 Mbps upload speed (close to what my cable provider offers). Tried it with and without traffic shaping configs.

hope it helps

Please, RE-READ my posts!

You just assumed the same wrong thing as mlabenda did, that I wrote about throughput.
But in fact i wrote about RESPONSE time.

Btw, just for the next guy who maybe wants to tell me that there is no bug,
when I can reproduce the described behaviour so explicitly simply by enabling/disabling certain features
then there is definitely a bug.

Manuel, while reproducing I also got the following in the log several times:
^{kernel: Warning: memory type dummynet leaked memory on destroy (X allocations, XXX bytes leaked).}

After upgrade to 1.3b4 (same as with 1.3b3)  from 1.231 also I've got also a very slow response.
Disabling whole advanced outbound NAT makes web page loading fast again... 

After removing the NAT rule with NOT (inverting the match) on WAN,
response with enabled outbound NAT stays OK.

I've tested this with generic image not on WRAP, and get the same behaviour as Maxe reported.
Not sure what causes this, but it isn't platfrom specific.

Troughput 10Mbps (DSL speed) is OK, same as with 1.231,
Great package!


Tnx, HansT.