diff --git a/data/ch_wireshark/sec_arp.tex b/data/ch_wireshark/sec_arp.tex index eafca6c..4dbce33 100644 --- a/data/ch_wireshark/sec_arp.tex +++ b/data/ch_wireshark/sec_arp.tex @@ -220,7 +220,7 @@ IP地址长度为4字节。每个字段的含义如下: \begin{figure}[!ht] \centering - \includegraphics[width=12cm]{wireshark-statistic} + \includegraphics[width=16cm]{wireshark-statistic} \caption{统计功能} \label{fig:c:wireshark_wireshark-statistic} \end{figure} diff --git a/data/ch_wireshark/sec_ip.tex b/data/ch_wireshark/sec_ip.tex index 7fff86c..026d906 100644 --- a/data/ch_wireshark/sec_ip.tex +++ b/data/ch_wireshark/sec_ip.tex @@ -248,7 +248,7 @@ tracert命令(Linux)格式和常用参数如图\ref{fig:tracert-cmd}所示 \begin{figure}[!ht] \centering - \includegraphics[width=12cm]{wireshark-monitor} + \includegraphics[width=16cm]{wireshark-monitor} \caption{Wireshark监视器界面} \label{fig:c:wireshark_wireshark-monitor} \end{figure} @@ -258,7 +258,7 @@ tracert命令(Linux)格式和常用参数如图\ref{fig:tracert-cmd}所示 \begin{figure}[!ht] \centering - \includegraphics[width=12cm]{ip-view} + \includegraphics[width=16cm]{ip-view} \caption{查看IP数据报} \label{fig:c:wireshark_ip-view} \end{figure} @@ -268,7 +268,7 @@ tracert命令(Linux)格式和常用参数如图\ref{fig:tracert-cmd}所示 \begin{figure}[!ht] \centering - \includegraphics[width=12cm]{echo-request} + \includegraphics[width=16cm]{echo-request} \caption{Echo request示例} \label{fig:c:wireshark_echo-request} \end{figure} @@ -302,7 +302,7 @@ tracert命令(Linux)格式和常用参数如图\ref{fig:tracert-cmd}所示 \begin{figure}[!ht] \centering - \includegraphics[width=12cm]{wireshark-filter-setup} + \includegraphics[width=16cm]{wireshark-filter-setup} \caption{在Wireshark中设置过滤条件} \label{fig:c:wireshark_wireshark-filter-setup} \end{figure} diff --git a/data/ch_wireshark/sec_tcp.tex b/data/ch_wireshark/sec_tcp.tex index f3cfb9b..8dfea35 100644 --- a/data/ch_wireshark/sec_tcp.tex +++ b/data/ch_wireshark/sec_tcp.tex @@ -193,7 +193,7 @@ CUBIC\footnote{\href{https://www.researchgate.net/publication/220623913}{CUBIC: 应运而生。 CUBIC的关键特征是:cwnd窗口的增长依赖两次丢包的时间。 2016年,谷歌提出了 -BBR\footnote{\href{https://research.google/pubs/pub45646/}{BBR: Congestion-Based Congestion Control}} +BBR\footnote{\href{https://queue.acm.org/detail.cfm?id=3022184}{BBR: Congestion-Based Congestion Control}} 拥塞控制算法,它不再基于丢包感知来调整cwnd, 而是利用估算的带宽和延迟直接推测拥塞程度进而确定发送窗口。 @@ -232,7 +232,7 @@ BBR\footnote{\href{https://research.google/pubs/pub45646/}{BBR: Congestion-Based \texttt{nmap} & 网络扫描 & \url{https://nmap.org/man/zh/index.html}\\ \hline \texttt{curl} & 文本浏览器 & \url{https://man.linuxde.net/curl}\\ \hline \texttt{wget} & 下载Web文件 & \texttt{wget /}\\ \hline - \texttt{tc} & 流量控制 & \href{https://man7.org/linux/man-pages/man8/tc.8.html}{TC命令手册} \\ \hline + \texttt{tc} & 流量控制 & \href{https://man7.org/linux/man-pages/man8/tc.8.html}{tc命令手册} \\ \hline \texttt{iptables} & 防火墙配置 & \url{https://man.linuxde.net/iptables}\\ \hline \texttt{netwox} & 网络工具 & \url{https://sourceforge.net/projects/ntwox/}\\ \hline \texttt{ss} & Socket状态 & \texttt{ss –atn}\\ \hline @@ -366,7 +366,7 @@ BBR\footnote{\href{https://research.google/pubs/pub45646/}{BBR: Congestion-Based \begin{enumerate} \item 编写一对简单的TCP连接程序, 也可以直接运行指导书提供的Python程序 - (源代码见\ref{subsec:c:wireshark:s:tcp_additionalprg}节中的附件)。 + (源代码见本节最后的\nameref{subsec:c:wireshark:s:tcp_additionalprg})。 在客户端快速发送数据给服务端,而服务端则有意缓慢地接收数据, 观察TCP如何用窗口大小值进行流量控制。虚拟机两端分别运行 \texttt{python3 server.py}和\texttt{python3 client.py}。 diff --git a/figure/chapters/wireshark/ip-view.png b/figure/chapters/wireshark/ip-view.png index 588ea3c..c334323 100644 Binary files a/figure/chapters/wireshark/ip-view.png and b/figure/chapters/wireshark/ip-view.png differ