Networking issue - truenas taking router ip

TrueNAS General
1

Not sure where to go on this one:

Ive been playing with dockge and frigate - changing to network host mode etc.

Symptoms of my issue is the whole networks traffic has been slow to respond - its resolving the router ip (192.168.1.1) as truenas (192.168.1.3)

I kow this because when I tried to access the router it would load and let me login to truenas on 1.1 - even though that IP is not allocated to truenas.

Its not a DNS thing - I dont refer to my gateway by name and wasn’t accessing pfsense via dns.

If I access shell on truenas scale (EE) and go ifconfig I get a bunch of interfaces, including one with my routers IP:


br-8ebe2f918b10: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 192.168.1.1  netmask 255.255.255.0  broadcast 192.168.1.255
        ether 02:42:8c:6d:b8:ab  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Why would this be accessible to my general network? ShouId blow away dockge and consider a vm with all my custom docker stuff there as the app catalog doesn’t have everything i need?

2

This is a docker bridge network by looks of it. Usually these have an address in the range of something like 172.17.0.0/16 or similar.

3

…which raises the question, did you change your address pool (see below)?

image
image454×607 9.22 KB

If so, I’d bet good money that’s your problem.

1 Like
4

Where is that screen? The networking section only has the main system IP.

I am familiar with dhcp, DNS and setting ups etc, but can’t figure out this strange behaviour. That br listing is my best guess, but it could be unrelated. Is it something I can delete or at least comment out directly in a conf file in shell to test and see what breaks?

5

It’s part of the apps settings.

6

Screenshot_20250628_072446_Chrome
Screenshot_20250628_072446_Chrome1440×2918 219 KB

None of the apps in truenas apps section have the IP directly.

Screenshot_20250628_072655_Chrome
Screenshot_20250628_072655_Chrome1440×2918 153 KB

7

Actually, I remember now I was trying to get frigate to work after moving hosts, and I did try adding a bridge to the networking through docker compose in dockge, and I put in the local network, which was a mistake apparently, but that config is gone so I’m not sure why the br interface still exists or how to clean it up

8

Fingers crossed I sorted it:

Shell on the dockge image
docker network ls
(find the name of the interface br-8ebe2f918b10 - in this case frigate_static-network)
docker network rm frigate_static-network

So my own stupidity trying things royally effected the network. lesson learned.