login
Header Space

 
 

freebsd-pf mailing list

FromSubjectsort iconDate
Ivan Petrushev
Why this rule doesn't score a match?
Hmmm, yes I'm on FreeBSD 7 I tried these pass rules before - nothing gets logged. I thought traffic is going both TO these ports and FROM these ports. Let's take for example a simple HTTP connection. The browser communicates to the remote server trough remote port 80 and says 'GET /index.html', then closes the connection. The HTTP server on the remote side opens a connection to the local machine (on some of our local port range)... but what is the port number on his side? I think that it is again 80...
Jul 23, 2:28 pm 2008
Jon Radel
Re: Why this rule doesn't score a match?
HTTP doesn't work like that. The client opens a connection from an arbitrary port (generally high and pseudo-random) to port 80 (or 8080, or whatever the published port the server listens on is). The server does NOT open a connection to you. Your initial packet to the web server from YOU port NNNN to SERVER port 80 never gets through your rule set so there's never a response from the server to get logged. You'd do much better, if this is a workstation on which you run a webbrowser...
Jul 23, 3:04 pm 2008
Ivan Petrushev
Re: Why this rule doesn't score a match?
Hi Jon, Aaahhh, I see now - these FROM rules must be TO rules :D Thank you both for your replies. I'm going to monitor the outbond connections as well, but I think I will be OK then. This was the little stone in the shoe. I've already managed to let ICMP trough that 'block all' ;) Btw, I like the way pflog is working - deploying tcpdump on pflog0 and track down the logged packets. Is there a way to create another pflog device and use it for some different rules? I've seen there is an option to ...
Jul 23, 3:21 pm 2008
Thomas Rasmussen
Re: Why this rule doesn't score a match?
Hello, To create another pflog interface do: ifconfig pflog1 create And to create it at boot time add: cloned_interfaces="pflog1" to /etc/rc.conf Regards Thomas _______________________________________________ freebsd-pf@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail to "freebsd-pf-unsubscribe@freebsd.org"
Jul 23, 4:57 pm 2008
Ivan Petrushev
Why this rule doesn't score a match?
Hello, I'm trying very simple 'block all, allow a few' firewall, but something doesn't seem right. As far as I remember 'the right matched rule' is taken and executed - this doesn't seem working here. Here is my firewall: ##################### #macros if = "re0" ext_ip = "10.10.10.21" tcp_services = "{http, https, ssh, domain, 5190, 5222, ftp, 1025}" udp_services = "{domain, 5190, 5222, ftp}" #filter block in log on $if pass on $if proto tcp from any port $tcp_services pass on $if proto udp...
Jul 23, 1:25 pm 2008
FreeBSD
Re: Why this rule doesn't score a match?
You should try "pass in on $if proto tcp from any to $ext_ip port $tcp_services flags S/SA keep state" and "pass in on $if proto udp from any to $ext_ip port $udp_services keep state" Your rule expect the traffic to came FROM $tcp_services but it is goint TO those ports. You can omit the "flags S/SA keep state" and the "keep state" if you're using FreeBSD 7, it is added automatically. I would also suggest you to use "block all log" instead of "block in log" and specifiy rules for your out...
Jul 23, 1:43 pm 2008
Walter Venable
Limiting client bandwidth with PF
Hi all, I'm having some trouble getting pf to do what I want. I'm a newbie to pf, so I can't get my configuration quite right. We have a 3Mb/1Mb connection and I want to limit my clients each to 128Kbps/64Kbps. First things first, limit them to 128Kbps, but that isn't even working, as clients are still maxing at 3Mbps: $ cat /etc/pf.conf int_if="rl0" ext_if="nfe0" int_net="192.168.2.0/24" altq on $ext_if hfsc bandwidth 3Mb queue { clients } queue clients bandwidth 128Kb hfsc ( default rio...
Jul 23, 9:03 am 2008
Catalin Miclaus
RE: Limiting client bandwidth with PF
Hello Walter, There are some open bugs for pf with altq. You may want to consider ipfw and pipes to achieve same. Best Regards Catalin Miclaus Network/Security ISP-Data Starcomms Ltd. -----Original Message----- From: owner-freebsd-pf@freebsd.org [mailto:owner-freebsd-pf@freebsd.org] On Behalf Of Walter Venable Sent: Wednesday, July 23, 2008 2:04 PM To: freebsd-pf@freebsd.org Subject: Limiting client bandwidth with PF Hi all, I'm having some trouble getting pf to do what ...
Jul 23, 10:51 am 2008
Lyle Scott III
Re: Limiting client bandwidth with PF
I have used PF for a few years on various servers and would like to play with ALTQ functionality (finally have some time!), yet I read about quite a few 'bugs' with pf/altq ... Should I even bother? It is posts such as these that are quite discouraging! (not hating on poster :) ) I think FreeBSD is the greatest OS ever and I love the functionality (and syntax) of PF... and would love to see ALTQ throw in to the mix. On Wed, Jul 23, 2008 at 10:51 AM, Catalin Miclaus <catalin@starcomms.com&g...
Jul 23, 3:10 pm 2008
Michal Buchtik
Re: Limiting client bandwidth with PF
You can limit only OUTGOING traffic (from router point of view). So change the line to: altq on $int_if hfsc bandwidth 3Mb queue { clients } Michal _______________________________________________ freebsd-pf@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-pf To unsubscribe, send any mail to "freebsd-pf-unsubscribe@freebsd.org"
Jul 23, 11:35 am 2008
Ivan Petrushev
Problems in basic usage of ALTQ
Hello, I'm trying to do very simple traffic shaping on my box with ALTQ. For beginning I want just to restrict HTTP downloading speed (which is port 80) to a fixed number... lets say 100Kbps. I'm on ADSL line providing me 12Mb down / 2Mb up, (and I know every ADSL tutorial recommend limiting uploads) but for syntax learning purposes let's concentrate only on limiting downloading speed. I've read some tutorials and I've reached to the following code: [code] ### Queueing # I'm not sure what to set ...
Jul 23, 5:03 am 2008
previous daytodaynext day
July 22, 2008July 23, 2008July 24, 2008
speck-geostationary