The parameters local and remote-netmask are set according to the -ifconfig directive which you want to execute on the client machine to configure the remote end of the tunnel. Push virtual IP endpoints for client tunnel, overriding the -ifconfig-pool dynamic allocation. If you want guaranteed assignment, use -ifconfig-push They do not guarantee that the given common name will always receive the given IP address. Note that the entries in this file are treated by OpenVPN as suggestions only, based on past associations between a common name and IP address. This is useful if you would like to treat file as a configuration file. If seconds = 0, file will be treated as read-only. Maintaining a long-term association is good for clients because it allows them to effectively use the -persist-tun option.įile is a comma-delimited ASCII file, formatted as. The goal of this option is to provide a long-term association between clients (denoted by their common name) and the virtual IP address assigned to them from the ifconfig-pool. Persist/unpersist ifconfig-pool data to file, at seconds intervals (default=600), as well as on program startup and shutdown. I was thinking the prefix would be "Network:" so it would display as "Network:br0". In 6.4 rc2 rc4, the editor always loads in Basic View. In 6.3.5, if I switch the docker editor to Advanced View, it "sticks" until I change it back. I never bothered to report it as it isn't really doing any harm.ġ. Regarding 3 it has always been the case that if you change from bridge to host the ports becomes variables in the run command. Thanks for adding that smdion! It should have been on my list I was thinking the prefix would be "Network:" so it would display as "Network:br0"Ħ. If the network is more complex than a /24, the user should know what they are doing so just leave the whole thing freeform.ĥ. Basically just trying to make things easier/obvious for the user.
I was thinking that if the network uses a standard /24 subnet it could display the first three octets and only the fourth would be editable. Unfortunately both the host and container ports are now 8182 so the docker doesn't work.Ĥ. Change back to bridge mode and now it sends "-p 8182:8182/tcp". Change port from 8181 to 8182 (I was suggesting this option could be disabled or even hidden when in host mode) and it sends "TCP_PORT_8182"="8182". Change to host mode and the run command sends "TCP_PORT_8181"="8181". Stay in bridge mode, change "Host Port 1" from 8181 to to 8182 and the run command sends "-p 8182:8181/tcp" as I would expect. A little bummed, was hoping for more of "bridge mode on a different ip". View assigned IP addresses is doable, put it on my listĢ. not sure what to prefix, still open for ideasĦ.
nice thought but we loose flexibility, subnet may be different size or do you mean switch view when /24?ĥ. this is already in place, do you have an example?Ĥ. macvlan works similar to host mode, but allows individual IP addresses for the containersģ. Maybe a regression error, need to test and verifyĢ. Ability to view assigned IP addresses of dockers from the dockerMan page.ġ. Perhaps we could add a prefix to the display such as "Network: br0"?Ħ. In the "Network Type" dropdown (Bridge/Host/None/br0), br0 is rather unfriendly.
Does this imply that containers on br0 have full access to the network similar to "Host" mode?Ī potential enhancement idea would be to prevent users from changing a port setting when the Network Type doesn't allow it.Īnother idea would be when you are working a standard /24 subnet, only give users the option to input the final octet of an ip address rather than allowing/making them input the whole thing. And you also can't assign multiple dockers to the same IP. I noticed that when you select a Network Type of "br0", changing the port has no effect. In 6.4 rc2, the editor always loads in Basic View. I've been playing with this for a few days and have some questions / ideas: I really like the new feature to assign IP addresses to individual dockers.