I think this should be re-opened. The solution that is documented does not follow the spirit of hairpin NAT, which is that traffic on port N not actually destined to the inside target should not be redirected.

Of course, external services with the same port is not available
This is what you should expect from NAT rules (110)
Works exactly as configured

Have you confirmed that you can access an external service(i.e. in the 192.168.0.20/24 network) hosted on port 22, and it is not being redirected to 172.24.33.33:22 after applying the rules above?

Went with telegraf support instead

There will be no ZeroTier in VyOS due to its license
see https://www.zerotier.com/2019/10/30/on-the-gpl-to-bsl-transition/

Any movement on this? ZeroTier integration would be fantastic.

Please post at forum.vyos.io for support

decided to go with HAProxy

it seems no additional work needed for LibreNMS so i close this one

sorry, but their licensing model incompatible with what we do.

ZeroTier was added to the Ubiquiti EdgeRouter (which runs a vyatta fork) as a demo. Relevant to this thread:
https://blog.kruyt.org/zerotier-on-edgerouter-p2/

This is a support request,
please use forum.vyos.io for such request

Ok, closing as wontfix

Please test with latest rolling and not a custom build.

Or may be you could tell me where I can include this commands? Also I need to setup correct owners for /config/user-data/zabbix/ dir, there is zabbix-proxy DB...

how could I show it to you? Which version have you try to update? I think simple chown in update script could fix it!
Also i think it could be compare with changing of list of users and thous IDs:
Old system list:

can´t reproduce

Impossible to reproduce

Please open this one as I want to get help from experts.

This is a support request,
closing in favor of forum post
https://forum.vyos.io/t/bgp-communities-filtering/3969/2

I see the same issue, does this need tests ?

stop spamming

See T1283

we now reworking this in favor of a cloud-init backed system with ovf environment as configuration source
this now passing VMWare certification and will be available shortly

retest

Please retest with the latest rolling
if the problem still persists, reopen

can't reproduce
please try latest rolling and if the problem still persists
create new ticket with full config and env spec

no retest were done, rejecting

archiving

Hello
Please submit this on forum.vyos.io since it's a most likely configuration issue
provide complete config (you can strip public ips, but keep private)
Also can recommend using 1.2 as 1.1.x EOLed now

Can´t reproduce, works fine for me

you must use quotes
tshark -i eth1 -f 'host 10.217.10.254'

Current implementation of clustering requires rework, see T985

No plan to add this to the base image

this chain does not exist anymore in 1.2

no update

no plans for this in any near future

no manner to handle this efficiently at this time

not relevant anymore

not relevant anymore

Not relevant since we moved to FRR

dnsmasq dropped in 1.2
forwarder implementation was rewritten in python

Please retest on 1.2 and resubmit if issue exists

AFAICT frr has the correct computation.