On Mon, Aug 31, 2009 at 07:48:32PM +, Stef Walter wrote:
> Julian Elischer wrote:
> > there are two ways to go with this one being what you have done teh
> > other to add fib info to the messages, Apparently
> > OpenBSD has implemented the second by re-using a disused field.
> > (I'm ve only be
Old Synopsis: Kernel panic after trying set monitor wlanmode on Intel 3945 ABG
(wpi driver)
New Synopsis: [wpi] [panic] Kernel panic after trying set monitor wlanmode on
Intel 3945 ABG (wpi driver)
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible
The following reply was made to PR kern/138292; it has been noted by GNATS.
From: "Paul A. Procacci"
To: ,
Cc:
Subject: Re: kern/138292: [zyd] [usb8] "zyd0: device timeout" with ZyXEL G-202
Date: Tue, 1 Sep 2009 00:02:58 -0500
I've got the same problem here for what it's worth.
zyd0: on
Hi Hiroki,
>
> 2) Issue of subnet-router anycast address with a global address
>
> Thanks for the fixes! With the two patches 1) and 3) are gone, but
> 2) still remains. Is there something I can help to narrow down it?
>
Hmm... I tried multiple test cases and all seem to work as expected.
lly.
Here's the patch:
http://people.freebsd.org/~bz/20090831-01-plug-new-arp-mbuf-leak.diff
Thanks for your help in advance.
/bz
looks pretty right...
all the paths I followed through did the right thing WRT locks and mbufs.
___
freebsd-net@fre
he patch:
http://people.freebsd.org/~bz/20090831-01-plug-new-arp-mbuf-leak.diff
Thanks for your help in advance.
/bz
--
Bjoern A. Zeeb What was I talking about and who are you again?
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org
On Mon, 2009-08-24 at 12:12 -0700, Graham Smith wrote:
> requiring creation of native vlan (vlan 0) and why native vlan are
> most suitable for this scene ?
Cisco highly recommend changing the management VLAN away from VLAN1.
Here's an example, of using alternative native VLANs, ironically, on t
Li, Qing wrote:
> There are other commands through the routing socket that
> can trigger routing messages. For example, issuing "ifconfig"
> to add and remove interface addresses.
Thanks for taking a look at this and catching that problem. Here's a new
patch which does the following:
* Both rt_d
The following reply was made to PR kern/134931; it has been noted by GNATS.
From: Stef Walter
To: "Li, Qing"
Cc: "freebsd-net@FreeBSD.org" ,
bug-follo...@freebsd.org, jul...@elischer.org
Subject: Re: kern/134931 [patch] Unbreak setfib + routing daemons
Date: Mon, 31 Aug 09 20:00:13 UTC
This
Julian Elischer wrote:
> there are two ways to go with this one being what you have done teh
> other to add fib info to the messages, Apparently
> OpenBSD has implemented the second by re-using a disused field.
> (I'm ve only been told this second hand)
It seems like they've taken apart the rtm_fl
Stef Walter wrote:
Currently route messages are sent to all listeners of PF_ROUTE,
regardless or which FIB the listener socket was started on.
The upshot of this is that one can't really use routing daemons together
with multiple FIBs. The routing daemon sees the messages from the
alternate FIBs
On Mon, Aug 31, 2009 at 05:20:08PM +, Stef Walter wrote:
> The following reply was made to PR kern/134931; it has been noted by GNATS.
>
> From: Stef Walter
> To: bug-follo...@freebsd.org, co...@211.ru
> Cc:
> Subject: Re: kern/134931:[route] [fib] Route messages sent to all socket
> liste
Stef Walter wrote:
I agree in principle with Mark that having future route messages might
be able to let routing daemons differentiate between various fibs and
manage them, and that this might be a feature However any
implementation of that would likely break API and ABI, and very probabl
Old Synopsis: gre(4) interface does not come up after reboot
New Synopsis: [gre] gre(4) interface does not come up after reboot
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Aug 31 17:36:28 UTC 2009
Responsible-Changed-Why:
Mo
Hi Stef,
I am not sure if this patch is complete.
There are other commands through the routing socket that
can trigger routing messages. For example, issuing "ifconfig"
to add and remove interface addresses.
At the moment these types of routing messages do not have
a fib associated with them, w
The following reply was made to PR kern/134931; it has been noted by GNATS.
From: Stef Walter
To: bug-follo...@freebsd.org, co...@211.ru
Cc:
Subject: Re: kern/134931:[route] [fib] Route messages sent to all socket
listeners
regardless of setfib
Date: Mon, 31 Aug 09 17:20:06 UTC
This is a mu
Currently route messages are sent to all listeners of PF_ROUTE,
regardless or which FIB the listener socket was started on.
The upshot of this is that one can't really use routing daemons together
with multiple FIBs. The routing daemon sees the messages from the
alternate FIBs and rapidly gets con
Old Synopsis: NULL pointer dereference in gif_input() in file sys/net/if_gif.c
New Synopsis: [gif] [patch] NULL pointer dereference in gif_input() in file
sys/net/if_gif.c
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: gavin
Responsible-Changed-When: Mon Aug 31 14:
Synopsis: [ucom] WARNING: attempt to net_add_domain(netgraph) after
domainfinalize()
Responsible-Changed-From-To: freebsd-usb->freebsd-net
Responsible-Changed-By: gavin
Responsible-Changed-When: Mon Aug 31 11:55:54 UTC 2009
Responsible-Changed-Why:
I believe this is more likely to be a problem a
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
Old Synopsis: Memory leak in hfsc_class_modify() in file
sys/contrib/altq/altq/altq_hfsc.c
New Synopsis: [altq] [patch] Memory leak in hfsc_class_modify() in file
sys/contrib/altq/altq/altq_hfsc.c
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-
21 matches
Mail list logo
