lvs-devel
|
To: | Hans Schillstrom <hans@xxxxxxxxxxxxxxx> |
---|---|
Subject: | Re: [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support |
Cc: | Hans Schillstrom <hans.schillstrom@xxxxxxxxxxxx>, LVS-Devel <lvs-devel@xxxxxxxxxxxxxxx>, Simon Horman <horms@xxxxxxxxxxxx>, "wensong@xxxxxxxxxxxx" <wensong@xxxxxxxxxxxx>, "daniel.lezcano@xxxxxxx" <daniel.lezcano@xxxxxxx> |
From: | Julian Anastasov <ja@xxxxxx> |
Date: | Tue, 2 Nov 2010 02:17:39 +0200 (EET) |
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. Regards -- Julian Anastasov <ja@xxxxxx> -- To unsubscribe from this list: send the line "unsubscribe lvs-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | Re: [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support, Hans Schillstrom |
---|---|
Next by Date: | Re: [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support, Hans Schillstrom |
Previous by Thread: | Re: [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support, Hans Schillstrom |
Next by Thread: | Re: [v2 PATCH 0/4] IPVS: Backup Adding Ipv6 and Persistence support, Hans Schillstrom |
Indexes: | [Date] [Thread] [Top] [All Lists] |