<p>Is it possible to have the log output for icecast read a variable from a header sent to the server? Currently I am setting up an icecast server in Kuberenetes and I'm trying to get source IP preservation onto the stream for analyzing log data. However even with the necessary steps on kubernetes side I am not seeing the logs for icecast have source IP. How ever I was able to sniff incoming request and I am seeing:</p>

<pre><code>X-Real-IP: 142.x.x.x
X-Forwarded-For: 142.x.x.x
</code></pre>

<p>As headers coming into the server. </p>

<p>Is it possible to get these into the logs somehow?</p>

Pablo Marti Cordero
<p>Not at the moment.</p>

<p>We plan to support reverse proxying in release 2.5.</p>

<p>Our general recommendation at the moment is to <em>not</em> reverse proxy Icecast due to many possible problems beyond just losing the originating IP address.</p>

<p>Just expose the Icecast ports directly to the Internet, e.g. through port forwarding.</p>

<p><strong>edit:</strong> <a href="https://kubernetes.io/docs/concepts/services-networking/service/#multi-port-services" rel="nofollow noreferrer">You can just declare <code>protocol: TCP</code> ports for your service.</a> also "Proxy-mode: iptables"</p>
