<?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 Re: Port Redirecting using xinetd. in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839643#M88879</link>
    <description>Hi,&lt;BR /&gt;It is not possible to see real IP address of the visitor from apache logs as the xinetd acts as a proxy ( in other words port address&lt;BR /&gt;translation or NAT overload ).&lt;BR /&gt;&lt;BR /&gt;Therefore the packets originationg from xinetd&lt;BR /&gt;server will have source IP of xinetd server and&lt;BR /&gt;destination IP of apache server. Now apache server will send the content to the xinetd server . xinetd server will take care of forwarding the content to the visitor. ( stateful port forwarding)&lt;BR /&gt;&lt;BR /&gt;Only one solution to overcome this is to use xinetd logging option.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;service web &lt;BR /&gt;{ &lt;BR /&gt;port = 80 &lt;BR /&gt;log_type        = FILE /var/log/webaccess.log&lt;BR /&gt;log_on_success  = PID HOST EXIT&lt;BR /&gt;bind = 212.26.219.29 &lt;BR /&gt;socket_type = stream &lt;BR /&gt;protocol = tcp &lt;BR /&gt;user = root &lt;BR /&gt;redirect = 192.168.1.31 80 &lt;BR /&gt;type = UNLISTED &lt;BR /&gt;wait = no &lt;BR /&gt;} &lt;BR /&gt;&lt;BR /&gt;#touch /var/log/webaccess.log &lt;BR /&gt;&lt;BR /&gt;Restart xinetd daemon&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;U.SivaKumar&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
    <pubDate>Wed, 06 Nov 2002 08:06:44 GMT</pubDate>
    <dc:creator>U.SivaKumar_2</dc:creator>
    <dc:date>2002-11-06T08:06:44Z</dc:date>
    <item>
      <title>Port Redirecting using xinetd.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839642#M88878</link>
      <description>Hi all,&lt;BR /&gt;&lt;BR /&gt;I am using xinetd to redirect incomming requests on port 80 from one of my IP's (on a redhat box) to be redirected to a machine inside the intranet. So far so good.. the other machine (a webserver from a customer running apache). The problem is that the logging of the apache server only sees the 1st machine as 'source-ip', meaning web-traffic statistics are incomplete as they only show the firewall machine. Is there anyway (with xinetd or other way) to have the webserver machine see the REAL ip from the visitor?&lt;BR /&gt;&lt;BR /&gt;The entry for xinetd used is:&lt;BR /&gt;&lt;BR /&gt;service web&lt;BR /&gt;{&lt;BR /&gt; port = 80&lt;BR /&gt; bind = 212.26.219.29&lt;BR /&gt; socket_type = stream&lt;BR /&gt; protocol = tcp&lt;BR /&gt; user = root&lt;BR /&gt; redirect = 192.168.1.31 80&lt;BR /&gt; type = UNLISTED&lt;BR /&gt; wait = no&lt;BR /&gt;}&lt;BR /&gt;&lt;BR /&gt;hardware setup:&lt;BR /&gt;&lt;BR /&gt;machine 1 (internet connection):&lt;BR /&gt;eth0: 217.8.98.137 (internet)&lt;BR /&gt;eth1: 192.168.1.30 (internal)&lt;BR /&gt;eth2: 212.26.219.29 (internet, used for redirection)&lt;BR /&gt;&lt;BR /&gt;machine 2 (just internal network)&lt;BR /&gt;eth0: 192.168.1.31&lt;BR /&gt;&lt;BR /&gt;Thanks in advance...&lt;BR /&gt;-NvR</description>
      <pubDate>Wed, 06 Nov 2002 06:50:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839642#M88878</guid>
      <dc:creator>Nico van Royen</dc:creator>
      <dc:date>2002-11-06T06:50:44Z</dc:date>
    </item>
    <item>
      <title>Re: Port Redirecting using xinetd.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839643#M88879</link>
      <description>Hi,&lt;BR /&gt;It is not possible to see real IP address of the visitor from apache logs as the xinetd acts as a proxy ( in other words port address&lt;BR /&gt;translation or NAT overload ).&lt;BR /&gt;&lt;BR /&gt;Therefore the packets originationg from xinetd&lt;BR /&gt;server will have source IP of xinetd server and&lt;BR /&gt;destination IP of apache server. Now apache server will send the content to the xinetd server . xinetd server will take care of forwarding the content to the visitor. ( stateful port forwarding)&lt;BR /&gt;&lt;BR /&gt;Only one solution to overcome this is to use xinetd logging option.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;service web &lt;BR /&gt;{ &lt;BR /&gt;port = 80 &lt;BR /&gt;log_type        = FILE /var/log/webaccess.log&lt;BR /&gt;log_on_success  = PID HOST EXIT&lt;BR /&gt;bind = 212.26.219.29 &lt;BR /&gt;socket_type = stream &lt;BR /&gt;protocol = tcp &lt;BR /&gt;user = root &lt;BR /&gt;redirect = 192.168.1.31 80 &lt;BR /&gt;type = UNLISTED &lt;BR /&gt;wait = no &lt;BR /&gt;} &lt;BR /&gt;&lt;BR /&gt;#touch /var/log/webaccess.log &lt;BR /&gt;&lt;BR /&gt;Restart xinetd daemon&lt;BR /&gt;&lt;BR /&gt;regards,&lt;BR /&gt;U.SivaKumar&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Nov 2002 08:06:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839643#M88879</guid>
      <dc:creator>U.SivaKumar_2</dc:creator>
      <dc:date>2002-11-06T08:06:44Z</dc:date>
    </item>
    <item>
      <title>Re: Port Redirecting using xinetd.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839644#M88880</link>
      <description>This will log all visitors that browse pages on the webserver but as web-stats it can't be used. I guess we have to live with it.&lt;BR /&gt;Thanks anyway for the reaction.&lt;BR /&gt;&lt;BR /&gt;- NvR</description>
      <pubDate>Thu, 07 Nov 2002 08:46:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839644#M88880</guid>
      <dc:creator>Nico van Royen</dc:creator>
      <dc:date>2002-11-07T08:46:42Z</dc:date>
    </item>
    <item>
      <title>Re: Port Redirecting using xinetd.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839645#M88881</link>
      <description>Look at putting Apache on the machine you are forwarding from and using its proxy services to the machine on the  intranet.  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 07 Nov 2002 16:25:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839645#M88881</guid>
      <dc:creator>Bill Thorsteinson</dc:creator>
      <dc:date>2002-11-07T16:25:06Z</dc:date>
    </item>
    <item>
      <title>Re: Port Redirecting using xinetd.</title>
      <link>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839646#M88882</link>
      <description>I agree with using Apache to proxy being an option, but unless you have need to run apache locally (which it doesn't sound like you do) I'd suggest setting up squid to handle this for you.</description>
      <pubDate>Wed, 13 Nov 2002 21:56:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/port-redirecting-using-xinetd/m-p/2839646#M88882</guid>
      <dc:creator>Mark Bainter</dc:creator>
      <dc:date>2002-11-13T21:56:08Z</dc:date>
    </item>
  </channel>
</rss>

