| Age | Commit message (Collapse) | Author |
|---|
|
OK pamela
|
|
|
|
ignore if sysctl -a is used.
OK bluhm@
|
|
in ieee80211com's ic_flags because we haven't been paying attention to
them (they're not in the same place in the code and hence easy to miss).
Move them to a dedicated variable to avoid this problem in the future.
Add a new 'stayauth' nwflag which can be set to let net80211 ignore
deauth frames. This can be useful when deauth frames are being
persistently spoofed by an attacker. Idea from beck@
ok beck@ phessler@
|
|
at the end of void functions.
First one pointed out by Andrey Sokolov via bugs@
|
|
ok sthen@
|
|
|
|
ok kettenis
|
|
RTM_IFINFO seen. As dhclient no longer commits suicide to restart the
protocol this should be very low cost.
This will help some trunk(4) setups after some pending network stack
commits.
Requested by & ok florian@
|
|
list of ioctls in bridge(4).
OK ccardenas@ kn@ phessler@
|
|
(again?): when adding the default route, set it with the interface
address of the interface we are configuring. This way its possible to
have two default routes (from two running dhclient processes) in the
routing table. Since wireless interfaces have a higher prio value,
when a physical interface is connected it will be prefered (for new
connections).
ok krw@ mumble yes mumble claudio@
|
|
during rekeying to make sure that the response is not rejected.
From Tobias Heider
"much more stable" dhill@
|
|
encrypted payloads. Also increment message id only for valid
messages.
From Tobias Heider
ok sthen@
|
|
in the block list it answers with rcode REFUSED.
|
|
ok krw@, jsg@
|
|
on-disk one to give us a better chance on root KSK roll. Either we
were online during the time the key rolled or we are running on a
version of unwind(8) that has the new KSK.
|
|
(bug found and fixed by Petr Hoffmann _at_ oracle.com)
OK kn@
|
|
great input by Ingo, Jason and Klemens
OK schwarze@, OK kn@, OK jmc@
|
|
resolver context. Otherwise we will ignore the answer later on
anyway.
|
|
|
|
okay schwarze@, jmc@
|
|
help/ok claudio
|
|
This and pledge("rpath") can go once we switch to RTM_PROPOSAL.
|
|
has been modified. Use name of disk being edited in fdisk(8) editor
prompt.
Idea from tb@.
ok tb@ deraadt@
|
|
|
|
a vnd. Seperate out the code a fair bit.
|
|
|
|
okay deraadt@
|
|
OK deraadt@
|
|
I'm considering simply deleting mount_vnd -- are there any users of this
bizzare feature?
|
|
|
|
|
|
|
|
option which will ease distribution build.
not connected to the build yet.
|
|
reported by Fabio Scotoni <fabio at esse dot ch>;
also garbage collect one .Tn while here
|
|
|
|
this complements txprio and should finish support for RFC 2983
ok claudio@
|
|
`-t table -T add|replace ...' would only check for duplicate tables in case
addresses where actually to the table.
Instead of using a positive number of added addresses as prove for
successful table operations, rely on the fact that CREATE_TABLE() is
guaranteed to be called only if pf(4) can be accessed, that is
warn_duplicate_tables() will return.
This improves duplicate detection rate as warnings are now also emitted
even when table commands eventually leave tables unchanged.
OK benno sashan
|
|
revision 1.689 introduced warn_duplicate_tables() unconditionally, breaking
the parser on tables withs insufficient permissions to open pf(4):
$ echo 'table <t>' | pfctl -nf-
pfctl: pfr_get_tables: Bad file descriptor
So simply check whether pfctl is able to get the table list first. If not,
instead of silently avoiding namespace collision checks, print a brief
notice iff `-v' is given to help finding duplicate definitions by hand:
$ echo 'table <t>' | ./obj/pfctl -vnf-
table <t>
stdin:1: skipping duplicate table checks for <t>
Reported by Rivo Nurges, thanks!
OK benno sashan
|
|
better...
|
|
|
|
(discussed with many at tech@)
OK deraadt@, kn@, sthen@, tedu@
|
|
These were deprecated with 6.3, but instead of removing them all together,
keep [-]vlan and [-]vlandev as aliases for [-]vnetid and [-]parent.
Alias idea from sthen
OK dlg sthen benno
|
|
|
|
qsfp was originally defined in SFF-8436, but the management interface
now seems to be managed in SFF-8636, so this uses sff8636 as a
prefix for qsfp things. the same spec applies to qsfp+ and probably
qsfp28.
XFP and QSFP share a bunch of offsets for where strings are located,
so this factors out the printing of those strings from the xfp code
and uses it from both the xfp and qsfp handling.
i have a qsfp+ to 4x sfp+ cable that looks like this with the new
code:
transceiver: QSFP+
model: Amphenol 601110005 rev A
serial: CN0HVVVFxxxxxxx date: 2013-04-18
if i ever get a pair of optics i can work on the diags
|
|
xfp uses a different page layout compared to sfp. xfp uses info in
INF-8077, not SFF-8472, and by default provides the info at page
1, not 0.
myx(4) supports xfp modules, but doesn't support i2c writes so it
cannot change the page the chip is looking at. it appears that myx
defaults to page 1 for xfp, so if the first read of page 0 fails
with ENXIO, try to read page 1 instead.
a 10G-PCIE-8A-R myx with the only xfp module i could find lying
around looks like this:
transceiver: XFP
model: Intel Corp TXN181070850X1J rev B3
serial: USC2048M95 date: 2005-04-13
im not sure if it's worth spending much more time on these though..
|
|
|
|
(like media/joinlist do) rather than totally separate; this also allows
"ifconfig -a sff" or "ifconfig ix sff".
tweak display format to make it look closer to the standard lines.
ok deraadt
|
|
because these are the commonly used terminology
ok claudio sthen
|
|
|
