Age | Commit message (Collapse) | Author |
|
fixes pflog attributing states wrongly to anchors and pfctl -vvsn/sr
showing wrong state counters for anchor rules. found by camield@,
ok henning@, -stable candidate
|
|
by default label.
- fill in kn_data with the number of bytes available, same
behavior as FreeBSD/NetBSD.
ok tedu@
|
|
First match wins, just like "no {binat,nat,rdr}". henning@, dhartmei@ ok
|
|
and behaved incorrectly when used with v6. impliment the v6 case too.
ok canacar mcbride
|
|
problems with adaptive timeouts, max-states limits, and rules not being
freed from memory.
Diff from Chris Pascoe.
ok henning@ dhartmei@
|
|
|
|
forgot to commit...
|
|
ok millert@
|
|
|
|
interface. Where the most common DLT is the one with the smallest id.
This fixes tcpdump for atw(4) that attaches multiple bpf hooks.
Tested: millert@, Sigfred Haversen, otto@, mcbride@, sturm@, krw@,
Steve Shockley
OK millert@ deraadt@
|
|
from jaredy@, ok henning@, mcbride@, deraadt@
|
|
being inserted, so that the counter does not wrap back when the state
is removed. This fixes pfsync setups with adaptive timeouts.
From Chris Pascoe
ok canacar@ dhartmei@ henning@ deraadt@
|
|
reported by Robert Stone ( robert at arbor net ) via PR 3852
This is a different fix since gre(4) may carry non-ip packets.
tested by Robert Stone and markus@ ok markus@ deraadt@
|
|
|
|
sideffects in IPv6 land, noticed by Johan Fredin <griffin@legonet.org>
|
|
from Max Laier <max@love2party.net>
|
|
extends the bitmap to 64bits. Also repair SADB_GET. hshoexer@ ok.
|
|
create an interface entry with the same name. Prevents panics due to
subsequent invalid refcounting.
from Chris Pascoe
ok dhartmei@ henning@
|
|
ok krw@ henning@
|
|
copy.
ok millert@ deraadt@ henning@
|
|
|
|
to a route.
the label is sent over the routing socket wrapped into a new
struct sockaddr_rtlabel, allowing for handling it like any other sockaddr.
struct rtentry only contains a (16 bit) label-ID, with the actual labels
kept outside the routing table.
ID allocator code inspired by my own code for altq and pf tags.
mostly hacked at the c2k4 hackathon, markus ok
|
|
updates to; this allows pairs of pfsync firewalls to protect the traffic
with IPSec.
|
|
|
|
certain rare cases.
ok mcbride@ dhartmei@
|
|
|
|
as an extension to the sequence number got disabled because of the failing idle
limit on PAWS checks. One more thing off my todo list. I need an intern
|
|
|
|
|
|
daniel found it.
|
|
requested by deraadt
|
|
ok henning@
|
|
on v6 addresses.
Reported by Ilya A. Kovalenko, fix from Cedric Berger.
|
|
does not get overwritten.
Report and fix from Chris Pascoe.
|
|
|
|
which drivers are hotpluggable. since we removed the stupid check from pfctl
a few days ago nothing relies on this any more.
ok pb@ mcbride@
|
|
|
|
|
|
|
|
From Seishi Hiragushi via FreeBSD PR kern/49957.
Also, while we're here, make the loop counter size_t.
ok mcbride@
|
|
by "ifconfig fxp0 group foobar" "ifconfig xl0 group foobar"
these two interfaces are in one group.
Every interface has its if-family as default group.
idea/design from henning@, based on some work/disucssion from Joris Vink.
henning@, mcbride@ ok.
|
|
remaining TODO:
- "forward" case kernel behavior (IPv4 too), then pfctl syntax change
- red-black tree
|
|
pfctl is assuming that the keyword == 0 in its parser! (see decl for "dir").
|
|
the link0 flag via ifconfig(8). OK markus@, canacar@ also tested by ish@
|
|
ok millert@
|
|
caveats: (to be addressed soon)
- "scrub in" should queue fragments back into ip6intrq again, but
somehow it does not happen - the packet is kept inside reass queue.
need investigation
- ip6_forwarding path is not tested
- does not use red-black tree. somehow red-black tree behaved badly
and was not robust. performance issue, the above one is more
important.
good things:
- "scrub out" is perfectly ok
- i think now we can inspect upper-layer protocol fields (tcp port)
even if ip6 packet is fragmented.
- reass queue will be cleaned up properly by timeout (60sec). we might
want to impose pool limit as well
|
|
ok itojun claudio
|
|
encapsulating all such access into wall-defined functions
that makes sure locking is done as needed.
It also cleans up some uses of wall time vs. uptime some
places, but there is sure to be more of these needed as
well, particularily in MD code. Also, many current calls
to microtime() should probably be changed to getmicrotime(),
or to the {,get}microuptime() versions.
ok art@ deraadt@ aaron@ matthieu@ beck@ sturm@ millert@ others
"Oh, that is not your problem!" from miod@
|
|
ktable being destroyed, which makes it unsafe in a SLIST_FOREACH.
Fix from Chris Pascoe
|
|
Based in part on a diff from Matthew Gream.
|