<?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: Static routes in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612682#M85087</link>
    <description>You can selectively control the network interfaces using&lt;BR /&gt;&lt;BR /&gt;ifup ifname&lt;BR /&gt;ifdown ifname&lt;BR /&gt;&lt;BR /&gt;And i think that you need to configure the routes for every network interface configuration file. And according to the ifup script, the file should be named ifcfg-vlan* and probably, route-vlan*.</description>
    <pubDate>Fri, 26 Aug 2005 07:24:20 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2005-08-26T07:24:20Z</dc:date>
    <item>
      <title>Static routes</title>
      <link>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612679#M85084</link>
      <description>Hi, I´ve a Blade BL20p with RHEL3 Update 3 and multiple NICs. When I disconnect and connect the cable for one NIC the associated routes to this NIC disappears but when the connection is restored the routes never appears.&lt;BR /&gt;&lt;BR /&gt;It´s true that I can try to put the file "/etc/sysconfig/network-scripts/route-eth0" to restore the routes for this interface. But when I´ve vlans for this interface, I need to put mulitple files like  "/etc/sysconfig/network-scripts/route-eth0.vlanid"?&lt;BR /&gt;</description>
      <pubDate>Fri, 26 Aug 2005 06:10:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612679#M85084</guid>
      <dc:creator>JBR</dc:creator>
      <dc:date>2005-08-26T06:10:13Z</dc:date>
    </item>
    <item>
      <title>Re: Static routes</title>
      <link>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612680#M85085</link>
      <description>If you restart the network:&lt;BR /&gt;&lt;BR /&gt;service network restart&lt;BR /&gt;&lt;BR /&gt;The default route configuration in /etc/sysconfig/network-scripts &lt;BR /&gt;&lt;BR /&gt;should re-establish routes.&lt;BR /&gt;&lt;BR /&gt;I'm not sure abut the route-eth0.vlanid trick, but you should try it on a test box. It really can't hurt to give it a try on a non-production server.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 26 Aug 2005 06:13:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612680#M85085</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2005-08-26T06:13:15Z</dc:date>
    </item>
    <item>
      <title>Re: Static routes</title>
      <link>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612681#M85086</link>
      <description>Thanks Steven, but if you try to restart the network service, Itis possible that the others NICs lose their links? or not?&lt;BR /&gt;&lt;BR /&gt;My problem is that rarely only one NIC at time lose his link, and the associated routes for this interface disappear. I only need to restore the routes for this interface, vlans included.... &lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Fri, 26 Aug 2005 06:23:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612681#M85086</guid>
      <dc:creator>JBR</dc:creator>
      <dc:date>2005-08-26T06:23:39Z</dc:date>
    </item>
    <item>
      <title>Re: Static routes</title>
      <link>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612682#M85087</link>
      <description>You can selectively control the network interfaces using&lt;BR /&gt;&lt;BR /&gt;ifup ifname&lt;BR /&gt;ifdown ifname&lt;BR /&gt;&lt;BR /&gt;And i think that you need to configure the routes for every network interface configuration file. And according to the ifup script, the file should be named ifcfg-vlan* and probably, route-vlan*.</description>
      <pubDate>Fri, 26 Aug 2005 07:24:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612682#M85087</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-08-26T07:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Static routes</title>
      <link>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612683#M85088</link>
      <description>Interface specific static routes are searched in /etc/sysconfig/network-scripts/route-${INTERFACE}. There is also a&lt;BR /&gt;global file /etc/sysconfig/static-routes. This file is used for non interface-specific static-routes.&lt;BR /&gt;&lt;BR /&gt;Example for a static route defined in /etc/sysconfig/network-scripts/route-${INTERFACE}:&lt;BR /&gt;&lt;BR /&gt;123.4.5.6/25 via 123.8.7.8&lt;BR /&gt;&lt;BR /&gt;I use "service network restart" very often and never had problems. You can even issue this over a ssh connection and keep your connection, although it might be smart to have a console connection handy just in case.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Ross&lt;BR /&gt;</description>
      <pubDate>Sat, 27 Aug 2005 20:12:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/static-routes/m-p/3612683#M85088</guid>
      <dc:creator>Ross Minkov</dc:creator>
      <dc:date>2005-08-27T20:12:34Z</dc:date>
    </item>
  </channel>
</rss>

