关于 INADDR_ANY 的问题 [英] Question about INADDR_ANY

查看:27
本文介绍了关于 INADDR_ANY 的问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

常量 INADDR_ANY 是所谓的 IPv4 通配符地址.这通配符 IP 地址对于绑定 Internet 的应用程序很有用多宿主主机上的域套接字.如果应用程序在多宿主主机将套接字绑定到其主机的 IP 地址之一,然后socket只能接收发送的UDP数据报或TCP连接请求到那个 IP 地址.然而,我们通常希望在一个应用程序上多宿主主机能够接收数据报或连接请求指定任何主机的 IP 地址,并将套接字绑定到通配符 IP 地址使这成为可能.

The constant INADDR_ANY is the so-called IPv4 wildcard address. The wildcard IP address is useful for applications that bind Internet domain sockets on multihomed hosts. If an application on a multihomed host binds a socket to just one of its host’s IP addresses, then that socket can receive only UDP datagrams or TCP connection requests sent to that IP address. However, we normally want an application on a multihomed host to be able to receive datagrams or connection requests that specify any of the host’s IP addresses, and binding the socket to the wildcard IP address makes this possible.

struct sockaddr_in server_address;
int server_sockfd = socket(AF_INET, SOCK_STREAM, 0);
memset(&server_address, 0, sizeof(struct sockaddr_in));
server_address.sin_family = AF_INET;
server_address.sin_addr.s_addr = htonl(INADDR_ANY); // here is my quesion
server_address.sin_port = htons(9734);

bind(server_sockfd, (struct sockaddr*)&server_address, sizeof(server_address));

问题>

如果我们将socket绑定到一个特定的IP地址,那么这个socket只能接收发送到那个IP地址的UPD/TCP请求.

If we bind the socket to a specific IP address, then the socket can only receive UPD/TCP requests sent sent to that IP address.

正如我在上面的代码中所示,现在套接字 server_sockfd 与 INADDR_ANY 绑定.我只是在这里感到困惑 b/c 如果套接字可以在互联网上接收任何请求,它如何仍然可以正常工作.互联网上有大量的 UDP/TCP 请求,如果套接字响应每个人,,怎么还能用?

As I show in the above code, now the socket server_sockfd is bound with INADDR_ANY. I just feel confused here b/c if the socket can receive any request on the internet, how it can still work well. There are tons of requests of UDP/TCP on internet, if the socket responses to everybody, , how can it still work?

//更新客户端代码//

// updated code for client side //

int
main(int argc, char *argv[])
{
    struct sockaddr_in6 svaddr;
    int sfd, j;
    size_t msgLen;
    ssize_t numBytes;
    char resp[BUF_SIZE];

    if (argc < 3 || strcmp(argv[1], "--help") == 0)
        usageErr("%s host-address msg...
", argv[0]);

    /* Create a datagram socket; send to an address in the IPv6 somain */

    sfd = socket(AF_INET6, SOCK_DGRAM, 0);      /* Create client socket */
    if (sfd == -1)
        errExit("socket");

    memset(&svaddr, 0, sizeof(struct sockaddr_in6));
    svaddr.sin6_family = AF_INET6;
    svaddr.sin6_port = htons(PORT_NUM);
    if (inet_pton(AF_INET6, argv[1], &svaddr.sin6_addr) <= 0)
        fatal("inet_pton failed for address '%s'", argv[1]);

    /* Send messages to server; echo responses on stdout */

    for (j = 2; j < argc; j++) {
        msgLen = strlen(argv[j]);
        if (sendto(sfd, argv[j], msgLen, 0, (struct sockaddr *) &svaddr,
                    sizeof(struct sockaddr_in6)) != msgLen)
            fatal("sendto");

        numBytes = recvfrom(sfd, resp, BUF_SIZE, 0, NULL, NULL);
        if (numBytes == -1)
            errExit("recvfrom");

        printf("Response %d: %.*s
", j - 1, (int) numBytes, resp);
    }

    exit(EXIT_SUCCESS);
}

//更新服务器端代码

int
main(int argc, char *argv[])
{
    struct sockaddr_in6 svaddr, claddr;
    int sfd, j;
    ssize_t numBytes;
    socklen_t len;
    char buf[BUF_SIZE];
    char claddrStr[INET6_ADDRSTRLEN];

    /* Create a datagram socket bound to an address in the IPv6 somain */

    sfd = socket(AF_INET6, SOCK_DGRAM, 0);
    if (sfd == -1)
        errExit("socket");

    memset(&svaddr, 0, sizeof(struct sockaddr_in6));
    svaddr.sin6_family = AF_INET6;
    svaddr.sin6_addr = in6addr_any;                     /* Wildcard address */
    svaddr.sin6_port = htons(PORT_NUM);

    if (bind(sfd, (struct sockaddr *) &svaddr,
                sizeof(struct sockaddr_in6)) == -1)
        errExit("bind");

    /* Receive messages, convert to uppercase, and return to client */

    for (;;) {
        len = sizeof(struct sockaddr_in6);
        numBytes = recvfrom(sfd, buf, BUF_SIZE, 0,
                            (struct sockaddr *) &claddr, &len);
        if (numBytes == -1)
            errExit("recvfrom");

        /* Display address of client that sent the message */

        if (inet_ntop(AF_INET6, &claddr.sin6_addr, claddrStr,
                    INET6_ADDRSTRLEN) == NULL)
            printf("Couldn't convert client address to string
");
        else
            printf("Server received %ld bytes from (%s, %u)
",
                    (long) numBytes, claddrStr, ntohs(claddr.sin6_port));

        for (j = 0; j < numBytes; j++)
            buf[j] = toupper((unsigned char) buf[j]);

        if (sendto(sfd, buf, numBytes, 0, (struct sockaddr *) &claddr, len) !=
                numBytes)
            fatal("sendto");
    }
}

//更新了如何运行此服务器/客户端程序.

// updated for how to run this server/client programs.

$ ./server_program &
[1] 31047
$ ./client_program ::1 ciao // Send to server on local host
Server received 4 bytes from (::1, 32770)
Response 1: CIAO

推荐答案

它不会获取对 Internet 上每个 IP 地址的请求(a),它会获取对它的每个 IP 地址的请求服务.例如,它可能有多个网卡,每个网卡都有一个单独的 IP 地址,或者它可能有一个能够管理多个 IP 地址的网卡(它甚至可能有多个网卡,每个网卡都能够处理多个 IP 地址.

It doesn't get requests for every IP address on the internet(a), it gets requests for every IP address that it services. For example, it may have multiple NICs, each with a separate IP address or it may have a single NIC capable of managing multiple IP addresses (it may even have multiple NICs, each capable of handling multiple IP addresses.

要查看的关键片段是:

...我们通常希望多宿主主机上的应用程序能够接收指定任何主机 IP 地址(我的斜体)的数据报或连接请求.

... we normally want an application on a multi-homed host to be able to receive datagrams or connection requests that specify any of the host’s IP addresses (my italics).

换句话说,您可能有一个多宿主设置,其中您的机器服务 10.0.0.1510.0.0.16.使用 INADDR_ANY 将允许您获取这两个地址的流量,无需获取对 10.0.0.17 的请求,而10.0.0.17 可能是长凳的另一端(或地球的另一端).

In other words, you may have a multi-homed set-up where your machine services 10.0.0.15 and 10.0.0.16. Using INADDR_ANY will allow you to pick up traffic for both those addresses, without picking up requests for 10.0.0.17 which may be the machine on the other end of the bench (or other side of the planet).

下表,顶行是请求目的地,左列是您正在侦听的地址,显示您是否会收到请求 (Y) (<代码>N):

The following table, with the top row being request destinations and the left column being the address you're listening on, shows whether you'll be given a request (Y) or not (N):

Request to>  10.0.0.15  10.0.0.16  10.0.0.17
Bind to:    *-------------------------------
10.0.0.15   |    Y          N          N
10.0.0.16   |    N          Y          N
INADDR_ANY  |    Y          Y          N

<小时>

(a)它甚至没有看到网络上的绝大多数请求.绝大多数甚至没有到达您最近的路由器(甚至可能是您的 ISP).即使那些确实将它发送到离您最近的路由器,您的特定机器可能看不到它们是否去往本地网段上的另一台机器(尽管存在混杂模式).


(a) It doesn't even see the vast majority of requests on the net. The vast majority don't even make it to your nearest router (or probably even your ISP). Even those that do make it to your nearest router, your particular machine might not see if they're destined for another machine on the local segment (promiscuous mode notwithstanding).

这篇关于关于 INADDR_ANY 的问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆