<?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 Route added automaticly ?? in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71769#M6524</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a strange issue regarding a ip route for a single host on my netapp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A route for a single host is added automaticliy with " Link# " as gateway. But it's not a good route. This host is not in the same subnet as the netapp.&lt;/P&gt;&lt;P&gt;Normaly, to join this host, the default gateway should work. Instead of this, this strange route appear automaticly.&lt;/P&gt;&lt;P&gt;If I delete it and then ping the remote host, this route appear another time. If I delete it and then add manually a good route to send packet to the default gateway, it's work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone now why this route come automaticly&lt;/P&gt;&lt;P&gt;The router separate the both subnet is a server free BSD based with two NICs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:24:50 GMT</pubDate>
    <dc:creator>vemery999</dc:creator>
    <dc:date>2025-06-05T06:24:50Z</dc:date>
    <item>
      <title>Route added automaticly ??</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71769#M6524</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a strange issue regarding a ip route for a single host on my netapp.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A route for a single host is added automaticliy with " Link# " as gateway. But it's not a good route. This host is not in the same subnet as the netapp.&lt;/P&gt;&lt;P&gt;Normaly, to join this host, the default gateway should work. Instead of this, this strange route appear automaticly.&lt;/P&gt;&lt;P&gt;If I delete it and then ping the remote host, this route appear another time. If I delete it and then add manually a good route to send packet to the default gateway, it's work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Someone now why this route come automaticly&lt;/P&gt;&lt;P&gt;The router separate the both subnet is a server free BSD based with two NICs&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:24:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71769#M6524</guid>
      <dc:creator>vemery999</dc:creator>
      <dc:date>2025-06-05T06:24:50Z</dc:date>
    </item>
    <item>
      <title>Re: Route added automaticly ??</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71772#M6525</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Does it still happen if you try to disable option ip.fastpath?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 19:49:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71772#M6525</guid>
      <dc:creator>aborzenkov</dc:creator>
      <dc:date>2012-06-18T19:49:17Z</dc:date>
    </item>
    <item>
      <title>Re: Route added automaticly ??</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71777#M6526</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is the system on any networks that utilize RIPv* and is routed on?&amp;nbsp; Per the manpage for routed:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;"Routed is a daemon invoked at boot time to manage the network routing tables.&amp;nbsp; It uses Routing&amp;nbsp; Information&amp;nbsp; Protocol,&amp;nbsp; RIPv1&amp;nbsp; (RFC 1058),&amp;nbsp; RIPv2&amp;nbsp; (RFC 1723),&amp;nbsp; and Internet Router Discovery Protocol (RFC 1256) to maintain the&amp;nbsp; kernel&amp;nbsp; routing&amp;nbsp; table.&amp;nbsp;&amp;nbsp; The&amp;nbsp; RIPv1 protocol is based on the reference BSD 4.3 daemon.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It listens on the udp socket for&amp;nbsp; the&amp;nbsp; route&amp;nbsp; service&amp;nbsp; for Routing&amp;nbsp; Information&amp;nbsp; Protocol&amp;nbsp; packets.&amp;nbsp; It also solicits multicast Router Discovery ICMP messages.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When started (or when a network interface is later&amp;nbsp; turned on),&amp;nbsp; routed&amp;nbsp; uses&amp;nbsp; an AF_ROUTE address family facility to find those directly connected interfaces&amp;nbsp; configured&amp;nbsp; into the&amp;nbsp; system and marked "up".&amp;nbsp; It adds necessary routes for the interfaces to the kernel routing&amp;nbsp; table.&amp;nbsp;&amp;nbsp; Soon&amp;nbsp; after being&amp;nbsp; first&amp;nbsp; started,&amp;nbsp; and provided there is at least one interface on which&amp;nbsp; RIP&amp;nbsp; has&amp;nbsp; not&amp;nbsp; been&amp;nbsp; disabled,&amp;nbsp; routed deletes&amp;nbsp; all&amp;nbsp; pre-existing&amp;nbsp; non-static&amp;nbsp; routes&amp;nbsp; in&amp;nbsp; kernel table.&amp;nbsp; Static routes in the kernel table are preserved."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could be a long shot but worth looking into real quick...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2012 19:44:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Route-added-automaticly/m-p/71777#M6526</guid>
      <dc:creator>mike_burris</dc:creator>
      <dc:date>2012-06-19T19:44:47Z</dc:date>
    </item>
  </channel>
</rss>

