Gateway setting in DHCP setup informs DHCP client (i.e. the far end) about IP address which it should use for communication outside its own subnet. The config you showed implies that 10.10.10.10 is client IP address and thus not very probable address of a gateway.thanks for the response. When you sayI'd say that gateway address in /ip dhcp-server network should be 10.10.10.1 ...
does that mean that the "gateway" address is always on the near end of the link in the separate subnet?
But then you know the topology of your networks so you shoukd know how devices in different betworks are supposed to communicate with each other.
Yes, I was talking about that. I suggest you to read the rest of firewall settings (both NAT and filters) to get an idea about how it all is supposed to work. I guess it'll help you understand the options better.I'm not clear on what you refer to when you sayDo you mean not to use "all ethernet" but to specify a specific single interface? That choice was made from the pull-down menu.I'd avoid using this ... AFAIK it's an interface-list (not interface)
In particular: even if "all ethernet" really did work as name implies (and, as I already wrote, I have my doubts about that), do you have any particular reason to exclude other interfaces (e.g. wifi interfaces)? It's fine not to set properties and if a property is not set, matcher will not check it ... so not setting in-interface means that in-interface won't be a deciding criteria when ROS decides whether a particular rule needs to be executed or not.
Statistics: Posted by mkx — Sat Mar 30, 2024 11:57 am