<?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: network info reg in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057424#M87375</link>
    <description>SEP came up with one solution, the other is to use NAT (Network Address Translation).&lt;BR /&gt;&lt;BR /&gt;Whilst IPChains can do limited NAT, I'd suggest using IPTables, as it is far more controllable.&lt;BR /&gt;&lt;BR /&gt;We will however require more descriptive details of what you are trying to do (i.e. trying to set up a gateway to another network, or something else etc.) so we can give you more accurate details.&lt;BR /&gt;&lt;BR /&gt;Things like the distribution and it's version you are using will help us also.</description>
    <pubDate>Wed, 27 Aug 2003 23:41:24 GMT</pubDate>
    <dc:creator>Stuart Browne</dc:creator>
    <dc:date>2003-08-27T23:41:24Z</dc:date>
    <item>
      <title>network info reg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057422#M87373</link>
      <description>Hi, i have two networks with 2 linux servers in each, ex: &lt;BR /&gt;&lt;BR /&gt;10.51.6.x and    10.51.16.x&lt;BR /&gt;&lt;BR /&gt;i can ping and telnet everything works fine, now to access 10.51.6.141(linux server) from 10.51.16.141 i want to use a different ip like 10.232.114.141(dont ask me why).  when i use this (10.232.114.141) it should map to 10.51.6.141 and send the packets, and get the response back. Is there any way this can be done. i heard that ip chains can be used. &lt;BR /&gt;&lt;BR /&gt;Please suggest&lt;BR /&gt;&lt;BR /&gt;i dont to create any more networks. &lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;chakri</description>
      <pubDate>Wed, 27 Aug 2003 06:24:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057422#M87373</guid>
      <dc:creator>Chakravarthi</dc:creator>
      <dc:date>2003-08-27T06:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: network info reg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057423#M87374</link>
      <description>If you are going to do this with a firewall use iptables.  ipchains is on the way out.&lt;BR /&gt;&lt;BR /&gt;This can be done with ifconfig&lt;BR /&gt;&lt;BR /&gt;ifconfig eth0:1 10.231.114.141 mask 255.255.255.0 up&lt;BR /&gt;&lt;BR /&gt;If thats creating a network I can't help that.  This assumes that eth0 is 10.51.6.141&lt;BR /&gt;&lt;BR /&gt;To make it permanent, /etc/sysconfig/network-scripts&lt;BR /&gt;&lt;BR /&gt;You also might want to take into account if sendmail.mc/sendmail.cf has any ip references it might become confused and fail.  Just have to make sure any network changes are thoroughly tested. sendmail won't bite you until you cycle the daemon.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Wed, 27 Aug 2003 06:56:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057423#M87374</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-08-27T06:56:07Z</dc:date>
    </item>
    <item>
      <title>Re: network info reg</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057424#M87375</link>
      <description>SEP came up with one solution, the other is to use NAT (Network Address Translation).&lt;BR /&gt;&lt;BR /&gt;Whilst IPChains can do limited NAT, I'd suggest using IPTables, as it is far more controllable.&lt;BR /&gt;&lt;BR /&gt;We will however require more descriptive details of what you are trying to do (i.e. trying to set up a gateway to another network, or something else etc.) so we can give you more accurate details.&lt;BR /&gt;&lt;BR /&gt;Things like the distribution and it's version you are using will help us also.</description>
      <pubDate>Wed, 27 Aug 2003 23:41:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-info-reg/m-p/3057424#M87375</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2003-08-27T23:41:24Z</dc:date>
    </item>
  </channel>
</rss>

