Searched refs:new_reply (Results 1 – 1 of 1) sorted by relevance
143 struct nf_conntrack_tuple *orig, new_reply; in ip_vs_nfct_expect_callback() local167 new_reply = ct->tuplehash[IP_CT_DIR_REPLY].tuple; in ip_vs_nfct_expect_callback()170 __func__, ct, ARG_TUPLE(&new_reply)); in ip_vs_nfct_expect_callback()171 new_reply.dst.u3 = cp->vaddr; in ip_vs_nfct_expect_callback()172 new_reply.dst.u.tcp.port = cp->vport; in ip_vs_nfct_expect_callback()183 new_reply = ct->tuplehash[IP_CT_DIR_REPLY].tuple; in ip_vs_nfct_expect_callback()186 __func__, ct, ARG_TUPLE(&new_reply)); in ip_vs_nfct_expect_callback()187 new_reply.src.u3 = cp->daddr; in ip_vs_nfct_expect_callback()188 new_reply.src.u.tcp.port = cp->dport; in ip_vs_nfct_expect_callback()200 nf_conntrack_alter_reply(ct, &new_reply); in ip_vs_nfct_expect_callback()