2025-03-19, 06:43 PM
I don't know if this is helpful information, but I figured doing a tcpdump might point to some clues. The following command was run on my NAS, with the output below -- each line wiht at timestamp corresponds to when I hit the refresh button on my browser when trying to connect to my jellyfin server on my main computer:
So my NAS is receiving the connection request. It just doesn't seem to be responding to it.
Code:
[arby@Nash ~]$ sudo tcpdump -i any port 8096
tcpdump: WARNING: any: That device doesn't support promiscuous mode
(Promiscuous mode not supported on the "any" device)
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
14:39:33.764714 enp42s0 In IP 192.168.1.112.41594 > Nash.8096: Flags [S], seq 2269463872, win 64240, options [mss 1460,sackOK,TS val 303552957 ecr 0,nop,wscale 7], length 0
14:39:43.088673 enp42s0 In IP 192.168.1.112.35156 > Nash.8096: Flags [S], seq 3055431730, win 64240, options [mss 1460,sackOK,TS val 303562281 ecr 0,nop,wscale 7], length 0
14:39:43.995989 enp42s0 In IP 192.168.1.112.52606 > Nash.8096: Flags [S], seq 3005522015, win 64240, options [mss 1460,sackOK,TS val 303563188 ecr 0,nop,wscale 7], length 0
14:39:44.776940 enp42s0 In IP 192.168.1.112.52612 > Nash.8096: Flags [S], seq 3852564276, win 64240, options [mss 1460,sackOK,TS val 303563969 ecr 0,nop,wscale 7], length 0
14:39:45.434303 enp42s0 In IP 192.168.1.112.52626 > Nash.8096: Flags [S], seq 3468579809, win 64240, options [mss 1460,sackOK,TS val 303564626 ecr 0,nop,wscale 7], length 0
So my NAS is receiving the connection request. It just doesn't seem to be responding to it.