Tag Info

New answers tagged


There is no default automatic packet logging within the Windows OS (that I am aware of). If you are trying to get statistics on an event that has already happened, you are probably out of luck. My best suggestion would be to scour the Event Viewer during the 10 minutes or so you are concerned about. Going forward however, there are many good packet capture ...


Traffic shaping for your users isn't a bad idea, but you're going about it in the wrong way - specifically, you're insisting on trying to shape inbound traffic. This quote comes from the Linux Advanced Routing and Traffic Control HOWTO With queueing we determine the way in which data is SENT. It is important to realise that we can only shape data that ...


If the iptables rules are applied on the host where the client is running, then you can make use of the owner module. This only works with outgoing packets, so you'd need to use CONNMARK target to store information from outgoing packets which you need when processing incoming packets. That approach does not work, if the packets are traveling over a network ...


Yes, you can use the Ident protocol to identify the user at the source. Well, you used to be able to. Nowadays the only people who expose ident servers to the Internet at large are IRC users who want a funky nickname. Oh, and people who've misconfigured their systems.


This is not achievable natively within the TCP/IP protocol, because... well, that's just not how the protocol works - it doesn't have a concept of users, and is designed to just transfer data between devices. The way this is generally done (rate-limiting a specific remote user) is through the use of sessions (layer 5 in your OSI networking model, which is 1 ...


I test to send 631 bytes, in the same net, from one Windows machine to another Windows machine and seems to work OK, but if I send the same date to the CentOS server, the server only catch the first 584 bytes. That does not make much sense. With UDP you receive either the full packet or nothing, unless the application explicitly calls send with a length ...


Since this is a TCP session, and there is only an ack, the session is already established. The source IP and port are the listening memcached server. The destination is the application server client. Looks to me like it's a heartbeat from the server to the client.

Top 50 recent answers are included