Hi,
On Apr 8, 2013, at 7:18, YongHyeon PYUN wrote:
> I don't have strong option on enabling that flag but I think it
> would be even better to have an option to enable/disable that
> feature(default off).
I agree that would be the better solution, but it's a larger patch to the
source.
> em(4)
On Mon, Apr 08, 2013 at 02:13:40PM +0200, Andre Oppermann wrote:
> On 05.04.2013 13:09, Matt Miller wrote:
> > Hey Rick,
> >
> > I believe Juan and I have root caused this crash recently. The t_state =
> > 0x1, TCPS_LISTEN, in the link provided at the time of the assertion.
> >
> > In tcp_input(),
On 09.04.2013 10:16, Peter Holm wrote:
On Mon, Apr 08, 2013 at 02:13:40PM +0200, Andre Oppermann wrote:
On 05.04.2013 13:09, Matt Miller wrote:
Hey Rick,
I believe Juan and I have root caused this crash recently. The t_state =
0x1, TCPS_LISTEN, in the link provided at the time of the assertio
Hi there,
Lately I was experiencing an issue while trying to recreate a particular setup
for my networking interfaces that I
would like to share.
I'm running FreeBSD 8.3, but I also see the same issue in FreeBSD 10.0
(CURRENT).
My setup looks like this:
em0 --- vlan0
Currently source address selection for raw packets under jails
uses prison_get_ip4 in the INADDR_ANY case.
This can cause an invalid source address to be used, including
using addresses which are unusable e.g. down interfaces
un-routable addresses etc.
I suspect this is a hang over from when jai
On Tue, Apr 09, 2013 at 10:35:30AM +0200, Andre Oppermann wrote:
> On 09.04.2013 10:16, Peter Holm wrote:
> > On Mon, Apr 08, 2013 at 02:13:40PM +0200, Andre Oppermann wrote:
> >> On 05.04.2013 13:09, Matt Miller wrote:
> >>> Hey Rick,
> >>>
> >>> I believe Juan and I have root caused this crash re
