Now I will simply put together a docker-compose file and run pihole in a container. Nginx is available at 192.168.0.210 while my node.js server is available at 192.168.0.51 Sudo ip addr add 192.168.0.210/28 dev piholenet0ĭocker network create -driver=macvlan -gateway=192.168.0.1 -subnet=192.168.0.0/24 -o parent=wlan0 piholenetĭocker run -net=piholenet -dit -name nginx-test-01 nginx:alpine nginx-debug -g 'daemon off ' Solved with a simpleĪs per Docker MACVLAN only works OutboundĪfter this, following your guide has worked perfectly fine: sudo ip link add piholenet0 link wlan0 type macvlan mode bridge It's apparently an ARP issue in the Linux Kernel version used in Raspbian. Good news! There is nothing wrong with the setup we've been trying to do. I also can't see piholenet0 listed on my router. However, when I go to 192.168.0.51 or 192.168.0.208 they both show the website I am hosting on node.js. RX errors 0 dropped 76 overruns 0 frame 0 TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
#Optimal mtu for vpn synology mac#
So far so good, I have both interfaces up and running with different IP and MAC addresses: Sudo ip link add piholenet0 link wlan0 type macvlan mode bridge Then, I do the following:ĭocker network create -driver=macvlan -gateway=192.168.0.1 -subnet=192.168.0.51/24 -o parent=wlan0 piholenet I've got a node.js server running on wlan0, port 80, ip 192.168.0.51. Could you have a look and see if you can help? I want to avoid port conflicts and thought macvlan would be the best solution. I'm stuck trying to get pihole working concurrently with a node.js server on Raspberry Pi 4. volume /etc/localtime:/etc/localtime:ro \ # Also I've added a fake mac address so the container always uses the samen mac, handy to make a reservation in your DHCP scope or do whatever you like to do with it. # Now start PiHole on a macvlan enabled IP address f.e. Don't forget to remove the container afterwards. # Browse to in your local network, you should see the nginx welcome page!. While ! ip link show eth0 | grep -q 'state UP ' doĭocker run -net=macvlan -dit -name nginx-test-01 -ip=192.168.1.211 nginx:alpine nginx-debug -g 'daemon off ' # It's also possible to create a scheduled task at startup as the root user, it's wise to append the following in front of the above commands TX packets:48 errors:0 dropped:0 overruns:0 carrier:0 RX packets:79 errors:0 dropped:0 overruns:0 frame:0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Macvlan0 Link encap:Ethernet HWaddr 92:8D:43:0E:E2:D8 # Check virtual adapter status with ifconfig # Specify part of the eth0 scope you'd like to reserve for macvlan0 Ip link add macvlan0 link eth0 type macvlan mode bridge # Create a Synology macvlan0 bridge network attached to the physical eth0, and add the ip range scope (sudo) # DHCP scope reservation for macvlan: 192.168.1.210/28 (Details below)