Search for a command to run...
A guy with a keen interest in computer networks, software development, web technologies, embedded systems, and programming. When I am bored you can find me bingeing anime series, reading novels, and tinkering with hardware and software.
What is your configuration on the router? And won't manually adding ip be tedious as the ipv6 could be dynamic?
Nothing special on the router side. The server machine is connected normally, the same as other devices in my house. I have written a blog about how to enable relay mode for ipv6 for the secondary router, you can check it out here https://blog.bimal1412.com.np/enable-ipv6-on-a-secondary-router-running-openwrt
As, for the other question, yes I am sure it will get tedious if you plan on using it to host something with ipv6 directly from the docker container without tunneling. But I am sure that can be solved by writing a bash script to automate the config to get the new ipv6 gateway if the IPv6 prefix changes.
Among the various challenges that were presented in the event, I had a lot of fun solving the forensic challenges. Among them was the challenge called InZiPtion. The initial challenge post was straightforward. We were provided with a zip file and up...
If you are not familiar with the restriction that Flutter-Based Apps have while proxying it's traffic for analysis proposes then you can head over to this blog and read more about it, Bypass SSL Pinning for Flutter Apps using reFlutter Framework | Me...
One of the greatest problems a person faces while self-hosting is the NAT. For people whose ISP doesn't provide port forwarding or a public IP, tunneling or using a VPN is the only way to expose self-hosted services to the internet. Having IPv6 is gr...
When it comes to custom router firmware, OpenWRT is probably the best. If you build the firmware by yourself, you can skip all the preinstalled LuCi Web UI things and dial down the RAM usage to just 3-4 MB. One of the cool things about OpenWRT is its...
Each container having its own public IPv6 will have tons of benefits. For example, if you are running a torrent client application on a docker container and using it for downloading torrents, with ipv6 assigned to it, it will able to communicate with peers having ipv6 directly and will be able to directly download from them. This will dramatically increase the torrent download speed and even make it possible for you to seed to others or use it as a seedbox. I know it's a strange use case that brought me to use this for my Docker containers, but I am sure it will have its own benefits for other users, especially the ones who are self-hosting stuff and are behind the NAT of their ISPs.
However, I have discovered other use cases for this. Like I can directly expose a service with the same ports from the same machine. With the help of Macvlan, every container will have its own virtual LAN port, meaning it will have its own MAC Address and will act as a LAN port directly connected to my primary router.
To do this first you have to know your IPV6 Prefix and IPV4 subnet of the network.
In my case, let's assume that I have ipv6 prefix 2400:1a00:XXXX:XXXXX::/64
First, go to your server's terminal and create a network with the Macvlan driver in your Docker. To do this enter the command below
docker network create -d macvlan --subnet 192.168.1.0/24 \
--gateway 192.168.1.1 \
--subnet 2400:XXXX:XXXX:XXXXX::/64 \
--gateway 2400:XXXX:XXXX:XXXX::1 \
--ipv6 -o parent=eth0 dualmac -o macvlan_mode=bridge
Make the changes on the subnet and gateway of both IPv4 and IPv6 according to your own Network setup. You can also set it for IPv6 only if you like.
On the parent= , you have to enter the name of the main network interface. And right after that line, you can see that I have written dualmac. You can write whatever you like, it's the network's name so name it as per your preference.
Once that's done, you have created a network with Macvlan, now you can assign it your container.
First, check the network if it has been correctly configured or not. You can do that by entering docker network inspect <Your Network Name>. In my case it's dualmac.
Observe the Subnet and Gateway and make sure they are correct.
Now assign your container to the network using Docker Compose. In your docker-compose config file add these to assign it to the network you have created.
You can let the docker container dynamically get the IPs, but it often ends up with getting IPs that have been used already, so it's better that you assign them manually from your docker-compose config file.
networks:
ipv6net:
ipv6_address: 2400:XXXXX:XXXXX:XXXXX::4
ipv4_address: 192.168.1.4
networks:
ipv6net:
name: dualmac
external: true
Place them as shown in the screenshot below. You can name the networks on the config as you like, in my case, I have named it ipv6net . And in the name: dualmac , enter the name of the docker network you created previously. And that's all. Now start your container using the config file, and you should see the container getting IPs directly from your primary router.
In the screenshot below, you can see the torrent client directly communicating with the IPv6 peers.
If you do docker network inspect on your newly created network, while running the containers using it, you can also see the IPs and MAC being used for the container.
Note:
If you only want your docker container to get the public IPv6 and nothing else, then you can simply set the network mode to host. With that, you won’t have to depend on macvlan or the hefty, troublesome docker network configurations. The container will act as a network host device and will request your network's DHCP server for IP assignment. And of course, your container will get IPv6. But make sure you have IPv6 enabled in the main docker configuration.
