https://community.splunk.com/t5/Getting-Data-In/Is-any-valid-in-a-networking-input/m-p/398735#M71082 <P>Hi, </P> <P>In an inputs.conf, is <CODE>[any://1111]</CODE> (for example) valid in a network input to use port 1111 for both TCP and UDP? Or do you need two seperate TCP and UDP stanzas w/ port 1111 specified?</P> Wed, 27 Feb 2019 00:18:01 GMT russell120 2019-02-27T00:18:01Z https://community.splunk.com/t5/Getting-Data-In/Is-any-valid-in-a-networking-input/m-p/398735#M71082 <P>Hi, </P> <P>In an inputs.conf, is <CODE>[any://1111]</CODE> (for example) valid in a network input to use port 1111 for both TCP and UDP? Or do you need two seperate TCP and UDP stanzas w/ port 1111 specified?</P> Wed, 27 Feb 2019 00:18:01 GMT https://community.splunk.com/t5/Getting-Data-In/Is-any-valid-in-a-networking-input/m-p/398735#M71082 russell120 2019-02-27T00:18:01Z https://community.splunk.com/t5/Getting-Data-In/Is-any-valid-in-a-networking-input/m-p/398736#M71083 <P>Hi russell120,</P> <P>according to the docs <A href="https://docs.splunk.com/Documentation/Splunk/latest/admin/Inputsconf#TCP:">https://docs.splunk.com/Documentation/Splunk/latest/admin/Inputsconf#TCP:</A> there is only <CODE>[tcp: ]</CODE> or <CODE>[udp: ]</CODE> listed as valid options. That means you need to create two seperate stanzas.</P> <P>Hope this helps ...</P> <P>cheers, MuS</P> Wed, 27 Feb 2019 00:38:24 GMT https://community.splunk.com/t5/Getting-Data-In/Is-any-valid-in-a-networking-input/m-p/398736#M71083 MuS 2019-02-27T00:38:24Z