RealTek 2.5 GbE (RTL8125) support?

2020-06-12 Thread Mel Pilgrim
Are RealTek 2.5 GbE NICs (RTL8125) supported? I don't see RLT8125 parts listed in if_re(4) or if_re.c, and that appears to be the only driver for RealTek gigabit NICs? ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo

Re: How to Increase TX Queue Priority for LACP Packets

2020-06-12 Thread Navdeep Parhar
On Fri, Jun 12, 2020 at 11:47:41PM +, Foster, Greg wrote: > FreeBSD Networkers, > > We are seeing LACP port flapping on our FreeBSD 10.4/12.1 systems under > different conditions. > > Can someone explain or point me to the information on how to queue the > LACP packets to a higher priority qu

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #8 from Ryan Moeller --- bnxt0: mem 0xe151-0xe151,0xe140-0xe14f,0xe1522000-0xe1523fff irq 54 at device 0.0 numa-domain 7 on pci1 bnxt0: Using 256 TX descriptors and 256 RX descriptors bnxt0: Using 0 RX queues 0

NDP Proxying Issue

2020-06-12 Thread Alex
Hi, I am running FreeBSD 12.1-RELEASE on DigitalOcean, where my Droplet is assigned 16 IPv6 addresses (2604::0 --> 2604::f). I would like it to respond to neighbor solicitation requests from DO, even though the IP being solicited is not bound to any interface on the machine. Based on my research,

How to Increase TX Queue Priority for LACP Packets

2020-06-12 Thread Foster, Greg
FreeBSD Networkers, We are seeing LACP port flapping on our FreeBSD 10.4/12.1 systems under different conditions. Can someone explain or point me to the information on how to queue the LACP packets to a higher priority queue ? We are using the Chelsio T580-LP-CR adapter/cxgbe driver. The Ches

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #7 from Ryan Moeller --- If you do pciconf -l -BbcevV it should be somewhere in the long list. If you can't get it though that's probably okay, there were some pretty good clues in the dmesg log already. -- You are receiving t

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #6 from Ian Smith --- Not sure how to obtain that, does not like pciconf bnxt0 or 1 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #5 from Ryan Moeller --- pciconf should have been for bnxt not bge. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #4 from Ian Smith --- truenas# pciconf -l -BbcevV bge0 bge0@pci0:193:0:0: class=0x02 card=0x08fd1028 chip=0x165f14e4 rev=0x00 hdr=0x00 vendor = 'Broadcom Inc. and subsidiaries' device = 'NetXtreme BCM572

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #3 from Ian Smith --- Created attachment 215503 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=215503&action=edit dmesg for ticket -- You are receiving this mail because: You are the assignee for the bug. __

[Bug 245981] BCM57414 not initializing

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 Ryan Moeller changed: What|Removed |Added CC||freql...@freebsd.org --- Comment #2

ndp -P => panic: prefix 0xfffff80011c56700 has referencing addresses

2020-06-12 Thread Ryan Stone
# ifconfig vtnet0 inet6 1::1 # ndp -P panic: prefix 0xf80011c56700 has referencing addresses cpuid = 1 time = 1591991817 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0022d08720 vpanic() at vpanic+0x19d/frame 0xfe0022d08770 panic() at panic+0x43/f

[Bug 247201] stat()'ing /dev/tap results in a new interface

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247201 Kyle Evans changed: What|Removed |Added CC||kev...@freebsd.org --- Comment #3 fro

[Bug 247201] stat()'ing /dev/tap results in a new interface

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247201 --- Comment #2 from Fabian Keil --- Quoting the man page: If the sysctl(8) variable net.link.tap.devfs_cloning is non-zero, the tap interface permits opens on the special control device /dev/tap. When this device is opened,

[Bug 247201] stat()'ing /dev/tap results in a new interface

2020-06-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247201 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv