Hi
it’s been a few days I think since last update (24.04.2.1) TrueNas can’t connect outside my lan.
Which means no catalog updates and no cloud backups…
I use a linux VM and was wondering whether the setup of the bridge could be the problem…
My router’s IP is 192.168.2.2 (yes, not 192.168.1.2), the TN’s IP is 192.168.2.101 and the linux VM’s IP is 192.168.2.53.
My guess would be that before you’ve setup the bridge you were using DHCP and now a staric ip, which means you have to manually set the Default gateway ( your Routers IP) and DNS Servers in the global network settings
Edit:
You’ve Set your Routers IP as nameserver If my rusty french knowlesdge is correct. Set the nameserver to something like 1.1.1.1 and 1.0.0.1 for cloudflare or 8.8.8.8 and 8.8.4.4 for google
No reason to do that; the router almost always acts as nameserver to the LAN. And the nameserver and gateway are set. I’m a little suspicious of the .2 IP address for it–there’s nothing inherently wrong with that, but I almost always see routers at either .1 or .254.
But I think the bigger problem is that physical interface has an address, and the bridge also has an address (and it’s the same address). The address on the physical interface needs to be removed.
It’s fixed now but I’m not sure how. At some point the IP was static and it was problematic. So I set it up as DHCP, seems like it was not completely working. So I unchecked DHCP, applied, rechecked DHCP, applied, and it seems to work now.
As @dan mentionned the router acts as a nameserver and is itself pointing to 1.1.1.1.
The .2 isn’t an issue either.
In any case thanks a lot to @dan and @LarsR
I must say I come from 10 years of half synology half qnap. I went towards these small machines because they were small and supposedly efficient and easy to handle. Turns out that TrueNas is much easier to handle, works perfectly (well except my DNS issue) and if the case I chose is bigger than my qnap it’s also dead silent and I only hear the HDD scratching a little from time to time. Thanks a lot to TrueNas and its community.
For the record : this is the current setup, and it works.
Annnnnnd it stopped working again.
Seems the only difference is an IPV6 adress ony my network adapter. But I did no such thing as touching even remotely IPV6. I haven’t checked the “auto setup” of IPV6 in the settings for instance… Should I ?
In your picture from above it shows that both the bridge and the nic have the same ip assigned to it. Remove the ip from the nic, it’s not possible for both the nic and the bridge to have an ip. The ip should only be on the bridge and the nic should be a member of that bridge