Fresh install TrueNas Scale 24.10 - Network Issues

TrueNAS General
,
1

Hello there,

I’m currently experiencing a “strange” issue.

I have a TrueNas instance running on a Asus Rogue Strix B350-F, i’m using that board dedicated ethernet connection.

I have a static IP configuration as well as GW and DNS configured.

Network-Card
Network-Card455×812 6.59 KB

I’m not able to reach the internet nor the GW.

The TrueNas Box is connected to the same switch as my PC and that switch is connected directly to the router.

I only have that network no VLANs nor different networks.

Global-Config
Global-Config751×873 21.1 KB

I already tried disabling the IPV6 this way:
System → Advance Settings → Sysctl → [net.ipv6.conf.all.disable_ipv6 - 1]

I also tried creating a static router: 0.0.0.0/0 192.168.10.1

Static-Route-Test
Static-Route-Test575×171 4.72 KB

Also i can ping devices on the LAN but not the GW.
pings
pings758×639 49.7 KB

From my PC i reach TrueNas as well as the GW

Has anyone had similar issues?

Thanks in advance.

Best regards,

Rodrigo

2

A bit of HW detail:

  • Asus Rogue Strix B350-F Gaming
  • Ryzen 3 2200G
  • 4xDDR 3200MHz 16GB non-ECC
  • Broadcom / LSI SAS2308
  • Broadcom / LSI SAS2008
  • 8x DELL SAS 800GB SSD
  • 8x DELL SAS 1.6TB SSD
  • On-Board 1GB Ethernet [Intel I211-AT]
  • 3x Noctua Fans 120MM [Intake]
  • 2x Noctua Fans 80MM [Outake]
3

A few more debugs.

Did a TCPDUMP on the shell of truenas and strange thing despite not having replies when pinging google or the pc on my LAN i see the replies on the TCPDUMP:

Output below

##################### Ping GW
20:10:59.406529 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 1, length 64
20:10:59.407235 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 1, length 64
20:11:00.424490 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 2, length 64
20:11:00.425643 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 2, length 64
20:11:01.448204 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 3, length 64
20:11:01.448885 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 3, length 64
20:11:02.472197 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 4, length 64
20:11:02.472875 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 4, length 64
20:11:02.622470 88:c3:97:52:60:15 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.10.1 (ff:ff:ff:ff:ff:ff) tell 192.168.10.62, length 46
20:11:02.736605 88:c3:97:52:60:15 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.10.1 (ff:ff:ff:ff:ff:ff) tell 192.168.10.62, length 46
20:11:03.167095 78:11:dc:41:21:b7 > ff:ff:ff:ff:ff:ff, ethertype ARP (0x0806), length 60: Request who-has 192.168.10.1 (ff:ff:ff:ff:ff:ff) tell 192.168.10.219, length 46
20:11:03.496503 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 5, length 64
20:11:03.497712 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 5, length 64
20:11:04.520190 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 6, length 64
20:11:04.520821 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 6, length 64
20:11:04.648400 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype ARP (0x0806), length 42: Request who-has 192.168.10.1 tell 192.168.10.10, length 28
20:11:04.648664 b0:76:1b:53:65:66 > b0:6e:bf:ba:9c:f0, ethertype ARP (0x0806), length 64: Reply 192.168.10.1 is-at b0:76:1b:53:65:66, length 50
20:11:05.544501 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 7, length 64
20:11:05.545547 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 7, length 64
20:11:06.568191 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 8, length 64
20:11:06.568884 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 8, length 64
20:11:07.592512 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 9, length 64
20:11:07.593538 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 9, length 64
20:11:08.071411 b0:76:1b:53:65:66 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 174: 192.168.10.1.54450 > 239.255.255.250.1900: UDP, length 132
20:11:08.331218 b0:76:1b:53:65:66 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 174: 192.168.10.1.54450 > 239.255.255.250.1900: UDP, length 132
20:11:08.591219 b0:76:1b:53:65:66 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 175: 192.168.10.1.54450 > 239.255.255.250.1900: UDP, length 133
20:11:08.616400 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 192.168.10.1: ICMP echo request, id 55469, seq 10, length 64
20:11:08.617034 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 192.168.10.1 > 192.168.10.10: ICMP echo reply, id 55469, seq 10, length 64
20:11:08.851094 b0:76:1b:53:65:66 > 01:00:5e:7f:ff:fa, ethertype IPv4 (0x0800), length 175: 192.168.10.1.54450 > 239.255.255.250.1900: UDP, length 133

##################### Ping GOOGLE
listening on enp4s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
20:11:35.809866 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 1, length 64
20:11:35.824060 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 1, length 64
20:11:36.840501 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 2, length 64
20:11:36.854786 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 2, length 64
20:11:37.864673 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 3, length 64
20:11:37.879081 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 3, length 64
20:11:38.888215 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 4, length 64
20:11:38.902588 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 4, length 64
20:11:39.912484 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 5, length 64
20:11:39.926267 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 5, length 64
20:11:40.936503 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 6, length 64
20:11:40.950805 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 6, length 64
20:11:41.960484 b0:6e:bf:ba:9c:f0 > b0:76:1b:53:65:66, ethertype IPv4 (0x0800), length 98: 192.168.10.10 > 8.8.8.8: ICMP echo request, id 2244, seq 7, length 64
20:11:41.975009 b0:76:1b:53:65:66 > 88:c3:97:52:60:14, ethertype IPv4 (0x0800), length 98: 8.8.8.8 > 192.168.10.10: ICMP echo reply, id 2244, seq 7, length 64
This text will be hidden

When pinging the PC i do have a reply on the ping and i see the same flow as displayed above for the GW.

4

Try setting TrueNAS to use DHCP for it’s interface. I think you have a few settings that aren’t working together. If you have screenshots, you can always set it back to how you have it now.

Edit Global Configuration - you have Inherit domain from DHCP?
DNS. Maybe set the alternate DNS you want on the GW and only point to it. Order of listings of DNS, as you have it may be weird.

What does the Network tab look like? shows interfaces, global configuration and static routes on my Nightly version of TrueNAS. I don’t know if yours is the same.

1 Like
5

Will try the DHCP.

Yeah the DNS order was change many time already i already tried with only the GW, only the google and so on so on…

The Network tab show all the setting posted on the prints all togther no change there.

Regarding the inherit domain… i was already desperate to see any change :sweat_smile:

6

After a couple of reboots and changind to DHCP trough CLI and trough web interface it finaly worked… althought everytime i try to put a static IP it will break Truenas and no comunictation will flow… i would say it’s a bug :frowning:

7

I don’t think it is a bug and it’s your setup causing a clash.

Have you checked your router settings? You don’t mention the model or anything.

8

I don’t really think it would be the router on the release 20.X.X (i believe it was 20th if not it was close i didn’t do an update for 2 years) that i was running i didn’t had any issues with seting static IPs nor do i have with any other device connected to that router.

Still it’s and ISP router the model is OptiXstar HG8247X6-8N GPON.

I also validated that the static IP was appearing as a static ARP entry on the router.

As soon as i configure static routing on TrueNas the same issue will happen, all outgoing traffic from TrueNas will not work but acessing web interface and ping the static IP of TrueNas works like a charm.

9

You can try submitting a bug. It would probably require you documenting the network and providing screenshots of your TrueNAS network settings with DHCP and then again with the problem. They would have to be able to reproduce the issue

Upper right of TrueNAS GUI is a Smile icon. It’s for Feedback / Report A Bug.

10

Thanks will probably do so.

And thanks for the work around sugestion :smiley: