ifconfig: difference between creating logical or alias network interface

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Assigning ipv6 to bonding interface - getting old as well as changed ipv6 in ifconfig output

Hi, I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your...

2. 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...

3. Homework & Coursework Questions

Creating a .profile, displaying system variables, and creating an alias

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Here is what I am supposed to do, word for word from my assignment page: 1. Create/modify and print a...

4. Solaris

No network cable But Network interface is UP and Running

I've one Netra 240 After changing main board and system configuration card reader, Network is not accessible any more, Network interfaces are always UP and Running even when there is no cable connected to Network interfaces. I tried to restart and plumb/unplumb with no luck. ifconfig -a...

5. UNIX and Linux Applications

Access to network interface (Mac-network)

Hi, I'm a italian student. For my thesis I develop a gateway with protocol 6lowpan. For that I must access to network interface to develope my personal stack based on standard 802.15.4. Can you help me? I need an explanation for that.

6. HP-UX

Creating a logical volume file

Hi to all, I am brand new to HP-UX but am quite familiar with Linux systems (Red Hat, Ubuntu etc..) I've just taken over a new HP-UX box and trying to work out how to create a logical volume. As well as creating the volume, which I am sure is very easy I need to create a special character...

7. Solaris

configure zones to have different network interface and network

i need to configure a zone to use different interface (bge2) than global and have connected to completely different network switch & to use its own defaultrouter and hosts file .. is it possible ..if so ..how ? Thanks

8. Solaris

Not showing n/w interface name in Solaris with ifconfig -a

hi frineds in sunfire 6800 server for one domain when ever i am giving ifconfig -a interface names like hme0,hme1.......are not showing.Actually in the server hme0,hme1,qfe are showing .when i was tried with the cat /etc/path_to_intstshowing tphysical interfcace names . after giving the...

9. UNIX for Dummies Questions & Answers

Error in creating logical partition

Dear Members, I am using SCO-Unix 5.0.5. I have created 2 logical drives but some of the blocks are overlapped and are now giving warning during startup. I have used fsck to settle the problems but to no avail. Kindly help me to sort out the problem. Thanks

10. IP Networking

OpenBSD + Network +ifconfig

This feels really silly, but i just dont get it.. I just installed openbsd on one of my machines, usually i dont have this problem, but now, when i try to use ifconfig to give myself an ipadress, i get this errormsg: OpenAMD# ifconfig ep0 192.168.51.16 ifconfig: SIOCGIFFLAGS: Device not...

LEARN ABOUT X11R4

vni

vni(7d)                                                               Devices                                                              vni(7d)

NAME

       vni - STREAMS virtual network interface driver

DESCRIPTION

       The  vni  pseudo  device  is  a  multi-threaded, loadable, clonable, STREAMS pseudo-device supporting the connectionless Data Link Provider
       Interface dlpi(7P) Style 2. Note that DLPI is intended to interact with IP, meaning that DLPI access to applications is not supported. (For
       example, snoop fails on the vni interface.)

       The  vni  device is a software-only interface and does not send or receive data. The device provides a DLPI upper interface that identifies
       itself to IP with a private media type. It can be configured via ifconfig(1M) and can have IP addresses assigned to it, making aliases pos-
       sible.

       The  vni  pseudo  device  is  particularly  useful in hosting an IP address when used in conjunction with the 'usesrc' ifconfig option (see
       ifconfig(1M) for examples).  The logical instances of the device can also be used to host addresses as an alternative to hosting them  over
       the loopback interface.

       Multicast  is not supported on this device. More specifically, the following options return an error when used with an address specified on
       vni: IP_MULTICAST_IF, IP_ADD_MEMBERSHIP, IP_DROP_MEMBERSHIP, IPV6_MULTICAST_IF, IPV6_JOIN_GROUP, IPV6_LEAVE_GROUP. In  addition,  broadcast
       is not supported.

       Because  there  is no physical hardware configured below it, no traffic can be received through nor transmitted on a virtual interface. All
       packet transmission and reception is accomplished with existing physical interfaces and tunnels. Because applications that deal with packet
       transmission  and  reception  (such  as packet filters) cannot filter traffic on virtual interfaces, you cannot set up a packet filter on a
       virtual interface. Instead, you should configure the policy rules to apply to the physical interfaces and tunnels, and  if  necessary,  use
       the virtual IP addresses themselves as part of the rule configuration. Also, note that the virtual interface cannot be part of an IP multi-
       pathing (IPMP) group.

FILES

       /dev/vni

           64-bit ELF kernel driver

SEE ALSO

       ifconfig(1M), in.mpathd(1M), ip(7P), ip6(7P)

SunOS 5.10                                                         18 July 2004                                                            vni(7d)

IP Networking