From: Hans Schillstrom <hans.schillstrom@ericsson.com>
To: Julian Anastasov <ja@ssi.bg>
Cc: Hans Schillstrom <hans@schillstrom.com>,
LVS-Devel <lvs-devel@vger.kernel.org>,
Simon Horman <horms@verge.net.au>,
"wensong@linux-vs.org" <wensong@linux-vs.org>,
"daniel.lezcano@free.fr" <daniel.lezcano@free.fr>
Subject: Re: [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support
Date: Tue, 2 Nov 2010 07:13:05 +0100 [thread overview]
Message-ID: <201011020713.06154.hans.schillstrom@ericsson.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1011020209520.2485@ja.ssi.bg>
On Tuesday 02 November 2010 01:17:39 Julian Anastasov wrote:
>
> Hello,
>
> On Mon, 1 Nov 2010, Hans Schillstrom wrote:
>
> >> As for ip_vs_sync_conn_options
> >> there is no app in mainline kernel 2.6.36+ that will trigger
> >> this parameter. And we do not know (yet) how to sync SEQs with
> >> Netfilter in the case for ip_vs_ftp.
> >
> > If we receive packets with ip_vs_sync_conn_options what shoud be done
> > - dropt that single conn msg ? (My vote)
> > or
> > - ignore ip_vs_sync_conn_options and try to process the message ?
> >
> > I leave the "dead code" in case it's needed later on.
> > (except for Version 1 receive)
>
> Why? Just copy data to cp->in_seq and cp->out_seq
> as before but for version 1 make sure the values in
> struct ip_vs_seq are sent in network order. If some APP
> provides diff != 0 these SEQs will be sent.
>
OK, I'll do that
--
Regards
Hans Schillstrom <hans.schillstrom@ericsson.com>
next prev parent reply other threads:[~2010-11-02 6:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-29 12:15 [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support Hans Schillstrom
2010-10-30 14:55 ` Julian Anastasov
2010-10-30 23:16 ` Simon Horman
2010-11-01 10:04 ` Hans Schillstrom
2010-11-01 15:30 ` Hans Schillstrom
2010-11-01 21:56 ` Julian Anastasov
2010-11-03 20:08 ` Hans Schillstrom
2010-11-06 0:56 ` Simon Horman
2010-11-06 10:02 ` Hans Schillstrom
2010-11-06 11:49 ` Simon Horman
2010-11-06 14:07 ` Julian Anastasov
2010-11-06 14:34 ` Simon Horman
2010-11-06 18:57 ` Julian Anastasov
2010-11-08 6:21 ` Simon Horman
2010-11-08 8:51 ` Julian Anastasov
2010-11-08 11:16 ` Simon Horman
2010-11-08 15:07 ` Hans Schillstrom
2010-11-08 21:45 ` Simon Horman
2010-11-08 20:59 ` Julian Anastasov
2010-11-08 21:49 ` Simon Horman
2010-11-08 23:01 ` Julian Anastasov
2010-11-09 0:43 ` Simon Horman
2010-11-08 15:15 ` Hans Schillstrom
2010-11-08 22:00 ` Simon Horman
2010-11-08 22:23 ` Hans Schillstrom
2010-11-09 0:39 ` Simon Horman
2010-11-08 23:19 ` Julian Anastasov
2010-11-09 0:48 ` Simon Horman
2010-11-01 10:03 ` Hans Schillstrom
2010-11-01 21:53 ` Julian Anastasov
2010-11-01 22:47 ` Hans Schillstrom
2010-11-02 0:17 ` Julian Anastasov
2010-11-02 6:13 ` Hans Schillstrom [this message]
2010-11-01 12:16 ` [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support -> option_param skip ? Hans Schillstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201011020713.06154.hans.schillstrom@ericsson.com \
--to=hans.schillstrom@ericsson.com \
--cc=daniel.lezcano@free.fr \
--cc=hans@schillstrom.com \
--cc=horms@verge.net.au \
--cc=ja@ssi.bg \
--cc=lvs-devel@vger.kernel.org \
--cc=wensong@linux-vs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.