[Bug 240825] Possible race between vlan interfaces and lagg(4) w/ em0/em1 post-EPOCH

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240825 Kubilay Kocak changed: What|Removed |Added CC||mm...@freebsd.org,

[Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new vlan created

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240818 Piotr Pietruszewski changed: What|Removed |Added CC||piotr.pietruszewski@intel.c

[Bug 236724] igb(4): Interfaces fail to switch active to inactive state

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 Kubilay Kocak changed: What|Removed |Added Blocks||240700 URL|

[Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementing (Unlimited) links

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240787 Aleksandr Fedorov changed: What|Removed |Added CC||aleksandr.fedorov@itglobal.

[Bug 239704] ixgbe(4): Only one queue (of eight) enabled on 12.0-RELEASE (ProLiant DL380 Gen10)

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239704 Kubilay Kocak changed: What|Removed |Added CC||n...@freebsd.org

[Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementing (Unlimited) links

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240787 --- Comment #4 from l...@donnerhacke.de --- Thank you for pointing me to phabricator. I'll try to find out how it works. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.

[Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementing (Unlimited) links

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240787 --- Comment #5 from l...@donnerhacke.de --- Moved to https://reviews.freebsd.org/D21803 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #21 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Thu Sep 26 15:37:40 UTC 2019 New revision: 352749 URL: https://svnweb.freebsd.org/changeset/base/352749 Log: MFC r352625: Revert

Re: rpc.statd already ipv6 clean?

2019-09-26 Thread Bjoern A. Zeeb
on-topic but here’s a diff from a work-tree of mine from sometime earlier this year: https://people.freebsd.org/~bz/20190926-01-golegacy.diff This is a lot of resolver and rpc (libc) code. I think this did compile but I am almost certain that a few changes are not doing the right thing and nee

Re: rpc.statd already ipv6 clean?

2019-09-26 Thread Rick Macklem
Mihir Luthra wrote: >Hiroki Sato wrote: >> >> >> I think you should learn TI-RPC API first. The nettype specifies a >> class of transport protocol, not address family. >> >> Thanks, I did some more research on TI-RPC today. >In `statd.c` what I see is in `create_service()`/`complete_service()`,

[Bug 240825] Possible race between vlan interfaces and lagg(4) w/ em0/em1 post-EPOCH

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240825 Hans Petter Selasky changed: What|Removed |Added CC||hsela...@freebsd.org ---

Re: rpc.statd already ipv6 clean?

2019-09-26 Thread Mihir Luthra
> > > I think you should learn TI-RPC API first. The nettype specifies a > class of transport protocol, not address family. > > Thanks, I did some more research on TI-RPC today. In `statd.c` what I see is in `create_service()`/`complete_service()`, transport info is being fetched through

[Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new vlan created

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240818 --- Comment #2 from Olivier Cochard --- Here is a user use case: FreeBSD as a router serving multiple customer: one customer per vlan. Each time we add a new customer, we add a VLAN… and the link re-init, so all the customers are

[Bug 240825] Possible race between vlan interfaces and lagg(4) w/ em0/em1 post-EPOCH

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240825 --- Comment #3 from Yaroslav Shvets --- However if destroy the broken vlan-interface and lagg-interface after FreeBSD booting, and create them again, the vlan-interface works. -- You are receiving this mail because: You are on the CC

[Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new vlan created

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240818 Andrey V. Elsukov changed: What|Removed |Added CC||a...@freebsd.org --- Comment

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 --- Comment #22 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Thu Sep 26 18:36:15 UTC 2019 New revision: 352766 URL: https://svnweb.freebsd.org/changeset/base/352766 Log: MFS r352749: Revert

[Bug 236724] igb(4): Interfaces fail to switch active to inactive state

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236724 Harald Schmalzbauer changed: What|Removed |Added CC||bugzilla.free...@omnilan.de

[Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report carrier loss.

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240658 Harald Schmalzbauer changed: What|Removed |Added Resolution|--- |DUPLICATE See

[Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report carrier loss.

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240658 Harald Schmalzbauer changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu

[Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade

2019-09-26 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233952 Mark Johnston changed: What|Removed |Added Resolution|--- |FIXED Status|Open

bridged vlan down but traffic still exists

2019-09-26 Thread Victor Gamov
Hi All I have vlan111 and vlan222 bridged into bridge2. Then multicast traffic from vlan111 sending and I get it at vlan222 even if 'ifconfig vlan222 down' issued. Is it bug or known feature? FreeBSD 12.0-STABLE r348449 GENERIC amd64 Thanks! -- CU, Victor Gamov

Re: rpc.statd already ipv6 clean?

2019-09-26 Thread Hiroki Sato
Mihir Luthra wrote in : lu> > lu> > lu> > I think you should learn TI-RPC API first. The nettype specifies a lu> > class of transport protocol, not address family. lu> > lu> > Thanks, I did some more research on TI-RPC today. lu> In `statd.c` what I see is in