Network System

24 October 2014

Checksum

  • Ethernet has a CRC check
  • TCP has a checksum header field for header and text
  • IP Header has checksum header field.
  • Kafka message has a CRC32 field.

References:

Ethernet

RFC 894 vs RFC 1042

2.2 Ethernet and IEEE 802 Encapsulation of TCP/IP Illustrated, Vol. 1: The Protocols (Addison-Wesley Professional Computing Series) 1st Edition says:

RFC 894 encapsulation is most commonly used.

And Ethernet_frame says:

Ethernet II frame, or Ethernet Version 2,[g] or DIX frame is the most common type in use today, as it is often used directly by the Internet Protocol.

Ethernet II frame means a RFC 894 frame. Ethernet_frame also says:

There exists an Internet standard for encapsulating IPv4 traffic in IEEE 802.2 LLC SAP/SNAP frames.[13] It is almost never implemented on Ethernet, although it is used on FDDI, Token Ring, IEEE 802.11 [clarification needed] and other IEEE 802 LANs.

IEEE 802.2 LLC SAP/SNAP frames are RFC 1042 frame. So it seems that RFC 894 is more much widely used than RFC 1042.

  • RFC 2464: Requirements for Internet Hosts – Communication Layers

TCP

Timeout

Socket API:

TCP:

  • tcp_retries1
  • tcp_retries2

Java

TCP Flags: PSH and URG

Congestion Control

TCP backoff:

One TCP connnection has one RTO timer.

Checksum

For the following back udp cksum error in the data captured by tcpdump, UDP / TCP Checksum errors from tcpdump & NIC Hardware Offloading has a good explanation.

13:50:36.947842 IP (tos 0x0, ttl 64, id 17989, offset 0, flags [DF], proto UDP (17), length 56)
    127.0.0.1.4445 > 127.0.0.1.54279: [bad udp cksum 0xfe37 -> 0x7e2b!] UDP, length 28
	0x0000:  4500 0038 4645 4000 4011 f66d 7f00 0001  E..8FE@.@..m....
	0x0010:  7f00 0001 115d d407 0024 fe37 5375 6e20  .....]...$.7Sun.
	0x0020:  4a61 6e20 3034 2031 333a 3530 3a33 3620  Jan.04.13:50:36.
	0x0030:  4353 5420 3230 3135                      CST.2015

MISC

Output form ifconfig.

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host


wlan0     Link encap:Ethernet  HWaddr 7c:7a:91:bf:de:3e  
          inet addr:10.62.32.163  Bcast:10.62.47.255  Mask:255.255.240.0
          inet6 addr: fe80::7e7a:91ff:febf:de3e/64 Scope:Link

Consider a server and a client which are running on the same machine. Moninoring with tcpdump draws the following conclusion. Whatever ip (127.0.0.1 or 10.62.32.163) the client use to connnect to the server, the lo interface is used.

IETF

Base 64:

{1}: AQ==
0000 00,01 0000

{1, 2}: AQI=
0000 00,01 0000, 00010 00

{1, 2, 3}: AQID
0000 00,01 0000, 00010 00,00 0011

HTTPS

DNS

CoreDNS

The following text describes how to use file plugin to serve a zone and do forwarding for other zones.

Corefile:

xxxyyyzzz.org {
    file xxxyyyzzz.org
    prometheus     # enable metrics
    errors         # show errors
    log            # enable query logs
}

. {
    forward . 192.168.1.1 # A vaid DNS server
    log
}

xxxyyyzzz.org:

$ORIGIN xxxyyyzzz.org.
@	3600 IN	SOA sns.dns.icann.org. noc.dns.icann.org. (
				2017042745 ; serial
				7200       ; refresh (2 hours)
				3600       ; retry (1 hour)
				1209600    ; expire (2 weeks)
				3600       ; minimum (1 hour)
				)

	3600 IN NS a.iana-servers.net.
	3600 IN NS b.iana-servers.net.

www     IN A     20.0.0.1

$ dig -p 1053 @localhost www.xxxyyyzzz.org +noall +answer

; <<>> DiG 9.10.6 <<>> -p 1053 @localhost www.xxxyyyzzz.org +noall +answer
; (2 servers found)
;; global options: +cmd
www.xxxyyyzzz.org.	3600	IN	A	20.0.0.1

$ dig -p 1053 @localhost www.baidu.com +noall +answer

; <<>> DiG 9.10.6 <<>> -p 1053 @localhost www.baidu.com +noall +answer
; (2 servers found)
;; global options: +cmd
www.baidu.com.		564	IN	CNAME	www.a.shifen.com.
www.a.shifen.com.	264	IN	A	61.135.169.125
www.a.shifen.com.	264	IN	A	61.135.169.121

Resources