[vnet] [epair] epair interface stops working after some time

[Kristof Provost]

On 5 Jan 2018, at 20:54, Reshad Patuck wrote:
> I have done the following on both servers to test what happens:
> - Created a new epair interface epair3a and epair3b
> - upped both interfaces
> - given epair3a IP address 10.20.30.40/24 (I don't have this subnet
> anywhere in my network)
> - attempted to ping 10.20.30.50
> - checked for any packets on epair3b
> On the server where epairs are working, I can see APR packets for
> 10.20.30.50, but on the server where epairs are not working I cant see 
> any
> packets on epair3b.
> I can however see the arp packets on epair3a on both servers.
>
So epair3a was not added to the bridge and epair3b was not added to a 
jail?
That’s interesting, because it should mean the problem is not with the 
bridge or jail.
As it affects ARP packets it also shouldn’t be a pf problem.
It might be worth unloading the pf module, just to re-confirm, but I 
wouldn’t expect it to make a difference.

> Please let me know if there is anything I can do the debug this issue 
> or if
> you need any other information.
>
Are you creating/destroying vnet jails at any point? Is there a 
correlation with that and the start of the epair issues?

Are there any errors in `netstat -s` or `netstat -i epair3a` ?

Regards,
Kristof