[Bug 166724] [re] if_re watchdog timeout

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 --- Comment #44 from Chris Hutchinson --- (In reply to Bob Smith from comment #42) The ideal number will vary by card (model/brand/...) We only ever experienced the watchdog(8) problem on any of our RealTek cards on FreeBSD-11.x. We have *n

[Bug 166724] [re] if_re watchdog timeout

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=166724 Ralf Wostrack changed: What|Removed |Added CC||ralf.wostr...@gmx.de --- Comment #

epoch and ath(4) - what should we be doing?

hi! I'd like to update ath(4) to properly work with epoch, as that whole "oh make taskqueues epoch aware" is just not enough for ath(4). Background: * receive is done using deferred taskqueues, but * receive queues are drained/handled too outside of taskqueues - notably during interface resets,

Re: How to work with in 1GbE network ?

On Thu, 20 Feb 2020 07:17:35 +0900, alan somers wrote: > > Make sure that dns resolution is working, forward and reverse. That's it ! I've mistaken to reset /etc/resolv.conf in which included local IP DNS. Thanks for pointed out my rudimentary mistakes. > > On Wed, Feb 19, 2020, 2:53 PM Eric

Re: vtnet IFF_NEEDSEPOCH?

On Tue, Feb 18, 2020 at 10:08:50PM +0100, Kristof Provost wrote: K> > K> with vtnet: K> > K> K> > K> DHCPDISCOVER on vtnet0 to 255.255.255.255 port 67 interval 5 K> > K> panic: Assertion in_epoch(net_epoch_preempt) failed at K> > K> /usr/src/sys/net/netisr.c:1093 K> > K> cpu

Re: How to work with in 1GbE network ?

Make sure that dns resolution is working, forward and reverse. On Wed, Feb 19, 2020, 2:53 PM Eric Joyner wrote: > Have you tried turning off jumbo frames? > > - Eric > > On Tue, Feb 18, 2020 at 10:04 PM KIRIYAMA Kazuhiko > wrote: > > > Hi, all > > > > I wonder how to work ixgbe in 1GbE network.

Re: How to work with in 1GbE network ?

Have you tried turning off jumbo frames? - Eric On Tue, Feb 18, 2020 at 10:04 PM KIRIYAMA Kazuhiko wrote: > Hi, all > > I wonder how to work ixgbe in 1GbE network. I tried to test > in below: > > internet > | > +---++ > | Netgear JGS516 | > +---+-+--+ +-

[Bug 187835] ngctl(8) strange behavior when adding more than 530 vlan through nethraph

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187835 --- Comment #5 from Vladislav V. Prodan --- I also show DHclient errors: ... Feb 20 01:15:12 core dhclient[22934]: ngeth298: not found Feb 20 01:15:12 core dhclient[22934]: exiting. Feb 20 01:15:12 core root[22937]: /etc/rc.d/dhclient: WAR

[Bug 187835] ngctl(8) strange behavior when adding more than 530 vlan through nethraph

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187835 Vladislav V. Prodan changed: What|Removed |Added Version|10.0-STABLE |12.1-STABLE -- You are rece

[Bug 187835] ngctl(8) strange behavior when adding more than 530 vlan through nethraph

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187835 --- Comment #4 from Vladislav V. Prodan --- In FreeBSD 12.1, after adding 300 vlans, the memory runs out to display the `ngctl list`. # ngctl list ngctl: send msg: No buffer space available # netstat -m 4220/1100/5320 mbufs in use (curren

[Differential] D23737: nat64: Get the IPv4 address from a NAT64 address when comparing addresses in a ICMP translate

neel_neelc.org updated this revision to Diff 68545. neel_neelc.org added a comment. I decided to use the existing function nat64_extract_ip4() to extract the IPv4 and removed my nat64_get_ip4(). I'm new to the FreeBSD TCP/IP stack, sorry. REPOSITORY rS FreeBSD src repository CHANGES S

[Bug 208205] re0 watchdog timeout

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208205 Chris Hutchinson changed: What|Removed |Added CC||portmas...@bsdforge.com --- Com

Re: terrible if_vmx / vmxnet3 rx performance with lro (post iflib)

On 18/02/2020 16:09, Andriy Gapon wrote: > My general experience with post-iflib vmxnet3 is that vmxnet3 has some > peculiarities that result in a certain "impedance mismatch" with iflib. > Although we now have a bit less code and it is a bit more regular, there are a > few significant (for us, at

[Differential] D23737: nat64: Get the IPv4 address from a NAT64 address when comparing addresses in a ICMP translate

ae added a comment. Also, how did test your changes? :) NAT64 currently is not widely used, thus changes here can break something and you will know about breakage when it will be not so easy to fix, e.g. after release. REPOSITORY rS FreeBSD src repository CHANGES SINCE LAST ACTION ht

[Differential] D23737: nat64: Get the IPv4 address from a NAT64 address when comparing addresses in a ICMP translate

ae added a comment. In D23737#521593 , @neel_neelc.org wrote: > Here, I also compare the destination addresses. Is this what you want? No, take a look at RFC 6052 p2.2. . REPOSITORY rS Fre