summaryrefslogtreecommitdiffstats
path: root/etc/rc.firewall
Commit message (Collapse)AuthorAgeFilesLines
* MFH: r284691julian2015-08-241-23/+15
| | | | | | | | | MFH: r284920 Remove 16 rules and replace by 2 by using a table. I've been doing this ever since there were tables. I could make more efficient by using "in recv" and "out xmit" instead of via but I'll leave that.
* MFC r273201, r273301:hrs2015-07-231-3/+21
| | | | | | | | | | Add support of "/{udp,tcp,proto}" suffix into $firewall_myservices, which interpreted the listed items as port numbers of TCP services. A service with no suffix still works and recognized as a TCP service for backward compatibility. It should be updated with /tcp suffix. Approved by: re (gjb)
* Whitespace nitkevlo2012-07-131-2/+2
|
* Spelling fixes for etc/uqs2012-01-071-5/+5
|
* Remove trailing white space. No functional changes.dougb2010-05-141-3/+3
|
* Fix grammar in comment.ume2010-04-111-3/+3
| | | | | Submitted by: "b. f." <bf1783__at__googlemail.com> MFC after: 3 days
* Disambiguate `IPs' to a more specific term.ume2010-04-081-6/+8
| | | | | Submitted by: Garrett Cooper <yanefbsd__at__gmail.com> MFC after: 3 days
* firewall_trusted_ipv6 was gone by r202460. Remove stale comment aboutume2010-04-071-6/+1
| | | | it as well.
* Remove the rules using 'me6'. Now, 'me' matches both any IPv6 addressume2010-01-171-45/+5
| | | | | | | and any IPv4 address configured on an interface in the system. Reviewed by: David Horn <dhorn2000__at__gmail.com>, luigi, qingli MFC after: 2 weeks
* The client type rule allows DHCP, implicitly. Since DHCPv6 usesume2010-01-091-0/+2
| | | | | | | link-local address unlike with DHCP, we need one more rule to allow the DHCPv6. Reported by: David Horn <dhorn2000__at__gmail.com>
* Since the IPv4 rule allows ICMP_TIMXCEED, allowume2010-01-071-1/+4
| | | | | ICMP6_TIME_EXCEEDED as well for workstation type firewall. It makes traceroute6 work.
* Add missing me6 rules. Now, the IPv6 rules become equivalentume2009-12-291-0/+29
| | | | | | to the IPv4 rules. Reported by: David Horn <dhorn2000__at__gmail.com>
* Unify rc.firewall and rc.firewall6, and obsolete rc.firewall6ume2009-12-021-10/+146
| | | | | | | and rc.d/ip6fw. Reviewed by: dougb, jhb MFC after: 1 month
* Allow the network addresses and interface names for the "client" andjhb2008-08-151-6/+15
| | | | | | | | | | | | "workstation" firewall types to be set from rc.conf so that rc.firewall no longer needs local patching to be usable for those types. For now I've set the variables in /etc/defaults/rc.conf to the previous defaults in /etc/rc.firewall. PR: bin/65258 Submitted by: Valentin Nechayev netch of netch.kiev.ua Silence from: net MFC after: 2 weeks
* For the "client" and "simple" network types, collapse the separate "net"jhb2008-08-151-14/+11
| | | | | | | | and "mask" variables into a single "net" variable that contains a full network address (including either a netmask or prefix length at the user's choice). Update the example settings to match. MFC after: 2 weeks
* Use 'me' rather than explicit IP addresses for the "simple" and "client"jhb2008-08-151-12/+9
| | | | | | | | firewall configurations. PR: bin/65258 Silence on: net@ MFC after: 1 week
* - back out my last commit as it seems to be wrong.danger2008-08-031-2/+0
| | | | Spotted by: das
* - dns queries might go also over TCP, so allow it.danger2008-07-171-0/+2
| | | | | Approved by: rink MFC after: 1 week
* Tweak rc.firewall to allow incoming limited broadcast traffic,keramida2008-06-061-0/+3
| | | | | | | | | when configured to run in 'client' mode. PR: conf/15010 Submitted by: Bill Trost, trost at cloud.rain.com Reviewed by: bz MFC after: 2 weeks
* Improve kernel NAT support in rc.firewallrafan2008-01-211-1/+7
| | | | | | | | | | - Allow IP in firewall_nat_interface, just like natd_interface - Allow additional configuration parameters passed to ipfw via firewall_nat_flags - Document firewall_nat_* in defaults/rc.conf Tested by: Albert B. Wang <abwang at gmail.com> MFC after: 1 month
* o Correct an info about "Firewalls and Internet Security" book: name,maxim2008-01-121-7/+6
| | | | | | | authors list, ISBN, URLs. PR: conf/119590 MFC after: 1 week
* s/IPFW(4)/ipfw(4) to match the actual man page name.rwatson2007-04-051-1/+1
| | | | Submitted by: ru
* In rc.firewall, make it clear that this is the setup for IPFW(4), and notrwatson2007-04-021-1/+1
| | | | | | | for the sundry other firewalls in the system. MFC after: 3 days Submitted by: Richard dot Clayton at cl dot cam dot ac dot uk
* Summer of Code 2005: improve libalias - part 2 of 2piso2006-12-291-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | With the second (and last) part of my previous Summer of Code work, we get: -ipfw's in kernel nat -redirect_* and LSNAT support General information about nat syntax and some examples are available in the ipfw (8) man page. The redirect and LSNAT syntax are identical to natd, so please refer to natd (8) man page. To enable in kernel nat in rc.conf, two options were added: o firewall_nat_enable: equivalent to natd_enable o firewall_nat_interface: equivalent to natd_interface Remember to set net.inet.ip.fw.one_pass to 0, if you want the packet to continue being checked by the firewall ruleset after being (de)aliased. NOTA BENE: due to some problems with libalias architecture, in kernel nat won't work with TSO enabled nic, thus you have to disable TSO via ifconfig (ifconfig foo0 -tso). Approved by: glebius (mentor)
* Give rc.firewall a polish and a new method.phk2006-10-281-16/+107
| | | | | | | | | | | | Factor out the loopback setup Use "me" instead of hardcoded $ip where possible. Add "workstation" which protects just this machine with stateful firewalling. Put the variables for this in rc.conf. Submitted by: Flemming Jacobsen <fj@batmule.dk> Reviewed by: cperciva
* don't match packets other than IPv4 against divert rule.ume2005-11-181-1/+1
| | | | | | | | divert supports only IPv4. Reported by: SAITOU Toshihide <toshi__at__ruby.ocn.ne.jp> Discussed with: suz MFC after: 1 day
* DNS should not necessarily be named(8), tweak the comment a bit.ru2003-11-021-1/+1
|
* Add a header: #!/bin/sh.trhodes2003-02-061-0/+1
| | | | PR: 44363
* Bring rc.firewall{,6} more in line with the word and spirit ofcjc2002-02-211-7/+17
| | | | | | | | | | | | | | | | rc.conf(5) and the files' inline documentation. - Add the "closed"-type, documented in both places, but which did not exist in the code. - When provided a ruleset, the system should not make any assumptions about the sites's policy and should add no rules of its own. - Make the "UNKNOWN" (documented in-line) actual work as advertised, load no rules. Prodded by: Igor M Podlesny <poige@morning.ru> MFC after: 1 week
* Remove a stale entry related to passing ARP with bridging and ipfw.luigi2001-12-271-2/+0
| | | | | | | | | This feature has been removed since 4.1 times and it is only a source of confusion. Same needs to be done on -stable. MFC after: 1 day
* Sync the code that sucks in rc.conf and friends with what's indd2001-08-141-5/+7
| | | | | | | | | | | | rc.firewall6. Specifically, don't do anything if [ -z ${source_rc_confs_defined} ]. Not doing this leads to a problem with dependencies: chkdepend will set, e.g., portmap_enable to YES if some service that needs portmap is enabled, but rc.network sources rc.firewall, which used to source defaults/rc.conf unconditionally, which would result in portmap_enable being set back to NO. PR: 29631 Submitted by: OGAWA Takaya <t-ogawa@triaez.kaisei.org>
* style nitobrien2001-03-061-1/+1
|
* Also deny 127.0.0.0/8 going out.obrien2001-03-051-1/+2
| | | | Submitted by: grimes
* Fix references to Chapman & Zwicky and Cheswick & Bellowin.des2001-02-251-3/+5
| | | | | PR: 24652 Submitted by: jjreynold@home.com
* Fix some glaring insecurities in the prototype firewall configurations.nsayer2001-02-201-8/+4
| | | | | | | | pass udp from any 53 to ${oip} allows an attacker to access ANY local port by simply binding his local side to 53. The state keeping mechanism is the correct way to allow DNS replies to go back to their source.
* Add copyright notices. Other systems have been barrowing our /etc filesobrien2000-10-081-2/+29
| | | | w/o giving any credit.
* Only install `divert natd' rule for predefined firewall types,ru2000-08-301-3/+1
| | | | | | | not when ${firewall_type} is set to a filename, as we know nothing about user's script specifics. Reported by: Bernhard Valenti <bernhard.valenti@gmx.net>
* Make natd(8) "compatible" with firewall_type="simple".ru2000-08-041-17/+46
| | | | PR: conf/13769, conf/20197
* Update rev 1.29 -- 'draft-manning-dsua' is now in its 3rd version.obrien2000-07-301-1/+3
|
* Add an explicit rule number to natd so you do not end up with twops2000-05-081-1/+1
| | | | | | rule 100's. Submitted by: Jan Koum <jkb@yahoo-inc.com>
* Add to defaults/rc.conf a new function source_rc_confs which rcsheldonh2000-04-271-0/+1
| | | | | | | | | | | | | | | | | scripts may use to source safely overrides in ${rc_conf_files} files. This protects users who insist on the bad practice of copying /etc/defaults/rc.conf to /etc/rc.conf from a recursive loop that exhausts available file descriptors. Several people have expressed interest in breaking this function out into its own shell script. Anyone who wants to embark on such an undertaking would do well to study the attributed PR. PR: 17595 Reported by: adrian Submitted by: Doug Barton <Doug@gorean.org>
* Back out the hook to execute the file ${firewall_type}. The intendedbsd2000-04-271-3/+1
| | | | | | | | | | purpose of the hook was to provide the ability for a shell program to instantiate the firewall rules instead of forcing them to be statically coded. This functionality was already present through the use of ${firewall_script}, and I see no need to keep the ${firewall_type} hook around. Reminded by: Dag-Erling Smorgrav <des@freebsd.org>
* Allow the firewall rules to be established by a shell script insteadbsd2000-04-161-1/+3
| | | | | | | of forcing them to be an 'ipfw' rules file. This allows one to determine interface addresses dynamically, etc. The rule is if the file referenced by ${firewall_type} is executable, it is sourced, but if it is just readable, it is used as input to 'ipfw' like before.
* Add a firewall_flags option that is used when ipfw processes a file. It allowspaul2000-02-061-1/+1
| | | | | | | you to run a preprocessor, such as m4, so that you can use macros in your rules file. Approved by: jkh
* Update this with the additional nets recomended by readingrgrimes2000-01-281-14/+26
| | | | | | | | | | | draft-manning-dsua-01.txt. Stop using public addresses as samples and use the recommended 192.0.2.0/24 netblock that has specifically been set aside for documentation purposes. Reviewed by: readers of freebsd-security did not respond to a request for review
* Minor whitespace fix.obrien1999-12-041-2/+1
|
* Pass IP fragments with non-zero offset. The semantics of matchingru1999-11-041-0/+6
| | | | | | IP fragments has been changed in src/sys/netinet/ip_fw.c,v 1.78. Reminded by: "Ronald F. Guilmette" <rfg@monkeys.com>
* Add commented entry to the lo0 section inviting bridge users tonsayer1999-10-241-0/+2
| | | | enable ARP on filtering bridges.
* Allow for incoming DNS UDP queries.ru1999-10-201-0/+2
|
* Fix a typo in a comment.mpp1999-09-301-1/+1
|
OpenPOWER on IntegriCloud