Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • and there is no port restrictions for incoming packets ? Commented Apr 16, 2018 at 17:49
  • @Bharat I should have specified that all traffic must come in and out of either port 80 or 443 on host1, thanks for pointing that out. I'll update the question to state that Commented Apr 16, 2018 at 18:29
  • Have you tried echo 1 > /proc/sys/net/ipv4/ip_forward? That will enable routing in the kernel. Commented Apr 16, 2018 at 18:36
  • @dogoncouch Just checked that file, kernel routing is enabled on host1. Do you know how to modify the rules to change the packet's destination port to 5015 after it leaves 443? Commented Apr 16, 2018 at 18:53
  • 1
    @Hans-MartinMosner I appreciate your advice, I'll specify and say that this is to ship application metadata using Filebeat (host1) to a hosted ELK stack on Logz.io (host2) under the network restrictions (which are a bureaucratic hassle to get altered). And of course, the module will only be deployed if all legal contracts and parameters were agreed and signed off on beforehand by all parties. Commented Apr 17, 2018 at 6:10