Re: LOR in iflib_timer

2017-10-30 Thread Stephen Hurd
Eric van Gyzen wrote: Twice a day, my router hits an LOR in iflib_timer when it jumps to the "hung" label. It's running r325049 (head 3 days ago). lock order reversal: 1st 0xfef36068 igb1:tx(0):call (igb1:tx(0):call) @ /usr/src/sys/kern/kern_mutex.c:182 2nd 0xf80003b0c150 igb1 (

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

2017-10-30 Thread Viktor Dukhovni
I am using FreeBSD 11.1 as the O/S for my DANE/SMTP adoption scanner. The system has an IPv4 static IPv4 and also a corresponding 6to4 address on stf0. The system is stable when I run IPv4-only scans, but crashes quickly as soon as I start a bulk scan that also connects to the IPv6 addresses of r

Re: VLANing between jails not segmenting traffic

2017-10-30 Thread Michael Gmelin
> On 30. Oct 2017, at 22:26, Eugene Grosbein wrote: > > 31.10.2017 4:08, Farhan Khan пишет: >> Hi all, >> >> I am trying to experiment with setting up two jails on different VLANs, but >> have not been able to segment traffic. >> >> My configuration was to create vlan1 for jail1 and vlan2 fo

Re: VLANing between jails not segmenting traffic

2017-10-30 Thread Eugene Grosbein
31.10.2017 4:08, Farhan Khan пишет: > Hi all, > > I am trying to experiment with setting up two jails on different VLANs, but > have not been able to segment traffic. > > My configuration was to create vlan1 for jail1 and vlan2 for jail2. > > I did the following commands: > ifconfig vlan1 creat

VLANing between jails not segmenting traffic

2017-10-30 Thread Farhan Khan
Hi all, I am trying to experiment with setting up two jails on different VLANs, but have not been able to segment traffic. My configuration was to create vlan1 for jail1 and vlan2 for jail2. I did the following commands: ifconfig vlan1 create vlan 1 vlandev em0 ifconfig vlan1 10.1.0.1/24 ifco

LOR in iflib_timer

2017-10-30 Thread Eric van Gyzen
Twice a day, my router hits an LOR in iflib_timer when it jumps to the "hung" label.  It's running r325049 (head 3 days ago). lock order reversal:  1st 0xfef36068 igb1:tx(0):call (igb1:tx(0):call) @ /usr/src/sys/kern/kern_mutex.c:182  2nd 0xf80003b0c150 igb1 (iflib ctx lock) @ /usr