The following reply was made to PR kern/171838; it has been noted by GNATS.
From: Venkat Duvvuru
To: freebsd-gnats-sub...@freebsd.org, freebsd-b...@freebsd.org
Cc:
Subject: Re: misc/171838: Possible lock reversal and duplicate locks as
reported by Witness
Date: Tue, 6 Nov 2012 13:10:43 +0530
Hiya,
On 2 November 2012 05:38, Gleb Smirnoff wrote:
> Hello networkers,
>
> some (most) of m_flags bits are describing features that can
> be present on a packet only, not on a single mbuf. Since we are
> close to exhaustion of available bits, and many subsystems prefer
> to use one of M_PRO
On 06.11.2012 09:27, Adrian Chadd wrote:
Hiya,
On 2 November 2012 05:38, Gleb Smirnoff wrote:
Hello networkers,
some (most) of m_flags bits are describing features that can
be present on a packet only, not on a single mbuf. Since we are
close to exhaustion of available bits, and many su
Hello,
The pfSense project uses the 6rd patch against the stf interface, which
works but does not work with prefix lengths larger then 32 bits.
What is the status of this work? As it is we can not support 6rd
networks that deploy a 41 bit prefix length with a 15 bit ipv4 mask for
a /56 deleg
Create vlan interface in cisco-style, eg vlan 3 on fxp0 is fxp0.3, but in
ngctl list i can't find node named fxp0.3. But i can see new
ethernet node
What cause this problem? Dot in the name of interface? How can i rename
unnamed node to use it?
--
Nikolay Nevzorov
__
The following reply was made to PR kern/152036; it has been noted by GNATS.
From: Nicholas Wilson
To: bug-follo...@freebsd.org, kby...@gmail.com
Cc:
Subject: Re: kern/152036: [libc] getifaddrs(3) returns truncated sockaddrs
for netmasks
Date: Tue, 06 Nov 2012 12:19:08 +
Note that althoug
Unfortunately netgraph doesn't allow dots in node names (or hook names),
because that would cause an ambiguity in parsing netgraph paths.
You can name an unnamed node by running "ngctl [nodeid]: name", but of
course the name must be both valid and unique.
On Tue, Nov 6, 2012 at 5:48 AM, Nikolay
On Nov 6, 2012, at 12:48 PM, Nikolay Nevzorov wrote:
> Create vlan interface in cisco-style, eg vlan 3 on fxp0 is fxp0.3, but in
> ngctl list i can't find node named fxp0.3. But i can see new
> ethernet node
> What cause this problem? Dot in the name of interface? How can i rename
> unnamed nod
