Using 1.2-rolling-201908171107 I configured:
set service dns forwarding domain example.com server '172.16.10.1' set service dns forwarding listen-address '172.18.201.10' set service dns forwarding name-server '1.1.1.1'
Using 1.2-rolling-201908171107 I configured:
set service dns forwarding domain example.com server '172.16.10.1' set service dns forwarding listen-address '172.18.201.10' set service dns forwarding name-server '1.1.1.1'
This error won't be fixed as the new Python/XML implementation of OpenVPN has been merged into current and will appear in the next rolling release.
This is actually invalid. There is no way with the current CLI design to specify the local address node with an optional subnet-mask leaf node.
Why not use curl which is inside the image?
Okay. Please test with latest rolling so we can possibly backport this to crux
I have no experience with Q-in-Q but does it even make sense to apply a firewall to the outer side of a Q-in-Q link? I understand to apply a firewall to the vif-c interface inside vif-s (as this can be trated as any regular vlan interface) but a firewall on the encapsulated interface?
@noitcennok stop polluting non relevant threads and stick to your original forum post.
@Dmity stripping is done here: https://github.com/vyos/vyatta-op/blob/current/scripts/vyos-strip-config.pl
Documentation updated in equueleus branch https://github.com/vyos/vyos-documentation/commit/eaa491df6f41fc175aa06618310c91087ecc8791