Well, after days of messing around with my setup I've come to understand
that the DUB-E100 is simply not an usable interface on either the WAN or
LAN side of a FreeBSD_8.3/pfSense_2.1-rc0 box. While it may take longer to
trip the bug, the DUB-E100 eventually loses connectivity even when used on
the
On Sat, Jun 22, 2013 at 12:25 PM, h bagade wrote:
> Hi all,
>
> I've deleted the interface ip address from routing table and only keep the
> network address. Nothing is behaving unusual afterwards. I think this
> loopback ip address is added for better performance. My question is would I
> get in
ethtool is just a passthrough. The drivers need to implement all of those hooks.
It wouldn't be that hard to reimplement. The drivers would have to
reimplement it anyway - they'd have to implement the generic set of
standard statistics, then export driver-specific things. You know, the
stuff our d
ethtool is GPL so I wouldn't expect it to show up around here :)
Implementing something like it for FreeBSD would be cool however, sometimes
sysctl just
seems clunky although its usually how i cope with driver things that might
be changed via
ethtool in Linux. Having to completely rebuild a kernel
Old Synopsis: Bug assigning HCA from IB to ETH
New Synopsis: [ofed] [patch] Bug assigning HCA from IB to ETH
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Wed Jun 26 23:10:19 UTC 2013
Responsible-Changed-Why:
Over to maintainer(s)
If someone ports the ethtool to FreeBSD, it will only work on the
i386/AMD64/ PC98 architectures.
Perhaps having these suggestions as options for the kernel/GENERIC conf
files would be better?
On Wed, Jun 26, 2013 at 6:39 PM, Takuya ASADA wrote:
> Hi,
>
> Because there was an discussion about n
Hi,
Because there was an discussion about new APIs to provide better support
for high performance NICs in Ottawa DevSummit BoF, I wrote a note about
"How Linux doing it" in that area.
I haven't get a enough chance to talk about it in the summit, but I decided
to upload the note on a Wiki.
Here's
This is a patch originially written from rwatson@ iirc.
https://github.com/pfsense/pfsense-tools/blob/master/patches/RELENG_10_0/pf_802.1p.diff
Remove the pf(4) craft and it should work for you.
On Wed, Jun 26, 2013 at 6:27 PM, John-Mark Gurney wrote:
> Alex Liptsin wrote this message on We
Alex Liptsin wrote this message on Wed, Jun 26, 2013 at 11:54 +:
> I work with FreeBSD 9.1 RELEASE.
> I had configured VLANs on my server, but I can't find a way to configure VLAN
> priority.
> How can I do it?
Looks like you can't w/ the default VLAN code:
BUGS
No 802.1Q features except
The following reply was made to PR kern/179901; it has been noted by GNATS.
From: Michael Gmelin
To: Mikolaj Golub
Cc: bug-follo...@freebsd.org
Subject: Re: kern/179901: [netinet] [patch] Multicast SO_REUSEADDR handled
incorrectly
Date: Wed, 26 Jun 2013 15:03:40 +0200
On Tue, 25 Jun 2013 18:2
Hello.
I work with FreeBSD 9.1 RELEASE.
I had configured VLANs on my server, but I can't find a way to configure VLAN
priority.
How can I do it?
Thanks.
Regards,
Alex Liptsin
Software Quality Assurance Engineer | Mellanox Technologies Ltd.
Office: +972 (74) 7236141
Mobile: +972(54) 7833986
Fax:
11 matches
Mail list logo
