DNS resolves but no packets return

[Gergorian]

I have a TrueNAS server (clean install of latest stable build) and it can't reach the update server or any of the plugin directories. I know it is having to do with my network configuration but I'm at a loss as to where to look. Ping lookups will resolve to the IP address but fails to return any packets. Does someone have an idea of what network settings I am forgetting to correct?
- Greg

 

[Redcoat]

Welcome to the forums!

Do you have a default gateway specified in Network>Global Configuration> Default Gateway?

 

[Gergorian]

Yes, my router's IP is set for that value. A couple things I'll add to my testing. I can't ping my router from the system (I've gotten maybe 1 or 2 responses out of a couple dozen packets sent). I was more successful in pinging my Win11 desktop with a 90%+ successful packet response. I can't ping the TrueNAS from my Win11 desktop though.
On a final note, they system is setup in my garage with a wireless repeater configured. I also get no reply from the repeater from the TrueNAS but 100% with <1ms responses when pinging the repeater from my Win11 desktop in the house. I'll try moving the box inside at least to test the TrueNAS network directly plugged into my wired in-home network but don't expect much to change there.

 

[ChrisRJ]

A diagram of the network would be helpful.

In a small local network anything but 100% success rate for ping means a serious problem. So it appears the issue is more on the network level in general.

 

[Gergorian]

The ONLY system that has issues accessing anything is the TrueNAS system. If I place a Windows box, or one of my other linux servers in the garage they all ping and resolve just fine. I am confident it is something to do with the network config on the TrueNAS setup but I'm at a loss as to what. I even did a clean/fresh install as this system was originally setup in my business so I wanted to make sure everything was clear. I've done nothing to the config of the default network post installation other than adding my router IP into the Gateway settings.

Below is my ping test - my router I get no replies, my desktop (plugged INTO my router) replies just fine. If I use any other box out in the garage (win/linux/mac) they ALL get replies from the router just fine.

root@mytruenas[~]# ping 10.0.2.1 <-- my router
PING 10.0.2.1 (10.0.2.1): 56 data bytes
^C
--- 10.0.2.1 ping statistics ---
11 packets transmitted, 0 packets received, 100.0% packet loss
root@gregkatnas[~]# ping 10.0.2.106 <-- my Win11 box
PING 10.0.2.106 (10.0.2.106): 56 data bytes
64 bytes from 10.0.2.106: icmp_seq=0 ttl=128 time=8.070 ms
64 bytes from 10.0.2.106: icmp_seq=1 ttl=128 time=7.171 ms
..... more ping results
64 bytes from 10.0.2.106: icmp_seq=3 ttl=128 time=59.591 ms
64 bytes from 10.0.2.106: icmp_seq=4 ttl=128 time=1.856 ms
^C
--- 10.0.2.106 ping statistics ---
13 packets transmitted, 13 packets received, 0.0% packet loss

 

[Gergorian]

A diagram of the network would be helpful.

In a small local network anything but 100% success rate for ping means a serious problem. So it appears the issue is more on the network level in general.

OK, you got me thinking. So I connected back to my wifi repeater and saw there was an update for the firmware. I installed that and it resolved the issue. Still not clear why other devices would connect thru it just fine but TrueNAS wouldn't, but it did end up being elsewhere in the network. Thank you for your response.
- Greg