On Sun, 15 Sept 2024 at 18:56, Sad Clouds
wrote:
> On Sun, 15 Sep 2024 18:01:07 +0100
> Doug Rabson wrote:
>
> > I just did a throughput test with iperf3 client on a FreeBSD 14.1 host
> with
> > an intel 10GB nic connecting to an iperf3 server running in a vnet jail
>
I just did a throughput test with iperf3 client on a FreeBSD 14.1 host with
an intel 10GB nic connecting to an iperf3 server running in a vnet jail on
a truenas host (13.something) also with an intel 10GB nic and I get full
10GB throughput in this setup. In the past, I had to disable LRO on the
tru
rs, representing developers and end users, are also interested
> in helping with the runtime spec. I would love to connect them with you and
> see how we may be able to work together.
>
> Thanks!
>
> Greg
>
>
>
> On Mon, Oct 9, 2023 at 11:19 AM Doug Rabson wrote:
>
On Mon, 9 Oct 2023 at 13:51, Greg Wallace
wrote:
> Hi all,
>
> I have been trying to stay tuned in to all the efforts to get a native OCI
> runtime on FreeBSD. There are a lot of people interested in this and
> several efforts underway.
>
> In the course of listening in on some of the OCI communi
In Linux container runtimes, typically netlink is used with network
namespaces to manage the interfaces and addresses for a container. This
typically involves briefly joining the network namespace to perform actions
like socket(AF_NETLINK, ...).
It would be nice to find a similar approach on FreeB
On Sun, 7 Aug 2022 at 09:04, Franco Fichtner wrote:
>
> > On 7. Aug 2022, at 9:38 AM, Doug Rabson wrote:
> >
> > I'm not sure what the problem is here? I'm using dhcpcd client in my
> home lab with pfsense acting as dhcp and dhcp6 server and it works gr
On Sun, 7 Aug 2022 at 08:08, Franco Fichtner wrote:
> Hi Ben,
>
> > On 7. Aug 2022, at 7:31 AM, Ben Woods wrote:
> >
> > Reason: ensure fresh installs of FreeBSD support using DHCPv6 and prefix
> delegation to obtain an IP address (not supported by dhclient or rtsold).
> Having it in ports/packa
, but should be documented.
> And ideally an option should be provided to use an alternative root if the
> user deems the risk unacceptable.
>
>
>
>
> On 30 June 2022 09:04:24 CEST, Doug Rabson wrote:
>>
>> I wanted to get a quick sanity check for my current appro
I wanted to get a quick sanity check for my current approach to container
networking with buildah and podman. These systems use CNI (
https://www.cni.dev) to set up the network. This uses a sequence of
'plugins' which are executables that perform successive steps in the
process - a very common setu
On 28 May 2008, at 20:57, Arno J. Klaassen wrote:
Hello,
my buildworld on a 7-stable-amd64 blocks on the following line :
TERM=dumb TERMCAP=dumb: ex - /files/bsd/src7/share/termcap/
termcap.src < /files/bsd/src7/share/termcap/reorder
ex(1) stays in lockd state, and is unkillable, either b
On 18 Oct 2005, at 13:21, Norikatsu Shigemura wrote:
On Mon, 17 Oct 2005 10:12:18 +0100
Doug Rabson <[EMAIL PROTECTED]> wrote:
The fwip implementation should be fully compatible with the RFC
standard. I'm happy for fwip to replace fwe in GENERIC unless anyone
else has an objectio
The fwip implementation should be fully compatible with the RFC
standard. I'm happy for fwip to replace fwe in GENERIC unless anyone
else has an objection.
On Saturday 15 October 2005 03:35, Katsushi Kobayashi wrote:
> Hi,
>
> Although I don't know the detail of fwe technology, I understand the
On Tue, 2004-05-18 at 17:21, Harti Brandt wrote:
> On Tue, 18 May 2004, Luigi Rizzo wrote:
>
> LR>On Tue, May 18, 2004 at 02:00:28PM +0100, Doug Rabson wrote:
> LR>> On Tue, 2004-05-18 at 09:48, Luigi Rizzo wrote:
> LR>> > I will try to remove as many assumptions
On Tue, 2004-05-18 at 09:48, Luigi Rizzo wrote:
> I will try to remove as many assumptions as possible.
> thanks for the feedback.
I think that in your prototype, the only assumption was in struct
llentry. I would suggest defining it as something like:
struct llentry {
struct llentry *lle
On Sunday 25 April 2004 17:49, Luigi Rizzo wrote:
> Here is a snapshot of the new arp code that i have been working on
> lately, based a on Andre's ideas. (I say 'ARP' for brevity, what i
> mean is the layer3-to-layer2 address translation code -- arp, aarp,
> nd6 all fit in the category).
Sorry fo
On Mon, 2004-02-02 at 05:50, Hidetoshi Shimokawa wrote:
> At Sat, 31 Jan 2004 15:27:03 +0100,
> Dario Freni wrote:
> >
> > [1 ]
> > Hi guys,
> > I was wondering if the standard implementation of IPoFW is planning to
> > be implemented. I'm not expert on device writing, I was also looking for
> >
On Tue, 2003-09-30 at 09:22, Bruce Evans wrote:
> That's one alternative. (Far too) many places already use the simple
> alternative of just using "struct device *". Grep shows 68 lines
> containing "struct device" in *.h and 32 in *.c. For "device_t", the
> numbers are 2140 in *.h and 5089 in
17 matches
Mail list logo
