Why is network-byte-order defined to be big-endian? [closed]

RFC1700 stated it must be so. (and defined network byte order as big-endian). The convention in the documentation of Internet Protocols is to express numbers in decimal and to picture data in “big-endian” order [COHEN]. That is, fields are described left to right, with the most significant octet on the left and the least significant … Read more

Docker Network Nginx Resolver

First off, you should be using the Docker embedded DNS server at 127.0.0.11. Your problem could be caused by 1 of the following: nginx is trying to use IPv6 (AAAA record) for the DNS queries. See https://stackoverflow.com/a/35516395/1529493 for the solution. Basically something like: http { resolver 127.0.0.11 ipv6=off; } This is probably no longer a … Read more

Windows Phone 8 emulator can’t connect to the internet

I think I’ve finally found the answer, but you’re probably not going to like it. It would appear that the phone emulator requires you to have a second network adapter to dedicate to this purpose. Personally, I run Windows 8 in VMWare, and so a second network adapter is free for me. Anyway, after you … Read more

Is 0.0.0.0 a valid IP address?

It is valid inasmuch as it contains four octets, each within the range 0 through 255 inclusive. However, it is not usable as a real IP address. RFC1700 (a) states that 0.0.0.0/8 (0.<anything>.<anything>.<anything>) is reserved as a source address only. You can get into situation where it appears you have this address but that’s normally … Read more

How to expose docker container’s ip and port to outside docker host without port mapping?

You can accomplish this with IP aliasing on the host. First, add a virtual interface on the host that has a different IP address than the primary interface. We’ll call the primary interface eth0 with IP 10.0.0.10, and the virtual interface eth0:1 with IP address 10.0.0.11. ifconfig eth0:1 10.0.0.11 netmask 255.255.255.0 up Now run the … Read more

What is the cost of many TIME_WAIT on the server side?

Each socket in TIME_WAIT consumes some memory in the kernel, usually somewhat less than an ESTABLISHED socket yet still significant. A sufficiently large number could exhaust kernel memory, or at least degrade performance because that memory could be used for other purposes. TIME_WAIT sockets do not hold open file descriptors (assuming they have been closed … Read more