| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: billf
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
+ implement "limit" rules, which permit to limit the number of sessions
between certain host pairs (according to masks). These are a special
type of stateful rules, which might be of interest in some cases.
See the ipfw manpage for details.
+ merge the list pointers and ipfw rule descriptors in the kernel, so
the code is smaller, faster and more readable. This patch basically
consists in replacing "foo->rule->bar" with "rule->bar" all over
the place.
I have been willing to do this for ages!
MFC after: 1 week
|
|
|
|
| |
Submitted by: LINT
|
|
|
|
|
|
|
| |
securelevel_gt() to check the securelevel, rather than direct access
to the securelevel variable.
Obtained from: TrustedBSD Project
|
|
|
|
|
| |
In ip_fw.[ch] change a couple of variable and field names to
avoid having types, variables and fields with the same name.
|
|
|
|
|
|
|
| |
fondling implementation details.
Created with: sed(1)
Reviewed by: md5(1)
|
| |
|
|
|
|
| |
The code (bridging and dummynet) actually worked fine!
|
|
|
|
| |
It compiles, but I cannot test functionality yet.
|
|
|
|
|
|
|
|
|
| |
splimp() -- we need it because dummynet can be invoked by the
bridging code at splimp().
This should cure the pipe "stalls" that several people have been
reporting on -stable while using bridging+dummynet (the problem
would not affect routers using dummynet).
|
|
|
|
|
|
| |
One of them fixes a potential panic when bridging is used and
you run out of mbufs (though i have no idea if the bug has
ever hit anyone).
|
|
|
|
|
| |
Submitted by: josh@zipperup.org
Submitted by: Robert Drehmel <robd@gmx.net>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Some dummynet code incorrectly handled a malloc()-allocated pseudo-mbuf
header structure, called "pkt," and could consequently pollute the mbuf
free list if it was ever passed to m_freem(). The fix involved passing not
pkt, but essentially pkt->m_next (which is a real mbuf) to the mbuf
utility routines.
* Also, for dummynet, in bdg_forward(), made the code copy the ethernet header
back into the mbuf (prepended) because the dummynet code that follows expects
it to be there but it is, unfortunately for dummynet, passed to bdg_forward
as a seperate argument.
PRs: kern/19551 ; misc/21534 ; kern/23010
Submitted by: Thomas Moestl <tmoestl@gmx.net>
Reviewed by: bmilekic
Approved by: luigi
|
|
|
|
| |
PR: 19544
|
|
|
|
|
| |
ambiguous data to the userland program (kernel operation was
safe, anyways).
|
| |
|
|
|
|
|
|
| |
It was not discussed and should probably not happen.
Requested by: msmith and others
|
|
|
|
|
|
|
|
| |
the type argument to *_HEAD and *_ENTRY is a struct.
Suggested by: phk
Reviewed by: phk
Approved by: mdodd
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
of the individual drivers and into the common routine ether_input().
Also, remove the (incomplete) hack for matching ethernet headers
in the ip_fw code.
The good news: net result of 1016 lines removed, and this should make
bridging now work with *all* Ethernet drivers.
The bad news: it's nearly impossible to test every driver, especially
for bridging, and I was unable to get much testing help on the mailing
lists.
Reviewed by: freebsd-net
|
|
|
|
| |
Approved-by: jordan
|
|
|
|
|
|
|
|
| |
similar to ipfilter's keep-state.
Look at the updated ipfw(8) manpage for details.
Approved-by: jordan
|
|
|
|
|
|
|
|
| |
dummynet (already fixed in -stable, was waiting for Jordan's
approval due to the code freeze).
Reported-By: Mike Tancsa
Approved-By: Jordan
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
now you can dynamically create rate-limited queues for different
flows using masks on dst/src IP, port and protocols.
Read the ipfw(8) manpage for details and examples.
Restructure the internals of the traffic shaper to use heaps,
so that it manages efficiently large number of queues.
Fix a bug which was present in the previous versions which could
cause, under certain unfrequent conditions, to send out very large
bursts of traffic.
All in all, this new code is much cleaner than the previous one and
should also perform better.
Work supported by Akamba Corp.
|
|
|
|
|
|
|
|
| |
pr_input() routines prototype is also changed to support IPSEC and IPV6
chained protocol headers.
Reviewed by: freebsd-arch, cvs-committers
Obtained from: KAME project
|
|
|
|
|
|
| |
code failed in handling things like "forward" actions.
Reported-and-tested-by: Jean-Hugues ROYER jhroyer@joher.com
|
| |
|
|
|
|
| |
Reviewed by: bde, luigi
|
|
|
|
|
| |
times resulting in higher bandwidth and lower delays.
Reported-by: Jamshid Madhavi
|
|
|
|
| |
int variable - this can't work on an Alpha.
|
|
|
|
|
|
|
| |
routines. The descriptor contains parameters which could be used
within those routines (eg. ip_output() ).
On passing, add IPPROTO_PGM entry to netinet/in.h
|
|
|
|
|
|
|
| |
+ plug an mbuf leak when dummynet used with bridging
+ make prototype of dummynet_io consistent with usage
+ code cleanup so that now bandwidth regulation is precise to the
bit/s and not to (8*HZ) bit/s as before.
|
|
|
|
|
|
|
|
| |
- unifdef -DCOMPAT_IPFW (this was on by default already)
- remove traces of in-kernel ip_nat package, it was never committed.
- Make IPFW and DUMMYNET initialize themselves rather than depend on
compiled-in hooks in ip_init(). This means they initialize the same
way both in-kernel and as kld modules. (IPFW initializes now :-)
|
|
|
|
| |
anywhere that I can see).
|
|
|
|
|
|
|
|
| |
the IP header (this would not work for bridged packets).
This has been fixed long ago in the 2.2 branch.
Problem noticed by: a few people
Fix suggested by: Remy Nonnenmacher
|
| |
|
|
|
|
| |
kernel compile
|
| |
|
| |
|
|
|
|
|
| |
* Use the correct type for timeout function.
* Add missing #include.
|
|
|
|
|
|
|
| |
problems reported recently (the rtentry pointer in the dummynet
queue was not initialized in all cases, resulting in spurious
rt_refcnt decreases in the lucky cases, and memory trashing in
other cases.
|
| |
|
| |
|
|
|