Hot answers tagged linux-networking
Setting an upper limit for packet size was done for two reasons: ensure reliable transmission of the data (longer data are more susceptible to being corrupted and their CRC have lower changes of detecting/correcting the corruption); ensure that all Ethernet-compliant device have at least a 1500 byte buffer to send/receive packets. As you suggested, the ...
No, this is not possible in the sense of a "normal" CPU. You could use CUDA or a similar library if supported on your GPU chip, but that is not at all useful for general server tasks. However, most servers that are not designed for GPU computing have very weak GPUs and wouldn't offer any real benefit anyway.
Your setup will probably do what you want, once you have a service listening on the concerned port(s). Iptables is a packet filter, not a connection endpoint.
Have you considered the possibility that your local system is already infected and has a keylogger on it that records all your passwords etc.? Especially if your adversaries may be targeting you directly? I would suggest the following: Use a secure local system, for example a system booted from an officially purchased LiveCD (or just a friend you know has ...
The bug is in the Version: 6.1.2 of nuttcp For more information and fix read this link https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745051 My suggestion is to use a new version. mkdir nuttcp cd nuttcp/ wget http://nuttcp.net/nuttcp/beta/nuttcp-7.3.3.c If you don’t have gcc sudo apt-get install build-essential manpages-dev compile program and run ...
You can achieve this by using virtualization, either with a bare-metal hypervisor (ESXi, Hyper-V, KVM) or containers (Solaris Zones, *BSD Jails, Linux LXC), depending if you need different operating systems for your servers. There is much debate over if this is a smart or terrible idea, so I won't lecture you on it much. There a guides out there how to ...
Found this googling a bit: Ethernet frame has 8 byte preamble, 6 byte source and 6 byte destination mac address, mac type of 2 bytes, and 4 bytes CRC. Assuming the MTU payload to be 1500 the total number of bytes comes to 1500 + 8 + 6 + 6 + 2 + 4 = 1526 bytes. Now between each frame there is a inter frame gap of 12 bytes which constitues 9.6micro ...
The libvirt is using TUN device for this purpose. You can manually create this device by following command: # /usr/bin/tunctl -t virbr0-nic
Bridging and routing are not the same. Bridging happens at a lower layer than routing. Essentially bridging behaves like a switch. The virtual switch implemented by the Linux bridging code will have one interface attached to the upper layers of the network stack as well as a number of physical interfaces. So in your case where there are two physical ...
I once had the same issue on a server. CentOS didnt add the route automaticly because the gateway is not in the same subnetmask (i guessed). You need to add a persistent/static route. CentOS documentation can be found here: https://www.centos.org/docs/5/html/5.2/Deployment_Guide/s1-networkscripts-static-routes.html Try the following for your route-eth0 ...
I'm assuming you are referring to this tutorial. With linux bridge, you are going to use your netem box as a switch, without even an ip but for management. This way, the client is going to communicate straight to your server. As long as you don't specify subinterfaces (eg eth0.101), your switch will forward all vlan tagged traffic as-is.
Only top voted, non community-wiki answers of a minimum length are eligible