<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Does Universal Forwarded supports Server Name Indication (SNI)? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Does-Universal-Forwarded-supports-Server-Name-Indication-SNI/m-p/482932#M82737</link>
    <description>&lt;P&gt;Hi there folks,&lt;/P&gt;

&lt;P&gt;I would like to ask if Universal Forwarder can support Server Name Indication (SNI)? That is extension of TLS protocol which can be used by nginx to deploy SNI-based-routing from UF`s to multiple hosts.&lt;/P&gt;

&lt;P&gt;INFO:&lt;BR /&gt;
- We have many clients with on-premise machines/laptops with Universal Forwarders sending traffic to our AWS Splunk Instances (Indexers). Our AWS Instances doesn&lt;CODE&gt;t have public IPv4 addresses and we would like to deploy single point of contact (nginx) with public IPv4 address for all TCP UF&lt;/CODE&gt;s traffic which then differentiate by destination.&lt;/P&gt;

&lt;P&gt;UF -&amp;gt; nginx with public IPv4 (SNI based-routing) -&amp;gt; AWS Target Indexer &lt;/P&gt;

&lt;P&gt;Pre-requisites:&lt;BR /&gt;
We need UF with enabled SSL - this is completed.&lt;BR /&gt;
We need UF with enabled SNI (Its needed to differentiate destination hosts)&lt;/P&gt;

&lt;P&gt;e.g. UF`s will send traffic to:&lt;BR /&gt;
client1.mydomain.com&lt;BR /&gt;
client2.mydomain.com&lt;/P&gt;

&lt;P&gt;Nginx will then route the traffic to destination.&lt;/P&gt;

&lt;P&gt;Have someone tried similar approach before? Also if you could give other suggestion for our solution will be much appreciated!&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;

&lt;P&gt;Kind Regards,&lt;BR /&gt;
Tihomir Stoyanov&lt;/P&gt;</description>
    <pubDate>Tue, 14 Jan 2020 13:43:19 GMT</pubDate>
    <dc:creator>tihomirstoyanov</dc:creator>
    <dc:date>2020-01-14T13:43:19Z</dc:date>
    <item>
      <title>Does Universal Forwarded supports Server Name Indication (SNI)?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Universal-Forwarded-supports-Server-Name-Indication-SNI/m-p/482932#M82737</link>
      <description>&lt;P&gt;Hi there folks,&lt;/P&gt;

&lt;P&gt;I would like to ask if Universal Forwarder can support Server Name Indication (SNI)? That is extension of TLS protocol which can be used by nginx to deploy SNI-based-routing from UF`s to multiple hosts.&lt;/P&gt;

&lt;P&gt;INFO:&lt;BR /&gt;
- We have many clients with on-premise machines/laptops with Universal Forwarders sending traffic to our AWS Splunk Instances (Indexers). Our AWS Instances doesn&lt;CODE&gt;t have public IPv4 addresses and we would like to deploy single point of contact (nginx) with public IPv4 address for all TCP UF&lt;/CODE&gt;s traffic which then differentiate by destination.&lt;/P&gt;

&lt;P&gt;UF -&amp;gt; nginx with public IPv4 (SNI based-routing) -&amp;gt; AWS Target Indexer &lt;/P&gt;

&lt;P&gt;Pre-requisites:&lt;BR /&gt;
We need UF with enabled SSL - this is completed.&lt;BR /&gt;
We need UF with enabled SNI (Its needed to differentiate destination hosts)&lt;/P&gt;

&lt;P&gt;e.g. UF`s will send traffic to:&lt;BR /&gt;
client1.mydomain.com&lt;BR /&gt;
client2.mydomain.com&lt;/P&gt;

&lt;P&gt;Nginx will then route the traffic to destination.&lt;/P&gt;

&lt;P&gt;Have someone tried similar approach before? Also if you could give other suggestion for our solution will be much appreciated!&lt;/P&gt;

&lt;P&gt;Thank you.&lt;/P&gt;

&lt;P&gt;Kind Regards,&lt;BR /&gt;
Tihomir Stoyanov&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2020 13:43:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Universal-Forwarded-supports-Server-Name-Indication-SNI/m-p/482932#M82737</guid>
      <dc:creator>tihomirstoyanov</dc:creator>
      <dc:date>2020-01-14T13:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: Does Universal Forwarded supports Server Name Indication (SNI)?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Does-Universal-Forwarded-supports-Server-Name-Indication-SNI/m-p/482933#M82738</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;Got an update from our seniors --&amp;gt; Universal Forwarder doesn`t support SNI at the moment.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Tihomir Stoyanov&lt;/P&gt;</description>
      <pubDate>Thu, 13 Feb 2020 12:45:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Does-Universal-Forwarded-supports-Server-Name-Indication-SNI/m-p/482933#M82738</guid>
      <dc:creator>tihomirvstoyano</dc:creator>
      <dc:date>2020-02-13T12:45:42Z</dc:date>
    </item>
  </channel>
</rss>

