kni mode: some ports can success to connect, some cannot ( on aws ec2) about f-stack

[Chithesus]

@jfb8856606 老铁, how does fstack judge which port to support? I found it set a bitmap for the port. is it a problem of aws?

[Chithesus]

config.ini:

[kni]
type=0
enable=1
method=accept
;The format is same as port_list
tcp_port=20
udp_port=53

---

ff_bind :

struct sockaddr_in my_addr;
bzero(&my_addr, sizeof(my_addr));
my_addr.sin_family = AF_INET;
my_addr.sin_port = htons(10000); // top:20000
my_addr.sin_addr.s_addr = htonl(INADDR_ANY);
int ret = ff_bind(client_socket, (struct linux_sockaddr *)&my_addr, sizeof(my_addr));
if (ret < 0) {
printf("ff_bind failed, sockfd:%d, errno:%d, %s\n", client_socket, errno, strerror(errno));
exit(1);
}

// loop3(NULL);

if (ff_connect(client_socket, (struct linux_sockaddr *)&server_addr, sizeof(server_addr)) < 0)
{
    printf("connect failed: %s\n", strerror(errno));
}
else {
    printf("connect success\n");
}

[Chithesus]

I run "tcpdump -i any -XSs0 " to catch all the message between client and server; I found client response to SYN_ACK message from server sometimes(client binding to certain ports can success to connect to server, but other ports fail to connect); i am sure server is ok