<?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 routing basic explanation in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419907#M86502</link>
    <description>Hi all,&lt;BR /&gt;bellow is a part o routing table&lt;BR /&gt;&lt;BR /&gt;Destination Gateway  Genmask           Iface&lt;BR /&gt;10.0.0.0    0.0.0.0  255.255.255.0     eth0&lt;BR /&gt;192.168.1.0 0.0.0.0  255.255.255.0     eth1&lt;BR /&gt;0.0.0.0     10.0.0.5 0.0.0.0        eth0&lt;BR /&gt;&lt;BR /&gt;my question is concerning to qateway 0.0.0.0,&lt;BR /&gt;what does 0.0.0.0 mean ? There is no gateway ?&lt;BR /&gt;&lt;BR /&gt;Or is there relation between 0.0.0.0 gateway and 0.0.0.0 destination ? (in sence all packets to 10.0.0.0 network go via 0.0.0.0 gw so the destination is also 0.0.0.0)&lt;BR /&gt;&lt;BR /&gt;many thanks &lt;BR /&gt;&lt;BR /&gt;M.</description>
    <pubDate>Thu, 11 Nov 2004 00:21:46 GMT</pubDate>
    <dc:creator>Mario_106</dc:creator>
    <dc:date>2004-11-11T00:21:46Z</dc:date>
    <item>
      <title>routing basic explanation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419907#M86502</link>
      <description>Hi all,&lt;BR /&gt;bellow is a part o routing table&lt;BR /&gt;&lt;BR /&gt;Destination Gateway  Genmask           Iface&lt;BR /&gt;10.0.0.0    0.0.0.0  255.255.255.0     eth0&lt;BR /&gt;192.168.1.0 0.0.0.0  255.255.255.0     eth1&lt;BR /&gt;0.0.0.0     10.0.0.5 0.0.0.0        eth0&lt;BR /&gt;&lt;BR /&gt;my question is concerning to qateway 0.0.0.0,&lt;BR /&gt;what does 0.0.0.0 mean ? There is no gateway ?&lt;BR /&gt;&lt;BR /&gt;Or is there relation between 0.0.0.0 gateway and 0.0.0.0 destination ? (in sence all packets to 10.0.0.0 network go via 0.0.0.0 gw so the destination is also 0.0.0.0)&lt;BR /&gt;&lt;BR /&gt;many thanks &lt;BR /&gt;&lt;BR /&gt;M.</description>
      <pubDate>Thu, 11 Nov 2004 00:21:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419907#M86502</guid>
      <dc:creator>Mario_106</dc:creator>
      <dc:date>2004-11-11T00:21:46Z</dc:date>
    </item>
    <item>
      <title>Re: routing basic explanation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419908#M86503</link>
      <description>"Destination 0.0.0.0" line speaks about default gateway - it means, all destinations which doesn't covered by other rules.&lt;BR /&gt;&lt;BR /&gt;and "gateway 0.0.0.0" means - this box has "direct connection" to this network - in other words, there is ethX in such network.</description>
      <pubDate>Thu, 11 Nov 2004 01:52:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419908#M86503</guid>
      <dc:creator>Vitaly Karasik_1</dc:creator>
      <dc:date>2004-11-11T01:52:13Z</dc:date>
    </item>
    <item>
      <title>Re: routing basic explanation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419909#M86504</link>
      <description>thanksand default GW is a router with interface to my network that handle all packets going through ?does it follow that all packets which are not going through default gw are packets to my network and are handled via ARP many thanks M.</description>
      <pubDate>Thu, 11 Nov 2004 14:42:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419909#M86504</guid>
      <dc:creator>Mario_106</dc:creator>
      <dc:date>2004-11-11T14:42:21Z</dc:date>
    </item>
    <item>
      <title>Re: routing basic explanation</title>
      <link>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419910#M86505</link>
      <description>Ok, a bit of a network/netmask lesson.&lt;BR /&gt;&lt;BR /&gt;The 'destination' is supposed to be the stub of a network address of which to match against the destination address of IP packets that pass through the routing table.&lt;BR /&gt;&lt;BR /&gt;Using the bit-mask of the 'genmask' value, it takes a given path if there is a match.&lt;BR /&gt;&lt;BR /&gt;0.0.0.0/0.0.0.0 works as a default route for the simple reason that *ALL* destination addresses match it.&lt;BR /&gt;&lt;BR /&gt;As packets filter through from the top of the routing table, as they match they get sent down different paths.  If all other routes didn't match, the default is taken.&lt;BR /&gt;&lt;BR /&gt;So using your routing table lets set up an example:&lt;BR /&gt;&lt;BR /&gt;Destination address: 192.168.1.32&lt;BR /&gt;&lt;BR /&gt;Packet hits the first route.  10.0.0.0/255.255.255.0.  This is not a match.&lt;BR /&gt;&lt;BR /&gt;Packet hits the second route.  192.168.1.0/255.255.255.0.  This is a match (the first 3 bytes fully match).  The routing table says to send it via the interface 'eth1' (as there is no gateway, it just sends it to the wire).  At this point, ARP tables etc. are used.&lt;BR /&gt;&lt;BR /&gt;Packet never hits third route.&lt;BR /&gt;&lt;BR /&gt;Destination address: 10.3.1.9&lt;BR /&gt;&lt;BR /&gt;Packet hits first route.  As the genmask is '255.255.255.0', the first 3 bytes have to match.  Packet does not match this rule.&lt;BR /&gt;&lt;BR /&gt;Packet hits second route.  Doesn't match.&lt;BR /&gt;&lt;BR /&gt;Packet hits thrid route.  As this is the default route, it forwards the packet to the machine '10.0.0.5' via eth0.&lt;BR /&gt;&lt;BR /&gt;This making sense? :)</description>
      <pubDate>Thu, 11 Nov 2004 17:38:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/routing-basic-explanation/m-p/3419910#M86505</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2004-11-11T17:38:43Z</dc:date>
    </item>
  </channel>
</rss>

