I'm not sure if you've fully read what I've explained, but this is a regular GRE (IPv4 over IPv6) Tunnel configured in VYOS and in the Huawei Routers. The communication doesn't works in this specific case. If we do VYOS to VYOS then everything is alright. But VYOS to Huawei is not working at all.

please , read the guidelines on this post . it doesn't see a bug if not a support task:

PR: https://github.com/vyos/vyos-1x/pull/3347

It is not a bug with the VyOS itself.
You don't need to create the task on Phabricator
Feel free to create a PR without the task https://github.com/vyos/vyos-documentation/tree/equuleus

Personally I dont think its a good idea to be able to use VyOS as a jumphost towards victims of scanning.

ok, i'll change a port list and nmap scenario

I'm not sure that a list of ports will be helpful in this way.
From time to time, we need to scan specific ports.
What about

force scan-port-host <x.x.x.x> proto <tcp|udp> port '8080-8081,9200'
force port--discovery-host <x.x.x.x> proto <tcp|udp> port '8080'
force port-scan host <x.x.x.x> proto <tcp|udp> port '8080'

And use native nmap binaries (as python3 nmap module is not installed by default)
Also, it has XML format if you want a custom table:

sudo nmap -oX - 127.0.0.1

@sever what do you think about it?

PR: https://github.com/vyos/vyos-1x/pull/3111

In T6108#179246, @Viacheslav wrote:

There is no 1.3.7 version ;)

There is no 1.3.7 version ;)

The issue persists in 1.3.4 too from what I have tested.

1.3.3 and rolling from 2020?

I can reproduce this on VyOS 1.4.0-rc3. It also appears that IPv6 addresses are only garbled on subinterfaces.

PR for 1.4 https://github.com/vyos/vyos-1x/pull/2810

PR for 1.5 https://github.com/vyos/vyos-1x/pull/2809