On 6/19/2014 4:57 AM, Massimiliano Stucchi wrote:
On 19/06/14 05:11, Darren Pilgrim wrote:
FreeBSD doesn't support 6rd. Ironically, pfSense does.
This is not entirely true. 6RD is about establishing a 6to4 tunnel to a
well-defined tunnel server in your provider's infrastructure, so as long
Reviving an old thread where Steve found this problem: A call to
getpeername on a connected tcp socket returns ENOTCONN with no prior
errors being reported by previous socket calls.
Please look at
http://lists.freebsd.org/pipermail/freebsd-net/2011-January/027647.html
for more details.
Here is a
On 06/20/14 15:20, Alan Somers wrote:
...
>
> Do you have a test case that can reproduce the panic?
>
> -Alan
>
Just run some UDP traffic on head or stable/10 and watch the refcount
leak on the transmitter.
# netperf -H ... -t UDP_STREAM
I see these two do ifa_ref (once per packet).
On Fri, Jun 20, 2014 at 1:15 PM, Navdeep Parhar wrote:
> Revision 264905 and 266860 that followed it seem to leak ifaddr
> references. ifa_ifwithdstaddr and ifa_ifwithnet both install a
> reference on the ifaddr returned to the caller but ip_output does not
> release it, eventually leading to a p
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967
--- Comment #10 from kved...@kvedulv.de ---
Hi Oliver,
(In reply to olivier from comment #8)
> The patch didn't solve Lagg regression between 9.2 and 10-stable (r267244).
>
> My configuration only use one lagg member (the second will be ad
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185967
kved...@kvedulv.de changed:
What|Removed |Added
CC||kved...@kvedulv.de
--- Comment
Revision 264905 and 266860 that followed it seem to leak ifaddr
references. ifa_ifwithdstaddr and ifa_ifwithnet both install a
reference on the ifaddr returned to the caller but ip_output does not
release it, eventually leading to a panic when the refcount wraps over
to 0 and the ifaddr is freed w
Hi Hiroki,
On Fri, Jun 20, 2014 at 12:48:03PM +0900, Hiroki Sato wrote:
> John Hay wrote
> in <20140619103513.ga92...@zibbi.meraka.csir.co.za>:
>
> jh> Hi Guys,
> jh>
> jh> freebsd-rc did not react, so I'm just checking on -net too.
> jh>
> jh> I found after upgrading that vlan handling broke.
Hello,
I've stumbled across the following panic when testing Xen netback with
if_bridge:
Kernel page fault with the following non-sleepable locks held:
exclusive sleep mutex if_bridge (if_bridge) r = 0 (0xf80006306c18) locked @
/usr/src/sys/m
KDB: stack backtrace:
X_db_symbol_values() at X_
On 2014-06-19 23:08, Hiroki Sato wrote:
Larry Rosenman wrote
in <20140619140801.ga65...@thebighonker.lerctr.org>:
le> > le> Ideas? (I may be an idiot, so any criticism welcomed).
le> > le>
le> > le> if you need the 1841's config, I can supply that as well.
It's using a Hurricane
le> > le> ele
On Thu, Jun 19, 2014 at 02:35:13PM -0700, George Neville-Neil wrote:
> On 4 Feb 2014, at 1:38, Eggert, Lars wrote:
>
> > Hi,
> >
> > below are two patches that implement RFC6937 ("Proportional Rate Reduction
> > for TCP") and draft-ietf-tcpm-newcwv-00 ("Updating TCP to support
> > Rate-Limited T
11 matches
Mail list logo
