Re: BCM57810 networkd card with SR-IOV : No driver detected
19.09.2020 5:10, Trevelian wrote: > I have a HP network card "533FLR-T" its based on "NetXtreme II BCM57810" > This card is capable to be used with SR-IOV, so I can have 64 NIC on each > physical port that I can passthrough from my Linux hypervisor to my Linux and > BSD guest VM. > > On Linux guest VM no problem I see the NIC on my VM and I can use it : > > |# lspci 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries > NetXtreme II BCM57810 10 Gigabit Ethernet Virtual Function| > > On BSD guest VM (I tested 11.3 and 12.1) the card seems to be not detected : > > |# dmesg pci0: at device 8.0 (no driver attached) # > pciconf -lv none0@pci0:0:8:0: class=0x02 card=0x3382103c chip=0x16af14e4 > rev=0x00 hdr=0x00 vendor = 'Broadcom Inc. and subsidiaries' device = > 'NetXtreme II BCM57810 10 Gigabit Ethernet Virtual Function' class = network > subclass = ethernet ||# kldload if_bxe kldload: can't load if_bxe: module > already loaded or in kernel| > || > > I try to force the driver with : > > |#devctl set driver pci0:0:8:0 bxe| > | > | > But it don't gave me any new network interface. > > Do you have any idea if its possible to make it work or the BXE driver is > just not compatible with the Virtual Function of this card ? It seems bxe(4) does not implement attaching to Virtual Function. Can't tell if it's by mistake or intentionally. CC'ing author of the driver davidch@ ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
BCM57810 networkd card with SR-IOV : No driver detected
Hello, I have a HP network card "533FLR-T" its based on "NetXtreme II BCM57810" This card is capable to be used with SR-IOV, so I can have 64 NIC on each physical port that I can passthrough from my Linux hypervisor to my Linux and BSD guest VM. On Linux guest VM no problem I see the NIC on my VM and I can use it : |# lspci 01:00.0 Ethernet controller: Broadcom Inc. and subsidiaries NetXtreme II BCM57810 10 Gigabit Ethernet Virtual Function| On BSD guest VM (I tested 11.3 and 12.1) the card seems to be not detected : |# dmesg pci0: at device 8.0 (no driver attached) # pciconf -lv none0@pci0:0:8:0: class=0x02 card=0x3382103c chip=0x16af14e4 rev=0x00 hdr=0x00 vendor = 'Broadcom Inc. and subsidiaries' device = 'NetXtreme II BCM57810 10 Gigabit Ethernet Virtual Function' class = network subclass = ethernet ||# kldload if_bxe kldload: can't load if_bxe: module already loaded or in kernel| || I try to force the driver with : |#devctl set driver pci0:0:8:0 bxe| | | But it don't gave me any new network interface. Do you have any idea if its possible to make it work or the BXE driver is just not compatible with the Virtual Function of this card ? Thanks for your help, Trevelian. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ifconfig_*="DHCP" in absence of server
18.09.2020 20:05, Gleb Popov wrote: > However, the networking on FreeBSD machines started to come up even longer. > I suspect this is because dhclient gradually increases the interval between > DHCP requests if it doesn't get an answer. Our dhclient does logging via syslog, so you should setup syslog.conf: !dhclient *.* /var/log/dhclient.log You'll know exactly what is happening. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ifconfig_*="DHCP" in absence of server
18.09.2020 20:05, Gleb Popov wrote:
>> Look for "background_dhclient" in the rc.conf manual page, it merely adds
>> "-b"
>> to dhclient flags.
>>
>>
> Thanks, this indeed improved things for the "netif" part of the problem.
> But it still waited 30s for "default route interface". I found the
> ${defaultroute_delay} variable in /etc/rc.d/defaultroute, which isn't
> documented, and set it to "1s" in /etc/rc.conf. This finally did the trick.
>
> However, the networking on FreeBSD machines started to come up even longer.
> I suspect this is because dhclient gradually increases the interval between
> DHCP requests if it doesn't get an answer. I haven't found a way to
> circumvent this. Any suggestions are welcome.
Read dhclient.conf(5) manual page :-)
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
NCR Global Customer Contact List
Hello, I just wanted to know if you're looking to acquire NCR Global Customer Contact List. Information Field: Names, Title, Email, Phone, Company Name, Company URL, Company physical address, SIC Code, Industry and Company Size (Revenue and Employee). Kindly let me know of your target interest so that I can get back to you with counts and pricing information. Regards, Jean Marcil Database Executive Lead Gen Marketing LLC If you do not wish to receive these emails. Please respond Exit. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: ifconfig_*="DHCP" in absence of server
On Fri, Sep 18, 2020 at 7:31 AM Eugene Grosbein wrote:
>
> Look for "background_dhclient" in the rc.conf manual page, it merely adds
> "-b"
> to dhclient flags.
>
>
Thanks, this indeed improved things for the "netif" part of the problem.
But it still waited 30s for "default route interface". I found the
${defaultroute_delay} variable in /etc/rc.d/defaultroute, which isn't
documented, and set it to "1s" in /etc/rc.conf. This finally did the trick.
However, the networking on FreeBSD machines started to come up even longer.
I suspect this is because dhclient gradually increases the interval between
DHCP requests if it doesn't get an answer. I haven't found a way to
circumvent this. Any suggestions are welcome.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: poor performance with Intel X520 card
On Fri, 10 Jul 2020 08:45:30 +0200 Patrick Lamaiziere wrote: > Hello, > > That is mostly for the record but it looks like the intel X520 is not > very good and generates a high level of interrupts. ... Oh I forgot to thank you all for yours replies, sorry. I will try to play with the parameters of ix at first and I will wait for the remplacement of the hardware for the rest. Regards, ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Fwd: Fragmentation of em(4) traffic (potentially others) when using vlanhwtag 12.2-BETA1
Cross-posting this issue that exists in the 12.2 cut. Cheers. -- Forwarded message - From: Jason Tubnor Date: Thu, 17 Sep 2020 at 10:49 Subject: Fragmentation of em(4) traffic (potentially others) when using vlanhwtag 12.2-BETA1 To: freebsd-stable Hi, Doing some edge case testing with 12.2-BETA1, I have come across fragmentation issues when vlanhwtag is enabled on the em(4) network device (device listed below), causing IPSec traffic moving through a bhyve 'router-on-a-stick' to tank on send. When you disable (-vlanhwtag), this issue goes away and full speed send is possible. Here is a snip of the traffic leaving for the internet after traversing several VLANs through a bhyve router with vlanhwtag enabled: 10:09:54.173412 Dest.443 > Source.60901: . ack 12384 win 492 (DF) 10:09:54.173936 Source.60901 > Dest.443: . 38413:39873(1460) ack 3837 win 1027 (frag 20228:1480@0+) 10:09:54.173937 Source > Dest: (frag 20228:1420@1480) pciconf -vlbc em0@pci0:0:25:0:class=0x02 card=0x308617aa chip=0x15028086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82579LM Gigabit Network Connection (Lewisville)' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xf7d0, size 131072, enabled bar [14] = type Memory, range 32, base 0xf7d39000, size 4096, enabled bar [18] = type I/O Port, range 32, base 0xf080, size 32, enabled cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 13[e0] = PCI Advanced Features: FLR TP Happy to provide further information if required and perform testing to make sure the 12.2 release is polished. Thanks, Jason. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
