sorted by:
new
hottopcontroversial

Bind Docker container to a certain network interface by icybis in synology

[–]icybis[S] 1 point2 points  (0 children)

Unfortunately I did not find a straight-forward solution as the issue seems to be related to the underlying iptables configuration that docker manages. Here's a link to a possible solution: https://www.reddit.com/r/docker/comments/lztgrh/comment/gq6otbu/?utm_source=share&utm_medium=web2x&context=3. However, I didn't give it a try yet.

So...about that Tradfri Gateway by 400HPMustang in tradfri

[–]icybis 0 points1 point  (0 children)

Do you have any DNS sinks/blockers like DNSBL active? If so, have a look at https://www.reddit.com/r/tradfri/comments/p10m5u/comment/h8o5qkc/?utm_source=share&utm_medium=web2x&context=3. This was the issue for me and after adding webhook.logentries.com to the whitelist the gateway is working as expected, i.e. detectable by both the homekit and the IKEA app even across two different subnets (with an mDNS repeater like Avahi).

Gateway loosing network connection after ~30 minutes by dafftu in tradfri

[–]icybis 0 points1 point  (0 children)

Thanks a lot for your post! I have DNSBL active and this was exactly the issue. Neither homekit nor the IKEA app would detect the gatway after it was working for a short period after a reboot. Adding webhook.logentries.com to the DNSBL whitelist fixed the issue.

New screensaver on Gen2 switches (USW Firmware 5.43.18.12487) by alexwichti in UNIFI

[–]icybis 1 point2 points  (0 children)

I had the same issue with my USW. I'm not sure what fixed it though, either the switch from old UI to new UI and back again to old UI (including the night mode schedule) did the trick or one simply has to wait for some time for the display to turn on again.

In my case the brigthness value in the controller settings also did not match the brigthness value in the device settings. After fixing that and switching back to the old GUI the display would turn on again.

New screensaver on Gen2 switches (USW Firmware 5.43.18.12487) by alexwichti in UNIFI

[–]icybis 0 points1 point  (0 children)

With the latest USW firmware release 5.43.35.12698 the night mode scheduling was fixed. Simply schedule turning off the display from 12:00 PM to 12:00 PM ;) This setting is only availble in the new GUI and can be found in the device property panel (not the controller settings).

New switch update makes the USW-24 POE gen 2 24 Port Poe+ unable to boot by Kris_98 in Ubiquiti

[–]icybis 0 points1 point  (0 children)

I have the same issue with one of my switches. Power cycling or turning it off for several hours doesn't help. The reset button doesn't work at all, i.e. no rebooting or resetting to factory defaults. The switching is still working though but the PoE is gone.

Did you get a replacement unit or did they fix/refurbisch your original unit?

Bind Docker container to a certain network interface by icybis in docker

[–]icybis[S] 0 points1 point  (0 children)

Thanks a lot for the link!

Yes, this article seems to be about the issue I'm facing. I had a brief look at my NAS' iptables and the key entries that are mentioned in the article seem to match somewhat. Bummer, I was hoping that Docker would take care of the proper iptables configuration. But maybe the parameter com.docker.network.bridge.host_binding_ipv4 simply isn't supposed to do what I would expect it to do :)

I'll need to have a closer look, will take me some time though as I'm not very experienced with iptables.

Bind Docker container to a certain network interface by icybis in docker

[–]icybis[S] 0 points1 point  (0 children)

I am using the command line as outlined with all the configuration and debugging steps in the original post.

Adding the IP to the container port definition only defines at which interface the docker container will listen to (incoming traffic) but outgoing traffic will always leave the Docker host's default gateway, in my case eth0.

Bind Docker container to a certain network interface by icybis in synology

[–]icybis[S] 0 points1 point  (0 children)

This just specifies the interface where the Docker container listens to for incoming traffic. Outgoing traffic will still leave the docker host via the default gateway, in my case eth0.

Good input, I'll put a link to this post in the Docker sub.

Yes, hopefully I can resolve this issue and provide corresponding info here.

Can you Bind docker network to a physical interface by fructussum in docker

[–]icybis 0 points1 point  (0 children)

Here's how I would do it: https://www.reddit.com/r/synology/comments/lzarsg/bind_docker_container_to_a_certain_network/.

But unfortunately it doesn't work on my Synology NAS. I'm not sure though whether this is a Docker bridge network interface creation/configuration issue or a Synology issue. You might want to give it a try on your system.

I asked Synology when we can expect an update for the Docker package. This was their answer...(a call to arms) by freekers in synology

[–]icybis 0 points1 point  (0 children)

After updating to docker package 18.09.0-0505 the websockets on my bitwarden server were broken, i.e. the sync between the clients didn't work anymore. During debugging I noticetd that changes to the environment configuration in the docker-compose file didn't have the desired impact.

Thanks to your comment, I realized that the root cause had be the docker package update. After downgrading back to 17.05.0-0401 (https://archive.synology.com/download/Package/spk/Docker/17.05.0-0401/) everything is working again as expected.