April 3, 20233 yr Hey all, was hoping to get some help better understanding the best practices of setting up a custom network in my docker containers. I'm running AdGuard and it required me to setup a custom network due the ports it uses being the same as unraid. Things seem to be running ok but what I noticed was that my router shows that my host server IP is the IP of my AdGuard docker container instead of the actual unraid IP and I'm curious why. It seemed to start doing that when I changed my custom network type from macvlan to ipvlan. I'm pretty much a newbie when it comes to custom networks in docker so was hoping to get some insight. I can attach any pictures if need be. Thanks!
April 3, 20233 yr 24 minutes ago, chris.olson said: It seemed to start doing that when I changed my custom network type from macvlan to ipvlan. Some routers don't deal well with ipvlan as ipvlan assigns the same MAC address to multiple devices on the ipvlan subnet. This confuses the router even though the IP addresses are different. Macvlan does not have this issue. Here is a potential solution.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.