Serangku - and also if use wil use ssh and ftp inside of ssh how can you limit their download/upload?

jigp
Davao City

| 1.2.2 |

Ok enjoy pfseing. :)
jigp
Davao City

| *** Welcome to pfSense 1.2.2-pfSense on freebsd *** |

The problem it's not limited to DMZ, I've just put it as example.

The traffic is being queued in the qlanRoot without a rule involving the affected interfaces. I mean, the queues are supposed to affect only WAN->LAN and LAN->WAN, aren't they?

I don't know if this is the correct behaviour or if we're dealing with a bug.

Thanks you.

Juanjo

The feature is there cause the schedules rearrangement has been done.

The answer to your question is when its done :).

Same thing. That does not work in 1.2.2..

jigp
Davao City

Hello,
1.2.3 RC1

Thanks

Hi can you please post your Firewall: Shaper: Queues? I just want to know how to limit p2p http dl/up. Thanks

jigp
Davao City

Please provide you Firewall: Shaper: Queues. So everyone can review it. Thanks

jigp
Davao City

Can you post your Firewall: Shaper: Queues please? thanks

jigp
Davao City

Does it work in 1.01 and 1.2.1? Thanks

jigp
Davao City

Okay… after some more testing, here goes.  Please correct me if I'm wrong!

It seems that what breaks the RRD graphs is when I put in rules to shape the OPT1 interface.  It also seems to cause the odd bug with the queue status page as well.

Odd thing is, that even though traffic shaping from what I'm reading does not work on multiple interfaces, it still seems to be working, as without the added rule, all OPT1 traffic goes to the default queues, which kinda makes shaping not work well for what I'm wanting to do.

So, the odd thing is that I'm reading that pfSense's traffic shaper does not support shaping over more than LAN/WAN interfaces, but if what I'm looking at is right, then it indeed does work, but it just screws up the queue status page and the RRD graphs.

Considering I may just be reading things incorrectly, can anyone confirm/deny this??

[Edit]

I think I might have figured out what was going on with the queue status page.  Now, I'm not a guru, nor do I have a lot of experience and knowledge, but I can think fairly logically, and I've been muddling over the problem here and there throughout the week, and I think I figured it out.

When we make a rule that includes another interface, I think the queues are being duplicated which would use that interface.  Would kinda make sense the way I was thinking about it, and would explain the oddity on the queue status page, and may explain somewhat why the RRD graphs are broken.

What is killing me is that if what I'm seeing is correct, the traffic is entering the queue that it is supposed to when I make a few rules to shape traffic and go downloading/browsing to test it.  I'm just not sure if the queues are being duplicated, or halved, or what.  Haven't really gotten that far.

Since Ermal seems to be the traffic shaping god-person here, hopefully he'll read this.  For now though, I figured my work-around was to put another box in front of the normal router with just the basic stuff, the port-forwards, and traffic shaping – then use the 'real' router to route the traffic where it should go.  Would really love to eliminate the extra box though, as I'm running out of room to stuff extra junk :P

Is 2.0 stable enough that it is passable, or should I hold out for official?  I know it is in alpha, but sometimes even alphas are pretty good :P

–--Disregard this bit as I've found a work-around, but would like to know about 2.0 beign stable enough for general use?----

Hey ermal, in light of what I'm finding in the other post I have here… are you sure it doesn't work?  So far I at least notice that my roommate's torrents are now properly going into the p2p queue when I make the rule for OPT1... still alot of traffic in default queues but that may be because he has random ports in his torrent config

Set up a NAT rule in addition to the 1:1 mapping and you should get reflection for that service.

You probably want to look at the Traffic Shaping forum.

Thank you for info.

just think of it in terms of upstream and downstream and it's much easier
wan = downstream
lan = upstream