Re: IP packet header visualization software

2017-11-01 Thread Kevin Oberman
On Wed, Nov 1, 2017 at 2:46 PM, DES <3...@inx.su> wrote: > Hello FreeBSD-Net, > > does anybody remember, around year 2004, there was a software application > available (either as port, or package). Unfortunately I do not recall the > application name and I'm not able to find it again, although I'v

Re: IP packet header visualization software

2017-11-01 Thread Bakul Shah
On Thu, 02 Nov 2017 00:46:25 +0300 DES <3...@inx.su> wrote: DES writes: > Hello FreeBSD-Net, > > does anybody remember, around year 2004, there was a software > application available (either as port, or package). Unfortunately I do > not recall the application name and I'm not able to find it ag

IP packet header visualization software

2017-11-01 Thread DES
Hello FreeBSD-Net, does anybody remember, around year 2004, there was a software application available (either as port, or package). Unfortunately I do not recall the application name and I'm not able to find it again, although I've reviewed the Ports collection from year 2005 which I have on

Low default setting of UDBHASHSIZE leads to unresponsive system

2017-11-01 Thread Lev Serebryakov
Now 11-STABLE (and 12-CURRENT too) have this: sys/netinet/udp_usrreq.c:#define UDBHASHSIZE 128 Looks like such low value could lead to 100% consumption of CPU by interrupt threads (igb queues in my case) on heavy incoming UDP traffic (torrents with uTP in my case). My system (E3-1220v3

Help provisioning a Samba AD in a jail on ZFS

2017-11-01 Thread Andrea Venturoli
Hello. As per subject, I'm building a new box which must host a jail running a Samba AD, but I have trouble provisioning it. Currently I'm trying samba44. I read a lot of material and I think I understand the problem: it seems the "samba-tool provision" script is incompatible with NFSv4ACL us

Re: FreeBSD 11.1-RELEASE: Kernel panic in ipv6_output() via tcp6_usr_connect()

2017-11-01 Thread Andrey V. Elsukov
On 31.10.2017 19:40, Viktor Dukhovni wrote: >> can you show your nat rules? > > Sure, igb0 is outside, igb1 is inside, the external IP > address is 100.2.39.101/24, the internal is 192.168.1.1/24. > The machine is the DNS server for the inside network and > does not NAT DNS traffic (makes thousand