Strange DSCP behaviour of TCP

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello!

Today I have noticed strange behaviour of TCP in Linux.

We send SYN packet with DSCP=63 to Linux server. If there is no 
firewall, server will respond with one of two possible packets:

1) If port is open, it will send us SYN,ACK with DSCP=0
2) If port is closed, it will respond with RST,ACK DSCP=63.

The question is: why DSCP of RST,ACK packet is set to DSCP value of SYN 
packet?

My kernel is 2.6.14. Didn't try with latest kernel yet.
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux