端口监听正常,局域网访问不了【着实费解!!】

问题遇到的现象和发生背景

安装odoo社区版版本,端口号8069
操作系统:Ubuntu Server 22.04
IP地址:192.168.1.120
python版本:Python 3.10.4
补充:端口22,就很正常,没有问题,怎么连接都可以!真是费解!!

运行结果及报错内容

局域网用浏览器打开访问 http://192.168.1.120:8069/ 访问不了,提示连接超时

我的解答思路和尝试过的方法

查看防火墙什么的【firewalld,iptables】,全部都未安装关闭了。

查看监听状态,正常

xiedaolin@nanjing:~$ sudo netstat -an | grep LISTEN
[sudo] password for xiedaolin: 
tcp        0      0 127.0.0.1:5432          0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:8069            0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:10025         0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:10028         0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.1:7790          0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:587             0.0.0.0:*               LISTEN     
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:465             0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN     
tcp        0      0 0.0.0.0:25              0.0.0.0:*               LISTEN     
tcp6       0      0 :::587                  :::*                    LISTEN     
tcp6       0      0 :::465                  :::*                    LISTEN     
tcp6       0      0 :::22                   :::*                    LISTEN     
tcp6       0      0 :::25                   :::*                    LISTEN

由于无图形界面,在本机通过curl命令,返回正常,说明监听没有问题

root@nanjing:~# curl localhost:8069
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>Redirecting...</title>
<h1>Redirecting...</h1>
<p>You should be redirected automatically to target URL: <a href="/web">/web</a>. If not click the link.

使用tcpdump命令工具抓包,发现有请求i过来,但是长度为0

root@nanjing:~# tcpdump -i any port 8069
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
16:54:28.961236 enp3s0 In  IP 192.168.1.122.52285 > nanjing.njbjc.com.8069: Flags [S], seq 4086347667, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:28.961237 enp3s0 In  IP 192.168.1.122.52286 > nanjing.njbjc.com.8069: Flags [S], seq 1367962423, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:29.217091 enp3s0 In  IP 192.168.1.122.52290 > nanjing.njbjc.com.8069: Flags [S], seq 1574040098, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:29.965667 enp3s0 In  IP 192.168.1.122.52285 > nanjing.njbjc.com.8069: Flags [S], seq 4086347667, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:29.965667 enp3s0 In  IP 192.168.1.122.52286 > nanjing.njbjc.com.8069: Flags [S], seq 1367962423, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:30.220735 enp3s0 In  IP 192.168.1.122.52290 > nanjing.njbjc.com.8069: Flags [S], seq 1574040098, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:31.977727 enp3s0 In  IP 192.168.1.122.52285 > nanjing.njbjc.com.8069: Flags [S], seq 4086347667, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:31.977728 enp3s0 In  IP 192.168.1.122.52286 > nanjing.njbjc.com.8069: Flags [S], seq 1367962423, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:32.232731 enp3s0 In  IP 192.168.1.122.52290 > nanjing.njbjc.com.8069: Flags [S], seq 1574040098, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:35.984742 enp3s0 In  IP 192.168.1.122.52285 > nanjing.njbjc.com.8069: Flags [S], seq 4086347667, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:35.984743 enp3s0 In  IP 192.168.1.122.52286 > nanjing.njbjc.com.8069: Flags [S], seq 1367962423, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
16:54:36.240711 enp3s0 In  IP 192.168.1.122.52290 > nanjing.njbjc.com.8069: Flags [S], seq 1574040098, win 64240, options [mss 1460,nop,wscale 8,nop,nop,sackOK], length 0
我想要达到的结果

局域网可以访问

看一下能不能ping通,或者在本机和远端telnet一下端口号

这种情况有一种可能性是入接口和回程接口不是同一接口,而网卡开启反向路由检测导致的不回包。检查一下路由,看入接口和回车路由是否是同一接口?
我抓了一下我这里的,tcp握手过程是len=0,而且没带-nn的话,回去反向查询ip成域名。你tcpdump -i any -nne tcp port 8069看看目的ip是否是192.168.1.120,是的话,就比较奇怪了,同网段的路由应该不会出错。

img