tcp-ip

I have a Linux virtual server with 2 NICs. eth0 <IP1> eth1 <IP2> arp_filter is turned on and rp_filter is set to be 2(loose mode). Policy-routing is configured as the following: table T1 default via <GW> dev eth0 src <IP1> 127.0.0.0/8 dev lo <LAN> dev eth0 src <IP1> table T2 default via <GW> dev eth1 src <IP2> 127.0.0.0/8 dev lo <LAN> dev eth1 src <IP2> ip rule add from <IP1> table T1 ip rule add from <IP2> table T2 After that, I can ping both binding floatingips of <IP1> and <IP2> from outside. However ping -I eth1 <some_domain> dosen't work. tcpdump shows that when I ping from eth1 to

I have a need to create a server farm that can handle 5+ million connections, 5+ million topics (one per client), process 300k messages/sec. I tried to see what various message brokers were capable so I am currently using two RHEL EC2 instances (r3.4xlarge) to make lots of available resources. So you do not need to look it up, it has 16vCPU, 122GB RAM. I am nowhere near that limit in usage. I am unable to pass the 600k connections limit. Since there doesn't seem to be any O/S limitation (plenty of RAM/CPU/etc.) on either the client nor the server what is limiting me? I have edited /etc

I am working with Netty 4. I see folowing options of Netty server: WRITE_BUFFER_HIGH_WATER_MARK and WRITE_BUFFER_LOW_WATER_MARK. The official page Related articles has link to Netty best practices (slides w/ video) by Norman Maurer . One of slides looks like this: ServerBootstrap bootstrap = new ServerBootstrap(); bootstrap.childOption(ChannelOption.WRITE_BUFFER_HIGH_WATER_MARK, 32 * 1024); bootstrap.childOption(ChannelOption.WRITE_BUFFER_LOW_WATER_MARK, 8 * 1024); and has this preface: Set sane WRITE_BUFFER_HIGH_WATER_MARK and WRITE_BUFFER_LOW_WATER_MARK But what is it WRITE_BUFFER_HIGH_WATER

I'm trying to understand what's happening under the hood to a network packet coming from the wire connected to the host machine and directed to an application inside a Docker container. If it were a classic VM, I know that a packet arriving on the host would be transmitted by the hypervisor (say VMware, VBox etc.) to the virtual NIC of the VM and from there through the TCP/IP stack of the guest OS, finally reaching the application. In the case of Docker, I know that a packet coming on the host machine is forwarded from the network interface of the host to the docker0 bridge, that is connected

I have a problem with my TCPIP connection Form programm. I have a code, where I'm trying to send and receive some data from server. The main problem of my app is how to reconcile some threads: myListenThread - to listening data from server myReadStreamThread - to read data from server System.Threading.Thread - main thread eg. to write data to server captureThread - to do another things like capturing images from camera Part of my code: private void buttonConnect_Click(object sender, EventArgs e) { try { Connect(); Connected = true; this.myListenThread = new Thread(new ThreadStart(Listen));