<?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: &amp;quot;ifconfig down&amp;quot; keeping the link state in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793900#M81345</link>
    <description>In Linux, you can configure a network interface UP without assigning an IP address to it. This stops the TCP/IP driver stack from using the interface, but the physical link will still be active and low-level access (e.g. tcpdump) is possible.&lt;BR /&gt;&lt;BR /&gt;If the interface is DOWN, you can switch it UP without assigning an IP address with a simple command:&lt;BR /&gt;&lt;BR /&gt;ifconfig &lt;ETHX&gt; up&lt;BR /&gt;&lt;BR /&gt;To remove an already-assigned IP address, you can either reset the IP of the interface to 0.0.0.0:&lt;BR /&gt;&lt;BR /&gt;ifconfig &lt;ETHX&gt; 0.0.0.0&lt;BR /&gt;&lt;BR /&gt;Or you can use "ip addr del &lt;ADDRESS&gt; dev &lt;ETHX&gt;".&lt;BR /&gt;&lt;BR /&gt;The state "UP without an IP address" would be the closest equivalent of HP-UX state "plumbed but not configured".&lt;BR /&gt;&lt;BR /&gt;---------&lt;BR /&gt;&lt;BR /&gt;The UP and RUNNING keywords refer to administrative and operational states, respectively. (In HP-UX, the "administrative state" and "operational state" are viewable with the "lanadmin -g mibstats &lt;PPA&gt;" command.)&lt;BR /&gt;&lt;BR /&gt;- if the interface has been commanded to activate, the interface will be UP; if not, it will be down (no keyword).&lt;BR /&gt;- if the interface is in working order (i.e. any required firmware files are loaded, the interface has been commanded to be UP and it has a valid physical link), the interface will be RUNNING.&lt;BR /&gt;&lt;BR /&gt;The implementation of the RUNNING state varies between different NIC drivers. In general, if a card is UP but not RUNNING, that indicates a problem: the card has been commanded to run, but is unable to do it at the moment.&lt;BR /&gt;&lt;BR /&gt;It is unusual to see an interface that is RUNNING but not UP: that might mean the command to shut down the interface has just been given, but the NIC hardware has not yet completed the shutdown.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/PPA&gt;&lt;/ETHX&gt;&lt;/ADDRESS&gt;&lt;/ETHX&gt;&lt;/ETHX&gt;</description>
    <pubDate>Wed, 01 Jun 2011 10:54:35 GMT</pubDate>
    <dc:creator>Matti_Kurkela</dc:creator>
    <dc:date>2011-06-01T10:54:35Z</dc:date>
    <item>
      <title>"ifconfig down" keeping the link state</title>
      <link>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793897#M81342</link>
      <description>Hi guys&lt;BR /&gt;&lt;BR /&gt;I have written down a bash script in RHEL to find out the switch name and port to which a ethernet interface is plugged. I'm interested even in the unconfigured interfaces, i.e., plugged with NO IP address assigned.&lt;BR /&gt;&lt;BR /&gt;The tcpdump tool is used BUT it does not work when the interface is DOWN ("ifconfig -a" shows it but "ifconfig" doesn't)&lt;BR /&gt;&lt;BR /&gt;The obviuos solution focuses on using the ifconfig command to set the interface UP and set back DOWN later.&lt;BR /&gt;&lt;BR /&gt;The command "ifconfig down" denies any *software* access to the interface (fine!) BUT shuts down the link, i.e., "ethtool" reports no link detected -- I do not want this, I wanto the set back to its previous state.&lt;BR /&gt;&lt;BR /&gt;Is there any way to set DOWN the interface without removing the physical link?&lt;BR /&gt;&lt;BR /&gt;I come from the HP-UX world, where the ifconfig actions "plumb" and "unplumb" would be required in this case... but Linux ifconfig does not offer those actions.&lt;BR /&gt;&lt;BR /&gt;Thanx in advance&lt;BR /&gt;&lt;BR /&gt;P.D: does anyone know the difference of the UP and RUNNING keywords in the ifconfig output?</description>
      <pubDate>Tue, 31 May 2011 16:53:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793897#M81342</guid>
      <dc:creator>Jdamian</dc:creator>
      <dc:date>2011-05-31T16:53:56Z</dc:date>
    </item>
    <item>
      <title>Re: "ifconfig down" keeping the link state</title>
      <link>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793898#M81343</link>
      <description>there should be startup/shutdown scripts called ifup and ifdown under /etc/sysconfig/network-scripts.&lt;BR /&gt;&lt;BR /&gt;to restart the interface of eth0, you could do&lt;BR /&gt;ifdown eth0 followed by ifup eth0&lt;BR /&gt;&lt;BR /&gt;or you can use the ip command, e.g.&lt;BR /&gt;ip link set eth0 down  &lt;BR /&gt;then&lt;BR /&gt;ip link set eth0 up</description>
      <pubDate>Tue, 31 May 2011 22:53:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793898#M81343</guid>
      <dc:creator>Wilfred Chau_1</dc:creator>
      <dc:date>2011-05-31T22:53:21Z</dc:date>
    </item>
    <item>
      <title>Re: "ifconfig down" keeping the link state</title>
      <link>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793899#M81344</link>
      <description>No, there is no script under /etc/sysconfig/network-scripts because that interface has no IP address assigned.&lt;BR /&gt;&lt;BR /&gt;The ip tool works as ifconfig:&lt;BR /&gt;&lt;BR /&gt;# ethtool eth4 | grep 'Link detected:'&lt;BR /&gt;        Link detected: yes&lt;BR /&gt;# ip link set eth4 up&lt;BR /&gt;# ip link set eth4 down&lt;BR /&gt;# ethtool eth4 | grep 'Link detected:'&lt;BR /&gt;        Link detected: no&lt;BR /&gt;</description>
      <pubDate>Wed, 01 Jun 2011 05:09:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793899#M81344</guid>
      <dc:creator>Jdamian</dc:creator>
      <dc:date>2011-06-01T05:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: "ifconfig down" keeping the link state</title>
      <link>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793900#M81345</link>
      <description>In Linux, you can configure a network interface UP without assigning an IP address to it. This stops the TCP/IP driver stack from using the interface, but the physical link will still be active and low-level access (e.g. tcpdump) is possible.&lt;BR /&gt;&lt;BR /&gt;If the interface is DOWN, you can switch it UP without assigning an IP address with a simple command:&lt;BR /&gt;&lt;BR /&gt;ifconfig &lt;ETHX&gt; up&lt;BR /&gt;&lt;BR /&gt;To remove an already-assigned IP address, you can either reset the IP of the interface to 0.0.0.0:&lt;BR /&gt;&lt;BR /&gt;ifconfig &lt;ETHX&gt; 0.0.0.0&lt;BR /&gt;&lt;BR /&gt;Or you can use "ip addr del &lt;ADDRESS&gt; dev &lt;ETHX&gt;".&lt;BR /&gt;&lt;BR /&gt;The state "UP without an IP address" would be the closest equivalent of HP-UX state "plumbed but not configured".&lt;BR /&gt;&lt;BR /&gt;---------&lt;BR /&gt;&lt;BR /&gt;The UP and RUNNING keywords refer to administrative and operational states, respectively. (In HP-UX, the "administrative state" and "operational state" are viewable with the "lanadmin -g mibstats &lt;PPA&gt;" command.)&lt;BR /&gt;&lt;BR /&gt;- if the interface has been commanded to activate, the interface will be UP; if not, it will be down (no keyword).&lt;BR /&gt;- if the interface is in working order (i.e. any required firmware files are loaded, the interface has been commanded to be UP and it has a valid physical link), the interface will be RUNNING.&lt;BR /&gt;&lt;BR /&gt;The implementation of the RUNNING state varies between different NIC drivers. In general, if a card is UP but not RUNNING, that indicates a problem: the card has been commanded to run, but is unable to do it at the moment.&lt;BR /&gt;&lt;BR /&gt;It is unusual to see an interface that is RUNNING but not UP: that might mean the command to shut down the interface has just been given, but the NIC hardware has not yet completed the shutdown.&lt;BR /&gt;&lt;BR /&gt;MK&lt;/PPA&gt;&lt;/ETHX&gt;&lt;/ADDRESS&gt;&lt;/ETHX&gt;&lt;/ETHX&gt;</description>
      <pubDate>Wed, 01 Jun 2011 10:54:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/quot-ifconfig-down-quot-keeping-the-link-state/m-p/4793900#M81345</guid>
      <dc:creator>Matti_Kurkela</dc:creator>
      <dc:date>2011-06-01T10:54:35Z</dc:date>
    </item>
  </channel>
</rss>

