On Mon, 14 May 2012 16:02:40 +0300, Ivo Vachkov wrote:
Hello all,
On Mon, May 14, 2012 at 1:52 PM, Monthadar Al Jaberi
montha...@gmail.comwrote:
On Sun, May 13, 2012 at 2:49 PM, Ivan Voras ivo...@gmail.com wrote:
On 13 May 2012 06:46, Ivo Vachkov ivo.vach...@gmail.com wrote:
At Tue, 8 May 2012 12:11:20 +0200,
Gergely CZUCZY wrote:
Hello,
I'd like to ask a few question in order to get some hardware to work
we've got recently.
The hardwares are the following:
- 2x dualport Mellanox ConnectX-3 VPI cards, with 56Gbps ports
- 4 computing modules with a
Hi,
If you'd like this kind of userland wifi mesh stuff to show up, we
first need someone to step up as net80211 adhoc/injection maintainer.
These userland mesh implementations rely on direction injection of
wifi frames to work and I believe our support is currently 'tricky'.
It also isn't at
Trying to use two interfaces connected to the same network with the same
default router. The two interfaces have two different IPs on the
same /28 and point at the same default router of .1. I have
successfully configured the machine such that data is coming *in* on
both interfaces, but the
The route selection is based on a hash function of source-ip and destination-ip
when
RADIX_MPATH is enabled. You do not need to perform specific actions, other than
perhaps
setting varying weights on each entry as an option. So depends on the traffic
destination
the chosen route may always be
On Tue, 2012-05-15 at 12:02 -0700, Li, Qing wrote:
The route selection is based on a hash function of source-ip and
destination-ip when
RADIX_MPATH is enabled. You do not need to perform specific actions, other
than perhaps
setting varying weights on each entry as an option. So depends
Hello!
I am using FreeBSD-9-stable.
I use Intel network cards (em, igb) with mtu=9000 (it's important, the
problem disappears if I switch to mtu=1500).
I have a number of servers running a few web-services written in our
company.
After a few days of working network suddenly stops
Li, Qing qing...@bluecoat.com wrote:
The route selection is based on a hash function of source-ip and
destination-ip when RADIX_MPATH is enabled. You do not need to perform
specific actions, other than perhaps setting varying weights on each
entry as an option. So depends on the traffic
On Tue, 2012-05-15 at 12:55 -0700, Sean Bruno wrote:
On Tue, 2012-05-15 at 12:02 -0700, Li, Qing wrote:
The route selection is based on a hash function of source-ip and
destination-ip when
RADIX_MPATH is enabled. You do not need to perform specific actions, other
than perhaps
On Tue, 2012-05-15 at 16:14 -0700, David DeSimone wrote:
suggests that there is only ONE default route, pointing to ONE
interface, igb0. Without an extra default route that is also pointing
to igb1, I can't see how the system woudl ever forward traffic out
igb1,
unless it was directed to the
Yes, you are right, I should have paid closer attention to the output, however,
what
I replied still apply to RADIX_MPATH in general.
Now, when I first introduced RADIX_MPATH, to get the (not always even) general
load
balancing among interfaces attached to the same prefix, you only need to add
Old Synopsis: arpresolve checks only the default FIB for the interface route
New Synopsis: [ipfw] arpresolve checks only the default FIB for the interface
route
Responsible-Changed-From-To: freebsd-bugs-freebsd-net
Responsible-Changed-By: gjb
Responsible-Changed-When: Wed May 16 03:57:09 UTC
Filed as
misc/167947
On May 12, 2012, at 10:21 AM, Nikolay Denev wrote:
On Jan 21, 2010, at 6:16 PM, Matt Burke wrote:
Box is running 8.0-RELEASE-p2 cvsupped two days ago.
NICs are em bonded with lagg failover and running a few vlan interfaces.
net.my_fibnum: 0
net.add_addr_allfibs:
13 matches
Mail list logo
