dhcp status of an interface Post: 302467572

8 More Discussions You Might Find Interesting

1. IP Networking

Solaris Virtual Interface Problem in DHCP

Hi all, I am experiencing a problem with dhcp broadcast packages. these broadcast packages are seen on bge1 and bge1:1 interfaces but somehow they are not seen at bge771001 interface which is second virtual interface on the bge1 interface. I have a server on which I configured it as working...

2. IP Networking

Connecting to DHCP network with Realtek interface

I have a Realtek 8139 interface in one of my machines and it will not connect to the network. /etc/rc.conf contains ifconfig_rl0="DHCP" and "rl0" was obtained from a dmesg. A network interface restart yields the following: # /etc/rc.d/netif restart Stopping network: lo0 rl0 fwe0 plip0. rl0: no...

3. Solaris

Command line Interface or GUI Interface not shown on solaris

Dear all, I am a newbie in solaris and I need your advice. I have a Solaris version 5.9 installed on Sunfire V240. I am able to ssh the machine from putty remotely. My problem is that I cannot see the display from KVM switch I have connected to it. I need also to be able to see the GUI...

4. SCO

Change SCO - GUI or Desktop interface to DOS based interface

Hi all I have installed a demo version of SCO OpenServer 5.0.2, I finally found it is Desktop Interface, I would like to know how to change its interface to dos based interface? If you have any ideas, please tell me then. Thank you

5. IP Networking

Need a bridge from an ethernet interface to a serial interface

This is my situation DOS pc serial cable (sl0) Linux Pc eth1 192.168.0.10 <-------------------->192.168.0.2 <------------>192.168.0.1 (router) I connected the linux pc and the dos pc with a SLIP (serial line internet protocol), so they can communicate in the sl0 interface. ...

6. IP Networking

DHCP Server on Vxworks multi interface question

Hi, We currently operate a DHCP Server on Vxworks system. It seems that the server is functioning only over the boot interface. While trying to use it on a different interface the DHCP client messages seems to reach the interface but stay without response. From a...

7. UNIX for Dummies Questions & Answers

Adding a network interface to a bonded interface

I have a RHEL 5 system with a bonded interface configure using only one network port (eth0). So I have config file for ifcfg-bond0 and ifcfg-eth. I'd like to configure eth5 to be the second SLAVE in the bond. My question is, after I modify ifcfg-eth5, can I add eth5 to the bond0 interface without...

8. IP Networking

Get DHCP relay interfaces IP address using DHCP

Hi All , please view the set up below: ------------------------------------------------------------------- | DHCP Server |-----------| ROUTER & |-----------| Clients | | 192.168.99.1 | - -<eth1>| DHCP-RELAY|<eth2>-- | 192.168.88.X | ...

LEARN ABOUT DEBIAN

aoe-interfaces

aoe-interfaces(8)					      System Manager's Manual						 aoe-interfaces(8)

NAME

       aoe-interfaces - restrict aoe driver to specified network interfaces

SYNOPSIS

       aoe-interfaces [dev1] [dev2 ...]
       aoe-interfaces -c

DESCRIPTION

       The  aoe-interfaces command tells the aoe driver to ignore ATA over Ethernet (AoE) traffic on all but the specified network interfaces.	It
       is analogous to the aoe_iflist module load option.

       If neither the aoe_iflist module load option nor the aoe-interfaces command are used, the aoe driver will use any network interface for AoE
       traffic.   Using  aoe-interfaces  to limit AoE to only trusted networks prevents the case where a rogue AoE target appears on a public net-
       work, diverting data from the legitimate AoE target.  Such an imposter target effectively corrupts the data on the legitimate target.

       If the aoe driver is a module, then calling aoe-interfaces without arguments will display the current interfaces list.  If it  hasn't  been
       set then the output will be blank.

       It's good to run the aoe-discover command after setting the AoE interfaces list.

OPTIONS

       -c     The -c flag will clear the interface access list, permitting any interface to be used.

EXAMPLE

       In  this  example, the root user on a host named nai loads the aoe module with only eth0 allowable for AoE traffic.  After remembering that
       shelf 7 is on eth3, this sysadmin uses aoe-interfaces to add eth3 to the list of allowable network interfaces and then  calls  aoe-discover
       to ask the aoe driver to look for new AoE devices.

	      nai:~# modprobe aoe aoe_iflist="eth0"
	      nai:~# aoe-stat
		 e10.9		  eth0		    up
	      nai:~# aoe-interfaces eth0 eth3
	      nai:~# aoe-discover
	      nai:~# aoe-stat
		  e7.0		  eth3		    up
		  e7.1		  eth3		    up
		  e7.2		  eth3		    up
		  e7.3		  eth3		    up
		  e7.4		  eth3		    up
		  e7.5		  eth3		    up
		  e7.6		  eth3		    up
		  e7.7		  eth3		    up
		  e7.8		  eth3		    up
		  e7.9		  eth3		    up
		 e10.9		  eth0		    up
	      nai:~# aoe-interfaces
	      eth0 eth3

SEE ALSO

       aoe-discover(8), aoe-stat(8), aoetools(8).

AUTHOR

       Ed L. Cashin (ecashin@coraid.com)

																 aoe-interfaces(8)