date:20210502

[Bug 238411] igb(4): Wake on Lan not working with Intel I210

2021-05-02 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238411 --- Comment #22 from Abraham122x --- What I can remember of my tests for my flashless NIC: - Some FreeBSD 11 releases: possible to set WOL flags with ifconfig (important is to avoid MCAST and UCAST flags, as they are triggered automatical

Re: IPsec performace - netisr hits %100

2021-05-02 Thread Andrey V. Elsukov

30.04.2021 23:32, Mark Johnston пишет: > Second, netipsec unconditionally hands rx processing off to netisr > threads for some reason, that's why changing the dispatch policy doesn't > help. Maybe it's to help avoid running out of kernel stack space or to > somehow avoid packet reordering in some

[Bug 238411] igb(4): Wake on Lan not working with Intel I210

2021-05-02 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238411 --- Comment #23 from Kaho Toshikazu --- Created attachment 224609 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=224609&action=edit patch:force to enable wol (In reply to Abraham122x from comment #22) I'm sorry, you are right.

Re: IPsec performace - netisr hits %100

2021-05-02 Thread Andrey V. Elsukov

30.04.2021 23:11, Özkan KIRIK пишет: > Hello, > > I'm using FreeBSD stable/12 built world on 12 April 2021. > my setup is: > [freebsd host cc0] <> [cc1 - same freebsd, but jail] > > without IPsec, I can achieve easily to 20Gbps. (test was run with different > source IPs using multiple ipe

Re: IPsec performace - netisr hits %100

2021-05-02 Thread Özkan KIRIK

Hello, The flamegraph is attached. # netstat -s ... ipsec: 0 inbound packets violated process security policy 0 inbound packets failed due to insufficient memory 0 invalid inbound packets 0 outbound packets violated process security policy 0 outbound packets

[Bug 238411] igb(4): Wake on Lan not working with Intel I210

2021-05-02 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238411 --- Comment #24 from Abraham122x --- (In reply to Kaho Toshikazu from comment #23) I applied your patch (except sub "em_get_wakeup" because I don't have the new enumerations in my package) and can confirm it does exactly what I need: ifcon

[Bug 241954] netgraph fails on concurrent node rename

2021-05-02 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241954 Lutz Donnerhacke changed: What|Removed |Added Status|New |Open CC|

Problem reports for n...@freebsd.org that need special attention

2021-05-02 Thread bugzilla-noreply

To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 254333] [tcp] sysctl net.inet.tcp.hostcache.list hangs

2021-05-02 Thread bugzilla-noreply

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254333 Richard Scheffenegger changed: What|Removed |Added Status|In Progress |Closed Resolution|

Re: Problem with resolver/host

2021-05-02 Thread Doug Hardie

> On 20 April 2021, at 14:12, Doug Hardie wrote: > > I suspect this is an issue with the resolver, but it could also be in host. > I have the following in /etc/resolv.conf: > > # Generated by resolvconf > nameserver fe80::213:72ff:fec3:180f%bge0 > nameserver fe80::120c:6bff:fee9:cdf7%bge0 > >