| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Noticed by: bde
|
|
|
|
| |
calculated dynamically here.
|
| |
|
| |
|
|
|
|
|
| |
PR: docs/42543
Submitted by: Michael Lyngbøl <lyngbol@bifrost.lyngbol.dk>
|
|
|
|
|
|
|
| |
the issue of not having any free bits left for additional commands.
Approved by: ken
MFC after: 4 weeks
|
|
|
|
|
|
|
|
|
|
|
|
| |
in /etc/fstab. This isn't a real fix though and I'm still not sure
why it started failing. mount(8) breaks up the nfs args into seperate
repeated '-o option=value' arguments. But, the altflags variable that
we use to track things is incrementally built up each time we see the
next option and shows us the cumulative set of flags, not just the
flag that we are currently looking at. As a result, the strstr hack
for looking up flags in a giant -o opt=val,opt=val, etc string was failing
and causing a segfault. I do not know what changed recently that caused
this to suddenly break, but the code has been rather bogus for some time.
|
|
|
|
|
| |
Approved by: ken
MFC after: 4 weeks
|
|
|
|
| |
Fixed other bugs in the usage message so that it matches the man page.
|
|
|
|
|
|
| |
anymore.
Sponsored by: DARPA & NAI Labs.
|
|
|
|
|
|
| |
disk utilities.
Discussed with: bde
|
|
|
|
|
|
|
| |
before growing partitions with growfs(8), if necessary.
PR: docs/42148
Submitted by: Chris S.J. Peron <maneo@bsdpro.com>
|
|
|
|
|
| |
Submitted by: Yutaka KAWASE <yutaka@mailhost.net>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
|
|
| |
communication with the remote NFS server if this flag is specified.
PR: bin/42003
Submitted by: Jean-Luc Richier <Jean-Luc.Richier@imag.fr>
|
|
|
|
|
|
| |
matches the synopsis given in the manual page.
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
going to gethostbyname2(3).
PR: bin/31632
MFC after: 3 days
|
| |
|
|
|
|
| |
"null pointer expression".
|
| |
|
| |
|
|
|
|
| |
specifications.
|
|
|
|
|
|
| |
as needed.
Approved by: ken, sheldonh (mentor)
|
|
|
|
|
|
|
|
|
| |
Also, for all interfaces in this mode pass all ethernet frames to upper layer,
even those not addressed to our own MAC, which allows packets encapsulated
in those frames be processed with packet filters (ipfw(8) et al).
Emphatically requested by: Anton Turygin <pa3op@ukr-link.net>
Valuable suggestions by: fenner
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
following Julian's good suggestion: since you can specify any match
pattern as an option, rules now have the following format:
[<proto> from <src> to <dst>] [options]
i.e. the first part is now entirely optional (and left there just
for compatibility with ipfw1 rulesets).
Add a "-c" flag to show/list rules in the compact form
(i.e. without the "ip from any to any" part) when possible.
The default is to include it so that scripts processing ipfw's
canonical output will still work.
Note that as part of this cleanup (and to remove ambiguity), MAC
fields now can only be specified in the options part.
Update the manpage to reflect the syntax.
Clarify the behaviour when a match is attempted on fields which
are not present in the packet, e.g. port numbers on non TCP/UDP
packets, and the "not" operator is specified. E.g.
ipfw add allow not src-port 80
will match also ICMP packets because they do not have port numbers, so
"src-port 80" will fail and "not src-port 80" will succeed. For such
cases it is advised to insert further options to prevent undesired results
(e.g. in the case above, "ipfw add allow proto tcp not src-port 80").
We definitely need to rewrite the parser using lex and yacc!
|
|
|
|
| |
Submitted by: many
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
render the syntax less ambiguous.
Now rules can be in one of these two forms
<action> <protocol> from <src> to <dst> [options]
<action> MAC dst-mac src-mac mac-type [options]
however you can now specify MAC and IP header fields as options e.g.
ipfw add allow all from any to any mac-type arp
ipfw add allow all from any to any { dst-ip me or src-ip me }
which makes complex expressions a lot easier to write and parse.
The "all from any to any" part is there just for backward compatibility.
Manpage updated accordingly.
|
|
|
|
| |
Approved by: ken, sheldonh (mentor)
|
|
|
|
|
|
|
|
|
| |
noting that the restrictions do not apply if the user invoking the
program is also the owner of the program.
Also, capitalize a section header properly.
PR: misc/41180
|
|
|
|
| |
pollution in <kvm.h>.
|
|
|
|
|
|
|
| |
breaking application ABI use unused ifreq.ifru_flags[1] for upper 16 bits in
SIOCSIFFLAGS and SIOCGIFFLAGS ioctl's.
Reviewed by: -hackers, -net
|
|
|
|
| |
Also submitted by: David Wolfskill <david@catwhisker.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement the M_SKIP_FIREWALL bit in m_flags to avoid loops
for firewall-generated packets (the constant has to go in sys/mbuf.h).
Better comments on keepalive generation, and enforce dyn_rst_lifetime
and dyn_fin_lifetime to be less than dyn_keepalive_period.
Enforce limits (up to 64k) on the number of dynamic buckets, and
retry allocation with smaller sizes.
Raise default number of dynamic rules to 4096.
Improved handling of set of rules -- now you can atomically
enable/disable multiple sets, move rules from one set to another,
and swap sets.
sbin/ipfw/ipfw2.c:
userland support for "noerror" pipe attribute.
userland support for sets of rules.
minor improvements on rule parsing and printing.
sbin/ipfw/ipfw.8:
more documentation on ipfw2 extensions, differences from ipfw1
(so we can use the same manpage for both), stateful rules,
and some additional examples.
Feedback and more examples needed here.
|
|
|
|
| |
constants as well.
|
|
|
|
| |
the header file.
|
|
|
|
| |
include sys/uio.h.
|
| |
|
| |
|
| |
|
|
|
|
| |
DESCRIPTION sections..
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Gregory Bond <gnb@itga.com.au>
Pr: 40872
|