Docker custom network issue

[XFNeo]

Ip address on "web" interface is 169.254.251.144
Behaviour was not changed, it is still the same problem.
The problem was not fixed in the latest versions of TOS and Docker App.

[Gremlin]

That looks like a generic ip address assigned by the network card when no specific ip address has been set. Check out either your fixed ip address or your DHCP settings.

[TMRyan]

Ip address on "web" interface is 169.254.251.144
Behaviour was not changed, it is still the same problem.
The problem was not fixed in the latest versions of TOS and Docker App.

Perhaps you can try replacing the switch, restarting the router, or checking the DHCP settings of the router.
Of course, you can also try reinstalling Docker.

[XFNeo]

Ip address on "web" interface is 169.254.251.144
Behaviour was not changed, it is still the same problem.
The problem was not fixed in the latest versions of TOS and Docker App.

Perhaps you can try replacing the switch, restarting the router, or checking the DHCP settings of the router.
Of course, you can also try reinstalling Docker.

What are you taking about? Which router? Which DHCP? "web" is a docker bridge interface.
Have you seen my previous message?
viewtopic.php?f=43&t=3817&start=10#p28608

[Gremlin]

In your earlier post the "web" ip is not what you state now. Also I notice "web" and eth1 have the same address.

You are (it seems) creating custom interfaces. The keyword is "custom" - don't see how TM can be resposible for fixing your custom installations.

[XFNeo]

{L_BUTTON_AT}Gremlin

Please read all thread. I have many times describe the issue.
eth1 it is one of physical TNAS ethernet which is not connected.

[davidecavestro]

{L_BUTTON_AT}TMRyan

Hey, on my F2-223 running TOS 5.1.40 I can see udhcpc running a script at /var/nas/udhcps which in turn seems to assign random IPs on the class 169.254.x.x Is it standard TOS stuff? I guess it spreads addresses both to physical TNAS ethernet when not plugged and to veth interfaces

Code: Select all

[********@**** ~]# ps -ef | grep dhcp
********   938     1  0 10:38 ?        00:00:00 udhcpc -i eth0 -S -s /var/nas/udhcps -b -x lease:172800
********  1310     1  0 10:38 ?        00:00:00 udhcpc -i eth1 -S -s /var/nas/udhcps -b -x lease:172800
******** 26306     1  0 11:04 ?        00:00:00 udhcpc -i br-83c2da26f871 -S -s /var/nas/udhcps -b -x lease:172800
******** 26332 26307  0 11:04 ?        00:00:00 udhcpc -i veth56c6abd -S -s /var/nas/udhcps -b -x lease:172800
******** 26677 11891  0 11:04 pts/1    00:00:00 grep dhcp
[********@**** ~]# ifconfig veth56c6abd
veth56c6abd: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 169.254.251.45  netmask 255.255.0.0  broadcast 169.254.255.255
        inet6 fe80::1082:f2ff:fe42:36b2  prefixlen 64  scopeid 0x20<link>
        ether 12:82:f2:42:36:b2  txqueuelen 0  (Ethernet)
        RX packets 4670  bytes 449337 (438.8 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 5436  bytes 7893157 (7.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

That said, some containers work properly, while some others complain for name resolution issues at least.

[tab3rware]

{L_BUTTON_AT}TMRyan

That said, some containers work properly, while some others complain for name resolution issues at least.

Hi, the name resolution problems could be the permissions problems?, check this viewtopic.php?f=43&t=4881

[davidecavestro]

Definitely yes... incidentally I have the same issues you had with nextcloud AIO https://github.com/nextcloud/all-in-one ... nt-6584461 but there could be something else undergoing for that.

I'm experimenting name resolution issues even with immich and other images.
I'll continue on the other thread where Bipe posted a workaround...

[XFNeo]

{L_BUTTON_AT}TMRyan

Any updates?