hi all
i have installed mikrotik RouterOS in docker
everything working perfect
only i have problem with L2TPV3 IP
it using port 115 and protocol is L2TP
i have problem with forwarding port 115 in docker
because that port is not TCP or UDP,it’s L2TP
anyone can help me for forwarding that port in docker?
How you done the port forwarding? Paste the NAT configuration here
That’s a neat trick. How?
Usually it’s the other way around.
it using port 115
No, it’s using IP protocol 115. (Source.) Ports are a TCP or UDP abstraction, but you’re speaking of L2TPv3 over IP.
anyone can help me for forwarding that port in docker?
You could try switching the container to one of the more advanced networking modes, such as host mode. That gets you off-topic for this forum, though.
You can find a lot of images for that in https://hub.docker.com/search?q=routeros
If it’s using port 115 he can simply map that if I understand correctly.
No, he shouldn’t change to host mode at all, because if he does that he is gonna loss his access over his host machine cause on docker level for that container there are ports like 22 and etc which in host mode will interfere with host machine (which is docker installed on) ports.
I wasn’t so much interested in “how can I download that myself” as in “how can I make that myself?”
However, your link led me to this Dockerfile, which shows one way: wrap QEMU to boot RouterOS VDI images inside the container. I was hoping for something more clever, like unpacking native x86 RouterOS filesystems into the container’s rootfs, then arranging for that to boot at container start.
If it’s using port 115 he can simply map that if I understand correctly.
We aren’t talking about TCP/IP port 115, nor about UDP/IP port 115, but about IP protocol number 115. Line 3, second field. I believe the core of the OP’s complaint stems from the fact that there is no parallel to “docker create --port” for forwarding entire IP protocol numbers into the container, such as for consumption by a low-level networking OS like RouterOS.
Thus my suggestion to expose the naked container to the host’s network stack.
many thanks for your reply,so i should reading documents about docker host for doing it