Yuri wrote on 04/01/2015 01:39:
Currently tap(4) device gets to 'down' state when the last process
closes it, regardless of the original 'up/down' state.
Will it be reasonable to modify this behavior and keep this bit
'was_up_before_open', and leave it 'up' if it was 'up' when it was first
opened
Hi,
I've got an urgent matter on my hands, my FreeBSD iScsibox has dropped it's
LACP trunk twice in the last 24 hours, which causes a whole lot of issues on my
VPS cluster, using that storage.
It's a FreeBSD box with two igb-interfaces in an LACP trunk with jumboframes
and vlans. If the conne
I run a small network composed of even smaller networks each
encapsulated in an autonomous system. I'd like to do traffic
accounting using netflow aggregated by ASN. My border routers run
FreeBSD and BIRD.
Right now, and this is mentioned in ng_netflow(4), we do not fill in
the source and destinat
On 4/1/15 6:50 PM, William Waites wrote:
I run a small network composed of even smaller networks each
encapsulated in an autonomous system. I'd like to do traffic
accounting using netflow aggregated by ASN. My border routers run
FreeBSD and BIRD.
Right now, and this is mentioned in ng_netflow(4)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967
--- Comment #18 from Jeroen van Heugten ---
In our case the problem was due to a bug in TSO (tcp segment offloading). This
has been resolved in 10.1. You can easily exclude issues TSO by turning it
temporary off for your interfaces (ifconfi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=171711
--- Comment #8 from dbl...@interplex.ca ---
I just opened a new bug:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199096 since my error is
similar but different.
--
You are receiving this mail because:
You are the assignee for the bug
On Wed, Apr 1, 2015 at 12:50 PM, William Waites
wrote:
> I run a small network composed of even smaller networks each
> encapsulated in an autonomous system. I'd like to do traffic
> accounting using netflow aggregated by ASN. My border routers run
> FreeBSD and BIRD.
>
> Right now, and this is m
Hi,
I posted into BR 171711 but as Andrey V. Elsukov pointed out, my issue is a bit
different so I opened a new one (BR 199096).
--
[cid:image001.gif@01D06C87.8255CBF0]
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/list
On 03/26/15 at 12:08P, hiren panchasara wrote:
> My mailclient is doing something funny. Sorry for that. Trying again to
> reply to this tread actually.
>
> On 03/26/15 at 09:55P, Andrey V. Elsukov wrote:
> > On 26.03.2015 00:48, hiren panchasara wrote:
> > > This is 3rd occurence of this panic. W
(Fixing the subject header. Oops)
On Wed, 1 Apr 2015 20:08:54 +0200, Nikolay Denev said:
> It's not ng_netflow, but if you need this today you can take a
> look at http://www.pmacct.net ? (there is a package/port too).
> It comes with BGP daemon (stripped down quagga) and can export
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197076
--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:
Author: jhb
Date: Wed Apr 1 21:48:59 UTC 2015
New revision: 280970
URL: https://svnweb.freebsd.org/changeset/base/280970
Log:
MFC 261790:
Add support for ma
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197076
John Baldwin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
On 04/01/2015 03:13, Miroslav Lachman wrote:
Doesn't sysctl net.link.tap.up_on_open=1 fix your problem?
net.link.tap.up_on_open only works on open.
I am going to create the corresponding net.link.tap.down_on_close.
It will have 3 values:
0: up/down state will not change on close
1: (default)
Additionally, pmacct doesn't seem to really work in FreeBSD -- as far as
the latest versions go.
Their use of 'return' (with no args) on functions that are meant to
return an int flat out makes it unable to compile on FreeBSD.
If you fix those by hand, it compiles, but just seems to segfault
14 matches
Mail list logo
