PROBLEM with captive portal and limite
-
rojocesar,
I just want to be sure I know what you are trying to do. Are you talking about per client limits or per pipe limits?
For port 80 and 443 you want 600kbps per client.
For the default allow you want 200kbps per client.Let me know if you really mean to limit all clients to 600kbps.
I wonder if your port 80 rule is interfering with the captive portal redirection of port 80 traffic. If you take out the rule for port 80, leave in the rule for port 443 and the default, do you have any luck? Does https traffic get limited like you want?
Ermal, what order do ipfw and pf rules get evaluated? Does it go through the ipfw rules first, and then the pf rules?
JoshWell i know it that captive portal has limiter per user but i want to use the limiter from Traffic Shaper why?? because i want to use rules in firewall, in the firewall i want to give rules for each port, for example limiter 600kbps only port 80 and port 443 (internet) and give rules limiter 200kbps all of them.
Hi Ermal.. here send your information
when now when i set up limiter and captive portal there is ping to my dns here send a picture but when i connect any webpage nothing here send other picture
i hope that all is ok send you a hug from Peru and thanks for your words stompro
….
more information.. I only set up limiter and doesn't work.. -
This is an example
For port 80 and 443 i want 400Kbps per client
For other ports i want 100Kpbs per client
But in firewall i can give more rules..captive portal doesn't use port 80 it use port 8000.
The others version of PFSENSE 2.0 work fine (excellent) 8) , but i want to use captive portal, when i set captive portal up all doesn't work >:( .
The pfsense is excellent but i need use captive portal and limiter i hope that Ermal can fixed all this problem :'( -
The captive portal rules automatically redirect port 80 connections to port 8000 or 8001 for clients that are not authenticated. That is how the splash page works.
run "ipfw list" and look for this line.
01990 fwd 127.0.0.1,8000 tcp from any to any dst-port 80 inThat forwards all connections with a destination port of 80 coming in the CP interface to localhost port 8000. So it does use port 80 :P
JoshThis is an example
For port 80 and 443 i want 400Kbps per client
For other ports i want 100Kpbs per client
But in firewall i can give more rules..captive portal doesn't use port 80 it use port 8000.
The others version of PFSENSE 2.0 work fine (excellent) 8) , but i want to use captive portal, when i set captive portal up all doesn't work >:( .
The pfsense is excellent but i need use captive portal and limiter i hope that Ermal can fixed all this problem :'( -
I just setup a config just like you described.
Port 80 traffic limited to 100kbit per user.
All other traffic limited to 500kbit per user.
When I connect a client, the splash page comes up, I'm able to log in, and I can confirm that my port 80 traffic is being limited to 100kbit.
I'm using
2.0-ALPHA-ALPHA
built on Sat Aug 22 01:39:53 UTC 2009
FreeBSD 7.2-RELEASE-p3 Nanobsd.Can you get it to work if you just limit all traffic to a certain speed. I'm wondering if you can simplify your config until you get something that works, and then add in more complexity to try and figure out what element is causing the problem.
Josh
-
all can simplify if captive portal and limiter works but at the momento only can use the limiter of captive portal… :'( I hope that Ermal fixed all..
-
and what's happend with limiter and captive portal problems??? is it fixed??? :'(
-
not yet. Since i have had no time to it.
-
well i will wait it.. :) thanks for your answer…
-
This works as expected on latest snapshot i tested.
Not sure what you have done just be aware that on the firewall->rules of the interface you have CP active you have to allow the traffic to pass too!Otherwise as i already told it works quite well.
-
THANKSSSSSSSSSSSSS SO MUCH.. all is right now..