Julian Anastasov writes:
> Hello,
>
> On Thu, 18 Jun 2015, Eric W. Biederman wrote:
>
>> My incremental patch for ipvs on top of everything else I have pushed
>> out looks like this:
>>
>> From: "Eric W. Biederman"
>> Date: Fri, 12 Jun 2015 18:34:12 -0500
>> Subject: [PATCH] ipvs: Pass st
Hello,
On Thu, 18 Jun 2015, Eric W. Biederman wrote:
> My incremental patch for ipvs on top of everything else I have pushed
> out looks like this:
>
> From: "Eric W. Biederman"
> Date: Fri, 12 Jun 2015 18:34:12 -0500
> Subject: [PATCH] ipvs: Pass struct net down to where it is needed
Cc' list trimmed as this is not longer about the original patch
submission.
Julian Anastasov writes:
> Hello,
>
> On Wed, 17 Jun 2015, Eric W. Biederman wrote:
>
>> p.s. I do have my patch that I can toss in your direction if you are
>> interested.
>
> Of course... I'll be able to
Hello,
On Wed, 17 Jun 2015, Eric W. Biederman wrote:
> p.s. I do have my patch that I can toss in your direction if you are
> interested.
Of course... I'll be able to check it after 8 hours...
Regards
--
Julian Anastasov
--
To unsubscribe from this list: send the line "unsub
Julian Anastasov writes:
> Hello,
>
> On Sun, 14 Jun 2015, Eric W. Biederman wrote:
>
>> This patshset roots out all of the very weird network namespace
>> computation logic (except for the code in ipvs) and fixes it. I really
>> don't like how the code has been essentially guessing which
Hello,
On Sun, 14 Jun 2015, Eric W. Biederman wrote:
> This patshset roots out all of the very weird network namespace
> computation logic (except for the code in ipvs) and fixes it. I really
> don't like how the code has been essentially guessing which network
> namespace to use.
>
>
Pablo Neira Ayuso writes:
> On Mon, Jun 15, 2015 at 07:26:13PM -0500, Eric W. Biederman wrote:
> [...]
>> So what I am in the processes of doing is reviewing and testing
>> the combined set of patches and hopefully I will have something
>> for you soon (tomorrow?). Unless Pablo has objections.
>
On Mon, Jun 15, 2015 at 07:26:13PM -0500, Eric W. Biederman wrote:
[...]
> So what I am in the processes of doing is reviewing and testing
> the combined set of patches and hopefully I will have something
> for you soon (tomorrow?). Unless Pablo has objections.
Please, feel free to take over my p
From: ebied...@xmission.com (Eric W. Biederman)
Date: Mon, 15 Jun 2015 19:26:13 -0500
> So what I am in the processes of doing is reviewing and testing
> the combined set of patches and hopefully I will have something
> for you soon (tomorrow?). Unless Pablo has objections.
I will be travelling
David Miller writes:
> From: ebied...@xmission.com (Eric W. Biederman)
> Date: Sun, 14 Jun 2015 22:07:30 -0500
>
>> While looking into what it would take to route packets out to network
>> devices in other network namespaces I started looking at the netfilter
>> hooks, and there is a lot of nasty
From: ebied...@xmission.com (Eric W. Biederman)
Date: Sun, 14 Jun 2015 22:07:30 -0500
> While looking into what it would take to route packets out to network
> devices in other network namespaces I started looking at the netfilter
> hooks, and there is a lot of nasty code to figure out which netwo
On Mon, Jun 15, 2015 at 10:06:27AM -0500, Eric W. Biederman wrote:
> Pablo Neira Ayuso writes:
>
> > Hi Eric,
> >
> > On Sun, Jun 14, 2015 at 10:07:30PM -0500, Eric W. Biederman wrote:
> >>
> >> While looking into what it would take to route packets out to network
> >> devices in other network n
Pablo Neira Ayuso writes:
> Hi Eric,
>
> On Sun, Jun 14, 2015 at 10:07:30PM -0500, Eric W. Biederman wrote:
>>
>> While looking into what it would take to route packets out to network
>> devices in other network namespaces I started looking at the netfilter
>> hooks, and there is a lot of nasty
Hi Eric,
On Sun, Jun 14, 2015 at 10:07:30PM -0500, Eric W. Biederman wrote:
>
> While looking into what it would take to route packets out to network
> devices in other network namespaces I started looking at the netfilter
> hooks, and there is a lot of nasty code to figure out which network
> na
While looking into what it would take to route packets out to network
devices in other network namespaces I started looking at the netfilter
hooks, and there is a lot of nasty code to figure out which network
namespace to filter the packets in.
Just passing the network namespace into the netfilte
15 matches
Mail list logo
