Hi folks,
We have been trying to track down a bad mbuf management for about two
weeks on a customized 7.1 base. I have finally been able to reproduce
it with a stock FreeBSD 7-STABLE (kernel from r225276, userland from
7.4).
With the help of the attached patches, I have just been able to
trigger
Hi,
I implemented Ethernet Flow Director sysctls to ixgbe(4), here's a detail:
- Adding removing signature filter
On linux version of ixgbe driver, it has ability to set/remove perfect
filter from userland using ethtool command.
I implemented similar feature, but on sysctl, and not perfect filter
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
On Mon, 2011-09-05 at 15:51 +0900, Takuya ASADA wrote:
> Hi,
>
> I implemented Ethernet Flow Director sysctls to ixgbe(4), here's a detail:
>
> - Adding removing signature filter
> On linux version of ixgbe driver, it has ability to set/remove perfect
> filter from userland using ethtool command.
Hello,
I think the ipfw(8) man page is a bit ambiguous in this area: does the
"me" pseudo-address (as in "allow tcp from any to me 80") also include ipv6?
Here's what the man page says on 8-stable:
"""
src and dst: {addr | { addr or ... }} [[not] ports]
An address (or a lis
On Mon, Sep 05, 2011 at 02:37:08PM +0200 I heard the voice of
Ivan Voras, and lo! it spake thus:
>
> There is no symmetrical "me4" option which leads me to think that
> "me" matches only ipv4 and "me6" only ipv6.
I can't answer for the code, but as far as I could tell as a user
that's the case.
On 5 September 2011 16:01, Matthew D. Fuller wrote:
> On Mon, Sep 05, 2011 at 02:37:08PM +0200 I heard the voice of
> Ivan Voras, and lo! it spake thus:
>>
>> There is no symmetrical "me4" option which leads me to think that
>> "me" matches only ipv4 and "me6" only ipv6.
>
> I can't answer for the
Hi,
> On Mon, 05 Sep 2011 14:37:08 +0200
> Ivan Voras said:
ivoras> There is no symmetrical "me4" option which leads me to think that "me"
ivoras> matches only ipv4 and "me6" only ipv6.
There is `me6' for rather backward compatibility.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Ai
On 5-9-2011 16:35, Ivan Voras wrote:
> On 5 September 2011 16:01, Matthew D. Fuller wrote:
>> On Mon, Sep 05, 2011 at 02:37:08PM +0200 I heard the voice of
>> Ivan Voras, and lo! it spake thus:
>>>
>>> There is no symmetrical "me4" option which leads me to think that
>>> "me" matches only ipv4 and
Hi,
> On Mon, 5 Sep 2011 16:35:06 +0200
> Ivan Voras said:
ivoras> So "tcp from me to any..." appears to match both... which would be
ivoras> fine, but then how do we match ipv4 only?
`ip4 from me to any proto tcp' should do the job.
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid
Hi,
It would seem that the ipfw binary from a 7.4 install is not
compatible with the in-kernel implementation of ipfw from 8-STABLE.
The following command returns junk:
# uname -a
FreeBSD 8.2-STABLE FreeBSD 8.2-STABLE #0: Mon Sep 5 13:26:22 EDT 2011
# ipfw show
65535 79609572473438209 95280647
-STABLE only implies that the ABI does not change during that release
line. It makes no guarantees when moving from one branch to the next.
On Mon, Sep 5, 2011 at 8:31 PM, Arnaud Lacombe wrote:
> Hi,
>
> It would seem that the ipfw binary from a 7.4 install is not
> compatible with the in-kernel
On Sun, 04 Sep 2011 12:30:53 +0300 Mikolaj Golub wrote:
MG> Apparently soreceive_stream() has an issue if it is called to receive data
as a
MG> mbuf chain (by supplying an non zero mbuf **mp0) and with MSG_WAITALL set.
MG> I ran into this issue with smbfs, which uses soreceive() exactly in t
Hi,
On Mon, Sep 5, 2011 at 3:14 PM, K. Macy wrote:
> -STABLE only implies that the ABI does not change during that release
> line. It makes no guarantees when moving from one branch to the next.
>
IIUC, FreeBSD does not provide binary backward compatibility between
version at all, is that it ?
T
Hi,
On Mon, Sep 5, 2011 at 4:18 PM, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Sep 5, 2011 at 3:14 PM, K. Macy wrote:
>> -STABLE only implies that the ABI does not change during that release
>> line. It makes no guarantees when moving from one branch to the next.
>>
> IIUC, FreeBSD does not provide
That's not what the COMPAT_* hooks are for.
They're for backwards compatibility of normal userland binaries, not
binaries which use a FreeBSD-specific kernel ABI.
Adrian
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
Hi,
On Mon, Sep 5, 2011 at 7:50 PM, Adrian Chadd wrote:
> That's not what the COMPAT_* hooks are for.
>
> They're for backwards compatibility of normal userland binaries, not
> binaries which use a FreeBSD-specific kernel ABI.
>
What do you define as "normal" and where do you draw the line ?
>Fr
Synopsis: [vlan] Packets transmitted on vlan(4) interfaces with a parent vge(4)
vanish.
State-Changed-From-To: open->feedback
State-Changed-By: yongari
State-Changed-When: Tue Sep 6 00:43:02 UTC 2011
State-Changed-Why:
It seems parent interface vge(4) thinks it does not have established
link. vg
On 09/05/2011 17:18, Arnaud Lacombe wrote:
> From my point of view, I should be able to run a FreeBSD 9.0 kernel
> (when released) on top of a FreeBSD 5 userland without such issues.
Unfortunately your expectation is completely unrealistic. We do our best
to maintain backward compatibility but som
On Mon, 5 Sep 2011, Arnaud Lacombe wrote:
On Mon, Sep 5, 2011 at 7:50 PM, Adrian Chadd wrote:
That's not what the COMPAT_* hooks are for.
They're for backwards compatibility of normal userland binaries, not
binaries which use a FreeBSD-specific kernel ABI.
What do you define as "normal" and
On 9/5/11 2:44 PM, Arnaud Lacombe wrote:
Hi,
On Mon, Sep 5, 2011 at 4:18 PM, Arnaud Lacombe wrote:
Hi,
On Mon, Sep 5, 2011 at 3:14 PM, K. Macy wrote:
-STABLE only implies that the ABI does not change during that release
line. It makes no guarantees when moving from one branch to the next.
21 matches
Mail list logo
