• 6 Posts
  • 11 Comments
Joined 1 year ago
cake
Cake day: October 2nd, 2023

help-circle




  • I presume you’re talking about this one ?

    sudo ip addr add 192.168.2.201/32 dev macvlan0

    I guess I didn’t explain properly but that is your auxiliary host’s IP. If you look at command 2 you’ll see

    --aux-address=“host=192.168.2.201”

    . Basically the CIDR notation

    /32

    is the same as the subnet mask

    255.255.255.255

    , only one IP address can be served in macvlan0.

    I was actually referring to ‘sudo ip route add 192.168.2.200/29 dev macvlan0’ for #3

    This one has me stumped. I hope you’re not one of those who deletes his Reddit posts because I may need to come back to this post one day 😁


  • I think I am about 99% of the way there. Seems like I got it mostly figured out, but I do have a couple questions for you. And thanks again for your time, you have no idea how much I appreciate you and your assistance in this.

    #1. After creating the docker network, you suggest creating the macvlan and the command for creating the macvlan involes ‘macvlan0’. I cannot use macvlan0 and instead am forced to use macvlan1 because macvlan0 is taken by the docker network we created just before creating the macvlan. Seems to be a conflict. I checked and there’s nothing else conflicting other than the already created macvlan0 from the step before.

    #2. After completing the steps, I can access my NAS as usual, the Nginx proxy manager is accessible via it’s macvlan IP, but I can also connect to the NAS and the Nginx from the auxillary host IP. What’s the deal with that?

    #3. Once all is said and done. Should my Nginx be connected to both the bridge network and the new macvlan or just the macvlan? It’s always connected to the bridge by default, but when I add the container to the new macvlan, am I supposed to disconnect it from the bridge?



  • Okay, so here’s where I’m confused. From my understanding you say all I did is create a docker network and I need to create a macvlan but the ‘npm_network’ that I created literally says macvlan beside it in the network tab of either container manager or portainer. Even the command literally says ‘create macvlan’ so I am confused why you say that’s not a macvlan and only a docker network.
    Am I making sense? Also, two other outdated guides ive seen on this describe it the same way. The way you describe it is a first that I’ve seen. Not saying you’re wrong, but there’s certainly a difference I’m noticing.


  • Here, let me show you what I did and you tell me where I went wrong.

    1. SSH into Synology NAS and Create macvlan network with modified command below to my system:sudo docker network create -d macvlan \-o parent=eth0 \–subnet=192.168.1.0/24 \–gateway=192.168.1.1 \npm_network

    2. Install Nginx Proxy Manager docker container

    3. Assign NPM to use the new macvlan network and assign it an IP on the subnet that’s not already in use with the following command:docker network connect --ip 192.168.1.99 npm_network nginx_proxy_manager

    4. Go into portainer and under container settings for NPM, ensure the container is connected to both the new macvlan with the info we used and also connected to the default bridge network.

    This is where I hit a wall. I still cannot connect to my web interface at this point when I feel like I should be able to with the macvlan ip 192.168.1.99

    What am I doing wrong?