I'm building a server to handle outbound NAT to the internet using FreeBSD 9.1
and its built-in distribution of pf. What I want to be able to do is NAT three
unique internal (private) VLANs to three unique public IPs. Our current setup
utilizes a single external IP address for all three internal
On May 31, 2013, at 7:37 PM, Peter Jeremy wrote:
> On 2013-May-30 17:54:53 -0500, Joe Moog wrote:
>> I'm building a server to handle outbound NAT to the internet using
>> FreeBSD 9.1 and its built-in distribution of pf. What I want to be
>> able to do is NAT thre
We have an iXsystems 1U server (E5) with an Intel 4-port ethernet NIC
installed, model I350-T4 (manufactured May of 2013). We're trying to bind the 4
ports on this NIC together into a single lagg port, connected LACP to a
distribution switch (Cisco 4900-series). We are able to successfully bind
On Aug 1, 2013, at 3:55 PM, Ryan Stone wrote:
> Have you tried using only two ports, but both from the NIC? My suspicion
> would be that the problem is in the lagg's handling of more than 2 ports
> rather than the driver, especially given that it is the igb driver in all
> cases.
Ryan:
We h
On Aug 1, 2013, at 4:27 PM, Joe Moog wrote:
> On Aug 1, 2013, at 3:55 PM, Ryan Stone wrote:
>
>> Have you tried using only two ports, but both from the NIC? My suspicion
>> would be that the problem is in the lagg's handling of more than 2 ports
>> rather than
On Aug 1, 2013, at 5:36 PM, Sean Bruno wrote:
>> UPDATE: After additional testing, I'm beginning to suspect the igb driver.
>> With our setup, ifconfig identifies all the ethernet ports as igb(0-5). I
>> configured igb0 with a single static IP address (say, 192.168.1.10), and was
>> able to c
On Aug 1, 2013, at 6:16 PM, John-Mark Gurney wrote:
> Joe Moog wrote this message on Thu, Aug 01, 2013 at 17:14 -0500:
>> On Aug 1, 2013, at 4:27 PM, Joe Moog wrote:
>>
>>> On Aug 1, 2013, at 3:55 PM, Ryan Stone wrote:
>>>
>>>> Have you tried usi
> Date: Fri, 02 Aug 2013 09:36:30 +0200
> From: Steve Read
> To: freebsd-net@freebsd.org
> Subject: Re: Intel 4-port ethernet adaptor link aggregation issue
> Message-ID: <51fb617e.2090...@netasq.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
All:
Thanks again to everybody for the responses and suggestions to our 4-port lagg
issue. The solution (for those that may find the information of some value) was
to set the value for kern.ipc.nmbclusters to a higher value than we had
initially. Our previous tuning had this value set at 25600,
