The NETMAP code is all self-contained, just delete what's inside the ifdef's
Jack
-Original Message-
From: Arnaud Lacombe [mailto:lacom...@gmail.com]
Sent: Wednesday, February 08, 2012 3:25 PM
To: Vogel, Jack
Cc: freebsd-net@freebsd.org
Subject: Missed packet on recent em(4)
Hi Jack,
Hi Jack,
For the record, on the following hardware:
em3@pci0:5:0:0: class=0x02 card=0x150415bb chip=0x150c8086 rev=0x00 hdr=0x00
and the following version of em(4):
em3: port 0xec00-0xec1f
mem 0xfebe-0xfebf,0xfebdc000-0xfebd irq 19 at device 0.0
on pci5
em3: Using an MSI interr
On Feb 8, 2012, at 1:53 PM, Коньков Евгений wrote:
> some host on LAN can send packets to MAC address of FreeBSD server
>
> and server accept packets even if frame is not in its subnet and pass them
> further %-)
>
> details here
> http://www.freebsd.org/cgi/query-pr.cgi?pr=164914
Um, what were
some host on LAN can send packets to MAC address of FreeBSD server
and server accept packets even if frame is not in its subnet and pass them
further %-)
details here
http://www.freebsd.org/cgi/query-pr.cgi?pr=164914
___
freebsd-net@freebsd.org maili
Julian Elischer wrote:
On 2/8/12 1:08 PM, Joe Holden wrote:
Hey guys,
The maximum fibs is currently 16 due to an mbuf limitation I believe?
Is there any scope for the number being increased?
it was designed to be able to be expanable... there is only the one place.
there are upcoming FIB cha
On 2/8/12 1:08 PM, Joe Holden wrote:
Hey guys,
The maximum fibs is currently 16 due to an mbuf limitation I
believe? Is there any scope for the number being increased?
it was designed to be able to be expanable... there is only the one place.
there are upcoming FIB changes and it may be a goo
Hey guys,
The maximum fibs is currently 16 due to an mbuf limitation I believe? Is
there any scope for the number being increased?
Ta,
J
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, se
- Original Message -
From: "Gary Palmer"
Running the following commands does indeed stop this
route add -inet6 :::0.0.0.0 -prefixlen 96 ::1 -reject
route add -inet6 ::0.0.0.0 -prefixlen 96 ::1 -reject
I found these in /etc/rc.d/network_ipv6 but I can't see why
these wouldnt be run o
On Wed, Feb 08, 2012 at 01:44:56PM -, Steven Hartland wrote:
> - Original Message -
> From: "Gleb Smirnoff"
> >> Any update on this, would have been nice to see a fix hit before
> >> 9.0. If you need any more information please let me know.
> >
> >AFAIK, this is no longer a problem in
2012/2/8 Gleb Smirnoff :
> A> I would appreciate further review from network/netgraph related
> A> people. I'm going to borrow a term from gnn and say "Silence implies
> A> consent." :-)
>
> I have only minor comments:
Thanks for your feedback!
Ivan, can you please review these?
Adrian
>
> 1.
On Wed, Feb 08, 2012 at 03:04:09PM +0100, Ermal Lu?i wrote:
E> 2012/2/8 Gleb Smirnoff :
E> > On Tue, Jan 31, 2012 at 12:02:04PM +0100, Luigi Rizzo wrote:
E> > L> if i understand what the patch does, i think it makes sense to be
E> > L> able to hook ipfw instances to specific interfaces/sets of inte
2012/2/8 Gleb Smirnoff :
> On Tue, Jan 31, 2012 at 12:02:04PM +0100, Luigi Rizzo wrote:
> L> if i understand what the patch does, i think it makes sense to be
> L> able to hook ipfw instances to specific interfaces/sets of interfaces,
> L> as it permits the writing of more readable rulesets. Right
Synopsis: [route] ntpd(8): Repeating RTM_MISS packets causing high CPU load for
ntpd
Responsible-Changed-From-To: freebsd-net->freebsd-rc
Responsible-Changed-By: glebius
Responsible-Changed-When: Wed Feb 8 13:55:07 UTC 2012
Responsible-Changed-Why:
I think, that solution to the problem lives som
On Wed, Feb 08, 2012 at 01:44:56PM -, Steven Hartland wrote:
S> - Original Message -
S> From: "Gleb Smirnoff"
S> > > Any update on this, would have been nice to see a fix hit before
S> > > 9.0. If you need any more information please let me know.
S> >
S> > AFAIK, this is no longer a
- Original Message -
From: "Gleb Smirnoff"
> Any update on this, would have been nice to see a fix hit before
> 9.0. If you need any more information please let me know.
AFAIK, this is no longer a problem in 9.0-RELEASE or in HEAD.
The cause for this number of misses is absense of a ro
Synopsis: [netinet] [patch] [panic] VIMAGE + carp panics the kernel
State-Changed-From-To: open->closed
State-Changed-By: glebius
State-Changed-When: Wed Feb 8 13:38:23 UTC 2012
State-Changed-Why:
Fixed.
Responsible-Changed-From-To: freebsd-net->glebius
Responsible-Changed-By: glebius
Responsib
On Tue, Jan 31, 2012 at 12:02:04PM +0100, Luigi Rizzo wrote:
L> if i understand what the patch does, i think it makes sense to be
L> able to hook ipfw instances to specific interfaces/sets of interfaces,
L> as it permits the writing of more readable rulesets. Right now the
L> workaround is start th
On Fri, Feb 03, 2012 at 07:03:11AM +0900, rozhuk...@gmail.com wrote:
r> I am writing a netgraph node for processing UDP packets passing through the
r> router / bridge.
r> Node must fully inspect the entire contents of the package, in some cases,
r> change them.
In this case you need something like
On Tue, Feb 07, 2012 at 02:30:08PM +, Tushar Mulkar wrote:
T> Hello,
T> A patch is developed that has following enhancements in lagg driver
T>
T> - Sending a gratuitous ARP when link state changes on primary port of
T> lag (kern/156226)
T> - Support of new ioctl command to change primary po
Dmitrij,
On Wed, Feb 08, 2012 at 10:50:11AM +, Dmitrij Tejblum wrote:
D> I would suggest to remove RTM_MISS messages at all. I believe that there
D> is no sofware that actually use it. OTOH, in some cases RTM_MISS
D> messages are really disturbing.
D>
D> E.g., a router without defaul
The following reply was made to PR kern/161899; it has been noted by GNATS.
From: Gleb Smirnoff
To: Steven Hartland
Cc: freebsd-gnats-sub...@freebsd.org
Subject: Re: kern/161899: Repeating RTM_MISS packets causing high CPU load
for ntpd
Date: Wed, 8 Feb 2012 16:59:44 +0400
> Any update on thi
The following reply was made to PR kern/161899; it has been noted by GNATS.
From: Dmitrij Tejblum
To: bug-follo...@freebsd.org
Cc:
Subject: Re: kern/161899: [route] ntpd(8): Repeating RTM_MISS packets causing
high CPU load for ntpd
Date: Wed, 08 Feb 2012 14:30:51 +0400
I would suggest to r
On Tue, Feb 07, 2012 at 03:27:10PM -0800, Adrian Chadd wrote:
A> I've been working with the patch author on this and although I haven't
A> yet had time to test it out myself, he's taken my suggestions on board
A> and continued improving things.
A>
A> The patch can be found in the PR:
A>
A> http:/
The following reply was made to PR kern/161899; it has been noted by GNATS.
From: "Steven Hartland"
To: "Eugene Grosbein"
Cc: ,
Subject: Re: kern/161899: [route] ntpd(8): Repeating RTM_MISS packets causing
high CPU load for ntpd
Date: Wed, 8 Feb 2012 09:53:03 -
- Original Mes
- Original Message -
From: "Eugene Grosbein"
This is known problem. You should remove "options FLOWTABLE"
from your kernel configuration, as it was removed from GENERIC
for such misbehaviours. That had fixed same problem for me.
We already have this removed due to the issues it cause
The following reply was made to PR kern/161899; it has been noted by GNATS.
From: Eugene Grosbein
To: Steven Hartland
Cc: freebsd-net@freebsd.org, bug-follo...@freebsd.org
Subject: Re: kern/161899: [route] ntpd(8): Repeating RTM_MISS packets causing
high CPU load for ntpd
Date: Wed, 08 Feb 20
08.02.2012 03:30, Steven Hartland пишет:
> The following reply was made to PR kern/161899; it has been noted by GNATS.
>
> From: "Steven Hartland"
> To:
> Cc:
> Subject: Re: kern/161899: [route] ntpd(8): Repeating RTM_MISS packets causing
> high CPU load for ntpd
> Date: Tue, 7 Feb 2012 09:24
27 matches
Mail list logo
