Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
[...]
route add -net 192.168.0.100 192.168.0.200 255.255.255.255 1
Destination Gateway Flags Refs Use Netif Expire
0.0.0.0&0x1 192.168.0.200 UGS 0 0 bge
Try:
route delete 0.0.0.0 -netmask 0.0.0.1
It worked!
[...]
A 0.0.0.0/0.0.0.1 route matches every IP with bit 0 clear and is
half the
Thanks for reporting that, will see it gets fixed!
Jack
On Mon, Nov 29, 2010 at 9:51 AM, Eugene Grosbein wrote:
> Hi!
>
> I've just noticed new sysctl named flow_control has wrong description
> due to obvious cut-n-paste 'cosmetic' error :-)
>
>em_add_rx_process_limit(adapter, "rx_proce
Hi!
I've just noticed new sysctl named flow_control has wrong description
due to obvious cut-n-paste 'cosmetic' error :-)
em_add_rx_process_limit(adapter, "rx_processing_limit",
> "max number of rx packets to process", &adapter->rx_process_limit,
em_rx_process_limit)
On Mon, Nov 29, 2010 at 09:54:55AM -0800, Jack Vogel wrote:
> Thanks for reporting that, will see it gets fixed!
More serious problem. I had experienced kernel panics for two em(4)-based
heavy loaded routers. I've checked PR database and found this PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=
Not sure what code you created this from, but its not the new driver, things
have
been reorganized and I do not believe this issue exists. Please test with
the latest.
Jack
On Mon, Nov 29, 2010 at 10:26 AM, Eugene Grosbein wrote:
> On Mon, Nov 29, 2010 at 09:54:55AM -0800, Jack Vogel wrote:
>
>
On Mon, Nov 29, 2010 at 11:10:22AM -0800, Jack Vogel wrote:
> Not sure what code you created this from, but its not the new driver,
Yes, that's for previous version and that's what keeps my production
servers from panicing.
> things have been reorganized and I do not believe this issue exists.
>
True, there is no check, I do not see a way in which the mbuf
pointer should be NULL, however, perhaps I should change things
to follow what the igb driver does, always checking for NULL and
freeing the existing mbuf to allow em_refresh_mbufs() to repop.
If you say you have had panics then there
You use `ifconfig ix0 vlanhwfilter`, its off by default, I assume you're
using the
new driver code from either HEAD or STABLE/8 now, right?
Try another experiment please: at line 4232 is a condition: if
((adapter->num_vlans) &&...
Change that to: if ((vtag) &&
See if either of those chang
I rebuilt from a tree checked out nov 1, 2010 and rebuilt hostapd and it
works now, so it looks like the import did break it
On Wed, Nov 24, 2010 at 5:20 PM, Adrian Chadd wrote:
> Hi,
>
> Would you please try -head just before rui committed his wpa/hostapd
> update and report back to -net and Ru
Would you please create a PR for it?
Rui hasgiven me a pointer where to look at fixing it so I'll include
that in the PR.
Adrian
On 30 November 2010 07:25, David Cornejo wrote:
> I rebuilt from a tree checked out nov 1, 2010 and rebuilt hostapd and it
> works now, so it looks like the import
Hi,
Can anyone confirm that bridging a mesh with a wired interface is not
working? I want to make sure that it is not a problem from my side.
When I ping from outside the mesh I get: "!valid or proxy" and "frame
not fwd'd, no path" from the debug information.
My setup is simple
STA --- MPP )) -
12 matches
Mail list logo
