Hi,
I am trying to understand following code segment in ftp_data_fixup in
ip_nat_ftp.c
/* Try to get same port: if not, try to change it. */
for (port = ct_ftp_info->port; port != 0; port++) {
tuple.dst.u.tcp.port = htons(port);
if (ip_conntrack_expect_related(ct, &tuple, &mask, NULL) == 0)
break;
}
How does this affect the ip_conntrack_expect_related which has already been
called in ip_conntrack_ftp.c, may be with a different (originally parsed from
the stream) port?
I tried forcibly replacing the port value and faced some problems. (as if the
port was busy)
Has this code-segment been tested?
Hemant
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/
I am trying to understand following code segment in ftp_data_fixup in
ip_nat_ftp.c
/* Try to get same port: if not, try to change it. */
for (port = ct_ftp_info->port; port != 0; port++) {
tuple.dst.u.tcp.port = htons(port);
if (ip_conntrack_expect_related(ct, &tuple, &mask, NULL) == 0)
break;
}
How does this affect the ip_conntrack_expect_related which has already been
called in ip_conntrack_ftp.c, may be with a different (originally parsed from
the stream) port?
I tried forcibly replacing the port value and faced some problems. (as if the
port was busy)
Has this code-segment been tested?
Hemant
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger
http://phonecard.yahoo.com/