committer filter by committer.
@path/to/ filter by path in repository.
committer@path/to/ filter by committer AND path in repository.
NNN or rNNN filter by revision.
NNN-MMM or rNNN-rMMM filter by revisions range (inclusive).
Multiple filters can be specified separated by spaces or comas in which case they'll be combined using OR operator.
|r339550||ae||Oct. 21, 2018, 5:55 p.m.||Add KPI that can be used by tunneling interfaces to handle IP addresses
appearing and disappearing on the host system. Such handling is need, because tunneling interfaces must use addresses, that are configured on the host as ingress addresses for tunnels. Otherwise the system can send spoofed packets with source address, that belongs to foreign host. The KPI uses ifaddr_event_ext event to implement addresses tracking. Tunneling interfaces register event handlers and then they are notified by the kernel, when an address disappears or appears. ifaddr_event_compat() handler from if.c replaced by srcaddr_change_event() in the ip_encap.c MFC after: 1 month Sponsored by: Yandex LLC Differential Revision: https://reviews.freebsd.org/D17134ViewVC
|r339548||vmaffione||Oct. 21, 2018, 5:15 p.m.||man: fix vale(4) port naming|
|r339547||kp||Oct. 21, 2018, 4:51 p.m.||vlan: Fix panic with lagg and vlan
vlan_lladdr_fn() is called from taskqueue, which means there's no vnet context set. We can end up trying to send ARP messages (through the iflladdr_event event), which requires a vnet context. PR: 227654 MFC after: 3 daysViewVC
|r339546||imp||Oct. 21, 2018, 4:49 p.m.||Remove stray refernce to pdq. Like the infamous twenty first of Johan
Sebastian Bach's twenty children, it hasn't been seen in many years.ViewVC
|r339545||ae||Oct. 21, 2018, 4:44 p.m.||Do not decrement RST life time if keep_alive is not turned on.
This allows use differen values configured by user for sysctl variable net.inet.ip.fw.dyn_rst_lifetime. Obtained from: Yandex LLC MFC after: 3 weeks Sponsored by: Yandex LLCViewVC
|r339544||ae||Oct. 21, 2018, 4:37 p.m.||Call inet_ntop() only when its result is needed.
Obtained from: Yandex LLC MFC after: 3 weeks Sponsored by: Yandex LLCViewVC
|r339543||imp||Oct. 21, 2018, 4:29 p.m.||Remove stray fatm reference.|
|r339542||ae||Oct. 21, 2018, 4:29 p.m.||Retire IPFIREWALL_NAT64_DIRECT_OUTPUT kernel option. And add ability
to switch the output method in run-time. Also document some sysctl variables that can by changed for NAT64 module. NAT64 had compile time option IPFIREWALL_NAT64_DIRECT_OUTPUT to use if_output directly from nat64 module. By default is used netisr based output method. Now both methods can be used, but they require different handling by rules. Obtained from: Yandex LLC MFC after: 3 weeks Sponsored by: Yandex LLC Differential Revision: https://reviews.freebsd.org/D16647ViewVC
|r339541||gjb||Oct. 21, 2018, 3:54 p.m.||Comment -DNDEBUG in head after r339436 when head was switched
from 12.0-ALPHA10 to 13.0-CURRENT. This edit was a mistake, and should have been applied to stable/12 upon branching, not head. Reported by: jbeich, dim Sponsored by: The FreeBSD FoundationViewVC
|r339540||andrew||Oct. 21, 2018, 3:43 p.m.||Split out the virtio mmio FDT attachment and add an ACPI attachment.
This allows the memory mapped I/O virtio driver to attach when we boot with ACPI tables, for example in some cases with QEMU emulating arm64. MFC after: 1 monthViewVC
|r339539||ae||Oct. 21, 2018, 3:10 p.m.||Add IPFW_RULE_JUSTOPTS flag, that is used by ipfw(8) to mark rule,|
|r339538||imp||Oct. 21, 2018, 3:09 p.m.||Tag this obsolete driver. It was obsolete in 3.x when the sym driver
supported all the "old" chips it did, so we should have killed it in 4, but 12 will do. It's a bit outside of the normal deprecation process, but given the extreme age, it's obsolete status for 8 major releases and the fact that I couldn't find any users who posted dmesgs with ncr0: in them after 2000 or 3.4. It may be too late for 12 (this change will be merged, but maybe not the next one to remove it), but it will be removed in 13 with the first round of other drivers tagged to be gone in 12. MFC after: 3 daysViewVC
|r339537||ae||Oct. 21, 2018, 3:02 p.m.||Add ifaddr_event_ext event. It is similar to ifaddr_event, but the|
|r339536||ae||Oct. 21, 2018, 2:48 p.m.||Fix grammar.
Reported by: yuripv MFC after: 3 weeksViewVC
|r339535||ae||Oct. 21, 2018, 2:40 p.m.||Do not allow use `create` keyword as hostname when ifconfig(8) is invoked
for already existing interface. It appeared, that ifconfig(8) assumes `create` keyword as hostname and tries to resolve it, when `ifconfig ifname create` invoked for already existing interface. This can produce some unexpected results, when hostname resolving has successfully happened. This patch adds check for such case. When an interface is already exists, and create is only one argument, return error message. But when there are some other arguments, just remove create keyword from the arguments list. Obtained from: Yandex LLC MFC after: 3 weeks Sponsored by: Yandex LLC Differential Revision: https://reviews.freebsd.org/D17171ViewVC